ANR9999D & ANR0379W messages 1

[almond247]

Hello All,

Recently we have been recieving the error messages below in our TSM Server log 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.
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

Thanks for any replies in advance!

TSM 5.3.3
Aix 5.3

 

[ProbablyDown]

http://publib.boulder.ibm.com/infoc...?topic=/com.ibm.itsmm.doc/update/ANR0379W.htm

Are you guys using ODBC to connect Access or something to the TSM database? Maybe its locking it?

Just a guess, but here is the link to the IBM messages doc if you haven't already been there...

 

[almond247]

Thanks,

Yes as a matter of fact, We are using ODBC. Would
someone have to be connecting to the ODBC at the
same time as the STgPOOL processes are running?
Or not necessarily? Not sure If this is
the cause but this is interesting I will
have to check into this.

best regards

 

[ProbablyDown]

Let me know if thats the case... Thanks..

 

[almond247]

Hello,

ProbablyDown

We still see these messages from time to time but they
are infrequent. I did see the message below during
queries using the ODBC, But it also occurs when
no one is using the ODBC. Also, Tivoli Support
said that this is a Backup Storage pool issue.

Thanks,
Regards

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.