|
Re: Expiring TDP for Oracle data
2002-08-08 15:01:59
Thanks Eric! That is exactly what I needed. My question now is whether
anyone has this process automated. Can I have the client or the server
automate the process to expire the backups?
Rob Schroeder
Famous Footwear
"Cowperthwaite,
Eric" To: ADSM-L AT VM.MARIST
DOT EDU
<eric.cowperthwai cc:
te AT EDS DOT COM> Subject: Re: Expiring
TDP for Oracle data
Sent by: "ADSM:
Dist Stor
Manager"
<[email protected]
.EDU>
07/31/2002 04:12
PM
Please respond to
"ADSM: Dist Stor
Manager"
Once the objects are deleted in RMAN, then you will need to run a TDPOSYNC
<tdposync syncdb -tdpo_optfile=[optfile name]> and that will sync the RMAN
catalog and TSM database and expire the files on your TSM Server
Eric W. Cowperthwaite
EDS
-----Original Message-----
From: Holger Speh [mailto:SPEH AT DE.IBM DOT COM]
Sent: Wednesday, July 31, 2002 1:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Expiring TDP for Oracle data
Theresa,
all Oracle backup objects are unique so there won't be any inactive
versions
which you can expire via TSM. You have to expire them "manually" with an
RMAN script doing a RMAN report obsolete first to find all no longer needed
Oracle backups and them doing a RMAN delete on these objects.
Mit freundlichen Grüssen / With kind regards,
Holger Speh
<http://www.ibm.com/>
IBM Global Services - Integrated Technology Services
Mobil: +49 (0)172 / 6365603
Fax: +49 (0)5341 / 892803
Notes: Holger Speh/Germany/IBM@IBMDE
email: speh AT de.ibm DOT com
Theresa Sarver <IFMC.tsarver AT SDPS DOT ORG>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
31.07.2002 18:39
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Expiring TDP for Oracle data
Hello;
I've been searching the archives on this subject all morning and I just
want
to double-check my findings.
Environment:
SP Model 9076 (1 Frame w/ 7 nodes)
AIX 4.3.3 ML8
P.S.S.P 3.2
ptfset 8
TSM 4.1.5
ORACLE 8.1.7/RMAN
TDP for Oracle v2.1.1 (I think?)
The DBA's have only been using TDP/RMAN for a few months now and around
July
10 they decided to start exprining some old backups. I noticed yesterday,
that the copy group had been setup improperly for TDP_Oracle:
STANDARD ACTIVE RMANCLASS STANDARD 1 1 0 1
STANDARD STANDARD RMANCLASS STANDARD 1 1 0 1
I modified the appropriate parameters last night (using TDP for Ocacle
Admin
Guide) and think it's right now:
STANDARD ACTIVE RMANCLASS STANDARD 1 0 0 0
STANDARD STANDARD RMANCLASS STANDARD 1 0 0 0
I ran 'expire inventory' shortly thereafter, this however did not remove
any
of the inactive databases:
/adsmorc : // cold_TESTR_1631_270302_22_1 (MC: DEFAULT)
Inactive, Inserted 03/27/02 16:32:19, Deactivated 07/10/02 15:18:10
ObjId: 0.58797993
So, from what I've read I have 3 options:
1) run some "delete object 0 xxxxxx" command (Could someone please
provide
me with any further information on this command?)
2) Create a new filespace, then delete the old one after several days
3) Using a TDPOSYNC command...depending on version. Anyone know if 2.1.1
supports the use of this command? - Can't find any reference in the TDP for
Oracle Manuel.
Thanks 'yet again' for your help;
Theresa
(See attached file: image001.gif)
image001.gif
Description: GIF image
|
|
|
