In testing of Oracle Enterprise Manager 11g R1 Grid Control we noticed frequent ORA-12599 errors in the alert logs of the monitored databases including the repository database. Upon further investigation we found that the ORA-12599 error message, such as the one below, was generated every time a connection was made to the target database as SYSDBA through Oracle Enterprise Manager 11g R1 Grid Control.
Tue Jun 01 11:23:03 2010
***********************************************************************
NI cryptographic checksum mismatch error: 12599.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 01-JUN-2010 11:23:03
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
Tue Jun 01 11:52:59 2010
Media Recovery Waiting for thread 1 sequence 135
Tue Jun 01 11:52:59 2010
RFS[38]: Selected log 5 for thread 1 sequence 135 dbid 459961910 branch 719914169
Tue Jun 01 11:52:59 2010
No errors were returned back to Grid Control nor did any of the process performed fail to complete. If you are seeing these messages in your alert logs you and you are not using encryption you can see if you are experiencing the same issue by simply logging into a database as SYSDBA through Grid Control and then log out of the database. If you are experiencing the same issue you should find two ORA-12599 messages in the alert log for the database one associated with the log in and one associated with the log out.
Our support ticket has been assigned Bug 9899797: 12599 ERRORS IN ALERT LOG WHEN CONNECT TO 11.2 DB AS SYSDBA IN GC 11.1. The following are bug numbers listed in My Oracle Support that are similar to what has been described in this document. All have a status of 16 – Support bug screening.
Bug 9850366: NI CRYPTOGRAPHIC CHECKSUM MISMATCH ERROR WHILE LOGGING OUT OF TARGET DB IN EM
Bug 9871805: LOGIN TO OEM CAUSES NI CRYPTOGRAPHIC CHECKSUM MISMATCH ERROR: 12599 MESSAGES IN
Bug 9844654: GC 11G REPOSITORY DB ALERT.LOG SHOWS TNS-12599
Bug 9881906: TNS ERROR IN ALERT LOG FOR 11.2 DB REPOSITORY
Bug 9830641: ORA-12599: TNS:CRYPTOGRAPHIC CHECKSUM MISMATCH
I too have encountered an increased frequency of the error ORA-12599, but was showing up before I installed OEM GC. Environment is IBM AIX 5.3 TL 9, Oracle 11gR1 instances, Oracle 11gR2 repository with OEM Version 11gR1. Any sharable solutions are welcome.
regards,
H.B. Tuthill, DBA
Hello H.B, thank you for visiting.
Are you seeing the 12599 errors on your repository database or your 11gR1 instances that are monitored by OEM GC?
The reason I ask is that I do not recall seeing issues with the 11gR1 targets. There are documented issues where 12599 is generated on 10gR2 and 11gR1 targets where monitored by OEM GC 10g. In those cases the issues were resolved by updating the JDBC driver in the OEM GC home.
The following was suggested by Oracle Support to work around the issue presented in this document.
Try adding the following to your
ORACLE_HOME/network/admin/sqlnet.orafile that resides in theORACLE_HOME/oms11g/network/adminand the SQLNET.ORA on the target instances.You should be able to make connections to both the repository and the target instances as SYSDBA via Oracle Enterprise Manager Grid Control 11gR1
Thanks for the great information – I have hit this bug head on and there has been a lack of information available as to why we are receiving the increased number of alerts.
Brenna Galbraith
Senior Oracle Consultant
All –
Oracle has published a workaround in base bug 9844654. Set SQLNET.ENCRYPTION_TYPES_SERVER = (3DES168) in your sqlnet.ora file and restart your listener. Worked for me for my EMGC 11g DB repository.
Sincerely,
Brenna Galbraith
Hello Brenna!
Thank you very much for the update on the bug and the published workaround.