Last night we have few severity call with below message
Fatal NI connect error 12537, connecting to:
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
Time: 10-Feb-2014 06:47:16
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (6224) as a result of ORA-609
Need to spend a lot of time in investigating and considering options like
sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=180
listener.ora: INBOUND_CONNECT_TIMEOUT_<listener>=120
and even changing kernel parameters for linux in /etc/sysctl.conf
#control IP packet forwarding
net.ipv4.ip_forward=1
But, thought for a while... as this is a 3 node RAC and we never faced this issue. But, I remember that during last PSU patching activity, we purposefully didn't started dbconsole to check who will be using as none from customer/application owned during KT.
But, finally..I have to work on this...
Metalink ID Lsnrctl Status is Failing and Alert.log Shows TNS-12537 and ORA-609 (Doc ID 950135.1)
saved my time further
===================================================================
Again, it is important to note that these errors are directly related to the startup of the EM Console product. The solution documented here will not apply to any other situation.
Note 430200.1 EM Throws Core Dumps and EMAgent is Thrashing
Notably:
"The nscd daemon may have gone rogue causing EM Agent to crash. The nscd is a OS daemon that provides a cache for the most common name service requests to improve performance (eg. LDAP, NIS, DNS etc...)"
Solution
Obtain the following document and perform the steps to solve the EM Agent issue. Note 430200.1
- EM Throws Core Dumps and EMAgent is Thrashing
In this particular case, the chkconfig nscd daemon and a reboot of the server were necessary to solve the problem.
=================================================================
In my case..... I just started dbconsole which was stopped after PSU patching and the alert log errors disappeared.
Fatal NI connect error 12537, connecting to:
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
Time: 10-Feb-2014 06:47:16
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (6224) as a result of ORA-609
Need to spend a lot of time in investigating and considering options like
sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=180
listener.ora: INBOUND_CONNECT_TIMEOUT_<listener>=120
and even changing kernel parameters for linux in /etc/sysctl.conf
#control IP packet forwarding
net.ipv4.ip_forward=1
But, thought for a while... as this is a 3 node RAC and we never faced this issue. But, I remember that during last PSU patching activity, we purposefully didn't started dbconsole to check who will be using as none from customer/application owned during KT.
But, finally..I have to work on this...
Metalink ID Lsnrctl Status is Failing and Alert.log Shows TNS-12537 and ORA-609 (Doc ID 950135.1)
saved my time further
===================================================================
Again, it is important to note that these errors are directly related to the startup of the EM Console product. The solution documented here will not apply to any other situation.
Changes
No changes would be necessary for this situation to arise.Cause
The problem was caused by an issue with the nscd daemon similar to the problem documented here:Note 430200.1 EM Throws Core Dumps and EMAgent is Thrashing
Notably:
"The nscd daemon may have gone rogue causing EM Agent to crash. The nscd is a OS daemon that provides a cache for the most common name service requests to improve performance (eg. LDAP, NIS, DNS etc...)"
Solution
Obtain the following document and perform the steps to solve the EM Agent issue. Note 430200.1
- EM Throws Core Dumps and EMAgent is Thrashing
In this particular case, the chkconfig nscd daemon and a reboot of the server were necessary to solve the problem.
=================================================================
In my case..... I just started dbconsole which was stopped after PSU patching and the alert log errors disappeared.
No comments:
Post a Comment