My Oracle Support Banner

Native Encryption with DBFIPS failing with ORA-12699 error when connecting as SYS or Any user (Doc ID 2717455.1)

Last updated on OCTOBER 08, 2020

Applies to:

Advanced Networking Option - Version 12.1.0.2 to 12.2.0.1 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

ORA-12699 are seen during user connections. It is noted that there is native encryption and SQLNET.FIPS_140=TRUE turned on.

Commenting SQLNET.FIPS_140=TRUE will stop this error. Sample sqlnet file is show below

 

#### sqlnet.ora file #########

SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT= (SHA1)
SQLNET.ENCRYPTION_CLIENT = REQUIRED
SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER= (SHA1)
SQLNET.ENCRYPTION_SERVER = REQUIRED
NAMES.DIRECTORY_PATH= (TNSNAMES, HOSTNAME, EZCONNECT)
SQLNET.ENCRYPTION_TYPES_CLIENT= (AES256)
SQLNET.ENCRYPTION_TYPES_SERVER= (AES256)
#SQLNET.FIPS_140 = TRUE

 

Changes

 Using Native encryption with SQLNET.FIPS_140=TRUE

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.