TNS-12599: TNS:cryptographic checksum mismatch

11gR1 and 11gR2 Target Database or Repository Producing Several TNS-12599 Errors in Alert.log File (Doc ID 1150874.1)

Symptoms

When Enterprise Manager logs in or out from a 11.1 (11gR1) or 11.2 (11gR2) target database or as the OMS database repository, it causes several TNS-12599 errors in the alert.log of the respective database.


11gR2:

***********************************************************************
NI cryptographic checksum mismatch error: 12599.

VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 14-JUL-2010 11:39:22
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
Wed Jul 14 11:48:14 2010
***********************************************************************

11gR1:

***********************************************************************
NI cryptographic checksum mismatch error: 12599.

VERSION INFORMATION:
TNS for Linux: Version 11.1.0.7.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.1.0.7.0 - Production
Time: 10-AUG-2011 16:18:44
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
Wed Aug 10 16:18:44 2011
***********************************************************************

Changes

11gR1 or 11gR2 target database or as the OMS database repository.

Cause

The Enterprise Manager OMS connects to the 11gR1 and 11gR2 target database using 10.2 JDBC Thin connection and AES256 encryption algorithm.

The 11gR1 and 11gR2 database does not support client JDBC connections using AES encryption, hence the TNS-12599: TNS:cryptographic checksum mismatch

Solution

Workaround:

on the target database side, set SQLNET.ENCRYPTION_TYPES_SERVER= (3DES168)  in sqlnet.ora

Patches for bug 9953045 and  bug 12360281 fix this problem.

- bug 9953045   is to fix the issue for repository connection made from OMS
- bug 12360281 is to fix target database connections made from OMS