The db2adutl command was issued against nodes that had been defined with archdelete and backupdelete as NO. As a result of the NO setting, we are getting the following message:
----
The current delete transaction failed. You do not have
sufficient authorization. Attempting to deactivate
backup image(s) instead...
Success.
----
Past ADSM Forum questions state that the archdelete and backupdelete should be YES!
I have now changed the archdelete and backupdelete to Yes for the affected TSM Nodes. My questions are:
1) does Inventory Expiration remove the 'deactivated files' or, do those objects become Orphaned within the TSM Database when the delete command was issued?
2) for those objects that the db2adutl can no longer see, what was the suggested fix to remove those objects from the APIB2 filespaces?
TSM V5.4
AIX V5.3
Bob
----
The current delete transaction failed. You do not have
sufficient authorization. Attempting to deactivate
backup image(s) instead...
Success.
----
Past ADSM Forum questions state that the archdelete and backupdelete should be YES!
I have now changed the archdelete and backupdelete to Yes for the affected TSM Nodes. My questions are:
1) does Inventory Expiration remove the 'deactivated files' or, do those objects become Orphaned within the TSM Database when the delete command was issued?
2) for those objects that the db2adutl can no longer see, what was the suggested fix to remove those objects from the APIB2 filespaces?
TSM V5.4
AIX V5.3
Bob