CBR4441I Delete of all rows from the Deleted Objects Table for volumes volser-1 and volser-2 failed.
Explanation
As a part of reinitialization processing, a request to discard all deletes pending against volumes volser-1 and volser-2 failed. Discarding pending deletes involves deletion of all rows, for the subject volumes, from the deleted objects table. The request was made during reinitialization processing and was retried several times. The failure is due to a DB2® timeout, deadlock, or other resource contention.
If the cartridge is being reinitialized as a result of being selected by OSMC shelf manager because the volume has expired, then the delete is attempted again after the next OAM Storage Management Component cycle selects the cartridge again.
If the cartridge is being reinitialized as a result of a Move Volume utility with DELETE option or a Volume Recovery with DELETE option specified, then all knowledge of the cartridge is purged from OAM. Therefore, in these cases the cartridge is not remounted and the delete from the deleted objects table is not attempted again at a later time. In this case, it is necessary to manually delete the rows associated with this cartridge from the deleted objects table.
System action
Associated with each volume, is a volume empty indicator which is a field in the volume table. Whenever a volume is mounted, if the logically empty indicator is set and there are still pending deletes against the volume, the multirow deletion will be attempted again, before the volume is actually reinitialized.
System programmer response
DELETE FROM DELOBJT
WHERE VOLSER=volser-1 OR VOLSER=volser-2;
Source
Object Access Method (OAM)
Routing Code
2,4,6
Descriptor Code
4