ORA-28179: client user name not provided by proxy

Cause : No user name was provided by the proxy user for the client user.

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

Either specify a client database user name, a distinguished name or an X.509 certificate.

update : 29-06-2017

ORA-28179 - client user name not provided by proxy
ORA-28179 - client user name not provided by proxy

  • ora-02439 : Unique index on a deferrable constraint is not allowed
  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-06559 : wrong datatype requested, string, actual datatype is string
  • ora-13466 : format not appropriate for specified compression method
  • ora-01051 : deferred rpc buffer format invalid
  • ora-22314 : method information mismatch in ALTER TYPE
  • ora-22341 : cannot assign supertype instance to subtype
  • ora-23302 : application raised communication failure during deferred RPC
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-30152 : File does not exist
  • ora-27045 : unable to close the file
  • ora-16230 : committing transaction string string string
  • ora-39031 : invalid filter name string
  • ora-04064 : not executed, invalidated string
  • ora-19254 : XQ0034 - too many declarations for function string
  • ora-13827 : null or zero length attribute specified in SQL profile collection
  • ora-14622 : Value string already exists in subpartition string
  • ora-24323 : value not allowed
  • ora-16752 : resource guard could not mount standby database
  • ora-31466 : no publications found
  • ora-01525 : error in renaming data files
  • ora-32167 : No payload set on the Message
  • ora-01080 : error in shutting down ORACLE
  • ora-14451 : unsupported feature with temporary table
  • ora-13198 : Spatial error: string
  • ora-27058 : file I/O question parameter is invalid
  • ora-29549 : class string.string has changed, Java session state cleared
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-31107 : Action failed as resource "string" is locked by name lock
  • ora-02091 : transaction rolled back
  • 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.