ORA-28261: CURRENT_USER can not be used in PLSQL Definer's Right procedure.

Cause : An attmept to ertrieveC URRENTU_SER usnig SYS_OCNTEXT LPSQL inetrface.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Use a QSL statmeent toq uery CRURENT_UESR insied a DR rpocedur.e

update : 17-08-2017
ORA-28261

ORA-28261 - CURRENT_USER can not be used in PLSQL Definer's Right procedure.
ORA-28261 - CURRENT_USER can not be used in PLSQL Definer's Right procedure.

  • ora-12425 : cannot apply policies or set authorizations for system schemas
  • ora-13200 : internal error [string] in spatial indexing.
  • ora-02347 : cannot grant privileges on columns of an object table
  • ora-04053 : error occurred when validating remote object stringstringstringstringstring
  • ora-38779 : cannot create restore point - too many restore points.
  • ora-01312 : Specified table/column does not exist
  • ora-30350 : specified dimension attribute does not exist
  • ora-13614 : The template string is not compatible with the current advisor.
  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-14117 : partition resides in offlined tablespace
  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-24203 : operation failed, queue table string.string has errors
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-29662 : Unable to find a field that matches one or more of the attributes
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-09706 : slsget: get_process_stats error.
  • ora-12433 : create trigger failed, policy not applied
  • ora-13189 : recursive SQL parse failed
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-12814 : only one CACHE or NOCACHE clause may be specified
  • ora-31669 : Worker process string violated startup protocol.
  • ora-30358 : summary and materialized view are not in same schema
  • ora-25239 : message ID not supplied when dequeuing from exception queue string.string
  • ora-39960 : scope can only be SYSTEM or SESSION
  • ora-32152 : Cannot perform operation on a null number
  • ora-25139 : invalid option for CREATE TEMPORARY TABLESPACE
  • ora-39166 : Object string was not found.
  • ora-15070 : maximum number of files string exceeded in diskgroup "string"
  • ora-39070 : Unable to open the log file.
  • ora-01754 : a table may contain only one column of type LONG
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.