| DB Down with the alert java.sql.SQLRecoverableException [message #488165] |
Wed, 05 January 2011 06:51  |
pradies
Messages: 250
Registered: May 2008
|
Senior Member |
|
|
Hi,
I am facing a problem of DB down just after getting the alert "java.sql.SQLRecoverableException: No more data to read from socket---java.sql.SQLRecoverableException: No more data to read from socket" and when I checked the Alert log file I didn't find any thing related to this.
Can some one tell me why my db is going down. and what is the solution for this.
Pradeep
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: DB Down with the alert java.sql.SQLRecoverableException [message #488497 is a reply to message #488490] |
Sat, 08 January 2011 02:36  |
John Watson
Messages: 8960
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
According to your alert log, you had some "Fatal NI connect error 12170." events. Don't worry about them, just suppress them by putting
diag_adr_enabled_listenername=OFF
in your sqlnet.ora file, if I remember correctly. They are nothing to do with the instance failing.
Then there was some sort of shutdown at 23:20:02 and a startup at 23:21:32. Do you know what was happening then? Is it possible that someone accidentally shut it down and re-started it immediately? (We've all done it, nothing to be ashamed of)
|
|
|
|
|
|
| Re: DB Down with the alert java.sql.SQLRecoverableException [message #488500 is a reply to message #488497] |
Sat, 08 January 2011 03:22 |
pradies
Messages: 250
Registered: May 2008
|
Senior Member |
|
|
Hi John,
As you said in your post I will add diag_adr_enabled_listenername=OFF in sqlnet.ora file. If the same errors persist in alert log file then i will back.
As you are talking about the server shutdown, No one is doing the shutdown db forcelly. Its going down automatically and alert is coming from application to us.
Regards
Pradeep
|
|
|
|
|
|
| Re: DB Down with the alert java.sql.SQLRecoverableException [message #488503 is a reply to message #488500] |
Sat, 08 January 2011 03:49 |
John Watson
Messages: 8960
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
Pradeep, you say Quote:No one is doing the shutdown db forcelly. Its going down automatically but your alert log saysShutting down instance (immediate)
License high water mark = 1744
Stopping Job queue slave processes, flags = 7
Tue Jan 04 23:21:32 2011
Starting ORACLE instance (normal)
I do not know of any automatic process that could shutdown an instance and then restart it. The default level of auditing will log all SYSDBA logons but nothing more; if I were you, I would go to the audit_dest and see who was logged on as SYSDBA at the time. And set audit-sys_operations=true so that you can track what is done next time.
|
|
|
|
|
|
|
|
| Re: DB Down with the alert java.sql.SQLRecoverableException [message #488579 is a reply to message #488500] |
Sun, 09 January 2011 23:59 |
pradies
Messages: 250
Registered: May 2008
|
Senior Member |
|
|
Hi John,
After placing the specified parameter in listener.ora file still I am facing the same errors in alert log files.
--------------------------------------------------
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Time: 09-JAN-2011 20:53:30
Tracing not turned on.
Tns error struct:
ns main err code: 12535
----------------------------------------------------
Pradeep
|
|
|
|
|
|
|
|
| Re: DB Down with the alert java.sql.SQLRecoverableException [message #488652 is a reply to message #488640] |
Mon, 10 January 2011 06:26 |
John Watson
Messages: 8960
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
You haven't read my post, and neither have you read the documentation. DIAG_ADR_ENABLED is a sqlnet.ora parameter, not a listener.ora parameter. Better read up on it before you proceed.
And as for your audit records, if you have enabled auditing for all sys operations, you will have in your audit trail a complete list of every command executed as sysdba, with details that should let you find the culprit.
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
