oracle rman backup expired but still active version on tsm

[shadab]

dear all,
i am facing this problem with my 10 nodes. my all tapes used for oracle backup is 100% utilised.
as per rman retention policy it should be 7 days. configuration on tsm side mgmt class is ok.
vere=1, verd=0 rete=0 reto=0. the node has the rights backdel=yes.

i checked rman backup logs the old backup status=expire, but the same piece of backup shows version=active

== RMAN BACKUP LOG==

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
3579576 Full 943.00M SBT_TAPE 00:01:31 24-FEB-15
BP Key: 3579582 Status: EXPIRED Compressed: NO Tag: DLYDB_BLOCK_24FEB20150201
Handle: rman_dly_dbf_BLOCK_20150224_S5421_P1_T872474673.bckp Media:
List of Datafiles in backup set 3579576
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- --------- ----
1 Full 130419188 24-FEB-15 /vol01/oracle/app/product/oradata/bpel/system01.dbf
2 Full 130419188 24-FEB-15 /vol01/oracle/app/product/oradata/bpel/undotbs01.dbf
4 Full 130419188 24-FEB-15 /vol01/oracle/app/product/oradata/bpel/users01.dbf
5 Full 130419188 24-FEB-15 /vol01/oracle/app/product/oradata/bpel/example01.dbf


RMAN>
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: sid=78 devtype=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
using channel ORA_DISK_1
no obsolete backups found



==TSM BACKUP LOG ==

NODE_NAME: BLOCK_DLY_ORA
FILESPACE_NAME: /BLOCK
FILESPACE_ID: 1
STATE: ACTIVE_VERSION
TYPE: FILE
HL_NAME: //
LL_NAME: rman_dly_dbf_BLOCK_20150224_S5421_P1_T872474673.bckp
OBJECT_ID: 708507444
BACKUP_DATE: 2015-02-24 01:33:09.000000
DEACTIVATE_DATE:
OWNER:
CLASS_NAME: DEFAULT


Any help and comments should be highly appreciable. all oracle nodes having same issue.

 

[Harry_Redl]

Hi,

you can use "tdposync" utility for synchronizing the RMAN and TSM catalogs - use with caution.

Harry

 

[shadab]

hi harry, thanks for your reply.
this is the first time i will suppose to use this utility. please can you tell me the major pros cons, and how safely i can use this utility.
Second thing, my backups says status=Expired , i didnt saw any piece of backup say obsolete. so is it ok if i ran my rman policy with statement "delete expired" (pls find below the altered piece of my rman script), hope it will not harm my existing backup of the node.

change archivelog all crosscheck;
DELETE NOPROMPT ARCHIVELOG UNTIL TIME "SYSDATE-2";

resync catalog;
report need backup;
show all;
delete noprompt obsolete;
delete expired ----- (i added this line now)
list backup summary;
EOF

please help in this , so i can do the same with all my nodes. thanks in advance

 

[Harry_Redl]

Hi,
in this case you may even not need this utility

Be aware that when the RMAN catalog contains backups marked as expired, RMAN still considers these objects as existing. If tdposync is invoked against these objects, it will recognize these objects in the RMAN catalog and on the Tivoli Storage Manager server and consider them to be in sync. Therefore, it is necssary to delete these objects from the RMAN catalog in order for them to be deleted from the Tivoli Storage Manager server. Use the Oracle crosscheck command to verify whether the backups exist. Then, use the Oracle delete expired command to remove their record from the RMAN catalog.

So first try to cleanup the RMAN catalog - things may solve themselves.

Harry