DB Server is not going Down After a reboot
1. Check the uptime. If it is Showing unexpected time then server is not rebooted.
2. Check the Logs.
[root@exampleDB ~]# tail -f /var/log/messages
Jul 23 19:30:14 exampleDB kernel: oracle: sending ioctl 2285 to a partition!
Jul 23 19:30:14 exampleDB kernel: oracle: sending ioctl 2285 to a partition!
Jul 23 19:30:14 exampleDB kernel: oracle: sending ioctl 2285 to a partition!
Jul 23 19:30:14 exampleDB kernel: oracle: sending ioctl 2285 to a partition!
That means an Oracle processes is not getting response from Storage.
3. Check that process id and Find out which LUN it is trying to access. try Fixing that Storage Communication issue.
4. If the Storage Communication issue is fixed but the server is still not came back. Please Kill All the process related to Oracle, the server will reboot as the reboot command is stuck for that process.
[root@exampleDB ~]# pkill -9 -u oracle
1. Check the uptime. If it is Showing unexpected time then server is not rebooted.
2. Check the Logs.
[root@exampleDB ~]# tail -f /var/log/messages
Jul 23 19:30:14 exampleDB kernel: oracle: sending ioctl 2285 to a partition!
Jul 23 19:30:14 exampleDB kernel: oracle: sending ioctl 2285 to a partition!
Jul 23 19:30:14 exampleDB kernel: oracle: sending ioctl 2285 to a partition!
Jul 23 19:30:14 exampleDB kernel: oracle: sending ioctl 2285 to a partition!
That means an Oracle processes is not getting response from Storage.
3. Check that process id and Find out which LUN it is trying to access. try Fixing that Storage Communication issue.
4. If the Storage Communication issue is fixed but the server is still not came back. Please Kill All the process related to Oracle, the server will reboot as the reboot command is stuck for that process.
[root@exampleDB ~]# pkill -9 -u oracle
0 Comments