Hendry's "Oracle and SQL Server DBA Stuff"

Oracle and SQL Server Database Solutions for DBA's please visit http://hendrydba.com for the latest posts. Thanks

Archive for the ‘RMAN10G’ Category

Restore Database Validate for READ ONLY in Oracle10g

Posted by Hendry chinnapparaj on August 22, 2011

Problem

The standard syntax works only for oracle11g, not for oracle10g with regard to Restore Validation of READONLY Tablespaces. It actually skips the readonly tablespaces (validates only read  write)

RESTORE DATABASE VALIDATE FORCE;

Solution

This will validate the read write and then readonly tablespaces.

Run

{

RESTORE DATABASE VALIDATE FORCE;

RESTORE DATABASE VALIDATE FORCE CHECK READONLY;

}

 

 

Posted in RMAN10G | Leave a Comment »

RMAN-06462: no backupsets found on device DISK that match specification

Posted by Hendry chinnapparaj on October 7, 2010

RMAN-06462: no backupsets found on device DISK that match specification

Problem:- This error can be caused due to many causes and one of the causes is in the syntax of the script as below

RMAN> connect target *
2> connect catalog *
3> BACKUP BACKUPSET ALL;
4> DELETE BACKUPSET DEVICE TYPE DISK COMPLETED BEFORE ‘SYSDATE-2’;
5> BACKUP INCREMENTAL LEVEL 1 NOT BACKED UP SINCE TIME ‘SYSDATE-1/2’ DEVICE TYPE DISK CUMULATIVE DATABASE FILESPERSET 8 FORMAT ‘/u03/oradata/flash_recovery_area/DEMO_KS/backupset/LF_%U’;
6> BACKUP FORMAT ‘LG_%U’ ARCHIVELOG ALL BACKUPSET ALL;
7> DELETE OBSOLETE;

Note:- In this case, the backup was failing due to the non-existence of the backup directory

Solution:- create the “backupset” directory under DEMO_KS, and all should be fine

Problem:- Another cause for Level 1 failing is that if you try to do a “Backup Backupset all”  without having any backupset in the backupset directory.

Solution:- Manually connect to RMAN, run the Level 1 backup as below

RMAN> BACKUP INCREMENTAL LEVEL 1 NOT BACKED UP SINCE TIME ‘SYSDATE-1/2’ DEVICE TYPE DISK CUMULATIVE DATABASE;

and then schedule the RMAN Script for future backups – it won’t fail as this will create the backupset in the disk.

 

Posted in RMAN10G | Leave a Comment »

Restore Tablespace

Posted by Hendry chinnapparaj on August 3, 2010

RESTORE TESTING FOR READ ONLY TABLESPACE
——————————————————————-

oracle@uatu009 backup>./oracle_main.ksh fixtest DDBOBK01
ORACLE_HOME = [/u01/oracle] ? /u01/oracle/product/10.2/db_1
RMAN> 2> 3> 4> 5> 6> 7>

Shutdown immediate

oracle@uatu009 fixtest>mv CB004_01.DBF CB004_01.DBF.ORI
oracle@uatu009 fixtest>mv CB004_02.DBF CB004_02.DBF.ORI

QL> conn / as sysdba
Connected to an idle instance.
SQL> startup
ORACLE instance started.

Total System Global Area  536870912 bytes
Fixed Size                  2085392 bytes
Variable Size             176164336 bytes
Database Buffers          352321536 bytes
Redo Buffers                6299648 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 29 – see DBWR trace file
ORA-01110: data file 29: ‘/u02/oradata/fixtest/CB004_02.DBF’

SQL> show parameter db_name

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_name                              string      fixtest

Recovery Manager: Release 10.2.0.4.0 – Production on Tue Aug 3 12:24:36 2010

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

connected to target database: fixtest (DBID=258344671, not open)
connected to recovery catalog database

RMAN> restore tablespace CB004;

Starting restore at 03-08-2010 12:26:17
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=539 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=538 devtype=DISK

channel ORA_SBT_TAPE_1: starting datafile backupset restore
channel ORA_SBT_TAPE_1: specifying datafile(s) to restore from backup set
restoring datafile 00029 to /u02/oradata/fixtest/CB004_02.DBF
channel ORA_SBT_TAPE_1: reading from backup piece 1clkdlo6_1_1
channel ORA_SBT_TAPE_1: restored backup piece 1
piece handle=1clkdlo6_1_1 tag=TAG20100803T111327
channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:00:08
channel ORA_SBT_TAPE_1: starting datafile backupset restore
channel ORA_SBT_TAPE_1: specifying datafile(s) to restore from backup set
restoring datafile 00030 to /u02/oradata/fixtest/CB004_01.DBF
channel ORA_SBT_TAPE_1: reading from backup piece 1glkdlrc_1_1
channel ORA_SBT_TAPE_1: restored backup piece 1
piece handle=1glkdlrc_1_1 tag=TAG20100803T111327
channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:00:08
Finished restore at 03-08-2010 12:26:49

-rw-r—–    1 oracle   dba         8396800 Aug  3 12:26 CB004_02.DBF
-rw-r—–    1 oracle   dba         8396800 Aug  3 12:26 CB004_01.DBF

SQL> show parameter db_name

NAME                                 TYPE        VALUE
———————————— ———– ——————————
db_name                              string      fixtest
SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01113: file 29 needs media recovery
ORA-01110: data file 29: ‘/u02/oradata/fixtest/CB004_02.DBF’

SQL> recover database;
Media recovery complete.
SQL> alter database open;

Database altered.

SQL> select name,open_mode from v$database;

NAME      OPEN_MODE
——— ———-
fixtest   READ WRITE

RESTORE TESTING FOR READ WRITE TABLESPACE

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

oracle@uatu009 fixtest>pwd
/u02/oradata/fixtest
oracle@uatu009 fixtest>ls -lrt users01.dbf
-rw-r—–    1 oracle   dba         5251072 Aug  3 12:32 users01.dbf

oracle@uatu009 fixtest>mv users01.dbf users01.dbf.ori

SQL> startup
ORACLE instance started.

Total System Global Area  536870912 bytes
Fixed Size                  2085392 bytes
Variable Size             176164336 bytes
Database Buffers          352321536 bytes
Redo Buffers                6299648 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 4 – see DBWR trace file
ORA-01110: data file 4: ‘/u02/oradata/fixtest/users01.dbf’

Recovery Manager: Release 10.2.0.4.0 – Production on Tue Aug 3 12:37:16 2010

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

connected to target database: fixtest (DBID=258344671, not open)
connected to recovery catalog database

RMAN> restore tablespace users;

Starting restore at 03-08-2010 12:37:32
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=539 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.5.1.0
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=538 devtype=DISK

channel ORA_SBT_TAPE_1: starting datafile backupset restore
channel ORA_SBT_TAPE_1: specifying datafile(s) to restore from backup set
restoring datafile 00004 to /u02/oradata/fixtest/users01.dbf
channel ORA_SBT_TAPE_1: reading from backup piece 0tlkdlbh_1_1
channel ORA_SBT_TAPE_1: restored backup piece 1
piece handle=0tlkdlbh_1_1 tag=TAG20100803T111327
channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:00:07
Finished restore at 03-08-2010 12:37:51

RMAN> recover tablespace users;

Starting recover at 03-08-2010 12:38:29
using channel ORA_SBT_TAPE_1
using channel ORA_DISK_1

starting media recovery
media recovery complete, elapsed time: 00:00:01

Finished recover at 03-08-2010 12:38:32

SQL> alter database open;

Database altered.

Posted in RMAN10G | Leave a Comment »

create RMAN catalog in catalog database and register target database

Posted by Hendry chinnapparaj on July 23, 2010

Create rman user in recovery catalog database

Here it is oracle10g – 10.2.0.4

CREATE USER RMAN112D

IDENTIFIED BY VALUES ‘***’

DEFAULT TABLESPACE RMAN112D

TEMPORARY TABLESPACE TEMP

PROFILE DEFAULT

ACCOUNT UNLOCK;

GRANT RECOVERY_CATALOG_OWNER TO RMAN112D;

GRANT RESOURCE TO RMAN112D;

ALTER USER RMAN112D DEFAULT ROLE ALL;

GRANT CREATE SESSION TO RMAN112D;

GRANT SELECT ANY DICTIONARY TO RMAN112D;

GRANT UNLIMITED TABLESPACE TO RMAN112D;

rcatd:/u01/oracle > rman target / catalog rman112d/****@rcatd

Recovery Manager: Release 10.2.0.4.0 – Production on Fri Jul 23 10:30:31 2010

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

connected to target database: RCATD (DBID=8342000)

connected to recovery catalog database

RMAN> create catalog;

recovery catalog created

Register the 11gr2 target database ot the catalog created above

————————————————————————

apex4:/u01/oracle/product/11.2/network/admin> echo $ORACLE_SID

apex4

apex4:/u01/oracle/product/11.2/network/admin> rman target / catalog rman112d/****@rcatd

Recovery Manager: Release 11.2.0.1.0 – Production on Fri Jul 23 10:37:50 2010

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

connected to target database: APEX4 (DBID=89650738)

connected to recovery catalog database

RMAN> register database;

database registered in recovery catalog

starting full resync of recovery catalog

full resync complete

RMAN> show all;

RMAN configuration parameters for database with db_unique_name APEX4 are:

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS;

CONFIGURE BACKUP OPTIMIZATION ON;

CONFIGURE DEFAULT DEVICE TYPE TO ‘SBT_TAPE’;

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE ‘SBT_TAPE’ TO ‘CF_%F’;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘CF_%F’;

CONFIGURE DEVICE TYPE ‘SBT_TAPE’ PARALLELISM 1 BACKUP TYPE TO BACKUPSET;

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE ‘SBT_TAPE’ TO 1;

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE ‘SBT_TAPE’ TO 1;

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;

CONFIGURE CHANNEL 1 DEVICE TYPE ‘SBT_TAPE’ PARMS  “ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)”;

CONFIGURE MAXSETSIZE TO UNLIMITED;

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM ‘AES128’; # default

CONFIGURE COMPRESSION ALGORITHM ‘BASIC’ AS OF RELEASE ‘DEFAULT’ OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘/u01/oracle/product/11.2/dbs/snapcf_apex4.f’; # default

RMAN>

Posted in RMAN10G | Leave a Comment »

ORA-19643: datafile 323: incremental-start SCN is too recent

Posted by Hendry chinnapparaj on June 4, 2010

Problem

———-

The incremental backup throws up ORA-19643 complaining on the datafile checkpoint SCN as older.

RMAN> BACKUP INCREMENTAL LEVEL 1 NOT BACKED UP SINCE TIME ‘SYSDATE-1/2’ DEVICE TYPE DISK CUMULATIVE DATABASE

FILESPERSET 8 FORMAT ‘/u03/oradata/flash_recovery_area/CPSOA1_JS/backupset/LF_%U’;

Starting backup at 03-06-2010 18:22:56

allocated channel: ORA_DISK_1

channel ORA_DISK_1: sid=702 devtype=DISK

channel ORA_DISK_1: starting compressed incremental level 1 datafile backupset

channel ORA_DISK_1: specifying datafile(s) in backupset

input datafile fno=00023 name=/u02/oradata/cpsoa1/BWA_LM_DATA_64M_02.DBF

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/03/2010 18:23:42

ORA-19643: datafile 323: incremental-start SCN is too recent

ORA-19640: datafile checkpoint is SCN 18624685831 time 04/07/2009 15:15:04

Solution

————

Do the backup based on the SCN time in the error above, which takes care of the other datafiles as well.

RMAN> BACKUP INCREMENTAL FROM SCN 18624685831 DEVICE TYPE DISK CUMULATIVE DATABASE FILESPERSET 8 FORMAT ‘/u03/oradata/flash_recovery_area/CPSOA1_JS/backupset/LF_%U’;

Starting backup at 03-06-2010 18:59:28

using channel ORA_DISK_1

RMAN-06755: WARNING: datafile 269: incremental-start SCN is too recent; using checkpoint SCN 18624685314 instead

RMAN-06755: WARNING: datafile 270: incremental-start SCN is too recent; using checkpoint SCN 18624685323 instead

RMAN-06755: WARNING: datafile 271: incremental-start SCN is too recent; using checkpoint SCN 18624685332 instead

RMAN-06755: WARNING: datafile 272: incremental-start SCN is too recent; using checkpoint SCN 18624685341 instead

RMAN-06755: WARNING: datafile 273: incremental-start SCN is too recent; using checkpoint SCN 18624685351 instead

RMAN-06755: WARNING: datafile 274: incremental-start SCN is too recent; using checkpoint SCN 18624685360 instead

RMAN-06755: WARNING: datafile 275: incremental-start SCN is too recent; using checkpoint SCN 18624685370 instead

RMAN-06755: WARNING: datafile 276: incremental-start SCN is too recent; using checkpoint SCN 18624685379 instead

RMAN-06755: WARNING: datafile 277: incremental-start SCN is too recent; using checkpoint SCN 18624685389 instead

RMAN-06755: WARNING: datafile 278: incremental-start SCN is too recent; using checkpoint SCN 18624685399 instead

RMAN-06755: WARNING: datafile 279: incremental-start SCN is too recent; using checkpoint SCN 18624685408 instead

RMAN-06755: WARNING: datafile 280: incremental-start SCN is too recent; using checkpoint SCN 18624685417 instead

RMAN-06755: WARNING: datafile 281: incremental-start SCN is too recent; using checkpoint SCN 18624685426 instead

RMAN-06755: WARNING: datafile 282: incremental-start SCN is too recent; using checkpoint SCN 18624685436 instead

RMAN-06755: WARNING: datafile 283: incremental-start SCN is too recent; using checkpoint SCN 18624685446 instead

RMAN-06755: WARNING: datafile 284: incremental-start SCN is too recent; using checkpoint SCN 18624685456 instead

RMAN-06755: WARNING: datafile 285: incremental-start SCN is too recent; using checkpoint SCN 18624685465 instead

RMAN-06755: WARNING: datafile 286: incremental-start SCN is too recent; using checkpoint SCN 18624685475 instead

RMAN-06755: WARNING: datafile 287: incremental-start SCN is too recent; using checkpoint SCN 18624685484 instead

RMAN-06755: WARNING: datafile 288: incremental-start SCN is too recent; using checkpoint SCN 18624685494 instead

RMAN-06755: WARNING: datafile 289: incremental-start SCN is too recent; using checkpoint SCN 18624685504 instead

RMAN-06755: WARNING: datafile 290: incremental-start SCN is too recent; using checkpoint SCN 18624685514 instead

RMAN-06755: WARNING: datafile 291: incremental-start SCN is too recent; using checkpoint SCN 18624685523 instead

RMAN-06755: WARNING: datafile 292: incremental-start SCN is too recent; using checkpoint SCN 18624685532 instead

RMAN-06755: WARNING: datafile 293: incremental-start SCN is too recent; using checkpoint SCN 18624685542 instead

RMAN-06755: WARNING: datafile 294: incremental-start SCN is too recent; using checkpoint SCN 18624685552 instead

RMAN-06755: WARNING: datafile 295: incremental-start SCN is too recent; using checkpoint SCN 18624685561 instead

RMAN-06755: WARNING: datafile 296: incremental-start SCN is too recent; using checkpoint SCN 18624685571 instead

RMAN-06755: WARNING: datafile 297: incremental-start SCN is too recent; using checkpoint SCN 18624685580 instead

RMAN-06755: WARNING: datafile 298: incremental-start SCN is too recent; using checkpoint SCN 18624685590 instead

RMAN-06755: WARNING: datafile 299: incremental-start SCN is too recent; using checkpoint SCN 18624685599 instead

RMAN-06755: WARNING: datafile 300: incremental-start SCN is too recent; using checkpoint SCN 18624685608 instead

RMAN-06755: WARNING: datafile 301: incremental-start SCN is too recent; using checkpoint SCN 18624685617 instead

RMAN-06755: WARNING: datafile 302: incremental-start SCN is too recent; using checkpoint SCN 18624685627 instead

RMAN-06755: WARNING: datafile 303: incremental-start SCN is too recent; using checkpoint SCN 18624685637 instead

RMAN-06755: WARNING: datafile 304: incremental-start SCN is too recent; using checkpoint SCN 18624685647 instead

RMAN-06755: WARNING: datafile 305: incremental-start SCN is too recent; using checkpoint SCN 18624685656 instead

RMAN-06755: WARNING: datafile 306: incremental-start SCN is too recent; using checkpoint SCN 18624685666 instead

RMAN-06755: WARNING: datafile 307: incremental-start SCN is too recent; using checkpoint SCN 18624685677 instead

RMAN-06755: WARNING: datafile 308: incremental-start SCN is too recent; using checkpoint SCN 18624685687 instead

RMAN-06755: WARNING: datafile 309: incremental-start SCN is too recent; using checkpoint SCN 18624685696 instead

RMAN-06755: WARNING: datafile 310: incremental-start SCN is too recent; using checkpoint SCN 18624685706 instead

RMAN-06755: WARNING: datafile 311: incremental-start SCN is too recent; using checkpoint SCN 18624685715 instead

RMAN-06755: WARNING: datafile 312: incremental-start SCN is too recent; using checkpoint SCN 18624685725 instead

RMAN-06755: WARNING: datafile 313: incremental-start SCN is too recent; using checkpoint SCN 18624685735 instead

RMAN-06755: WARNING: datafile 314: incremental-start SCN is too recent; using checkpoint SCN 18624685744 instead

RMAN-06755: WARNING: datafile 315: incremental-start SCN is too recent; using checkpoint SCN 18624685753 instead

RMAN-06755: WARNING: datafile 316: incremental-start SCN is too recent; using checkpoint SCN 18624685763 instead

RMAN-06755: WARNING: datafile 317: incremental-start SCN is too recent; using checkpoint SCN 18624685773 instead

RMAN-06755: WARNING: datafile 318: incremental-start SCN is too recent; using checkpoint SCN 18624685783 instead

RMAN-06755: WARNING: datafile 319: incremental-start SCN is too recent; using checkpoint SCN 18624685793 instead

RMAN-06755: WARNING: datafile 320: incremental-start SCN is too recent; using checkpoint SCN 18624685803 instead

RMAN-06755: WARNING: datafile 321: incremental-start SCN is too recent; using checkpoint SCN 18624685813 instead

RMAN-06755: WARNING: datafile 322: incremental-start SCN is too recent; using checkpoint SCN 18624685822 instead

channel ORA_DISK_1: starting compressed full datafile backupset

channel ORA_DISK_1: specifying datafile(s) in backupset

input datafile fno=00023 name=/u02/oradata/cpsoa1/BWA_LM_DATA_64M_02.DBF

input datafile fno=00323 name=/u04/oradata/cpsoa1/CB055_01.DBF

skipping datafile 00323 because it has not changed

input datafile fno=00346 name=/u04/oradata/cpsoa1/CB078_01.DBF

input datafile fno=00222 name=/u02/oradata/cpsoa1/CSHTRAP.DBF

input datafile fno=00120 name=/u02/oradata/cpsoa1/CPS_LM_DATA_64M_01.DBF

channel ORA_DISK_1: starting piece 1 at 03-06-2010 18:59:37

Posted in RMAN10G | Leave a Comment »

RMAN Delete failures due to Mismatched status RMAN-06207,RMAN-06214

Posted by Hendry chinnapparaj on May 31, 2010

Problem

————

The Delete obsolete command could not delete some files due to mismatched status.

RMAN> delete obsolete;

RMAN retention policy will be applied to the command

RMAN retention policy is set to recovery window of 30 days

allocated channel: ORA_SBT_TAPE_1

channel ORA_SBT_TAPE_1: sid=760 devtype=SBT_TAPE

channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0

using channel ORA_DISK_1

Deleting the following obsolete backups and copies:

Type                 Key    Completion Time    Filename/Handle

——————– —— —————— ——————–

Backup Set           16778666 30-04-2010 10:21:19

Backup Piece       16778668 30-04-2010 10:21:19 CF_c-183511008-20100430-04

Backup Set           16779716 30-04-2010 12:27:07

Do you really want to delete the above objects (enter YES or NO)? yes

RMAN-06207: WARNING: 13 objects could not be deleted for DISK channel(s) due

RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status

RMAN-06210: List of Mismatched objects

RMAN-06211: ==========================

RMAN-06212:   Object Type   Filename/Handle

RMAN-06213: ————— —————————————————

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-00

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-01

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-02

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091208-01

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091218-00

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091218-01

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091218-02

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091218-03

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-00

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-01

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-02

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-03

RMAN-06214: Backup Piece    /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-04

Solution

———–

Do a crosscheck of the backuppiece which has the issue a

RMAN> crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-00’;

using channel ORA_SBT_TAPE_1

using channel ORA_DISK_1

crosschecked backup piece: found to be ‘EXPIRED’

backup piece handle=/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-00 recid=18616 stamp=704280485

Crosschecked 1 objects

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-01’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-02’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091208-01’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091218-00’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091218-01’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091218-02’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091218-03’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-00’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-01’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-02’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-03’;

crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100112-04’;

crosscheck backuppiece ”;

crosscheck backuppiece ”;

After crosscheck, run the delete obsolete again

RMAN> delete obsolete;

RMAN retention policy will be applied to the command

RMAN retention policy is set to recovery window of 30 days

using channel ORA_SBT_TAPE_1

using channel ORA_DISK_1

Deleting the following obsolete backups and copies:

Type                 Key    Completion Time    Filename/Handle

——————– —— —————— ——————–

Backup Set           16795362 01-05-2010 10:21:30

Backup Piece       16795364 01-05-2010 10:21:30 CF_c-183511008-20100501-05

Backup Set           17277715 30-11-2009 09:28:06

Backup Piece       17277743 30-11-2009 09:28:06 /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-00

Backup Set           17277716 30-11-2009 09:29:02

backup piece handle=/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-00 recid=18616 stamp=704280485

deleted backup piece

backup piece handle=/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-01 recid=18617 stamp=704280541

deleted backup piece

backup piece handle=/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20091130-02 recid=18618 stamp=704280591

deleted backup

RMAN> delete obsolete;

RMAN retention policy will be applied to the command

RMAN retention policy is set to recovery window of 30 days

using channel ORA_SBT_TAPE_1

using channel ORA_DISK_1

no obsolete backups found

other commands to delete are

————————————–

RMAN> crosscheck backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100511-49’;

allocated channel: ORA_SBT_TAPE_1

channel ORA_SBT_TAPE_1: sid=689 devtype=SBT_TAPE

channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0

using channel ORA_DISK_1

crosschecked backup piece: found to be ‘AVAILABLE’

backup piece handle=/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100511-49 recid=25248 stamp=718721036

Crosschecked 1 objects

RMAN> delete force backuppiece ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100511-49’;

using channel ORA_SBT_TAPE_1

using channel ORA_DISK_1

List of Backup Pieces

BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name

——- ——- — — ———– ———– ———-

16971260 16971238 1   1   AVAILABLE   DISK        /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100511-49

Do you really want to delete the above objects (enter YES or NO)? yes

deleted backup piece

backup piece handle=/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100511-49 recid=25248 stamp=718721036

Deleted 1 objects

RMAN> delete noprompt backuppiece       ‘/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100511-08’;

using channel ORA_SBT_TAPE_1
using channel ORA_DISK_1

List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
——- ——- — — ———– ———– ———-
16970426 16970385 1   1   AVAILABLE   DISK        /u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100511-08
deleted backup piece
backup piece handle=/u01/oracle/product/10.2/db_1/dbs/CF_c-183511008-20100511-08 recid=25182 stamp=718719698
Deleted 1 objects

Posted in RMAN10G | Leave a Comment »