ORA-28150: proxy not authorized to connect as client

Cause : A proxy user attempted to connect as a client, but the proxy was not authorized to act on behalf of the client.

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

Grant the proxy user permission to perform actions on behalf of the client by using the ALTER USER ... GRANT CONNECT command.

update : 17-08-2017

ORA-28150 - proxy not authorized to connect as client
ORA-28150 - proxy not authorized to connect as client

  • ora-12640 : Authentication adapter initialization failed
  • ora-31000 : Resource 'string' is not an XDB schema document
  • ora-06917 : CMX: error in data read (too many bytes read)
  • ora-02801 : Operations timed out
  • ora-22809 : nonexistent attribute
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-26762 : Cannot autogenerate name for parameter string because of the following reason: string
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-39177 : invalid compression value string
  • ora-29966 : The only binding of an operator cannot be dropped
  • ora-22283 : filename contains characters that refer to parent directory
  • ora-14114 : partitioned table cannot have column with object, REF, nested table, array datatype
  • ora-30150 : Invalid argument passed to OCIFile function
  • ora-16066 : remote archival disabled
  • ora-13119 : invalid edge_id [string]
  • ora-19044 : character length specified for XMLSerialize is too small.
  • ora-12077 : temporary updatable materialized view log does not exist
  • ora-00350 : log string of instance string (thread string) needs to be archived
  • ora-07394 : unable to append string to text file
  • ora-19811 : cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
  • ora-19266 : XQ0046 - invalid URI
  • ora-25190 : an index-organized table maintenance operation may not be combined with other operations
  • ora-31478 : could not detach LogMiner session after change set advance
  • ora-22132 : hexadecimal string does not correspond to a valid REF
  • ora-16193 : Primary and standby network encryption mismatch
  • ora-01859 : a non-alphabetic character was found where an alphabetic was expected
  • ora-24809 : amount specified will not fit in the lob buffers
  • ora-09292 : sksabln: unable to build archive file name
  • ora-40101 : Data Mining System Error string-string-string
  • ora-00042 : Unknown Service name string
  • 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.