ORA-28156: Proxy user 'string' not authorized to set role 'string' for client 'string'

Cause : A proxy user has not been granted the right to use a role on behalf of a client.

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

Execute the command ALTER USER GRANT CONNECT THROUGH PROXY to grant the needed role.

update : 24-05-2017

ORA-28156 - Proxy user 'string' not authorized to set role 'string' for client 'string'
ORA-28156 - Proxy user 'string' not authorized to set role 'string' for client 'string'

  • ora-13525 : error with computing space usage for sysaux occupant
  • ora-19201 : Datatype not supported
  • ora-19288 : XP0017 - invalid number of arguments to function - string
  • ora-38955 : Source platform string not cross platform compliant
  • ora-14173 : illegal subpartition-extended table name syntax
  • ora-01293 : mounted database required for specified LogMiner options
  • ora-00268 : specified log file does not exist 'string'
  • ora-02320 : failure in creating storage table for nested table column string
  • ora-13860 : Invalid service name
  • ora-19504 : failed to create file "string"
  • ora-12687 : Credentials expired.
  • ora-36840 : (XSLMGEN10) Cube string.string!string has no measures
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-16007 : invalid backup control file checkpoint
  • ora-27144 : attempt to kill process failed
  • ora-30201 : Unable to load NLS data object
  • ora-12228 : TNS:protocol adapter not loadable
  • ora-16657 : reinstatement of database in progress
  • ora-36768 : (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions.
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-27007 : failed to open file
  • ora-15070 : maximum number of files string exceeded in diskgroup "string"
  • ora-15002 : parameter LOCK_NAME_SPACE exceeds limit of string characters
  • ora-36610 : (XSLMS00) Unable to locate a message file for OLAP message: value
  • ora-31404 : all input parameters are null
  • ora-13066 : wrong feature geometry or element type
  • ora-39030 : invalid file type string
  • ora-19040 : Element string does not match expected string.
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-04099 : trigger 'string' is valid but not stored in compiled form
  • 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.