Question & Answer
Question
If we install a fixpack on top of a MSCS cluster, it will not update the DBM CFG file in the shared location. How can we make sure that DB2 on both host is updated correctly along with the instance?
Cause
This is a current limitation of DB2 MSCS environment.
Answer
When updating a MSCS cluster, the current procedure requires the host that is to be
updated to be disconnected from the DB2INSTPROF.
In order to update the instance that consist of the DBM CFG file, we need to de-cluster
MSCS. This is so the local DBM CFG file stored in the C: drive will be updated with the
fix pack, and then when we re-cluster to create MSCS, the updated DBM CFG file will be
copied to the shared disk.
Assuming we start with a MSCS configuration
1) De-cluster MSCS to replace the instance back to the local host with the command:
db2mscs –u <instance name>
2) Stop db2 instance on the host that originally has the db2 instance created:
db2stop
3) Run db2install on both hosts with the "work with existing copy" specified to
update DB2.
4) Re-cluster the MSCS cluster with the command:
db2mscs –f <path to mscs.cfg>
Note:
Please contact your Sales Rep to submit a potential design change towards a future release.
Or please open a ticket, Request For Enhancement at https://www.ibm.com/developerworks/rfe/
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21987571