DB2 10.5 for Linux, UNIX, and Windows

Stopping a member

DB2® members are stopped as part of a global db2stop or an individual db2stop command. This topic focuses on stopping a single member.

About this task

Issue the db2stop member command if you want to stop a member on a host but keep other instance processes on the host up and running. This means that other members or cluster caching facilities on the same host will not be affected. However, note that stopping a member is not a sufficient prerequisite for performing maintenance on the host, because the host still remains a viable failover target for other members.

Restrictions

You cannot stop a member if there are any active database connections on the member. If the member is in restart light mode and has not yet completed member crash recovery (that is, at least one of the databases is inconsistent on that member), it cannot be stopped using a db2stop command. However, it can be stopped by using the FORCE option. It is strongly recommended that you do not stop a member undergoing crash recovery.

Procedure

To stop a member, issue this command:
db2stop member member-id