24-JAN-2013 13:50:32 * node_down * bsspbbi1 * 0It looks like Listener has been stopped by CRS, Because of "bsspbbi1 node_down".
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.216.45)(PORT=1521)))
No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.216.35)(PORT=1521)))
Listener completed notification to CRS on stop
24-JAN-2013 13:50:32 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=bsspbbi1.etpi.com.ph)(USER=oracle))(COMMAND=stop)(ARGUMENTS=64)(SERVICE=LISTENER_BSSPBBI1)(VERSION=169870336)) * stop * 0
With that, can I assume that the cause is the network traffic? Since all LANs uses 1 physical network card?Maybe..
Is there anything we can adjust in Oracle? is there a Timeout settings that can be configured? Or we need to adjust the hardware already?Is This site helpful 4u?
What will be the effect if we increase the misscount parameter? Will that greatly impact the performance?==
user583843 wrote:Thanks for this, can you explain it further? Are you saying that network might not be the problem, and it might be the disk i/o?
you need to add this line in Red Hat Enterprise Linux 4.vmx so that disk will not hang.
May be your disks I/O is more and because of that node was rebooted, try above command.