LSP Keep On Failing With ORA-00600: internal error code, arguments: [600] Error In Logical Standby Database.

(Doc ID 2223464.1)

Last updated on APRIL 17, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information in this document applies to any platform.

Symptoms

Log mining has failed with below error


LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1234, /u01/app/oracle/oradata/DB1/DB1_0001_1234.arc
LOGMINER: End mining logfile for session 1 thread 1 sequence 1234, /u01/app/oracle/oradata/DB1/DB1_0001_1234.arc
ORA-00600: internal error code, arguments: [2619], [1235], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2619], [1235], [], [], [], [], [], [], [], [], [], []
LogMiner process death detected
LOGSTDBY: logminer process death detected, exiting.
LOGSTDBY: logminer process died with status 600
ORA-00600: internal error code, arguments: [600], [], [], [], [], [], [], [], [], [], [], []
LOGSTDBY Analyzer process AS00 server id=0 pid=33 OS id=12453 stopped
ORA-01280: Fatal LogMiner error.
ORA-00600: internal error code, arguments: [600], [], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], [], [], [], [], []

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms