TNS-12599: TNS:cryptographic Checksum Mismatch in alert.log after enabling of encryption on the server side

(Doc ID 1927120.1)

Last updated on AUGUST 11, 2016

Applies to:

Advanced Networking Option - Version 11.2.0.3 and later
JDBC - Version 11.2.0.3.0 and later
Information in this document applies to any platform.

Symptoms

The following errors appear in the alert.log for example:

 

NI cryptographic checksum mismatch error: 12599.

VERSION INFORMATION:
  TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
  TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
  Oracle Bequeath NT Protocol Adapter for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
Time: 11-SEP-2014 09:55:38
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 Sep 11 09:55:38 2014

 

Changes

This typically starts when you configure network encryption on the server side (only) with sqlnet.ora parameters

SQLNET.ENCRYPTION_SERVER = required
SQLNET.ENCRYPTION_TYPES_SERVER = (AES256)

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms