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-05-2017

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-14324 : values being added already exist in DEFAULT partition
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-09700 : sclin: maximum number of latches exceeded
  • ora-28169 : unsupported certificate type
  • ora-12991 : column is referenced in a multi-column constraint
  • ora-01925 : maximum of string enabled roles exceeded
  • ora-16559 : out of memory at string
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-32411 : materialized view definition query exceeds the maximum length
  • ora-09874 : TASDEF_READ: read error, unable to read tasdef@.dbf file.
  • ora-06253 : NETNTT: cannot read arguments from address file
  • ora-24141 : rule set string.string does not exist
  • ora-01804 : failure to initialize timezone information
  • ora-30358 : summary and materialized view are not in same schema
  • ora-16527 : unable to allocate SGA heap
  • ora-13777 : invalid list of attribute names
  • ora-06816 : TLI Driver: could not set the SPX SAP address
  • ora-01325 : archive log mode must be enabled to build into the logstream
  • ora-29346 : invalid tablespace list
  • ora-35076 : (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.
  • ora-13378 : invalid index for element to be extracted
  • ora-29881 : failed to validate indextype
  • ora-28518 : data dictionary translation has illegal translation type
  • ora-15026 : disk 'string' is not an ASM disk
  • ora-10927 : trace name context forever
  • ora-06708 : TLI Driver: message receive failure
  • ora-06917 : CMX: error in data read (too many bytes read)
  • ora-32742 : Hang analysis initialize failed
  • ora-13426 : invalid window parameter for subset operation
  • 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.