ORA-19566: exceeded limit of 0 corrupt blocks for file usando SET MAXCORRUPT for datafile

including current SPFILE in backup set
channel t2: starting piece 1 at Oct 11 2016 13:33:26
channel t3: finished piece 1 at Oct 11 2016 13:34:41
piece handle=TECHDATABASKETDB_1_ON_INC0_DIARIO_edri3he6_1_1.DBF tag=BK_ON_INC0_DIA_20161011084106 comment=API Version 2.0,MMS Version 6.3.0.0
channel t3: backup set complete, elapsed time: 00:11:23
channel t4: finished piece 1 at Oct 11 2016 13:35:41
piece handle=TECHDATABASKETDB_1_ON_INC0_DIARIO_eeri3hl7_1_1.DBF tag=BK_ON_INC0_DIA_20161011084106 comment=API Version 2.0,MMS Version 6.3.0.0
channel t4: backup set complete, elapsed time: 00:08:38
channel t2: finished piece 1 at Oct 11 2016 13:40:22
piece handle=TECHDATABASKETDB_1_ON_INC0_DIARIO_egri3i16_1_1.DBF tag=BK_ON_INC0_DIA_20161011084106 comment=API Version 2.0,MMS Version 6.3.0.0
channel t2: backup set complete, elapsed time: 00:06:56
channel t1: finished piece 1 at Oct 11 2016 13:48:52
piece handle=TECHDATABASKETDB_1_ON_INC0_DIARIO_e7ri3gdp_1_1.DBF tag=BK_ON_INC0_DIA_20161011084106 comment=API Version 2.0,MMS Version 6.3.0.0
channel t1: backup set complete, elapsed time: 00:42:51
released channel: t1
released channel: t2
released channel: t3
released channel: t4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on t3 channel at 10/11/2016 10:59:44
ORA-19566: exceeded limit of 0 corrupt blocks for file +DATA/TECHDATABASKETDB/datafile/TECHDATA1.281.887801123</pre>

Blocos corrompidos:

Copyright (c) 1982, 2013, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options


OWNER                          SEGMENT_TYPE       SEGMENT_NAME                                                                      PARTITION_NAME                      FILE# CORR_START_BLOCK# CORR_END_BLOCK# BLOCKS_CORRUPTED DESCRIPTION
------------------------------ ------------------ --------------------------------------------------------------------------------- ------------------------------ ---------- ----------------- --------------- ---------------- --------------
118           3653944         3653944                1 Free Block
118           3653949         3653949                1 Free Block
118           3653954         3653954                1 Free Block
118           3653959         3653959                1 Free Block

Uma ação paliativa para garantir pelo menos o backup é utilizar a sintaxe “SET MAXCORRUPT for datafile ” para o datafile que está corrompido. Com isso , o backup terminará sem erros. No entanto, a corrupção dos blocos permanecerá.
Execução com a sintaxe “SET MAXCORRUPT” no backup. Note que coloquei o ID do datafile que apresentou erro, no caso 118, e o número aceitável de até 4 blocos corrompidos.

[TECHDATABASKETDB_1]> rman

Recovery Manager: Release 11.2.0.4.0 - Production on Wed Oct 12 00:25:15 2016

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN> connect target /

connected to target database: TECHDATABASKETDB_1 (DBID=3495312623)

RMAN> connect catalog user/password@string

connected to recovery catalog database

RMAN>  run {
 # Perform allocate channel
 allocate channel t1 type 'sbt_tape'
    parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_techdatabsket_db.opt)';
 allocate channel t2 type 'sbt_tape'
    parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_techdatabsket_db.opt)';
 allocate channel t3 type 'sbt_tape'
    parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_techdatabsket_db.opt)';
 allocate channel t4 type 'sbt_tape'
    parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_techdatabsket_db.opt)';
 
 #Check corruption
 SET MAXCORRUPT for datafile 118 to 4;

 # Perform archive log current
 sql 'alter system archive log current';
 sql 'alter system switch logfile';
 
 backup 
    incremental level 0 check logical database
    keep until time '(sysdate+30)' logs
    format 'TECHDATABASKETDB_1_ON_INC0_DIARIO_%U.DBF'
    tag 'BK_ON_INC0_DIA_20161011084106'
    filesperset 10
    include current controlfile;
 
 # Perform trace's do controlfile
 sql 'alter database backup controlfile to trace';
 }2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 

allocated channel: t1
channel t1: SID=4106 instance=TECHDATABASKETDB_1 device type=SBT_TAPE
channel t1: Data Protection for Oracle: version 6.3.0.0

Execução finalizada com sucesso…

piece handle=TECHDATABASKETDB_1_ON_INC0_DIARIO_ivri59dl_1_1.DBF tag=BK_ON_INC0_DIA_20161011084106 comment=API Version 2.0,MMS Version 6.3.0.0
channel t3: backup set complete, elapsed time: 00:16:35
channel t1: finished piece 1 at 12-OCT-16
piece handle=TECHDATABASKETDB_1_ON_INC0_DIARIO_iuri59d6_1_1.DBF tag=BK_ON_INC0_DIA_20161011084106 comment=API Version 2.0,MMS Version 6.3.0.0
channel t1: backup set complete, elapsed time: 00:18:20
channel t2: finished piece 1 at 12-OCT-16
piece handle=TECHDATABASKETDB_1_ON_INC0_DIARIO_j1ri5abk_1_1.DBF tag=BK_ON_INC0_DIA_20161011084106 comment=API Version 2.0,MMS Version 6.3.0.0
channel t2: backup set complete, elapsed time: 00:07:06
channel t4: finished piece 1 at 12-OCT-16
piece handle=TECHDATABASKETDB_1_ON_INC0_DIARIO_j0ri5a7q_1_1.DBF tag=BK_ON_INC0_DIA_20161011084106 comment=API Version 2.0,MMS Version 6.3.0.0
channel t4: backup set complete, elapsed time: 00:11:31
Finished backup at 12-OCT-16

sql statement: alter database backup controlfile to trace
released channel: t1
released channel: t2
released channel: t3
released channel: t4