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 : 21-08-2017

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

  • ora-22908 : reference to NULL table value
  • ora-19956 : database should have no offline immediate datafiles
  • ora-12451 : label not designated as USER or DATA
  • ora-22295 : cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
  • ora-29818 : column name not properly specified
  • ora-08005 : specified row does not exist
  • ora-33280 : (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.
  • ora-12431 : invalid audit action
  • ora-07510 : scgbrm: $getlki unexpected return on lockid string
  • ora-24391 : invalid fetch operation
  • ora-01353 : existing Logminer session
  • ora-01175 : data dictionary has more than the string files allowed by the instance
  • ora-14297 : Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-30357 : this PL/SQL function cannot be supported for query rewrite
  • ora-30121 : 'string' is not an allowable value for 'string'
  • ora-12514 : TNS:listener does not currently know of service requested in connect descriptor
  • ora-10932 : trace name context forever
  • ora-16660 : FSFO operation attempted in absence of a broker configuration
  • ora-01257 : cannot reuse database file string, unknown file size
  • ora-28108 : circular security policies detected
  • ora-27473 : argument string does not exist
  • ora-07757 : slemcc: invalid handle
  • ora-36316 : (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another.
  • ora-12073 : request cannot be processed
  • ora-19759 : block change tracking is not enabled
  • ora-04077 : WHEN clause cannot be used with table level triggers
  • ora-14104 : RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-15204 : database version string is incompatible with diskgroup string
  • ora-02297 : cannot disable constraint (string.string) - dependencies exist
  • 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.