Re: ANR9999D & ANR0379W Lock messages occurring

John Thanks,

Yes, This is the only script running on this TSM server
at the time this is occurring.

Regards


John Monahan wrote:

> I've seen this before with multiple scripts trying to run at the same
> time.  Is this the only script running at the time?
>
> ______________________________
> John Monahan
> Consultant Infrastructure Solutions Group
> Computech Resources, Inc.
> Office: 952-833-0930 ext 109
> Cell: 952-221-6938
> http://www.computechresources.com
>
> Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 05/18/2006 10:15 AM
> Please respond to
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> ANR9999D & ANR0379W Lock messages occurring
>
> Hello All,
>
> I have a open PMR with IBM for the below errors that are
> occurring in our TSM Server log during a Daily script.
> These messages are not showing up every day but frequently enough,
> This is happening during the (migrate stgpool backuppool lowmig=0)
> and at times the Backup STGpool portion's of the script. The script
> process completes successfully. Yesterday the migrate portion
> of the script kept failing due to the ANR0379W message but would
> retry itself as migration should and finally ended successfully.
> Has anyone seen this before or had this occurred in there
> TSM environment?
>
> serial
> BACKUP DB DEVCLASS=BKP TYPE=INCREMENTAL wait=yes
> serial
> BA STG backuppool R359XPOOL maxpr=10 wait=yes
> serial
> migrate stgpool backuppool lowmig=0 wait=yes <<<<<<<<
> serial
> BA STG H359XPOOL R359XPOOL maxpr=10 wait=yes
>
> 05/14/06 14:43:16     ANR9999D tmlock.c(908): ThreadId<75> Attempt to
> release
> unheld shared lock.(SESSION: 6574, PROCESS: 13)
> 05/14/06 14:43:16     ANR9999D ThreadId<75> issued message 9999 from:
> <-0x000000010001c240 outDiagf <-0x0000000100041770
> tmUnlock <-0x00000001002575e8 SsUnlockVolName <-0x000000
> 01002f41a8 asFreeLeaseLockVol <-0x000000010033d6d0
> CheckSetBackupOptimization <-0x000000010033f33c
> AfBackupPoolQueueThread <-0x000000010000e9dc StartThread
> <-0x09000000003f52f8 _pthread_body
>
> 05/14/06 14:43:18     ANR9999D tmlock.c(908): ThreadId<75> Attempt to
> release
>  unheld shared lock.
> 05/14/06 14:43:18     ANR9999D ThreadId<75> issued message 9999 from:
>  <-0x000000010001c240 outDiagf <-0x0000000100041770
>  tmUnlock <-0x00000001002575e8 SsUnlockVolName <-0x000000
>  01002f41a8 asFreeLeaseLockVol <-0x000000010033d6d0
>  CheckSetBackupOptimization <-0x000000010033f33c
>  AfBackupPoolQueueThread <-0x000000010000e9dc StartThread
> <-0x09000000003f52f8 _pthread_body
>
> 05/15/06 12:37:41     ANR9999D tmlock.c(908): ThreadId<65> Attempt to
> release
>  unheld shared lock.(SESSION: 24272, PROCESS: 54)
> 05/15/06 12:37:41     ANR9999D ThreadId<65> issued message 9999 from:
>   <-0x000000010001c240 outDiagf <-0x0000000100041770
>    tmUnlock <-0x00000001002575e8 SsUnlockVolName <-0x000000
>    01002f41a8 asFreeLeaseLockVol <-0x000000010033d6d0
>    CheckSetBackupOptimization <-0x000000010033f33c
>    AfBackupPoolQueueThread <-0x000000010000e9dc StartThread
>    <-0x09000000003f52f8 _pthread_body
>
> 05/17/06 11:03:54     ANR0379W A server database deadlock situation has
> been
>  encountered; the lock request for the af bitfile root
>  lock,  will be denied to resolve the deadlock.
> 05/17/06 11:04:00     ANR0379W A server database deadlock situation has
> been
>  encountered; the lock request for the af bitfile root
> lock,  will be denied to resolve the deadlock.
> 05/17/06 11:04:06     ANR0379W A server database deadlock situation has
> been
> encountered; the lock request for the af bitfile root
> lock,  will be denied to resolve the deadlock.
> 05/17/06 11:04:12     ANR0379W A server database deadlock situation has
> been
> encountered; the lock request for the af bitfile root
> lock,  will be denied to resolve the deadlock.
> 05/17/06 11:04:17     ANR0379W A server database deadlock situation has
> been
> encountered; the lock request for the af bitfile root
> lock,  will be denied to resolve the deadlock.
> 05/17/06 11:04:23     ANR0379W A server database deadlock situation has
> been
> encountered; the lock request for the af bitfile root
> lock,  will be denied to resolve the deadlock.
> 05/17/06 11:14:33     ANR0379W A server database deadlock situation has
> been
> encountered; the lock request for the af bitfile root
> lock,  will be denied to resolve the deadlock.
> 05/17/06 11:19:41     ANR0379W A server database deadlock situation has
> been
> encountered; the lock request for the af bitfile root
> lock,  will be denied to resolve the deadlock.
> 05/17/06 11:19:47     ANR0379W A server database deadlock situation has
> been
> encountered; the lock request for the af bitfile root
> lock,  will be denied to resolve the deadlock.
>
> Thanks for any replies in advance!
>
> TSM 5.3.3
> Aix 5.3