Doc ID: Note:277620.1 Type: PROBLEM
Last Revision Date: 11-JAN-2006 Status: PUBLISHED

The information in this document applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.4
This problem can occur on any platform.

Errors
ORA-01110 datafile :
ORA-10560
ORA-10564
ORA-10567
ORA-600 [3020] "Stuck Recovery"

Symptoms
Adding a new datafile on Primary database may raise a ORA-600 [3020] on standby database running in managed recovery mode with STANDBY_FILE_MANAGEMENT set to AUTO.

Standby alert log shows below error stack:
___________________________________

Tue Jun 22 21:36:04 2004
Recovery created file /oracle/BP2/sapdata13/undo_3/undo.data3
Successfully added datafile 73 to media recovery
Datafile #73: '/oracle/BP2/sapdata13/undo_3/undo.data3'
Tue Jun 22 21:36:09 2004
Errors in file /oracle/BP2/saptrace/background/bp2_mrp0_15619.trc:
ORA-00600: internal error code, arguments: [3020], [306184198], [1], [107745],
[17757], [960], [], []
ORA-10567: Redo is inconsistent with data block (file# 73, block# 6)
ORA-10564: tablespace PSAPUNDO
ORA-01110: data file 73: '/oracle/BP2/sapdata13/undo_3/undo.data3'
ORA-10560: block type 'KTFB Bitmapped File Space Bitmap'
MRP0: Background Media Recovery terminated with error 600
Changes
A new datafile was added on Primary database with standby database having STANDBY_FILE_MANAGEMENT set to AUTO.
Cause
This issue is addressed in Bug.3615851
Fix
Bug.3615851 is fixed in 9.2.0.6 patchset. There are also one-off patches available on 9.2.0.4 and 9.2.0.5 on some platforms - search for the underlying bug number, 3467364.

Workaround:

- shutdown standby database which is signalling ORA-600 [3020]
- manually copy the newly added datafile to standby. Make sure copying is done with tablespace in hot backup mode.
- restart managed recovery (MRP) on standby.
References

Bug 3615851 - Ora-600 [3020] On Stdby Adding Datafile To Primary