:

ORA-00600 Internal Error Code, arguments [3020], [9]

The Problem

We are running Windows Server 2003, Sp2 on both the primary  and standby DB servers, using Oracle 11.2.0.2. We are using a data guard  physical standby DB, also.

We have a large tablespace due to a migration that we had completed as a one-off to load the data into the new database. I attempted to  shrink some of the datafiles to make them more manageable and not use up unnecessary space. After making the changes I checked that the physical standby database had been updated properly and found some errors in the alert log:

ORA-00600: internal error code, arguments: [3020], [9],  [490111], [38238847], [], [], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file# 9,  block# 490111, file offset is 4014989312 bytes)
ORA-10564: tablespace CDC_PUBLISHER_X1M
ORA-01110: data file 9: ‘D:\ORADATA\CTS\CDC_PUBLISHER_X1M02.DBF’
ORA-10561: block type ‘TRANSACTION MANAGED DATA BLOCK’, data  object# 1367456
Incident details in: D:\diag\rdbms\dg\incident\incdir_66377\db_pr02_4048_i66377.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging  details.
Slave exiting with ORA-600 exception

The Cause

Oracle support say that this is a bug which is fixed in  11.2.0.2 patchset 14 (which was not out for Windows at the time of writing).

The Solution

The first thing to do would be to apply the patch which  fixes the issue. Failing that, or perhaps in addition to that if it’s required,  you can take the following steps to resolve the issue:

1. On the standby database stop apply

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

2. Shutdown the standby database

SHUTDOWN IMMEDIATE;

3. Shutdown the primary database

SHUTDOWN IMMEDIATE;

4. Copy the affected files from the primary to the standby database

Copy File1 File2

5. Restart the primary DB

STARTUP

6. Start the standby DB and restart apply services

STARTUP MOUNT ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT  FROM SESSION;

Hopefully this has helped to resolve your issue, but you may also be facing a very similar ORA-00600 error. Well, I think it is the same one but under slightly different conditions which has the same ORA-00600, arguments: [3020] error code.

Like it, share it...

Category: ORA 600


Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *