ADSM-L

Re: TDP for Oracle Version Expiration

2002-10-29 14:54:05
Subject: Re: TDP for Oracle Version Expiration
From: Joshua Bassi <jbassi AT IHWY DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 29 Oct 2002 11:49:32 -0800
Is there anyway to automate the execution of this process?


--
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


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rob Schroeder
Sent: Tuesday, October 29, 2002 6:18 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for Oracle Version Expiration

The connect string is usually the name of the RMAN recovery catalog and
the
user id and password is the oracle user id that was given access to the
recovery catalog.  So this is ours.

Go to the agentoba directory (default c:\program
files\tivoli\tsm\agentoba)

tdposync syncdb

user ID: rman
password: rman
connect string: rcat

begin date: 01/01/2002
end date: 10/14/2002


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:  Re: TDP for
Oracle Version Expiration
                      Manager"
                      <[email protected]
                      .EDU>


                      10/28/2002 06:12
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






What is the correct syntax of this command?  What is the "Catalog 1
Connect String" supposed to be?


--
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


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rob Schroeder
Sent: Monday, October 28, 2002 3:56 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for Oracle Version Expiration

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>