Disassociating a database mount resource with an existing DPF database

You can disassociate a database with a database mount resource in a Pacemaker-managed DPF Db2 instance by using the Db2 Cluster Manager (db2cm) utility.

About this task

The following prerequisites must be met before proceeding with the procedure:

The target database must exist.
The target database must be in a location from which a connection can be made.
The mount target must be eligible for mount creation. For more information, see the prerequisites section of Associating a mounted remote file system with a Mutual Failover Db2 partition.
Mount points cannot be nested (one mount requires another mount to be available first).

You can dissociate the following database mount resources with a Pacemaker-managed DPF Db2 database:

Local database directory

The following placeholder is used in the command statements throughout this procedure. This represent a value that you can change to suit your organization:

<database_name> is the name of the database to be associated with the database mount on the Db2 instance.

Procedure

As the root user, add a mount point for the database resource to the partition on your Db2 instance:
```
[root@host1~]# db2cm -delete -dbMount -db <database_name>
```
As the root user, verify that the database mount resource has been associated with the cluster domain of your DPF Db2 instance:
```
[root@host1~]# db2cm -status
```

Example

The following example shows the command syntax and output from disassociating a database with a database mount resource on a Pacemaker-managed Db2 instance:

[root@host1~]# db2cm –delete -dbMount -db testdb
Mount resources have been removed successfully for database testdb.

The following example shows the command syntax and output from verifying that a database mount resource has been added to a Pacemaker-managed Db2 instance:

[root@host1~]# db2cm -status
2024-11-12-07.44.52
-------------------
Cluster Summary:
  * Stack: corosync (Pacemaker is running)
  * Current DC: dpf-srv-1 (version 2.1.6-4.db2pcmk.el9-6fdc9deea29) - partition with quorum
  * Last updated: Tue Nov 12 07:44:52 2024 on dpf-srv-1
  * Last change:  Tue Nov 12 07:36:08 2024 by root via cibadmin on dpf-srv-3
  * 4 nodes configured
  * 16 resource instances configured

Node List:
  * Online: [ dpf-srv-1 dpf-srv-2 dpf-srv-3 dpf-srv-4 ]

Full List of Resources:
  * db2_partition_db2inst1_0        (ocf:heartbeat:db2partition):    Started dpf-srv-1
  * db2_partition_db2inst1_1        (ocf:heartbeat:db2partition):    Started dpf-srv-1
  * db2_partition_db2inst1_2        (ocf:heartbeat:db2partition):    Started dpf-srv-2
  * db2_partition_db2inst1_3        (ocf:heartbeat:db2partition):    Started dpf-srv-2
  * db2_partition_db2inst1_4        (ocf:heartbeat:db2partition):    Started dpf-srv-3
  * db2_partition_db2inst1_5        (ocf:heartbeat:db2partition):    Started dpf-srv-3
  * db2_ethmonitor_dpf-srv-1_eth0  (ocf:heartbeat:db2ethmon):       Started dpf-srv-1
  * db2_ethmonitor_dpf-srv-2_eth0  (ocf:heartbeat:db2ethmon):       Started dpf-srv-2
  * db2_ethmonitor_dpf-srv-3_eth0  (ocf:heartbeat:db2ethmon):       Started dpf-srv-3
  * db2_ethmonitor_dpf-srv-4_eth0  (ocf:heartbeat:db2ethmon):       Started dpf-srv-4

QDevice Information:
  * Not configured