ORA-28045: SSL authentication between database and OID failed

Cause : Server failed to authenticate itself to the Directory.

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

Make sure the sqlnet.ora used is pointing to the wallet with the right certificate.

update : 21-08-2017

ORA-28045 - SSL authentication between database and OID failed
ORA-28045 - SSL authentication between database and OID failed

  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-19258 : XQ0038 - unsupported or duplicate default collation specified
  • ora-29368 : consumer group string does not exist
  • ora-01563 : rollback segment is PUBLIC, need to use the keyword PUBLIC
  • ora-22999 : CLOB or NCLOB data may have been corrupted
  • ora-12329 : database string is closed; no operations are permitted
  • ora-02270 : no matching unique or primary key for this column-list
  • ora-31686 : error creating worker processes
  • ora-16046 : Archive log destination failed due to failed dependent destination
  • ora-19283 : XQ0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.
  • ora-01283 : Options specified is invalid
  • ora-13454 : GeoRaster metadata is invalid
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-10574 : Test recovery did not corrupt any data block
  • ora-19237 : XP0017 - unable to resolve call to function - string:string
  • ora-28154 : Proxy user may not act as client 'string'
  • ora-32400 : cannot use object id columns from materialized view log on "string"."string"
  • ora-02161 : invalid value for MAXLOGFILES
  • ora-07276 : no dba group in /etc/group.
  • ora-10642 : Found rollback segments in dictionary managed tablespaces
  • ora-39305 : schema "string" does not exist
  • ora-12531 : TNS:cannot allocate memory
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-13791 : cannot resume a tuning task created to tune a single statement
  • ora-23346 : primary key or object ID is undefined for table or materialized view string
  • ora-32515 : cannot issue ORADEBUG command; waited number ms for process string
  • ora-13915 : Critical byte based free space threshold value is greater than warning threshold value.
  • ora-38401 : synonym string not allowed
  • ora-02314 : illegal use of type constructor
  • ora-01555 : snapshot too old: rollback segment number string with name "string" too small
  • 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.