Comments on: ORA-00600 [kgeade_is_0] http://www.usn-it.de/index.php/2008/04/07/ora-00600-kgeade_is_0/ Martin Klier - Oracle, Linux, MS SQL Server Fri, 17 Feb 2012 03:49:51 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: usn http://www.usn-it.de/index.php/2008/04/07/ora-00600-kgeade_is_0/comment-page-1/#comment-28 usn Sun, 13 Apr 2008 12:36:45 +0000 http://www.usn-it.de/?p=41#comment-28 Can you cold-out the RAC for some minutes and restart CRS, and make sure that all DB processes live that way? My interpretation of that is the partial death of some processes, the error being just a secondary effect. Usn Can you cold-out the RAC for some minutes and restart CRS, and make sure that all DB processes live that way? My interpretation of that is the partial death of some processes, the error being just a secondary effect.
Usn

]]> By: Curtis R. http://www.usn-it.de/index.php/2008/04/07/ora-00600-kgeade_is_0/comment-page-1/#comment-27 Curtis R. Sun, 13 Apr 2008 03:32:43 +0000 http://www.usn-it.de/?p=41#comment-27 Running into this on 3 out of 4 nodes in a RAC. Any more details? Running into this on 3 out of 4 nodes in a RAC. Any more details?

]]> By: usn http://www.usn-it.de/index.php/2008/04/07/ora-00600-kgeade_is_0/comment-page-1/#comment-17 usn Mon, 07 Apr 2008 14:33:44 +0000 http://www.usn-it.de/?p=41#comment-17 Okay, found out what happened: The RAC was in reconfiguration state (node fence due to heavy load), and at synchronous reboots of the two nodes the network stack for the bonded interconnect was initialized too late on Node1. Somehow, the instance started, but immediately after that the CRS decided to fence the local node (1) to avoid split brain. But starting of the instance was already in progress, and some background processes died due to a lack of interconnect I guess. That might be where the ORA-447 comes from. Weird, but if you need details send me an email. Usn Okay, found out what happened:

The RAC was in reconfiguration state (node fence due to heavy load), and at synchronous reboots of the two nodes the network stack for the bonded interconnect was initialized too late on Node1.

Somehow, the instance started, but immediately after that the CRS decided to fence the local node (1) to avoid split brain. But starting of the instance was already in progress, and some background processes died due to a lack of interconnect I guess. That might be where the ORA-447 comes from.

Weird, but if you need details send me an email.
Usn

]]>