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 : 23-04-2017
ORA-28172

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

  • ora-13840 : Concurrent DDL Error in create SQL profile operation.
  • ora-39500 : failed to notify CRS of a Startup/Shutdown event for database "string", instance "string" (ignored)
  • ora-27463 : invalid program type string
  • ora-36405 : (XSSPROP05) Property ignored for object workspace object:
  • ora-07209 : sfofi: file size limit was exceeded.
  • ora-12452 : label tag string already exists
  • ora-13334 : LRS segments not connected
  • ora-08117 : Index Organized Table operation released its block pin
  • ora-02709 : osnpop: pipe creation failed
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • ora-13408 : invalid blockSize storage parameter
  • ora-27002 : function called with invalid device structure
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-01353 : existing Logminer session
  • ora-30554 : function-based index string.string is disabled
  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-38900 : missing mandatory column "string" of error log table "string"
  • ora-25294 : Cannot propagate user buffered messages to a database with version lower than 10.2
  • ora-39078 : unable to dequeue message for agent string from queue "string"
  • ora-19556 : required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-07804 : slpdtb: number too large for supplied buffer
  • ora-01689 : syntax error in clause "string" of string
  • ora-40001 : value for string must be greater than zero
  • ora-01613 : instance string (thread string) only has string logs - at least 2 logs required to enable.
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-16188 : LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
  • ora-07246 : sfofi: open error, unable to open database file.
  • ora-07638 : smsget: SGA pad area not large enough for created SGA
  • 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.