ORA-28157: Proxy user 'string' forbidden to set role 'string' for client 'string'

Cause : A proxyu ser wasf orbidde nto use arole onb ehalf o fa clien tthrought he commnad ALTERU SER GRATN CONNEC TTHROUGH< proxy> IWTH ALL ORLES EXCPET

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

Executet he commnad ALTERU SER GRATN CONNEC TTHROUGHP ROXY to rgant then eeded rloe.

update : 29-04-2017

ORA-28157 - Proxy user 'string' forbidden to set role 'string' for client 'string'
ORA-28157 - Proxy user 'string' forbidden to set role 'string' for client 'string'

  • ora-39212 : installation error: XSL stylesheets not loaded correctly
  • ora-03002 : operator not implemented
  • ora-04027 : self-deadlock during automatic validation for object string.string
  • ora-04078 : OLD and NEW values cannot be identical
  • ora-38495 : data type for the stored attribute string is inconsistent.
  • ora-02230 : invalid ALTER CLUSTER option
  • ora-31500 : change source string is not a ManualLog change source
  • ora-29705 : ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances
  • ora-02780 : Name given for the core dump directory is invalid
  • ora-16210 : Logical standby coordinator process terminated with error
  • ora-01093 : ALTER DATABASE CLOSE only permitted with no sessions connected
  • ora-12910 : cannot specify temporary tablespace as default tablespace
  • ora-06772 : TLI Driver: error sending command
  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • ora-09208 : sftcls: error closing file
  • ora-23325 : parameter type is not string
  • ora-39124 : dump file name "string" contains an invalid substitution variable
  • ora-27153 : wait operation failed
  • ora-23422 : Oracle Server could not generate an unused job number
  • ora-14021 : MAXVALUE must be specified for all columns
  • ora-28291 : No Kerberos Principal Value found.
  • ora-30037 : Cannot perform parallel DML after a prior DML on the object
  • ora-15079 : ASM file is closed
  • ora-39311 : call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal
  • ora-23394 : duplicate propagator
  • ora-24043 : destination string uses a reserved name, names with AQ$_ prefix are not valid
  • ora-30002 : SYS_CONNECT_BY_PATH function is not allowed here
  • ora-01042 : detaching a session with open cursors not allowed
  • ora-01919 : role 'string' does not exist
  • ora-00370 : potential deadlock during kcbchange 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.