Re: expiration Oracle backups
2005-10-13 11:08:02
Neil,
Here is the output of 'list backups' and 'crosscheck backup of databases' for
the ERK oracle instance:
# rman target rman/rman nocatalog
Recovery Manager: Release 8.1.7.4.0 - Production
RMAN-06005: connected to target database: ERK (DBID=39192858)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN> list backup;
RMAN-03022: compiling command: list
RMAN> allocate channel for delete type 'sbt_tape'
2> parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo_erk.opt)';
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: delete
RMAN-08500: channel delete: sid=12 devtype=SBT_TAPE
RMAN-08526: channel delete: Tivoli Data Protection for Oracle: version 5.2.0.0
RMAN> crosscheck backup of database;
RMAN-03022: compiling command: XCHECK
RMAN-03023: executing command: XCHECK
RMAN>
No backups are found any more. The TSM node name for the Oracle backup is
server_ORA_ERK. Here is the output of two queries in TSM:
q node server_ORA_ERK f=d;
Node Name: server_ORA_ERK
Platform: TDP Oracle SUN
Client OS Level: 5.8
Client Version: Version 5, Release 3, Level 0.11
Policy Domain Name: POL_client
Last Access Date/Time: 10/13/2005 15:04:17
Days Since Last Access: <1
Password Set Date/Time: 10/12/2005 14:34:14
Days Since Password Set: 1
Invalid Sign-on Count: 0
Locked?: No
Contact:
Compression: Client
Archive Delete Allowed?: Yes
Backup Delete Allowed?: Yes
Registration Date/Time: 10/12/2005 11:42:20
Registering Administrator: ADMIN
Last Communication Method Used: Tcp/Ip
Bytes Received Last Session: 2,073
Bytes Sent Last Session: 2,170
Duration of Last Session: 4.00
Pct. Idle Wait Last Session: 0.00
select state, ll_name, backup_date from backups where
node_name='server_ORA_ERK';
STATE LL_NAME BACKUP_DATE
------------------ ------------------ ------------------
ACTIVE_VERSION df_571506337_1_1 2005-10-12
15:44:32.000000
ACTIVE_VERSION df_571506339_2_1 2005-10-12
15:44:32.000000
...
The node is allowed to delete it's own backups and all of the backups are still
active. No errors are found in the tdpoerror.log file.
During the deletion of the backups in RMAN, new sessions are opened and closed
in the activity log for the node but no other messages are logged.
Any other ideas about what might be the issue? If required, I'll log a PMR of
course.
thanks,
Kurt
________________________________
From: ADSM: Dist Stor Manager on behalf of Neil Rasmussen
Sent: Thu 13/10/2005 16:38
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] expiration Oracle backups
Kurt,
When deleting Rman objects on the TSM Server, TDP Oracle uses the delete
function on objects....the objects do not move to inactive they are just
simply deleted from the TSM Server. So if you are certain that Rman is
deleting the objects from the controlfile, then my guess is that your TSM
Node is not configured with "backdel=yes". One simple way to know what is
going on during the deletion is to look in the tdpoerror.log this should
tell you if the objects are being deleted or if there is an error
occurring during the delete. Unfortunately, Oracle ignores errors that
come from the delete functions so any error that TDP Oracle gives during
deletion is lost, the only way to know for sure is the "tdpoerror.log"
Regards,
Neil Rasmussen
Software Development
Data Protection for Oracle
rasmussn AT us.ibm DOT com
Kurt Beyers <Kurt.Beyers AT DOLMEN DOT BE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/13/2005 06:19 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
expiration Oracle backups
Hello,
My environment is the following:
TSM 5.3.2 server on Windows2003
Sun Solaris 5.8 with Oracle 8.1.7.4 with a TSM BA client 5.3.x and the TDP
for databases 5.3
The backup of the Oracle databases is already working. The metadata of the
backups is written in the control files of the Oracle database.
The backups are bound to a mgmt class with the correct settings (as every
object receives a unique name in TSM).
The expiration must first be done in Oracle with a script, eg expire the
backups older than X days. Could anybody share a working script? I'm still
struggling to get it working as it should.
But how are the backups made inactive in the TSM database after they have
been deleted in Oracle? The 'tdposync' tool only works when the metadata
is stored in a recovery catalog database. And after a forced deletion of
the backups in RMAN, they do not become inactive in TSM either. How can
the metadata in the TSM database be synchronized with the metadata in
Oracle (control file) .
I know this must have been discussed in the past already, but a search of
the old threads didn't clear it out yet.
thanks a lot,
Kurt
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: expiration Oracle backups,
Kurt Beyers <=
|
|
|