My Oracle Support Banner

TNS-12599 And No More Data To Read From Socket With JDBC 19C When Native Encryption Is Enabled In The Database (Doc ID 2793241.1)

Last updated on OCTOBER 08, 2024

Applies to:

JDBC - Version 19.3 and later
Information in this document applies to any platform.

Symptoms

An application connects with JDBC 19c and often gets "No more data to read from socket" when accessing Oracle database with encryption enabled.

The encryption parameters in the database are:

SQLNET.ENCRYPTION_TYPES_SERVER = (AES256)
SQLNET.ENCRYPTION_TYPES_CLIENT = (AES256)
SQLNET.ENCRYPTION_SERVER = REQUIRED
SQLNET.ENCRYPTION_CLIENT = REQUIRED
SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER = (SHA1)
SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT = (SHA1)
SQLNET.CRYPTO_CHECKSUM_SERVER = REJECTED
SQLNET.ALLOWED_LOGON_VERSION=8

When the issue occurs, the exception 'No more data to read from socket' is reported on the client, and there is a TNS-12599: TNS:cryptographic checksum mismatch at the same time reported at the database side.

Changes

 

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.