oracle probe - oracle 19.0.0.0 Profile X, instance X, cannot connect to database: (ORA-12649: Unknown encryption or data integrity algorithm )

[Nick Barlow]

Hi all,

Just wondering if anyone is experiencing the error message below on oracle 19
oracle probe version 5.45-T1
restarting the probe temporarily allows connection, then it fails again at a later time.

Profile X, instance X, cannot connect to database: (ORA-12649: Unknown encryption or data integrity algorithm )

[David Michel]

At the robot with the oracle probe, is the oracle client version 12.2 or 18.1?

[Nick Barlow]

ora client is 19.0.0.0

[Nick Barlow]

19 isnt supported bah
Is there a test or beta version in the pipeline ?
We have 4.45-T1 , which fixes the _from_ typo issue

[David Michel]

After asking the question, reviewed the release notes and found: 

• Added support for Oracle 18C RAC and 19c NON-RAC and RAC databases.
  
  mmm, but that conflicts with the supported versions chart. So dev is going to look into documentation conflict, but too late for anything today. 
  
  So went back to searching on that oracle error code, there's nothing in KBs but this time checked cases and got a hit which might help you out. 

The error "ORA-12649" occurs between your oracle client and server. ORA-12500 to ORA-12699
https://docs.oracle.com/database/121/ERRMG/ORA-12500.htm#ERRMG-GUID-BD6AAC21-3F15-4F70-B3C5-064ADCF5EC51 ORA-12649:
Unknown encryption or data integrity algorithm
Cause: A list-of-algorithms parameter included an algorithm name that was not recognized.
Action: Either remove that algorithm name, correct it if it was misspelled, or install the driver for the missing algorithm.

[Nick Barlow]

Thanks for the info. Let me know if you heard anything back.

[David Michel]

As for the documentation dev will correct the page so you can check there next week. 
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/oracle-oracle-database-monitoring/oracle-oracle-database-monitoring-release-notes.html

[Nick Barlow]

To make things more difficult to troubleshoot, this is an intermittent issue, and restarting the probe restores service.
I've put in a lua script on a nas schedule, to restart the affected probes every hour, as a workaround.

[Stephen Danseglio]

Hi Nick,

TNS-12649 Unknown encryption or data integrity algorithm
Cause: A SQL*Net list-of-algorithms parameter included an algorithm name that was not recognized.

Action: Either remove that algorithm name, correct it if it was misspelled, or install the driver for the missing algorithm.

Attach the sqlnet.ora file

Steve

------------------------------
Support Engineer
Broadcom
US
------------------------------

[David Michel]

The intermittent nature and restart workaround leads me to think it might be helpful to check things at the oracle client, and if there is a commonality between the instances with the problem. 

Not familiar with oracle, but this page seems to show how to setup logging at the client. 
https://docs.oracle.com/cd/A57673_01/DOC/net/doc/NWTR23/apa.htm

[Nick Barlow]

Hi David,

The sqlnet.ora is configured as follows. A stable configuration has also been compared to this one, and is identical

SQLNET.ENCRYPTION_SERVER=REQUIRED

SQLNET.CRYPTO_CHECKSUM_SERVER=REQUIRED

SQLNET.ENCRYPTION_TYPES_SERVER=(AES256,AES192,AES128)

SQLNET.CRYPTO_CHECKSUM_TYPES_SERVER=(SHA1)

SQLNET.ENCRYPTION_CLIENT=REQUIRED

SQLNET.CRYPTO_CHECKSUM_CLIENT=REQUIRED

SQLNET.ENCRYPTION_TYPES_CLIENT=(AES256,AES192,AES128)

SQLNET.CRYPTO_CHECKSUM_TYPES_CLIENT=(SHA1)

Thanks