| listener stopped suddenly [message #395996] |
Fri, 03 April 2009 08:11  |
knight
Messages: 111
Registered: January 2009
|
Senior Member |
|
|
10g RAC two node setup on solaris.
listener suddenly went down today ( on both nodes ).
I could only find foll. messages logged in listener.log
03-APR-2009 14:13:13 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=server-02)(USER=oracle))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=169870336)) * status * 0
03-APR-2009 14:13:13 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(server=dedicated)(service_name=prod)(failover_mode=(type=select)(method=basic))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.160.12.12)(PORT=44830)) * establish * PROD * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
.
.
.
.
Currently tracing is not enabled for listener.
Is there any way that the cause for this can be detected.
Also the foll. messages are in alert log
ALTER SYSTEM SET service_names='' SCOPE=MEMORY SID='PROD1';Fri Apr 3 14:08:43 2009
Immediate Kill Session#: 3732, Serial#: 7794
was this statement fired implicitly by oracle server ??
or by user??
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
