ORA-28172: distinguished name not provided by proxy

Cause : A client user is to be identified using a distinguished name, but none was provided by the proxy user.

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

Provide a distinguished name.

update : 28-05-2017
ORA-28172

ORA-28172 - distinguished name not provided by proxy
ORA-28172 - distinguished name not provided by proxy

  • ora-28043 : invalid bind credentials for DB-OID connection
  • ora-01493 : invalid SAMPLE size specified
  • ora-36267 : (XSCGMDLAGG09) workspace object has no dimensions, so it cannot have a qualified data reference.
  • ora-23395 : object "string"."string" of type "string" does not exist or is invalid
  • ora-32502 : Cannot execute command. Flash Freeze is not in effect
  • ora-06712 : TLI Driver: error on accept
  • ora-01019 : unable to allocate memory in the user side
  • ora-27454 : argument name and position cannot be NULL
  • ora-29894 : base or varray datatype does not exist
  • ora-09910 : Unable to find ORACLE password file entry for user.
  • ora-15114 : missing or invalid ASM file name
  • ora-26051 : internal error parsing packed decimal format string
  • ora-01217 : logfile member belongs to a different logfile group
  • ora-37002 : Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.
  • ora-13372 : failure in modifying metadata for a table with spatial index
  • ora-09800 : Process sensitivity label retrieval failed.
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-07626 : smsget: sga already mapped
  • ora-14018 : partition bound list contains too few elements
  • ora-38782 : cannot flashback database to non-guaranteed restore point 'string'
  • ora-32627 : illegal pattern in MODEL FOR LIKE loop
  • ora-14299 : total number of partitions/subpartitions exceeds the maximum limit
  • ora-31206 : DBMS_LDAP: PL/SQL - Invalid LDAP search scope.
  • ora-07219 : slspool: unable to allocate spooler argument buffer.
  • ora-09290 : sksaalo: error allocating memory for archival
  • ora-06922 : CMX: bad write length
  • ora-38792 : encountered unknown flashback record from release string
  • ora-33092 : (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace.
  • ora-16525 : the Data Guard broker is not yet available
  • ora-09344 : spsig: error signalling thread
  • 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.