Menu
▾
▴
#2230 db2 still out of sync after reboot - affects cnm
DB2 is still not loading right after a reboot and it is affecting CNM. This is after doing the workaround on an existing system. I re-issued db2sqlsetup -S -o and added values to /etc/rc.db2.
cat /etc/rc.db2
!/usr/bin/ksh
EXTSHM=ON
export EXTSHM
[c250mgrs12-pvt][/]> uptime
07:47PM up 6 mins, 1 user, load average: 2.07, 1.45, 0.69
[c250mgrs12-pvt][/]> lsnwloc
FR015-CG04-SN001-DR0 STANDBY_CNM_EXCLUDED
FR015-CG06-SN003-DR0 STANDBY_CNM_EXCLUDED
FR015-CG03-SN000-DR0 STANDBY_CNM_EXCLUDED
FR015-CG05-SN002-DR0 STANDBY_CNM_EXCLUDED
[c250mgrs12-pvt][/]> chnwm -d
cnmd has been deactivated successfully
[c250mgrs12-pvt][/]> su - xcatdb
$ db2
(c) Copyright IBM Corporation 1993,2007
Command Line Processor for DB2 Client 9.7.4
You can issue database manager commands and SQL statements from the command
prompt. For example:
db2 => connect to sample
db2 => bind sample.bnd
For general help, type: ?.
For command help, type: ? command, where command can be
the first few keywords of a database manager command. For example:
? CATALOG DATABASE for help on the CATALOG DATABASE command
? CATALOG for help on all of the CATALOG commands.
To exit db2 interactive mode, type QUIT at the command prompt. Outside
interactive mode, all commands must be prefixed with 'db2'.
To list the current command option settings, type LIST COMMAND OPTIONS.
For more detailed help, refer to the Online Reference Manual.
db2 => connect to xcatdb
Database Connection Information
Database server = DB2/AIX64 9.7.4
SQL authorization ID = XCATDB
Local database alias = XCATDB
db2 => db2stop force
DB20000I The DB2STOP command completed successfully.
db2 => db2start
DB20000I The DB2START command completed successfully.
db2 => quit
DB20000I The QUIT command completed successfully.
$ exit
[c250mgrs12-pvt][/]> chnwm -a
CNM is deactivated, need to activate it
Threads came up in timely fashion. Daemon is running
[c250mgrs12-pvt][/]> lsnwloc
FR015-CG06-SN003-DR0 STANDBY
FR015-CG05-SN002-DR0 STANDBY
FR015-CG04-SN001-DR0 STANDBY
FR015-CG03-SN000-DR0 STANDBY
Discussion
So we probably need to work together. Can you do a tabdump site and xCAT is successfully accessing the database after reboot If so DB2 is running after reboot, and the DB2 restart is working ok.
Assuming DB2 and xCAT are up and running after reboot. Was CNM running with the database before reboot. If you do a chnwm -d and stop it before the reboot then it will not start after reboot. That is their design point. If cnm is active before the reboot and is not coming back up after the reboot with this fix in place then we need to get Wesley involved because we had this working on his AIX machine, but changes have been going into their code.
Yes, xcat is functional after the reboot. I can use it with no issues.
Wes will try on FVT machine. If he cannot create the problem there he will have to debug on the System test machine. It was working in FVT a couple of months ago.
Okay. Let me know. We can easily recreate on our machines.
The setup is based on this website http://publib.boulder.ibm.com/infocenter/tivihelp/v4r1/index.jsp?topic=%2Fcom.ibm.rm33.doc%2Ffrc_t_connect_db2_aix.html
I think what we are missing since the db2sqlsetup script was not used due to the system already being setup is rc.db2 plus
su - xcatdb
db2set DB2ENVLIST=EXTSHM
We are verifying this now on FVT machine.
We have a workaround change the line in /etc/inittab on the EMS as such
fmc:2:respawn:/opt/IBM/db2/V9.7/bin/db2fmcd #DB2 Fault Monitor Coordinator
fmc:2:respawn:su - root "-c /opt/IBM/db2/V9.7/bin/db2fmcd" #DB2
This is a workaround while we contact DB2
This will have CNM come up on reboot but will not help if you have a database crash. Then you will manually stop and start DB2 and then start CNM
This change is only for AIX
Contacted DB2 development. They think this may be a bug. We may have to apply a service pack. They are getting back to me.
I got this back from DB2, I believe the release date for PTF5 is Oct but I am verifying this with them. I suggest that we do not put on the workaround below because we will probably forget to remove it when we put on the fix from DB2. We should just work with the manual workaround of after reboot.
stop xcatd
su - xcatdb
db2stop force
db2start
exit
The start CNM
This was from DB2 development.
The problem is fixed in V97FP5. There is an APAR and defect:
wsdbu00808222
IC73564
So the fix in DB2 is for the monitoring daemon db2fmcd to run the db2profile which has the env variable EXTSHM set. There is no use of rc.db2 so the db2sqlsetup code and documentation should be change not to do any setup of rc.db2. It is useless.
We have documented a workaround. The software fix is in fixpack 5 for DB2 which will out end of Oct.