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 : 26-09-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-31657 : data filter name can not be defaulted
  • ora-29268 : HTTP client error string
  • ora-29828 : invalid name for implementation type
  • ora-28500 : connection from ORACLE to a non-Oracle system returned this message:
  • ora-12081 : update operation not allowed on table "string"."string"
  • ora-12341 : maximum number of open mounts exceeded
  • ora-29517 : recursive resolution failed for a referenced class
  • ora-01496 : specified chain row table form incorrect
  • ora-12826 : hung parallel query server was killed
  • ora-30937 : No schema definition for 'string' (namespace 'string') in parent 'string'
  • ora-38708 : not enough space for first flashback database log file
  • ora-36735 : A value exceeded the MAX specification
  • ora-02457 : The HASH IS option must specify a valid column
  • ora-27121 : unable to determine size of shared memory segment
  • ora-39120 : Table string can't be truncated, data will be skipped. Failing error is: string
  • ora-02374 : conversion error loading table string.string
  • ora-13260 : layer table string does not exist
  • ora-32018 : parameter cannot be modified in memory on another instance
  • ora-19663 : cannot apply current offline range to datafile string
  • ora-38736 : Wrong thread number string in flashback log file header.
  • ora-19649 : offline-range record recid string stamp string not found in file string
  • ora-06732 : TLI Driver: cannot alloc t_discon
  • ora-26054 : Direct Path Context prepared for a different mode than operation requested.
  • ora-01038 : cannot write database file version string with ORACLE version string
  • ora-22620 : buffer size too small to hold the value
  • ora-33030 : (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
  • ora-32810 : foreign queue string is not registered
  • ora-30680 : debugger connection handshake failed
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-31155 : attribute string not in XDB namespace
  • 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.