I had an interesting problem today and I was wondering if someone had the same and have a solution or explanation for it.
I had to install FixPack 7, v9.7 (we were on FP2) on one of our servers. We have 3 instances there: db2inst1, db2inst2 and db2arh; on db2inst1 and db2arh DB2AUTOSTART is set to YES.
I stopped WAS and application and I have set DB2AUTOSTART to OFF but instance was continuously autorestarted, over and over. I have set AUTORESTART to OFF, just to be on safe side, but that didn't help either. I've ran sqllib/bin/ipclean and killed all db2bp processes, but again, db2inst1 started again. There was no connections on database, that puzzles me even more.
Same thing happened with db2arh, but not with db2inst2.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
2 replies Latest Post - 2013-01-16T14:39:28Z by Noh.Aonne
Pinned topic Instance - autostart
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-16T14:39:28Z at 2013-01-16T14:39:28Z by Noh.Aonne
mwandishi 100000PY7N47 PostsACCEPTED ANSWER
Re: Instance - autostart2013-01-16T14:31:15Z in response to Noh.AonneHi Noh,
I suspect it's the fault monitor process; spawned from /etc/inittab. I refer you too:
db297: egrep -i db2fm /etc/inittab
fmc:2:respawn:/opt/IBM/db2/V10.1/bin/db2fmcd #DB2 Fault Monitor Coordinator
You may need to comment it out. Also check: ps -eafld | grep db2fmcd