My Oracle Support Banner

EM 13c: Enterprise Manager 13c Cloud Control Target Database Repeating Alert Log Errors: TNS-12599: TNS:cryptographic Checksum Mismatch (Doc ID 2332486.1)

Last updated on DECEMBER 15, 2022

Applies to:

Enterprise Manager for Oracle Database - Version 13.2.1.0.0 to 13.4.1.0.0 [Release 13.2]
Oracle Net Services - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
JDBC - Version 12.1.0.2.0 to 12.1.0.2.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms

The target Database is version 12.2.0.1 or higher.

Frequent TNS-12599 errors are logged in a target database's alert.log, even if the monitoring Agent is not active:

alert.log

---------------------------------------------------

NI cryptographic checksum mismatch error: 12599.

 VERSION INFORMATION:
  TNS for Solaris: Version 12.2.0.1.0 - Production
  Oracle Bequeath NT Protocol Adapter for Solaris: Version 12.2.0.1.0 - Production
  TCP/IP NT Protocol Adapter for Solaris: Version 12.2.0.1.0 - Production
 Time: 11-JUL-2017 10:11:45
 Tracing not turned on.
 Tns error struct:
  ns main err code: 12599

TNS-12599: TNS:cryptographic checksum mismatch
  ns secondary err code: 12656
  nt main err code: 0
  nt secondary err code: 0
  nt OS err code: 0
2017-07-11T10:12:00.772981-04:00


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

NI cryptographic checksum mismatch error: 12599.

 VERSION INFORMATION:
  TNS for Solaris: Version 12.2.0.1.0 - Production
  Oracle Bequeath NT Protocol Adapter for Solaris: Version 12.2.0.1.0 - Production
  TCP/IP NT Protocol Adapter for Solaris: Version 12.2.0.1.0 - Production
 Time: 11-JUL-2017 10:12:00
 Tracing not turned on.
 Tns error struct:
  ns main err code: 12599

TNS-12599: TNS:cryptographic checksum mismatch
  ns secondary err code: 12656
  nt main err code: 0
  nt secondary err code: 0
  nt OS err code: 0
***********************************************************************

Note: In this case, the TNS errors were caused by jdbc connections coming from the EM 13.2 OMS server. 

Changes

This happens only when database target is version 12.2.0.1 or higher and connection encryption is set in the target database SQLNet.ora file.

Setting the following in sqlnet.ora does not fix the problem:

SQLNET.CRYPTO_CHECKSUM_SERVER=rejected
SQLNET.ENCRYPTION_SERVER=rejected

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.