vkravindran
ADSM.ORG Member
Hi,
I have a peculiar problem with 2 of our TSM servers, which are clustered, and defined as library clients to each other.
On both of them, when the expire inventory command runs, the command hangs, and I can't cancel it. When this happens, I am not able to issue any of the 'q drm' or select from DRMEDIA commands. It just hangs. The only way out is to restart TSM.
The PREPARE command hangs too.
I am also not able to delete volhist records. The command hangs.
I see lot of "ANR4513E A database lock conflict was encountered in
processing sequential volume history information.
(SESSION: 8829)"
errors in the actlog, but it doesn't tell me what volume.
When I restart TSM, the DRM commands runs fine, until I run expiration or PREPARE or VOLHIST commands.
This is causing problems for the people to query and checkout DRM tapes.
I have opened up a Sev 1 ticket with IBM, but so far no help.
I tried to delete the cross-server definitions and the cross-library definitions, but that does not help.
Has anyone come across this situation in the past?
This is the environment:
SUN T-2000
Solaris 10 OS
TSM server 5.4.2.0
DB and log sizes are good. BUFPOOL size is good. IBM verified that.
Thanks in advance
Rav
I have a peculiar problem with 2 of our TSM servers, which are clustered, and defined as library clients to each other.
On both of them, when the expire inventory command runs, the command hangs, and I can't cancel it. When this happens, I am not able to issue any of the 'q drm' or select from DRMEDIA commands. It just hangs. The only way out is to restart TSM.
The PREPARE command hangs too.
I am also not able to delete volhist records. The command hangs.
I see lot of "ANR4513E A database lock conflict was encountered in
processing sequential volume history information.
(SESSION: 8829)"
errors in the actlog, but it doesn't tell me what volume.
When I restart TSM, the DRM commands runs fine, until I run expiration or PREPARE or VOLHIST commands.
This is causing problems for the people to query and checkout DRM tapes.
I have opened up a Sev 1 ticket with IBM, but so far no help.
I tried to delete the cross-server definitions and the cross-library definitions, but that does not help.
Has anyone come across this situation in the past?
This is the environment:
SUN T-2000
Solaris 10 OS
TSM server 5.4.2.0
DB and log sizes are good. BUFPOOL size is good. IBM verified that.
Thanks in advance
Rav