Block recover RMAN., Error ORA-00267 to recover block RMAN Options

[Bruno Costa]

Hi my name is Bruno and I am having a problem with corrupt blocks:

Alert log messages:
Corrupt block relative dba: 0x0206c41f (file 67, block 443423)
Fractured block found during buffer read
Data in bad block:
type: 6 format: 2 rdba: 0x0206c41f
last change scn: 0x0000.86d0bc65 seq: 0x1 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x33433231
check value in block header: 0x18c0
computed block checksum: 0xf44b
Reread of rdba: 0x0206c41f (file 67, block 511367) found same corrupted data
Mon Apr 19 15:05:23 2010
Corrupt Block Found
TSN = 5, TSNAME = CBILL_DATA_LARGE
RFN = 8, BLK = 511367, RDBA = 33997855
OBJN = 428701, OBJD = 290074, OBJECT = BIN_INVOICED_INPUT, SUBOBJECT =
SEGMENT OWNER = CBILLSGCPR_SCH, SEGMENT TYPE = Table Segment

=======================================================================

I tried to recover the block with RMAN and got the following error;

Recovery Manager: Release 10.2.0.3.0 - Production on Mon Apr 19 15:34:39 2010
Copyright © 1982, 2005, Oracle. All rights reserved.

RMAN> connected to recovery catalog database

RMAN> BLOCKRECOVER DATAFILE 67 BLOCK 511367;

RMAN> Starting blockrecover at 19-APR-10
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=470 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=2114 devtype=DISK

channel ORA_SBT_TAPE_1: restoring block(s)
channel ORA_SBT_TAPE_1: specifying block(s) to restore from backup set
restoring blocks of datafile 00067
channel ORA_SBT_TAPE_1: reading from backup piece vol96bpp_1_1
channel ORA_SBT_TAPE_1: restored block(s) from backup piece 1
piece handle=vol96bpp_1_1 tag=TAG20100321T213026
channel ORA_SBT_TAPE_1: block restore complete, elapsed time: 02:03:59

starting media recovery

archive log thread 1 sequence 148360 is already on disk as file /z11/oradata/sgc10pr/archive/SGC10PR1_148360_637018302.arc
archive log thread 1 sequence 148361 is already on disk as file /z11/oradata/sgc10pr/archive/SGC10PR1_148361_637018302.arc
.....
........
..........
............
archive log thread 1 sequence 149954 is already on disk as file /z11/oradata/sgc10pr/archive/SGC10PR1_149954_637018302.arc
archive log thread 1 sequence 149955 is already on disk as file /z11/oradata/sgc10pr/archive/SGC10PR1_149955_637018302.arc
archive log thread 1 sequence 149956 is already on disk as file /z11/oradata/sgc10pr/archive/SGC10PR1_149956_637018302.arc
archive log thread 1 sequence 149957 is already on disk as file /z11/oradata/sgc10pr/archive/SGC10PR1_149957_637018302.arc
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of blockrecover command at 04/19/2010 17:44:02
ORA-00283: recovery session canceled due to errors
ORA-00267: name of archived log file not needed

Error description:
ORA-00267: name of archived log file not needed
Cause: During media recovery, the name of an archived redo log file was entered, but no name was requested.
Action: Continue media recovery, but do not enter a new log name.

Rman restores the backup piece of the last INC-0 and all the archived logs until now. I do not enter any new log name.
The problem is that initially there were other blocks which were usually fixed and is now giving this error.

The commands utilized to do the recover were the following:

1 - RMAN> BLOCKRECOVER CORRUPTION LIST;
2 - RMAN> BLOCKRECOVER DATAFILE 67 BLOCK 511367;

In both commands the error is the same. Has anyone experienced this?

Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options

SQL> SELECT * FROM V $ DATABASE_BLOCK_CORRUPTION;

FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTION TYPE
---------- ---------- ---------- ------------------ ---------
67 443423 1 0 FRACTURED
67 510992 3 0 CORRUPT
67 511044 1 0 CORRUPT
67 511367 1 0 CORRUPT


Thanks,

Bruno Costa.

[Kamran Agayev A.]

Haven't faced such case. Moreover, there's no information on metalink according this error

Is there any information written to the alert.log file about the recovery process?

[Bruno Costa]

Haven't faced such case. Moreover, there's no information on metalink according this error

Is there any information written to the alert.log file about the recovery process?

Thanks Kamran
Including, this error appears during recover utilizing the procedure described in:
http://kamranagayev.wordpress.com/2010/03/...ng-rman-backup/


Alert log:

Tue Apr 20 11:47:16 2010
Media Recovery Log /z11/oradata/sgc10pr/archive/SGC10PR1_149535_637018302.arc
Tue Apr 20 11:47:35 2010
Media Recovery Log /z11/oradata/sgc10pr/archive/SGC10PR1_149536_637018302.arc
Tue Apr 20 11:47:56 2010
Media Recovery Log /z11/oradata/sgc10pr/archive/SGC10PR1_149537_637018302.arc
Tue Apr 20 11:49:52 2010
Media Recovery Log /z11/oradata/sgc10pr/archive/SGC10PR1_149537_637018302.arc (restored)
Block media recovery failed with error 267
Tue Apr 20 11:49:52 2010
Errors in file /home/oracle/app/oracle/admin/sgc10pr/udump/sgc10pr_ora_372.trc:
ORA-00267: name of archived log file not needed

Trace log:

more /home/oracle/app/oracle/admin/sgc10pr/udump/sgc10pr_ora_372.trc
/home/oracle/app/oracle/admin/sgc10pr/udump/sgc10pr_ora_372.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /home/oracle/app/oracle/product/10.2.0
System name: SunOS
Node name: gyn-cpqd-08
Release: 5.10
Version: Generic_142900-03
Machine: sun4u
Instance name: sgc10pr
Redo thread mounted by this instance: 1
Oracle process number: 241
Unix process pid: 372, image: oracle@gyn-cpqd-08 (TNS V1-V3)

*** 2010-04-20 09:24:17.204
*** ACTION NAME:(0000022 STARTED104) 2010-04-20 09:24:17.202
*** SERVICE NAME:(SYS$USERS) 2010-04-20 09:24:17.202
*** SESSION ID:(1842.18741) 2010-04-20 09:24:17.202
Begin Media Recovery of 1 blocks
*** 2010-04-20 09:24:17.214
Media Recovery add redo thread 1
Start recovery at thread 1 ckpt scn 20818873467 logseq 149480 block 248691
End recovery at scn 20987809951
*** 2010-04-20 09:38:30.404
Resized overflow buffer to 9216K (for 8274K LWN)
*** 2010-04-20 09:38:53.400
Resized overflow buffer to 13312K (for 12888K LWN)
*** 2010-04-20 09:39:13.035
Resized overflow buffer to 14336K (for 13411K LWN)
*** 2010-04-20 09:47:17.145
*** ACTION NAME:(0000023 STARTED104) 2010-04-20 09:47:17.145
Block media recovery failed with error 267
ORA-00267: name of archived log file not needed
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 27188896Kb in 1380.03s => 19.24 Mb/sec
Total physical reads: 27188896Kb
Longest record: 62Kb, moves: 0/89263249 (0%)
Change moves: 343/2281 (15%), moved: 0Mb
Longest LWN: 14223Kb, moves: 6368/809611 (0%), moved: 4010Mb
Buffer resizes = 3
Overflow buffer = 0Kb (0 blocks)
Last redo scn: 0x0004.d9dc2d1c (20834954524)
----------------------------------------------
*** 2010-04-20 09:47:17.175
Media Recovery drop redo thread 1
*** 2010-04-20 10:20:25.759
*** ACTION NAME:(0000040 STARTED104) 2010-04-20 10:20:25.759
Begin Media Recovery of 1 blocks
*** 2010-04-20 10:20:25.830
Media Recovery add redo thread 1
Start recovery at thread 1 ckpt scn 20818873467 logseq 149480 block 248691
End recovery at scn 20988356585
*** 2010-04-20 10:33:59.925
Resized overflow buffer to 9216K (for 8274K LWN)
*** 2010-04-20 10:34:22.659
Resized overflow buffer to 13312K (for 12888K LWN)
*** 2010-04-20 10:34:43.135
Resized overflow buffer to 14336K (for 13411K LWN)
*** 2010-04-20 10:42:24.124
*** ACTION NAME:(0000041 STARTED104) 2010-04-20 10:42:24.124
Block media recovery failed with error 267
ORA-00267: name of archived log file not needed
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 27188896Kb in 1318.39s => 20.14 Mb/sec
Total physical reads: 27188896Kb
Longest record: 62Kb, moves: 0/89263249 (0%)
Change moves: 343/2281 (15%), moved: 0Mb
Longest LWN: 14223Kb, moves: 6368/809611 (0%), moved: 4010Mb
Buffer resizes = 3
Overflow buffer = 0Kb (0 blocks)
Last redo scn: 0x0004.d9dc2d1c (20834954524)
----------------------------------------------
*** 2010-04-20 10:42:24.151
Media Recovery drop redo thread 1
*** 2010-04-20 11:27:24.107
*** ACTION NAME:(0000058 STARTED104) 2010-04-20 11:27:24.106
Begin Media Recovery of 1 blocks
*** 2010-04-20 11:27:24.235
Media Recovery add redo thread 1
Start recovery at thread 1 ckpt scn 20818873467 logseq 149480 block 248691
End recovery at scn 20988661144
*** 2010-04-20 11:41:20.726
Resized overflow buffer to 9216K (for 8274K LWN)
*** 2010-04-20 11:41:46.102
Resized overflow buffer to 13312K (for 12888K LWN)
*** 2010-04-20 11:42:08.632
Resized overflow buffer to 14336K (for 13411K LWN)
*** 2010-04-20 11:49:52.865
*** ACTION NAME:(0000059 STARTED104) 2010-04-20 11:49:52.865
Block media recovery failed with error 267
ORA-00267: name of archived log file not needed
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 27188896Kb in 1348.75s => 19.69 Mb/sec
Total physical reads: 27188896Kb
Longest record: 62Kb, moves: 0/89263249 (0%)
Change moves: 343/2281 (15%), moved: 0Mb
Longest LWN: 14223Kb, moves: 6368/809611 (0%), moved: 4010Mb
Buffer resizes = 3
Overflow buffer = 0Kb (0 blocks)
Last redo scn: 0x0004.d9dc2d1c (20834954524)
----------------------------------------------
*** 2010-04-20 11:49:52.913
Media Recovery drop redo thread 1

[HAL9000]

"this error appears during recover utilizing the procedure "

If it's not on MetaLink you must open an iTar and let Oracle support resolve it.

[Bruno Costa]

I opened a call at mletalink..

Thanks

[Bruno Costa]

After opening a call I received this response in Metalink;

I found several bugs for the ORA-00267 error, however none are related exactly with RMAN blockrecover command. At this time, there is no fix or known workaround for this error.

There are two options:

1. I can log a bug to investigate, in which case we would require additional events to be set and trace files collected.

- OR -

2. You can restore the corrupted datafile and then recover to resolve the corrupt block issues.

Regards,

Patti
Global Customer Services

[SteveC]

Thanks for the feedback.