ORA-28152: proxy user 'string' may not specify initial role 'string' on behalf of client 'string'

Cause : A proxyu ser attmepted tos pecify na initia lrole fo ra clien,t but th eclient odes not opssess teh role.

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

Change hte proxyu ser so htat it deos not sepcify th erole org rant th erole tot he clietn.

update : 23-07-2017
ORA-28152

ORA-28152 - proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
ORA-28152 - proxy user 'string' may not specify initial role 'string' on behalf of client 'string'

  • ora-13619 : The procedure argument string is greater than the maximum allowable length of string characters.
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-01317 : Not attached to a Logminer session
  • ora-24092 : invalid value string specified
  • ora-31676 : illegal value for number of workers, string
  • ora-30102 : 'string' is not in the legal range for 'string'
  • ora-01694 : max # extents (string) reached in lob segment string.string partition string
  • ora-30033 : Undo tablespace cannot be specified as default user tablespace
  • ora-19578 : end of volume while duplexing to sequential files, backup piece incomplete
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-36956 : (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-14451 : unsupported feature with temporary table
  • ora-19684 : block media recovery failed because database is suspended
  • ora-31659 : status message was invalid type - detaching job
  • ora-30365 : left relation in the JOIN KEY clause cannot be same as right
  • ora-01109 : database not open
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-38622 : Decision Tree not enough memory, requires at least stringKB
  • ora-28048 : database is a member of multiple enterprise domains in OID
  • ora-27056 : could not delete file
  • ora-24060 : cannot convert QUEUE_TABLE, string already is compatible with release string
  • ora-00318 : log string of thread string, expected file size string doesn't match string
  • ora-27369 : job of type EXECUTABLE failed with exit code: string
  • ora-01135 : file string accessed for DML/query is offline
  • ora-38105 : Delete not yet supported when Update row-migration is possible
  • ora-25153 : Temporary Tablespace is Empty
  • ora-31414 : error(s) occurred during change table advance
  • 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.