Funny that, I got that same ORA-600 and ORA-15240 error combination last week, when playing around with Dataguard on 10gR2 (newly created test databases).
Dataguard is in "High Availability Mode" (set via Enterprise Manager GC). In my case someone had opened the standby (alter database open), thinking that it was the primary. Redo apply of course stopped. The error started popping up on the primary *after* the standby was closed and mounted and Dataguard started again. Bouncing the primary stopped it, but apart from the message no ill effects were apparent. I did extensively search google and MOS but sould not find a clear explanation.
All on Windows 2003, EMGC is 10gR5, Primary and Standby on different machines, 10.2.0.2.
Cheers, Tony Peter Hitchman wrote:
Hi Tyfanie, I believe I have the same problem, but I am migrating between 11.1 and 11.2 on Linux 64 bit platfom. I tried a couple of time to migrate and one time the asmca failed the other time it said it worked, but in fact failed. In the ASM alert log I see the error: ORA-00600: internal error code, arguments: [kfeInvokeLockCallback06], [30], [], [], [], [], [], [], [], [], [], [] ORA-15240: attribute name SAGE_ONLY is invalid Basically the ASM instance shutsdown, but the OUI does not recognzie this and blindly stumbles on outputing "Oracle not available" in the logs. I have an SR open with Oracle but so far no response. Also I started a thread on the list last week and a patch was suggested, but I thought I should go via Oracle Support to be sure! I would be interested to know if you see something similar in your ASM alert log. One other thing, having the environment variable ORA_CRS_HOME set to the original CRS home will also break the migration, because the wrong crsctl programme gets called, assuming of course you are on a *nix platform. Regards Pete -- //www.freelists.org/webpage/oracle-l
-- //www.freelists.org/webpage/oracle-l
