Re: LOCKCYCLE02 error
> Can one revert from 5.2.3.4 to 5.2.3.3 without restoring the tsm db? Yes! Just uninstall, then reinstall. Of course it is always recommended to do full back up of your db first, just in case. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence.
Re: LOCKCYCLE02 error
Thanks. That appears to be it exactly. Can one revert from 5.2.3.4 to 5.2.3.3 without restoring the tsm db? David >>> [EMAIL PROTECTED] 11/16/2004 11:13:33 PM >>> Likely suspect: IC43445: ABSTRACT: TSM SERVER ABENDS WITH ANR7837S INTERNAL ERROR LOCKCYCLE02 DETECTED ERROR DESCRIPTION: The TSM Server can crash with a LOCKCYCLE02 assertion failure. The assertion failure occurs as a result of a lock request being aborted which would occur from the resource monitor. The crash will only occur if more than 1 resource was waiting on a particular lock and 2 of those resources have been aborted due to resourcetimeout. Customer/L2 Diagnostics: The traceback for this problem will be the following: pkAbort pkLogicAbort CheckLockCycles TmFindDeadlock TmDeadlockDetector StartThread The dsmserv.err will report the following error messages: ANR7838S Server operation terminated. ANR7837S Internal error LOCKCYCLE02 detected. In the activity log just prior to the crash, you will most likely see at least 2 occurrances of the following message: ANR0538I A resource waiter has been aborted. Platforms affected: All 5.2.3.4 ITSM Servers Initial Impact: High Additional Keywords: Assert resource wait admres deadlock locking lockholder core dump logicabort MSGANR7837S LOCAL FIX: 1) Back-level the TSM Server to 5.2.3.3 or prior 2) Increasing the resourcetimeout may or may not provide relief depending on how long the resources have to wait. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 11/16/2004 20:56:45: > My tsm server 5.2.3.4 crashed tonight. In the dsmserv.err log I find > "ANR7837S Internal error LOCKCYCLE02 detected." Any ideas. I can't get > into the IBM/Tivoli ESR site tonight so I'll report via that route > tomorrow. A web search of the support site only found v4 hits. So > meanwhile if anyone has suggestions . . . > > I'm running TSM 5.2.3.4 64 bit mode on AIX 5.1 ML7 with a 3494 library > with 3590E drives. > > David
Re: LOCKCYCLE02 error
Likely suspect: IC43445: ABSTRACT: TSM SERVER ABENDS WITH ANR7837S INTERNAL ERROR LOCKCYCLE02 DETECTED ERROR DESCRIPTION: The TSM Server can crash with a LOCKCYCLE02 assertion failure. The assertion failure occurs as a result of a lock request being aborted which would occur from the resource monitor. The crash will only occur if more than 1 resource was waiting on a particular lock and 2 of those resources have been aborted due to resourcetimeout. Customer/L2 Diagnostics: The traceback for this problem will be the following: pkAbort pkLogicAbort CheckLockCycles TmFindDeadlock TmDeadlockDetector StartThread The dsmserv.err will report the following error messages: ANR7838S Server operation terminated. ANR7837S Internal error LOCKCYCLE02 detected. In the activity log just prior to the crash, you will most likely see at least 2 occurrances of the following message: ANR0538I A resource waiter has been aborted. Platforms affected: All 5.2.3.4 ITSM Servers Initial Impact: High Additional Keywords: Assert resource wait admres deadlock locking lockholder core dump logicabort MSGANR7837S LOCAL FIX: 1) Back-level the TSM Server to 5.2.3.3 or prior 2) Increasing the resourcetimeout may or may not provide relief depending on how long the resources have to wait. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 11/16/2004 20:56:45: > My tsm server 5.2.3.4 crashed tonight. In the dsmserv.err log I find > "ANR7837S Internal error LOCKCYCLE02 detected." Any ideas. I can't get > into the IBM/Tivoli ESR site tonight so I'll report via that route > tomorrow. A web search of the support site only found v4 hits. So > meanwhile if anyone has suggestions . . . > > I'm running TSM 5.2.3.4 64 bit mode on AIX 5.1 ML7 with a 3494 library > with 3590E drives. > > David
LOCKCYCLE02 error
My tsm server 5.2.3.4 crashed tonight. In the dsmserv.err log I find "ANR7837S Internal error LOCKCYCLE02 detected." Any ideas. I can't get into the IBM/Tivoli ESR site tonight so I'll report via that route tomorrow. A web search of the support site only found v4 hits. So meanwhile if anyone has suggestions . . . I'm running TSM 5.2.3.4 64 bit mode on AIX 5.1 ML7 with a 3494 library with 3590E drives. David
