tom.s
ADSM.ORG Member
Folks,
any help on the following would be appreciated...
I am running TSM 5.2.3.0 on Win2003. Recently TSM has been swamped by ANR9999D messages:
********************************************************
ANR9999D ssalloc.c(1378): ThreadId<62> Error locating storage pool
-6. Callchain: 104EAD79 outTextf()+1529 <- 10479E94
tsmInitializeServer()+472664 <- (SESSION: 17421, PROCESS: 343)
********************************************************
There would be around 7000 of them in the log every time expiration was run. Incidentally, the storage pool mentioned in the error does not exist, and I assume from the negative number it was a copy pool. A couple of days after this message appeared the server began to crash during certain client restore operations - particuler nodes, and particular bits of directory structure. If I restored the files without the directorys they come back OK. I suspect other things have caused it to crash as well, but I haven't managed to isolate what.
A DSMSERV AUDIT DB FIX=YES DETAIL=YES found a lot of stuff wrong and fixed it, however the server still crashes the same client restore.
The windows event log contains the following:
********************************************************
Event Type: Error
Event Source: ADSMServer
Event Category: None
Event ID: 27
Date: 27/04/2005
Time: 13:34:48
User: N/A
Computer: XIGBRS83
Description:
TSM Server Diagnostic: ANR9999D: ADSM Exception Information: file = pkthread.c, line = 2253,Code = c0000005, Address = 7C34FEDC
Attempt to read data at address 30~
********************************************************
Finally, though it doesn't seem to be causing the crash, the following ANR9999 message has appeared in the actlog since the audit:
********************************************************
ANR9999D smtrans.c(1397): ThreadId<53> Object header size
mismatch, replacing 377 with 375. Callchain: 104EAD79
outTextf()+1529 <- 103F293C tsmInitializeServer()+3EB10C
<- 43534544 Unknown <- (SESSION: 4)
********************************************************
I have raised this with support... but so far so frustrating!
If anybody has seen anything like this, I'd be grateful to hear from you.
Also, am I right in thinking that an UNLOAD, LOAD would can solve database corruption issues that an AUDIT can't?
Thanks in advance!
Tom
any help on the following would be appreciated...
I am running TSM 5.2.3.0 on Win2003. Recently TSM has been swamped by ANR9999D messages:
********************************************************
ANR9999D ssalloc.c(1378): ThreadId<62> Error locating storage pool
-6. Callchain: 104EAD79 outTextf()+1529 <- 10479E94
tsmInitializeServer()+472664 <- (SESSION: 17421, PROCESS: 343)
********************************************************
There would be around 7000 of them in the log every time expiration was run. Incidentally, the storage pool mentioned in the error does not exist, and I assume from the negative number it was a copy pool. A couple of days after this message appeared the server began to crash during certain client restore operations - particuler nodes, and particular bits of directory structure. If I restored the files without the directorys they come back OK. I suspect other things have caused it to crash as well, but I haven't managed to isolate what.
A DSMSERV AUDIT DB FIX=YES DETAIL=YES found a lot of stuff wrong and fixed it, however the server still crashes the same client restore.
The windows event log contains the following:
********************************************************
Event Type: Error
Event Source: ADSMServer
Event Category: None
Event ID: 27
Date: 27/04/2005
Time: 13:34:48
User: N/A
Computer: XIGBRS83
Description:
TSM Server Diagnostic: ANR9999D: ADSM Exception Information: file = pkthread.c, line = 2253,Code = c0000005, Address = 7C34FEDC
Attempt to read data at address 30~
********************************************************
Finally, though it doesn't seem to be causing the crash, the following ANR9999 message has appeared in the actlog since the audit:
********************************************************
ANR9999D smtrans.c(1397): ThreadId<53> Object header size
mismatch, replacing 377 with 375. Callchain: 104EAD79
outTextf()+1529 <- 103F293C tsmInitializeServer()+3EB10C
<- 43534544 Unknown <- (SESSION: 4)
********************************************************
I have raised this with support... but so far so frustrating!
If anybody has seen anything like this, I'd be grateful to hear from you.
Also, am I right in thinking that an UNLOAD, LOAD would can solve database corruption issues that an AUDIT can't?
Thanks in advance!
Tom