TNS-12599: TNS:cryptographic checksum mismatch

Have your alert logs been littered with TNS-12599 errors, after upgrading to OEM 11g? These errors started appearing in the alert logs on OEM repository database, and the monitored databases.


***********************************************************************

NI cryptographic checksum mismatch error: 12599.

VERSION INFORMATION:

TNS for Solaris: Version 11.2.0.1.0 – Production

Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.1.0 – Production

TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.1.0 – Production

Time: 24-MAR-2011 17:34:35

Tracing not turned on.

Tns error struct:

ns main err code: 12599

TNS-12599: TNS:cryptographic checksum mismatch

ns secondary err code: 2526

nt main err code: 0

nt secondary err code: 0

nt OS err code: 0

Thu Mar 24 18:24:51 2011

***********************************************************************

 

This is due to bug 9844654.  There is an easy workaround.  Modify the $ORACLE_HOME/network/admin/sqlnet.ora of each server involved, and add the following line:

SQLNET.ENCRYPTION_TYPES_SERVER= (3DES168)

 

Then restart the listeners involved.

This entry was posted in 11.2.0.2, Agent, OEM, Oracle and tagged , , , . Bookmark the permalink.

3 Responses to TNS-12599: TNS:cryptographic checksum mismatch

  1. Hector Sanchez says:

    Good tip… thank you!

  2. all three says:

    Excellent weblog!

  3. It’s really a nice and useful piece of info. I’m glad that you shared this helpful information with us. Please stay us up to date like this. Thank you for sharing.