OLOGGERD Reporting 'Fatal NI Connect Error 12516, Connecting To:' or ''Fatal NI connect error 12514, connecting to:' Messages In Clusterware Alert.log (Doc ID 2399048.1)

Last updated on JUNE 12, 2023

Applies to:

Symptoms

On : Exadata Upgrade to 12.2.1.1.6

GI Upgrade only

Clusterware alert log on Exadata Compute Node db01.anywhere.com reporting constant 'Fatal NI connect error 12516, connecting to' error messages.


ERROR
-----------------------

- Excerpt from alert.log:

Fatal NI connect error 12516, connecting to:
(DESCRIPTION=(CONNECT_TIMEOUT=60)(ADDRESS=(PROTOCOL=tcp)(HOST=xxxxx-scan)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<servicename_10>)(CID=(PROGRAM=ologgerd)(HOST=db01.anywhere.coml)(USER=root)))(SECURITY=(ENCRYPTION_CLIENT=requested)))

 VERSION INFORMATION:
  TNS for Linux: Version 12.2.0.1.0 - Production
  TCP/IP NT Protocol Adapter for Linux: Version 12.2.0.1.0 - Production
 Time: 08-MAY-2018 10:19:23
 Tracing not turned on.
 Tns error struct:
  ns main err code: 12564

TNS-12564: TNS:connection refused
  ns secondary err code: 12560
  nt main err code: 524

TNS-00524: Current operation is still in progress
  nt secondary err code: 115
  nt OS err code: 0
2018-05-08T10:19:50.537296-04:00


***********************************************************************



STEPS
-----------------------
Errors come after the Grid Infrastructure was upgraded to 12.2 from Platinum Patching activity.


BUSINESS IMPACT
-----------------------
Constant errors in clusterware log.

Cause