Last week on wednesday  we had experienced the following error in our instance 2 of the 2 node RAC setup in the alert log.
Wed Feb 14 23:34:30 2007
Errors in file /oracle/app/oracle/admin/SSKIDB/bdump/sskidb2_lms1_6811.trc:
ORA-00600: internal error code, arguments: [kjbrasr:pkey], [122722], [], [], [], [], [], []
Wed Feb 14 23:34:31 2007
Errors in file /oracle/app/oracle/admin/SSKIDB/bdump/sskidb2_lms1_6811.trc:
ORA-00600: internal error code, arguments: [kjbrasr:pkey], [122722], [], [], [], [], [], []
Wed Feb 14 23:34:31 2007
Trace dumping is performing id=[cdmp_20070214233431]
Wed Feb 14 23:34:38 2007
Errors in file /oracle/app/oracle/admin/SSKIDB/bdump/sskidb2_lms1_6811.trc:
ORA-00600: internal error code, arguments: [kjbrasr:pkey], [122722], [], [], [], [], [], []
Wed Feb 14 23:34:38 2007
LMS1: terminating instance due to error 484
Instance terminated by LMS1, pid = 6811
Due to the above the error the instance 2 was automatically restarted by the LMS ,pmon  process
For your infomation our system is 2 node RAC setup 10.2.0.2 version of database with ASM and also OS :Solaris 10
Later when we diagonised the error and gone through the Docs of metalink we realised it was caused becaused when DML activity was going on certain objects of the database and at the same time same objects were tried to rebuild and also at the same time some one trying to query that objects from instance 2.Hence LMS process had restarted the instance 2
Although when raised an SR with oracle it was found to be a BUG 4639236
.But since we knew the cause of the error we thought to avoid the bug rather then solving it by applying the patch by now running the rebuildind scripts simulatenously with any DML activity done on the same object
