facebook twitter youtube facebook facebook facebook

E-Mail : info@askmlabs.com

Phone : +1.215.353.8306

Latest Post

Deleting RMAN "NO EXPIRE" BACKUPS FROM TAPE

Written By askMLabs on Thursday, November 3, 2011 | 4:49 PM

The following steps are useful to delete the backups which are marked as NO-EXPIRE. No expire backup are the backups for which the retention policy will not apply and the backups remain till you manually and forcibly delete these backups.  The best example for No-expire backups are the backups kept for training purposes. After successfully creating any training environment, we will backup the database with NO-Expire option and these backups will be used to refresh the database every week.

The following commands show you how to delete these no-expire backups on tape from  RMAN CATALOG. This is useful in cases where if you made any changes to the databases and need to preseve these changes in the database forever, you will take new NO-EXPIRE backups and delete the old backups.

RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
145913  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
145914  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
145915  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
145916  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
145917  B  0  A SBT_TAPE    25-APR-11       1       1       YES        NOEXPIRE
147274  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147275  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147276  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147277  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147278  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147498  B  F  A SBT_TAPE    29-APR-11       1       1       NO         NOEXPIRE

RMAN> DELETE BACKUPSET 145913,145914,145915,145916,145917;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=522 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 05/01/2011 01:20:25
RMAN-06160: no backup pieces found for backup set key: 145913

RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
released channel: ORA_DISK_1
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=522 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: Data Protection for Oracle: version 5.5.2.0
RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
allocated channel: ORA_MAINT_SBT_TAPE_2
channel ORA_MAINT_SBT_TAPE_2: sid=525 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_2: Data Protection for Oracle: version 5.5.2.0
RMAN> DELETE BACKUPSET 145913,145914,145915,145916,145917;
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
145919  145913  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set9_piece1_copy1_20110425_09mal5t9_1_1
145920  145914  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set8_piece1_copy1_20110425_08mal5t9_1_1
145921  145915  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set11_piece1_copy1_20110425_0bmal6d9_1_1
145922  145916  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set7_piece1_copy1_20110425_07mal5t9_1_1
145923  145917  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set10_piece1_copy1_20110425_0amal6br_1_1
Do you really want to delete the above objects (enter YES or NO)? NO
RMAN> delete noprompt BACKUPSET 145913,145914,145915,145916,145917;
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
145919  145913  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set9_piece1_copy1_20110425_09mal5t9_1_1
145920  145914  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set8_piece1_copy1_20110425_08mal5t9_1_1
145921  145915  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set11_piece1_copy1_20110425_0bmal6d9_1_1
145922  145916  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set7_piece1_copy1_20110425_07mal5t9_1_1
145923  145917  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set10_piece1_copy1_20110425_0amal6br_1_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_MAINT_SBT_TAPE_1 channel at 05/01/2011 01:27:05
ORA-27191: sbtinfo2 returned error
Additional information: 2

RMAN> delete noprompt force BACKUPSET 145913,145914,145915,145916,145917;
List of Backup Pieces
BP Key  BS Key  Pc# Cp# Status      Device Type Piece Name
------- ------- --- --- ----------- ----------- ----------
145919  145913  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set9_piece1_copy1_20110425_09mal5t9_1_1
145920  145914  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set8_piece1_copy1_20110425_08mal5t9_1_1
145921  145915  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set11_piece1_copy1_20110425_0bmal6d9_1_1
145922  145916  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set7_piece1_copy1_20110425_07mal5t9_1_1
145923  145917  1   1   AVAILABLE   SBT_TAPE    backup_CRTRNG_3679252776_set10_piece1_copy1_20110425_0amal6br_1_1
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set9_piece1_copy1_20110425_09mal5t9_1_1 recid=7 stamp=749377449
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set8_piece1_copy1_20110425_08mal5t9_1_1 recid=8 stamp=749377449
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set11_piece1_copy1_20110425_0bmal6d9_1_1 recid=9 stamp=749377962
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set7_piece1_copy1_20110425_07mal5t9_1_1 recid=10 stamp=749377449
deleted backup piece
backup piece handle=backup_CRTRNG_3679252776_set10_piece1_copy1_20110425_0amal6br_1_1 recid=11 stamp=749377916
Deleted 5 objects
RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
147274  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147275  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147276  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147277  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147278  B  0  A SBT_TAPE    29-APR-11       1       1       YES        NOEXPIRE
147498  B  F  A SBT_TAPE    29-APR-11       1       1       NO         NOEXPIRE
RMAN>


Hope it helps

SRI

OEM Grid Control 10.2.0.1 Installation On Linux 5.4

In this article, we will discuss how to install OEM grid control 10.2.0.1 on Linux 5.4(32 bit).

Download the required software from the location : Download Software
Download the installation Document from the location : Download Installation Document

If you are planning to install OEM grid control in a vmware linux machine, Please follow the article VMware Server - Linux installation  and complete the linux machine creation. You can omit this point if you are directly provided with linux machine with OS linux 5.4.

Prepare the linux machine ( Linux 5.4 ) for the OEM grid control 10201 installation. Please use the article  Prepare Linux virtual machine for OEM Grid Control Installation. Though this is to prepare the linux machine for 11gR2 database, it holds good for OEM 10201 installation also. You can also refer the document mentioned above to prepare the linux machine for OEM grid control installation.

There are some identified Common Installation Errors while installing OEM 10201 on Linux 5.4. Please follow the article OEM Gridcontrol 10201 Installation Errors On Linux 5.4 to correct all the issues.

Follow the video to complete the installation of OEM grid control 10.2.0.1 on Linux 5.4.

Video will be uploaded very soon. <video place holder>

Hope It Helps
SRI
 
Support :
Copyright © 2013. askMLabs - All Rights Reserved
Proudly powered by Blogger