ORA-28154: Proxy user may not act as client 'string'

Cause : A proxy user may not assume the identity of a privileged user in order to limit the privileges that a proxy may possess.

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

Execute the statement again specify a client other than a privileged user.

update : 26-04-2017

ORA-28154 - Proxy user may not act as client 'string'
ORA-28154 - Proxy user may not act as client 'string'

  • ora-00346 : log member marked as STALE
  • ora-32626 : illegal bounds or increment in MODEL FOR loop
  • ora-30027 : Undo quota violation - failed to get string (bytes)
  • ora-12014 : table 'string' does not contain a primary key constraint
  • ora-13388 : invalid value for dst_spec parameter
  • ora-02205 : only SELECT and ALTER privileges are valid for sequences
  • ora-13830 : SQL profile with category string already exists for this SQL statement
  • ora-30510 : system triggers cannot be defined on the schema of SYS user
  • ora-25138 : %s initialization parameter has been made obsolete
  • ora-16130 : supplemental log information is missing from log stream
  • ora-31075 : invalid string declaration in XML Schema
  • ora-22902 : CURSOR expression not allowed
  • ora-08316 : sllfsk: Error seeking in file.
  • ora-14409 : inserted partition key is outside specified subpartition
  • ora-00166 : remote/local nesting level is too deep
  • ora-30740 : cannot grant UNDER privilege on this object
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-12041 : cannot record ROWIDs for index-organized table "string"."string"
  • ora-36220 : (XSLPDSC01) All dimensions in LIST number are also in the IGNORE clause.
  • ora-16506 : out of memory
  • ora-01374 : _log_parallelism_max greater than 1 not supported in this release
  • ora-01917 : user or role 'string' does not exist
  • ora-01097 : cannot shutdown while in a transaction - commit or rollback first
  • ora-19635 : input and output filenames are identical: string
  • ora-09808 : Could not obtain user clearance.
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-02060 : select for update specified a join of distributed tables
  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-08340 : This command not allowed on nCUBE, only one thread is ever used.
  • ora-01090 : shutdown in progress - connection is not permitted
  • 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.