Dataguard Physical Standby occurs ORA-600 [2130] after added new node to primary RAC database.
(Doc ID 759181.1)
Last updated on OCTOBER 09, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 10.2.0.4 [Release 9.2 to 10.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
1. Environments:
1). Dataguard system with physical standby database.
2). Primary database is RAC with 2 nodes and physical standby database is a single instance.
2. Added the 3th node to primary RAC database and performed the following steps on primary node1:
SQL>alter database add logfile thread 3
group 7 ('/<disk_path>/redo07.log') size 100M,
group 8 ('/<disk_path>/redo08.log') size 100M,
group 9 ('/<disk_path>t/redo09.log') size 100M;
SQL>alter database enable public thread 3;
SQL>create undo tablespace undotbs3 datafile '/<disk_path>/undotbs3.dbf' size 500m;
3. After the above mentioned steps the below errors occurred:
1). On the 3th node database alert log file reported similar errors:
Creating archive destination LOG_ARCHIVE_DEST_2: 'standby'
ARC0: Error 16099 Creating archive log file to 'standby'
Wed Jun 25 09:24:19 2008
Errors in file /home/oracle/admin/<oracle_sid>/bdump/<oracle_sid>_arc0_5143.trc:
ORA-16099: internal error ORA-00600 occurred at standby database
2). Trace file rac3_arc0_5143.trc displayed similar messages:
Error 16099 creating standby archive log file at host 'standby'
ARC0: Error 16099 Creating archive log file to 'standby'
kcrrfail: dest:2 err:16099 force:0
ORA-16099: internal error ORA-00600 occurred at standby database
RFS network connection lost at host 'standby'
Error 3113 detaching RFS from standby instance at host 'standby'
Ignoring kcrrvnc() detach error 3113
Standby database restarted; old mount ID 0x5dfa1b87 now 0x5dfb5175
RFS network connection lost at host 'standby'
Fail to ping standby 'standby', error = 3113
Error 3113 when pinging standby standby.
kcrrfail: dest:2 err:3113 force:0
Standby archive log instance not available at host 'standby'
Error 1034 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
Heartbeat failed to connect to standby 'standby'. Error is 1034.
kcrrfail: dest:2 err:1034 force:0
ORA-01034: ORACLE not available
Standby database restarted; old mount ID 0x5dfb5175 now 0x5dfb85c4
3). Physical standby database alert log file reported similar errors:
Wed Jun 25 10:02:52 2008
Errors in file /home/oracle/admin/<oracle_sid>/udump/<oracle_sid>_ora_8774.trc:
ORA-00600: internal error code, arguments: [2130], [0], [10], [3], [], [], [], []
ORA-600 signalled during: alter database register logfile '/home/oracle/orad...
4). ORA-600 trace file <oracle_sid>_ora_8774.trc displayed similar messages:
Reverting to 'old' standby current log 0
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [2130], [0], [10], [3], [], [], [], []
---Call Stack Trace---
ksedmp <- kgeriv <- kgeasi <- kccugg <- kcrrrfsoda <- kcrrrfsdsp <-
opirfs <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <-
sou2o <- main <- libc_start_main <- start
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |