if it's RMAN,
>
> > TDPO, or us with the problem. Our DBA's run TDPOSYNC fairly often to
> fix things up.
> > Something is wrong and we just haven't had time to track it down.
> I
> > have a script that queries the TSM backups table for files (rman
> >
ble for files (rman
> backup
> pieces) that are older than our retension period. I run it once a
week.
>
> Rick
>
>
>
>
>
>
>
>
> "Gee, Norman"
> LC.CA
> .GOV> To
> Sent by: "ADSM:
;ADSM: ADSM-L < at > VM.MARIST.EDU
> Dist Stor cc
> Manager"
> VM.MARIST Subject
> .EDU> Re: TSM TDP Oracle - Expiration
> Opinions
>
> 03/20/2009 0
To
> Sent by: "ADSM: ADSM-L < at > VM.MARIST.EDU
> Dist Stor cc
> Manager"
> VM.MARIST Subject
> .EDU> Re: TSM TDP Oracle - Ex
n backup
> pieces) that are older than our retension period. I run it once a week.
>
> Rick
>
>
>
>
>
>
>
>
> "Gee, Norman"
> LC.CA
> .GOV> To
> Sent by: "ADSM: ADSM-L < at > VM.MARIST.EDU
> Dist Stor
t once a week.
Rick
"Gee, Norman"
To
Sent by: "ADSM: ADSM-L@VM.MARIST.EDU
Dist Stor cc
Manager"
You will have to let RMAN do its job. Every RMAN backup piece and sets
have unique file names and will never place a prior backup into an
inactive status.
How would you expire a RMAN backup since every backup piece is still
active? Short of mass delete on filespace.
-Original Message-
F
