Stopping a cluster caching facility
A cluster caching facility (CF) is stopped as part of a global db2stop or an individual db2stop CF command. This topic focuses on stopping a single cluster caching facility.
About this task
Issue the db2stop CF command if you want to stop a cluster caching facility on a host while keeping other instance processes on the same host up and running.
Restrictions
You cannot stop the primary cluster caching facility individually if the secondary cluster caching facility is not in PEER state unless there are no active databases. If there is no active secondary cluster caching facility, the primary cluster caching facility cannot be stopped when there are active members. Also, you cannot stop the secondary cluster caching facility individually if there is no primary CF. In this instance, the secondary CF is either about to become primary CF or becoming primary CF. In this case, you can stop the secondary cluster caching facility by using the FORCE option.
Procedure
db2stop CF CF-identifier