Congratulations, it's a bug :-) It's not your fault. When ASM is upgrade to 11.2 and DB is 11.1.0.6, you will face this issue when try to open database instance. The base bug is *Bug 7311909: ORA-600 [KFDOFFLINE01] ERROR WHEN ONE OF THE FAILGROUPS IS OFFLINED Try to apply the fix for 7311909 (or PSU2 which includes 7311909), of cause, in your testing system first. Good luck. *-- Kamus <kamusis@xxxxxxxxx> Visit my blog for more : http://www.dbform.com Join ACOUG: http://www.acoug.org On Mon, Jun 21, 2010 at 6:31 PM, Peter Hitchman <pjhoraclel@xxxxxxxxx>wrote: > Hi, > When the database tries to open this appears in the ASM alert log. > > ORA-00600: internal error code, arguments: [kfeInvokeLockCallback06], > [30], [], [], [], [], [], [], [], [], [], [] > ORA-15240: attribute name SAGE_ONLY is invalid > > I cannot find any information on this, which is why I am going to > start again. I think I somehow managed to corrupt ASM, after the > initial run of the assistant failed during the grid infrastructure > install, when I had the ORA_CRS_HOME env var set to the 11.1 CRS home. > > Regards > Pete > > > On Sat, Jun 19, 2010 at 5:15 AM, Kumar Madduri <ksmadduri@xxxxxxxxx> > wrote: > > Hello > > I had a similar issue for couple of scenarios > > 1. ASM code tree was at a lower patch level than RDBMS code tree (like > PSU1 > > and PSU2 for example) > > 2. During ASM rebalance after additional LUNS were added and the RDBMS > > isntance would crash with the messages similar to what you had given > after > > ASM completes rebalance. > > > > I am interested in knowing how you resolved your issue though. > > > > Thank you > > Kumar > > > > On Thu, Jun 17, 2010 at 12:32 PM, Peter Hitchman <pjhoraclel@xxxxxxxxx> > > wrote: > >> > >> Hi, > >> > >> 2 Node RAC 11.1.0.6.0 database on OEL 64 bit > >> > >> This is a continuation of my last post. Got around the issues with the > >> assistants and upgraded the cluster software, the listener and ASM, > >> all of that appears to be working OK. > >> But when I try to open the database it looses the connection to ASM: > >> > >> ALTER DATABASE OPEN > >> This instance was first to open > >> Errors in file > >> /oracle/diag/rdbms/s3tsps/S3TSPS1/trace/S3TSPS1_asmb_11805.trc: > >> ORA-15064: communication failure with ASM instance > >> ORA-03113: end-of-file on communication channel > >> Process ID: > >> Session ID: 130 Serial number: 17 > >> ASMB (ospid: 11805): terminating the instance due to error 15064 > >> System state dump is made for local instance > >> System State dumped to trace file > >> /oracle/diag/rdbms/s3tsps/S3TSPS1/trace/S3TSPS1_diag_11763.trc > >> Thu Jun 17 09:13:04 2010 > >> ORA-1092 : opitsk aborting process > >> Trace dumping is performing id=[cdmp_20100617091304] > >> Instance terminated by ASMB, pid = 11805 > >> > >> I found a post from back in Feb this year with some dire warnings, but > >> not exactly this situation. Also I found a note on MOS about issues > >> with an 11.1 database (948456.1) and 11.2 grid infrastructure, this > >> suggested "pinning" the nodes, which I did but it made no difference. > >> > >> This is a test RAC I recently had put together, at first the upgrade > >> to the grid infrastructure would not work because the nodes were not > >> in subnets in the same vlan (11.1 did not care about this), so I got > >> that sorted and then went through the steps of telling the cluster > >> software about the changes. So I am wondering if I broke something > >> else along the way. But I do not want to tear it all down, just to get > >> back to the same place in a weeks time. > >> > >> So does anyone know what's going on here? Am I going to have to resort > >> to opening an SR with Oracle (I have been reading the recent posts > >> about all the bad experiences!). Surely Oracle have not created a > >> situation where by it is not possible to upgrade a database from 11.1 > >> that is using ASM! > >> > >> Regards > >> Pete > >> -- > >> //www.freelists.org/webpage/oracle-l > >> > >> > > > > > > > > -- > Regards > > Pete > -- > //www.freelists.org/webpage/oracle-l > > >