Putting hosts into maintenance mode

The term host referenced in this page refers to a Db2® member or Db2 cluster facility (CF) residing in either a physical host or a logical partition (LPAR) on supported platforms such as AIX. If you are applying software updates to Db2 cluster services or making changes to the server that impacts Db2, you must put the target host into maintenance mode. You can also put a host into maintenance mode if you want to ensure that members or cluster caching facilities are not restarted on the host when you are making updates to the operating system or hardware on the host.

Before you begin

Any Db2 server processes and any other processes accessing the file systems managed by Db2 cluster services must be shut down before running this command. A host cannot enter maintenance mode if any server processes are still active on the host. All instances must be stopped on the host before the host can enter maintenance mode. When the instance is stopped on the host, the host is no longer a viable recovery target for failed members.

To perform this task, you must be the Db2 cluster services administrator.

You can either put multiple hosts into maintenance mode one at a time while maintaining the quorum or put all the hosts into maintenance mode at the same time (by using the -all option which puts the entire peer domain into maintenance mode). Entering and exiting maintenance mode is reciprocal; if you put all of the hosts into maintenance mode, you cannot take just one out of maintenance mode.

Procedure