I just arrived at the company this morning and found the following error in the alarm log of a logic backup library:

Fri Nov 25 07:44:08 2011

Errors in file /home/oracle/admin/cms2009/bdump/cms2009_lsp0_19249.trc:

ORA-12801: error signaled in parallel query server P004

ORA-00600: internal error code, arguments: [kollasg:client lob on server], [], [], [], [], [], [], []

LOGSTDBY Apply process P005 pid=47 OS id=19263 stopped

…

Errors in file /home/oracle/admin/cms2009/bdump/cms2009_lsp0_19249.trc:

ORA-12801: error signaled in parallel query server P000

ORA-00600: internal error code, arguments: [KSFD_DECAIOPC], [0x24C52A500], [], [], [], [], [], []

LOGSTDBY Apply process P005 pid=47 OS id=19263 stopped

LOGSTDBY Apply process P004 pid=46 OS id=19261 stopped

LOGSTDBY Apply process P009 pid=50 OS id=19271 stopped

LOGSTDBY Apply process P010 pid=51 OS id=19273 stopped

LOGSTDBY Apply process P008 pid=49 OS id=19269 stopped

Fri Nov 25 07:44:14 2011

TLCR process death detected. Shutting down TLCR

So immediately check:

select * from v$Logstdby_state;

Finding that the logging application has stopped, you attempt to restart its logging application.

alter database start logical standby apply immediate;

The log application was found to be in good working order.

Since then, I have been searching for the cause of the error.
may be due to a bug:

Bug 7312623: Ora-00600 [KSFD_DECAIOPC] ON LOGICAL STANDBY DATABASE.

From “ITPUB blog” link: http://blog.itpub.net/23073818/viewspace-712043/, if you want to reprint, please indicate the source, otherwise will be investigated for legal responsibility.

Reproduced in: http://blog.itpub.net/23073818/viewspace-712043/