ADSM-L

Re: TDP for Oracle Version Expiration

2002-10-28 18:58:32
Subject: Re: TDP for Oracle Version Expiration
From: Rob Schroeder <robs AT FAMOUSFOOTWEAR DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 28 Oct 2002 17:55:35 -0600
Even easier is to use TDPOSYNC SYNCDB, and it lets you put a date range in.
Then you can select by reviewing the date of each backup you want to
keep/delete.  Much safer than typing the correct number in.  If you use a
crosscheck command daily, then old backups shoudln't hang around.

Rob Schroeder
Famous Footwear
608-827-3495 phone
608-662-6495 fax



                      Joshua Bassi
                      <jbassi AT IHWY DOT COM>        To:       ADSM-L AT 
VM.MARIST DOT EDU
                      Sent by: "ADSM:          cc:
                      Dist Stor                Subject:  TDP for Oracle Version 
Expiration
                      Manager"
                      <[email protected]
                      .EDU>


                      10/28/2002 05:49
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






All,

Here is the script directly out of the TDP for Oracle manual:

To remove an old backup, issue this command from the RMAN
prompt:
run
{
allocate channel for delete type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=c:\RMAN\scripts\tdpo.opt)';
change backupset primary_key delete;
}
Note: To enter a number value for the primary key variable, look up
the value in the RMAN catalog.


My question is: what exactly is the "primary key" variable?

--
Joshua S. Bassi
IBM Certified - AIX 4/5L, SAN, Shark
Tivoli Certified Consultant - ADSM/TSM
eServer Systems Expert -pSeries HACMP
AIX, HACMP, Storage, TSM Consultant
Cell (831) 595-3962
jbassi AT ihwy DOT com

<Prev in Thread] Current Thread [Next in Thread>