Re: rman and dbv disagree on datafile quality ?
- From: "Nilo Segura" <nilosegura@xxxxxxxxx>
- To: "Christian Antognini" <Christian.Antognini@xxxxxxxxxxxx>
- Date: Fri, 16 Mar 2007 14:57:06 +0100
Ciao,
The error is (was) ORA-19566: exceeded limit of 0 corrupt blocks for
file....
I just did the tests.. the validate option will return that nothing is wrong
RMAN> backup check logical validate tablespace stager_data;
Starting backup at 16-MAR-07
starting full resync of recovery catalog
full resync complete
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=211 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Tivoli Data Protection for Oracle: version 5.2.0.0
allocated channel: ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_2: sid=255 devtype=SBT_TAPE
channel ORA_SBT_TAPE_2: Tivoli Data Protection for Oracle: version 5.2.0.0
channel ORA_SBT_TAPE_1: starting full datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
input datafile fno=00004
name=/ORA/dbs03/oradata/ATLASSG/ATLASSGstager_data01
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:04:43
Finished backup at 16-MAR-07
But If I run again the level 0 backup..
RMAN> backup incremental level 0
database force format '%d_%T_%U_L0'
plus archivelog format '%d_%T_%U_L0arch'
delete all input;
2> 3> 4>
Starting backup at 16-MAR-07
current log archived
released channel: ORA_DISK_1
released channel: ORA_DISK_2
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=211 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Tivoli Data Protection for Oracle: version 5.2.0.0
allocated channel: ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_2: sid=255 devtype=SBT_TAPE
channel ORA_SBT_TAPE_2: Tivoli Data Protection for Oracle: version 5.2.0.0
channel ORA_SBT_TAPE_1: starting archive log backupset
channel ORA_SBT_TAPE_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=53093 recid=53340 stamp=617380083
channel ORA_SBT_TAPE_1: starting piece 1 at 16-MAR-07
channel ORA_SBT_TAPE_1: finished piece 1 at 16-MAR-07
piece handle=ATLASSG_20070316_l9icou7s_1_1_L0arch tag=TAG20070316T142809
comment=API Version 2.0,MMS Version 5.2.0.0
channel ORA_SBT_TAPE_1: backup set complete, elapsed time: 00:00:16
channel ORA_SBT_TAPE_1: deleting archive log(s)
archive log
filename=/ORA/dbs02/oracle/admin/arch/ATLASSG/ATLASSGarch/1_53093_584364727.dbf
recid=53340 stamp=617380083
Finished backup at 16-MAR-07
Starting backup at 16-MAR-07
using channel ORA_SBT_TAPE_1
using channel ORA_SBT_TAPE_2
channel ORA_SBT_TAPE_1: starting incremental level 0 datafile backupset
channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
input datafile fno=00004
name=/ORA/dbs03/oradata/ATLASSG/ATLASSGstager_data01
input datafile fno=00001 name=/ORA/dbs03/oradata/ATLASSG/ATLASSGsystem_01
input datafile fno=00003 name=/ORA/dbs03/oradata/ATLASSG/ATLASSGsysaux
channel ORA_SBT_TAPE_1: starting piece 1 at 16-MAR-07
channel ORA_SBT_TAPE_2: starting incremental level 0 datafile backupset
channel ORA_SBT_TAPE_2: specifying datafile(s) in backupset
input datafile fno=00005
name=/ORA/dbs03/oradata/ATLASSG/ATLASSGstager_indx01
input datafile fno=00002 name=/ORA/dbs03/oradata/ATLASSG/ATLASSGundo01_01
input datafile fno=00006 name=/ORA/dbs03/oradata/ATLASSG/ATLASSGundo01_02
channel ORA_SBT_TAPE_2: starting piece 1 at 16-MAR-07
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at
03/16/2007 14:32:01
ORA-19566: exceeded limit of 0 corrupt blocks for file
/ORA/dbs03/oradata/ATLASSG/ATLASSGstager_data01
continuing other job steps, job failed will not be re-run
channel ORA_SBT_TAPE_2: finished piece 1 at 16-MAR-07
piece handle=ATLASSG_20070316_lbicou8e_1_1_L0 tag=TAG20070316T142829
comment=API Version 2.0,MMS Version 5.2.0.0
channel ORA_SBT_TAPE_2: backup set complete, elapsed time: 00:08:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 03/16/2007 14:37:43
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at
03/16/2007 14:32:01
ORA-19566: exceeded limit of 0 corrupt blocks for file
/ORA/dbs03/oradata/ATLASSG/ATLASSGstager_data01
It is not consistent. If there is a bad block, it is not part of any
database object . The solution would be to recreate the tablespace, exp/imp
the user data.. but that would be the last solution.
ciao.
On 3/16/07, Christian Antognini <Christian.Antognini@xxxxxxxxxxxx> wrote:
Ciao Nilo
> Running a level 0 backup with RMAN will tell me that
> I have a bad block on one datafile (the backup will
> stop at that moment).
Out of curiosity, what is the exact error message?
> In the view V$DATABASE_BLOCK_CORRUPTION there is nothing.
Do you have the same behavior if you execute a BACKUP CHECK LOGICAL
VALIDATE TABLESPACE ?
Cheers,
Chris
--
Nilo Segura
Oracle Support - IT/DES
CERN - Geneva
Switzerland
Other related posts:
