I’ve been playing with TSIEM a bit in the last couple of days in preparation for some upcoming work, and I’ve had a recurring issue.
On both Windows Server 2003, and Windows Server 2008, (3 seperate VMs) I’ve installed TSIEM and the CIFCOPY DB2 instance has started refusing to start either straight away or a day or two later. Staying in the Starting state according to the Windows Services panel and db2syscs.exe seems to just at 100% CPU for no clear reason, and the logs weren”t telling me anything useful.
Found a few links scattered and stumbled across this technote:
File Sharing Violation of DB2 audit file might affect TSIEM
http://www-01.ibm.com/support/docview.wss?uid=swg21432619
But after looking for the file conflict, gave up on that one.
Finally a colleague pointed me at this:
DB2 – CIFCOPY – CIFINST-0 service hangs in “Starting” state
https://www-304.ibm.com/support/docview.wss?uid=swg21456785
And with a quick command, finally had a working DB2 instance again!
===========
EDIT: 17/2/14
It’s come to my attention that the technote above has expired. I found an archived copy of it, and reposted it below.
Symptom: The ITDS DB2 instance (“DB2 – IDSCOPY – IDSINST”) service remains unaffected and is started successfully.
Diagnosing the Problem: Log into the TSIEM Server as cifdbadm OS account (“DB2 – CIFCOPY – CIFINST-0” service account).
Perform the following troubleshooting steps:
– Terminate any db2syscs.exe, db2start,exe or db2stop.exe processes that are running under the “cifdbadm” OS user account (“DB2 – CIFCOPY – CIFINST-0” service account) in the task manager.
– Open a DB2 command window by executing “db2cmd” from Start->Run menu.
– Start the DB2 instance in debug mode as below (enter this in the newly opened DB2 command window)
MSDOS> db2start /d
– Verify if the following error is displayed:
SQL10007N Message "1073741510" could not be retrieved. Reason code: "4". 2010-04-14 13.19.46 0 0 SQL1042C An unexpected system error occurred. SQL1032N No start database manager command was issued. SQLSTATE=57019
Content: DB2 Support recommended the following resolution steps to address the error:
– Log into the TSIEM Server as cifdbadm OS account (“DB2 – CIFCOPY – CIFINST-0” service account).
– Stop TSIEM Services (Refer to Administration Guide for stopping TSIEM services)
– Terminate any db2syscs.exe, db2start,exe or db2stop.exe processes that are running under the “cifdbadm” OS user account (“DB2 – CIFCOPY – CIFINST-0” service account) in the task manager.
– Open a DB2 command window by executing “db2cmd” from Start->Run menu.
– Run the DB2 Instance Update command (db2iupdt)
MSDOS> db2iupdt cifinst /u:cifdbadm,pwdofcifdbadm
where:
cifinst is the name of the TSIEM Db2 instance
cifdbadm is “DB2 – CIFCOPY – CIFINST-0” service account
pwdofcifdbadm is the OS account password of the cifdbadm account
(Note: There is a comma (,) character in between the username and password in the command)
– Start the “DB2 – CIFCOPY – CIFINST-0” service from the Windows services panel and ensure that the service starts successfully.
– Start the TSIEM Services (Refer to Administration Guide for starting TSIEM services)
NOTE:
The execution of db2iupdt command can reset the audit settings on the TSIEM Self Audit Db2 instance (CIFINST) event source. Use the “db2audit describe” command for checking the current audit configuration of Db2 instance. For reconfiguring the audit settings on the Db2 instance, please refer to the TSIEM 2.0 documentation “Event sources and user information sources” -> “IBM DB2 Version 9.5 – 9.X” section.
Philip Nye 