Reclamation is failing instantly when run on one of our legacy TSM servers (5.5.7.0) on AIX
ANR3512E RECLAIM STGPOOL: Error encountered in accessing data storage - insufficient number of
mount points available for removable media.
ANS8001I Return code 14.
The MountLimit is set to drives for all the device classes, the Library Manager has 50 drives to this VTL, and 20 for the physical tape library. There are drives in use from some of the other library clients, but there are plenty free. The paths are all online for the Library Manager and the Library Client.
The Storage pools have no funny settings regarding reclamation, and the maxscratch is no where near the limit.
I can run move data on the volumes all day long, they either move to a new scratch or to one of the filling volumes.
When I run reclamation there are no errors on this TSM server or the Library manager, other than the ANR3512E message, which is returned instantly.
I think one of the tables is corrupt in the database, has anyone seen a problem like this before? Obviously as this is 5.5 there is no support from IBM, and this DB is 300GB so an audit is going to be a major outage :(
ANR3512E RECLAIM STGPOOL: Error encountered in accessing data storage - insufficient number of
mount points available for removable media.
ANS8001I Return code 14.
The MountLimit is set to drives for all the device classes, the Library Manager has 50 drives to this VTL, and 20 for the physical tape library. There are drives in use from some of the other library clients, but there are plenty free. The paths are all online for the Library Manager and the Library Client.
The Storage pools have no funny settings regarding reclamation, and the maxscratch is no where near the limit.
I can run move data on the volumes all day long, they either move to a new scratch or to one of the filling volumes.
When I run reclamation there are no errors on this TSM server or the Library manager, other than the ANR3512E message, which is returned instantly.
I think one of the tables is corrupt in the database, has anyone seen a problem like this before? Obviously as this is 5.5 there is no support from IBM, and this DB is 300GB so an audit is going to be a major outage :(