TDP not expiring objects - using delete object command to cleanup

droach

ADSM.ORG Senior Member
Joined
Jan 7, 2008
Messages
239
Reaction score
13
Points
0
Location
Cut and Shoot, Texas
I seem to have huge problem with TDP backup objects (SQL and Oracle) not getting expired or marked 'INACTIVE_VERSION'. My DBA's claim they are running their crosscheck scripts, but yesterday I manually deleted over 39,000 objects that were showing 'ACTIVE_VERSION' but way past our retention time.

Not sure why this is happening, but my question is what is the difference between these two commands:

tsm: SERVER178_SERVER1>delete object 84072789
Object 84072789 and 0 dependent object(s) deleted.

tsm: SERVER178_SERVER1>delete object 0 101071026
ANR2023E DELETE OBJECT: Extraneous parameter - 101071026.
ANS8001I Return code 3.


My TSM servers running v5.5 and v6.2 will accept the command with or without the leading '0', but my v6.3 server throws the error seen in the #2 command above and will only accept the command without the leading '0'.

Anyone know if the leading '0' is actually needed or what it is for?
 
Delete object is very dangerous command!!! Do those nodes have backup or archive delete rights?
 
Back
Top