Hi Rick, Off-hand I am not sure what the problem is, I think it would be a good idea to open a PMR if you have not already done so.
Best regards, - Andy ____________________________________________________________________________ Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | [email protected] IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome Product Wiki: https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager "ADSM: Dist Stor Manager" <[email protected]> wrote on 2015-02-13 10:41:55: > From: "Rhodes, Richard L." <[email protected]> > To: [email protected] > Date: 2015-02-13 10:44 > Subject: FW: v6.3.5 hung db2?? > Sent by: "ADSM: Dist Stor Manager" <[email protected]> > > Now this is really weird. > > TSM came up after we rebooted. But it threw a bunch of ANR9999 msgs, > then QUIT LOGGING. It seems to be running - I go onto a server and > did a incr bkup, but nothing is logging in the actlog. > > 02/13/15 10:00:22 ANR9999D_2891663292 GetDomainByNodeId > (pmcache.c:2645) Thread<280>: Node id 626 not found in table > Policy.Domain.Members. (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> issued message 9999 > from: (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010001ca7c > StdPutText (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010001d514 > OutDiagToCons (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001000090bc > outDiagfExt (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001004bf254 > GetDomainByNodeId (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001004beeec > pmOpenDomain (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001006ac78c > BeginVbTxn (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001006a4068 > SmNodeSession (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010053ca64 > SmSchedSession (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001005525d8 > HandleNodeSession (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x0000000100549c54 > DoNodeSched (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x0000000100544900 > smExecuteSession (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x0000000100078a7c > psSessionThread (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010000c264 > StartThread (SESSION: 125) > 02/13/15 10:00:22 ANR9999D_3095886799 HandleShortCircuitCodes > (dbieval.c:1072) Thread<280>: Invalid handle used from tbtbl.c > (10153). (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> issued message 9999 > from: (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010001ca7c > StdPutText (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010001d514 > OutDiagToCons (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001000090bc > outDiagfExt (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001000cbb28 > HandleShortCircuitCodes (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001000cb0a0 > DbiEvalSQLOutcomeX (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001000a0a18 > TblClose (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010019b13c > FreeTxnDesc (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010019af14 > dbiEndTxn (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001000458bc > DoEndFuncCallbacks (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x0000000100045d70 > tmAbortX (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001004bef60 > pmOpenDomain (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001006ac78c > BeginVbTxn (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001006a4068 > SmNodeSession (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010053ca64 > SmSchedSession (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x00000001005525d8 > HandleNodeSession (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x0000000100549c54 > DoNodeSched (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x0000000100544900 > smExecuteSession (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x0000000100078a7c > psSessionThread (SESSION: 125) > 02/13/15 10:00:22 ANR9999D Thread<280> 0x000000010000c264 > StartThread (SESSION: 125) > > It then threw this error and STOPPED LOGGING into actlog. > > 02/13/15 10:03:24 ANR0103E admattrm.c(806): Error 2332 > updating row in table "Global.Attributes". > > > > > From: Rhodes, Richard L. > Sent: Friday, February 13, 2015 9:49 AM > To: adsm-l mailing list ([email protected]) > Subject: v6.3.5 hung db2?? > > Two days ago we upgrade one of our TSM instances to v6.3.5 (from v6.3.4). > This is our first v6.3.5 instance. It runs on a AIX server. > > Last night at 19:32 it looks like DB2 went into some kind of a loop. > The instance became unresponsive. Dsmadmc cmds hung (didn't error, > just hung). > Dsmserv process was getting almost no cpu, while ds2sync was running the box > At 65-70% but had no disk I/O. I killed dsmserv, but db2 didn't go down. > I tried db2stop but it did nothing. Finally rebooted to get everything up. > The actlog shows no nasty errors. > > Just wondering if anyone else has had a runaway db2. > > Thanks > > Rick > > > > > > > ----------------------------------------- > > The information contained in this message is intended only for the > personal and confidential use of the recipient(s) named above. If > the reader of this message is not the intended recipient or an agent > responsible for delivering it to the intended recipient, you are > hereby notified that you have received this document in error and > that any review, dissemination, distribution, or copying of this > message is strictly prohibited. If you have received this > communication in error, please notify us immediately, and delete the > original message. >
