RMAN--ORA-00600: internal error code, arguments: [3020]

I encountered an issue where standby fell out of sync with primary.  When trying to place the standby in auto recovery again, I received the following error in the alert log:


ORA-00600: internal error code, arguments: [3020], [41], [41955], [172008419], [], [], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file# 41, block# 41955, file offset is 343695360 bytes)
ORA-10564: tablespace SYSTEM
ORA-01110: data file 41: '+DATA/spl1adg/datafile/system.317.766442357'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 15


After researching this issue in metalink, the proposed solution was to rebuild the standby.  After pondering over this for a bit, I did the following which allowed me to remedy the issue:

1. Took the datafile offline on standby.

SQL> alter database datafile 41 offline drop;

2. Took fresh backup of the datafile in question on primary.

RMAN> backup as backupset datafile 41;

3. Copied the backup piece over to the standby server.

4. Cataloged the backup piece to standby controlfile.

RMAN> catalog backuppiece '/mnt/operational_dba/SPL1/RMAN/SPL1_783876021_35_1';

5. Restored the datafile in question.


RMAN> restore datafile 41;


Starting restore at 21-MAY-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=7333 device type=DISK


channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00041 to +DATA/spl1adg/datafile/system.317.783881825
channel ORA_DISK_1: reading from backup piece /mnt/operational_dba/SPL1/RMAN/SPL1_783876021_35_1
channel ORA_DISK_1: piece handle=/mnt/operational_dba/SPL1/RMAN/SPL1_783876021_35_1 tag=TAG20120521T152021
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:36
Finished restore at 21-MAY-12

6. Placed datafile in question online on standby.

SQL> alter database datafile 41 online;

7. Placed standby in auto recovery mode again.

SQL> alter database recover managed standby database using current logfile disconnect;

ORA-0600 errors disappeared.


Comments

Post a Comment

Popular posts from this blog

ORA-17630: Mismatch in the remote file protocol version client 2 server 3

I was trying to create an Oracle Data Guard environment (physical standby) from an Oracle database running version 12.1.0.2. The database was running an older PSU version ("Database Patch Set Update : 12.1.0.2.161018 (24006101)") to be specific. Upon trying to build the standby by using RMAN DUPLICATE with ACTIVE DATABASE, I ran into the below error: executing Memory Script Starting backup at 16-JUL-18 RMAN-03009: failure of backup command on prm1 channel at 07/16/2018 13:51:46 ORA-17629: Cannot connect to the remote database server ORA-17630: Mismatch in the remote file protocol version client 2 server 3 continuing other job steps, job failed will not be re-run released channel: prm1 released channel: prm2 released channel: prm3 released channel: prm4 released channel: prm5 released channel: stb1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ====================...
Read more

ORA-00338: log {n} of thread {n} is more recent than control file

I received the following error in a primary database's alert log that I was supporting recently.   ORA-00312: online log 5 thread 1: '+DATA/db_name/onlinelog/group_5.297.846947859' ORA-00338: log 5 of thread 1 is more recent than control file The database has a DataGuard environment as well and below are the steps that I took to resolve the issue. 1.  First, I checked the status of the redo logs and their current sizes and status. SQL> select group#,bytes/1024/1024,status from v$log;     GROUP# BYTES/1024/1024 STATUS ---------- --------------- ----------------          1              50 INACTIVE          2              50 INACTIVE          3              50 INACTIVE          4             250 INACTIVE   ...
Read more

RMAN-10038: database session for channel prm3 terminated unexpectedly

Problem: I had an issue where I was trying to build a 1.7 TB Data Guard environment and kept receiving the highlighted error below.  I thought it was some type of fluke so I restarted the job 2 more times only to receive the same error. Fix: After researching the issue, I found it was because the sqlnet.ora needed to be configured correctly.  I added the entry " SQLNET.EXPIRE_TIME = 10 " to the sqlnet.ora on both the source and the target database servers under the RDBMS $ORACLE_HOME/network/admin.  Upon restarting the RMAN active database standby build, it was able to move past this error and built successfully. Starting backup at 07-MAY-17 channel prm1: starting datafile copy input datafile file number=00003 name=+DATA/testdb/datafile/undotbs1.262.940412881 channel prm2: starting datafile copy input datafile file number=00129 name=+DATA/testdb/datafile/welldoc1.390.940509955 channel prm3: starting datafile copy input datafile file number=00130 name=+DATA/...
Read more