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 : 27-04-2017

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-00405 : compatibility type "string"
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-28179 : client user name not provided by proxy
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-16151 : Managed Standby Recovery not available
  • ora-24155 : rule string.string not in rule set string.string
  • ora-25157 : Specified block size string is not valid
  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-13128 : current tiling level exceeds user specified tiling level
  • ora-00379 : no free buffers available in buffer pool string for block size stringK
  • ora-31653 : unable to determine job operation for privilege check
  • ora-13785 : missing target object for tuning task "string"
  • ora-25203 : invalid value string, DELAY should be non-negative
  • ora-01601 : illegal bucket size in clause "string" of string
  • ora-26521 : rpc initialization error
  • ora-19236 : XQ0016 - module declaration or import not supported
  • ora-02202 : no more tables permitted in this cluster
  • ora-26687 : no instantiation SCN provided for "string"."string" in source database "string"
  • ora-25247 : %s is not a recipient of specified message
  • ora-15121 : ASM file name 'string' contains an invalid diskgroup name
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-16660 : FSFO operation attempted in absence of a broker configuration
  • ora-26699 : STREAMS message consumer string already exists
  • ora-07200 : slsid: oracle_sid not set.
  • ora-00335 : online log string: No log with this number, log does not exist
  • ora-13527 : invalid baseline name
  • ora-39172 : Cannot remap transportable tablespace names with compatibility of string.
  • ora-26571 : %s.string.string: number of arguments (string) does not match replication catalog
  • ora-25105 : RECOVERABLE option can only be used with ALTER INDEX REBUILD
  • ora-03128 : connection is in blocking mode
  • 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.