Sometimes You can get “ORA-12599: TNS:cryptographic checksum mismatch ” error.
Details of error are as follows.
ORA-12599: TNS:cryptographic checksum mismatch
The error relates to an internally-filed bug ( not visible in My Oracle Support), but the high-level details are:
1) Establish connection enabling data integrity
2) Use the connection to execute a drop statement, drop directory TEST_DIR,
which is expected to fail for ORA-04043: object TEST_DIR does not exist.
3) then continue to use the connection to execute a select, select user from
The connection should still be usable at step 3). But when data integrity
types, SHA256, SHA384 and SHA512, is enabled on a jdbc thin connection, there
is “java.sql.SQLRecoverableException: IO Error: Checksum fail” instead of ORA
error in step 2), and step 3) fails for connection is closed.
Integrity types, SHA1 and MD5 do not have this problem. Only SHA256, SHA384
and SHA512 have this problem.
Apply Patch 20960881 on top of JDBC 126.96.36.199
as a workaround, ensure matching values for SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT = SHA1 in source and target databases used by ODI (workaround since SHA1 does not present the problem):
In Oracle DN 188.8.131.52 sqlnet.ora:
SQLNET.ENCRYPTION_CLIENT = REQUIRED SQLNET.ENCRYPTION_TYPES_CLIENT = (AES256, AES192, AES128) SQLNET.CRYPTO_CHECKSUM_CLIENT = REQUIRED SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT= (SHA1) SQLNET.ENCRYPTION_SERVER = REQUIRED SQLNET.ENCRYPTION_TYPES_SERVER = (AES256, AES192, AES128) SQLNET.CRYPTO_CHECKSUM_SERVER = REQUIRED SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER= (SHA256, SHA384, SHA512, SHA1)
Additionally, for this particular case where CONNECTION_PROPERTY_THIN_NET_CHECKSUM_LEVEL is set to an invalid value, change its value to:
Do you want to learn more details about RMAN, then read the following articles.
877 views last month, 2 views today