08/14/2019 11:59:59 ANR9999D_2835836899 InstGetDB2stmtPass1(instr.c:550) Thread<404>: Error in fetching DB2 statement stats, rc=235908/14/2019 11:59:59 ANR9999D Thread<404> issued message 9999 from:08/14/2019 11:59:59 ANR9999D Thread<404> 0x00000001000365b4 StdPutText08/14/2019 11:59:59 ANR9999D Thread<404> 0x000000010003784c OutDiagToCons08/14/2019 11:59:59 ANR9999D Thread<404> 0x000000010000cf08 outDiagfExt08/14/2019 11:59:59 ANR9999D Thread<404> 0x000000010019d0d0 IPRA.$InstGetDB2stmtPass108/14/2019 11:59:59 ANR9999D Thread<404> 0x00000001001a15e0 instrumentStart08/14/2019 11:59:59 ANR9999D Thread<404> 0x00000001012d7b98 AdmInstrumentBegin08/14/2019 11:59:59 ANR9999D Thread<404> 0x00000001008da68c AdmCommandLocal08/14/2019 11:59:59 ANR9999D Thread<404> 0x00000001008d7af0 admCommand08/14/2019 11:59:59 ANR9999D Thread<404> 0x00000001013fbe68 RunCommand08/14/2019 11:59:59 ANR9999D Thread<404> 0x00000001013f7a48 ServerMonTwentyMinThread08/14/2019 11:59:59 ANR9999D Thread<404> 0x0000000100010648 StartThread
Although the server started, I wanted to make sure this would not cause issues with the instance. I searched the error ANR9999D_2835836899 and found the following IBM APAR notice. It appears that after the upgrade you may have to manually upgrade the DB2 version using the DB2 update tool. While it appears to be a minor issue, I would recommend you check your instances after upgrade to verify whether you need to run the manual steps to resolve the errors. I've included them here for your convenience.
NOTE: I've added a couple commands (in bold) that we have had to add to the process to make it work.
Even though the db2-level might be updated to the latest version 220.127.116.11, run the below set of commands
Stop TSM server and issue the following commands as the instance owner.
- db2 start
- db2 force application all
- db2 terminate
login as root user and run
- /opt/tivoli/tsm/db2/instance/db2iupdt -d <instance name>
login as the instance owner ID and issue the command:
- db2updv111 -d TSMDB1
This issue is supposedly fixed in version 18.104.22.168 and higher.
Post a Comment