DBT8000-9999

DBT Message ID	Message	Explanation	User Response
DBT8000E	Adding the host machine `new-host-name` to the DB2 cluster failed. Either the specified host machine does not exist, or the new host machine is not accessible from other host machines in the cluster.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to add a new host machine to a DB2 cluster, but the host machine cannot be added because the specified host does not exist in the network, or cannot be contacted from other host machines in the DB2 cluster.	Verify that the specified host machine exists, and is reachable from other host machines in the DB2 cluster.
DBT8001W	The host machine `new-host-name` was not added to the DB2 cluster because the host machine is already a member of the DB2 cluster.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to add a new host machine to a DB2 cluster, but the host machine is already in the DB2 cluster.	No response is required.
DBT8004E	The db2cluster command failed because the user ID `user-ID` does not have authorization to issue this command.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. The options of the db2cluster command that you can use depend on your authorization level. Some options can only be specified by the DB2 cluster services administrator, others can only be specified if you are part of the SYSADM, SYSCTL, or SYSMAINT group, and a smaller subset of commands can be run by any user ID on the system. This message is returned when an attempt is made to use the db2cluster command to perform an operation that the user ID which issued the command is not authorized to perform.	Reissue the command with a user account that has the required authorization.
DBT8005E	The host machine `new-host-name` was added to the cluster manager domain, but could not be started in this domain because the host machine is in ONLINE state in another domain.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to add a host machine to a DB2 cluster, but the host machine is in ONLINE state in another peer domain.	To add the host machine to the current DB2 cluster manager domain, perform the following steps: Determine in which domain the host machine is ONLINE by issuing the lsrpdomain command. Bring the host machine offline in the other domain by issuing the stoprpnode command. Reissue the db2cluster command.
DBT8006E	Adding the host machine `host-machine-name` to the DB2 cluster failed because the necessary version of some required software is not installed on the host machine being added. Required software: `software-short-name`.	You can manage your DB2 cluster using the db2cluster utility. The installer invokes the db2cluster command to perform some install and instance management operations too. The db2cluster utility uses software such as IBM Tivoli System Automation for Multiplatforms (SA MP) and IBM General Parallel File System (GPFS), as well as other software, so supported versions of these software products must be installed on all host machines that you want to have in your DB2 cluster. This message is returned when an attempt is made to add a new host machine to a DB2 cluster, but the required version of the software identified by the runtime token `software-short-name` is not installed on the host machine.	Install the required software in one of the following ways: Manually install the required version of the software. If the software is bundled with the database product, use the installer to install the software.
DBT8007E	Adding the host machine `new-host-name` to the DB2 cluster failed because the host has not been prepared with the preprpnode command.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. Before a host machine can be added to a DB2 cluster, the host machine must be prepared by using the preprpnode utility. When the db2cluster utility adds a host machine to a DB2 cluster, the db2cluster utility issues the preprpnode command automatically. This message is returned when an attempt is made to add a new host machine to a DB2 cluster, but the host machine was not successfully prepare with the preprpnode command by the db2cluster utility.	Prepare the host machine by issuing the preprpnode command manually and then add the host machine to the DB2 cluster.
DBT8008E	Adding the host machine `new-host-name` to the DB2 cluster failed because the required version of GPFS is not installed on the host machine being added.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. The db2cluster utility uses IBM Tivoli System Automation for Multiplatforms (SA MP) software as well as IBM General Parallel File System (GPFS) software, so supported versions of these software products must be installed on all host machines that you want to have in your DB2 cluster. This message is returned when an attempt is made to add a new host machine to a DB2 cluster, but the required version of GPFS is not installed on the host machine.	Install the required software in one of the following ways: Manually install the required version of GPFS on the host machine. Use the database product installer to install the GPFS software that is bundled with the database software.
DBT8009E	Adding a disk to the file system `file-system-ID` failed because the file system does not exist.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to add a disk to an existing shared file system cluster, but the specified file system does not exist.	Reissue the command, specifying a file system that exists.
DBT8010W	The disk `disk-ID` was not added to the file system `file-system-ID` because the disk is already in the file system.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to add a disk to an existing shared file system cluster, but the disk is already in the specified file system.	No response is required.
DBT8011E	Adding the disk to the file system failed because of a problem with the disk. File system name: `file-system-ID`. Disk name: `disk-ID`. Disk problem reason code: `reason-code`.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to add a disk to an existing shared file system cluster, but there is a problem with the specified disk. The reason code indicates more specifically what the underlying problem is: 1 There was a general disk error. 2 The disk does not support SCSI-3 Persistent Reserve technology. 3 The disk is not directly attached to all the hosts in the shared file system cluster. 4 The disk is already in use by another GPFS file system, the OS file system, the OS itself, or something other than this GPFS file system. 5 The disk was not found. 6 The disk is already in use as a device container for a table space in a database. 7 The disk is already in use by a GPFS file system. A concurrent create file system or add disk to file system may have been run with the same disk. 8 The disk was not found in the partition block allocation file, /proc/partitions.	Perform the following troubleshooting steps: Verify the state and configuration of the disk and then reissue the command specifying a disk that is ready for use. Review related error information in the diagnostic (db2diag) log files. Additional user response corresponding to particular reason codes: 4 To determine where the disk is being used and to remove it: Locate which system is using the disk: If the disk is in use by another GPFS cluster file system, it will be in the disk list of one of the file systems on one of the clusters, which can be determined by running, on a host on each GPFS cluster, db2cluster -cfs -list -filesystem to get a list of file systems for that cluster and db2cluster -cfs -list -filesystem `file-system-ID` on each file system listed in that cluster. If the disk is in use by (mounted on) the OS file system, then it will be listed in the list of mounts on the OS: Linux: /proc/mounts HP, SUN: /etc/mnttab AIX: mntctl() NT: GetLogicalDriveStrings() Otherwise the disk is in use by the OS and is not suitable for use. Remove it from that system, if it is safe to do so. If the disk is in use by another GPFS file system, run db2cluster -cfs -remove -disk `disk-ID` -filesystem `file-system-ID` on a host of the cluster containing that file system. If the disk is in use by (mounted on) the OS file system, unmount it if it is safe to do so. 5 Ensure the disk is at the given disk path and is listed in /proc/partitions. 6 See the db2diag.log for more information as to which instances and databases are using the disk. If it is safe to do so, run drop db `database-ID` on each database mounted on the disk path to stop the disk from being used as a device container for table spaces in those databases. 7 To determine where the disk is being used and to remove it, on a host on each GPFS cluster: Run db2cluster -cfs -list -filesystem to get the list of file systems in the cluster. Run db2cluster -cfs -list -filesystem `file-system-ID` -disk on each file system listed to determine which file system the disk is in. 8 Ensure the input for -disk is a valid disk and can be found in /proc/partitions.
DBT8012E	Adding the host machine `new-host-name` to the DB2 cluster failed because the host machine is a member of another shared file system cluster.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to add a host machine to a DB2 cluster, but the host machine is in another shared file system cluster.	To add this host machine to this DB2 cluster, first remove the host machine from the other shared file system cluster.
DBT8013E	Adding the host machine `new-host-name` to the DB2 cluster failed because the host name is the same as the domain name.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. A db2cluster restriction is that no cluster node may have the same name as the cluster domain. This message is returned when an attempt is made to add a new host machine to a DB2 cluster, but the host machine name is the same as the name of the domain to which the host machine is being added.	Change the name of the host machine or the name of the domain, and then add the host machine.
DBT8014E	The db2cluster command failed because the value for the redundancy group id parameter is invalid.	You can create a replicated file system by using the db2cluster command. The redundancy group id parameter specifies the geographic location of disks in a DB2 pureScale cluster with storage replication. Valid values of redundancy group id are, 1 and 2. This message is returned when the value for the redundancy group id parameter is invalid.	Enter the command again by specifying a valid value for redundancy group id.
DBT8015E	The cluster manager was not stopped on the host machine `host-name` because that host is the only host in the DB2 cluster on which the cluster manager is currently running. Domain: `domain-name`.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. You can stop the cluster manager on a specified host machine by issuing the db2cluster command with the following parameters: -cm, -stop, and -host. However, to maintain operational quorum in the DB2 cluster, if the specified host machine is the only host machine in the DB2 cluster on which the cluster manager is currently running, the db2cluster utility will not stop the cluster manager on that host machine. This message is returned when an attempt is made to stop the cluster manager on the only host machine in a DB2 cluster on which the cluster manager is running.	To stop the domain, reissue the db2cluster command with the following parameters: -stop, and -domain.
DBT8016E	The db2cluster command failed because redundancy group id `ID` has been defined multiple times.	You can create a replicated file system by using the db2cluster command. This message is returned when the same redundancy group id was specified multiple times with different lists of disks.	Enter the command again by specifying different redundancy group ids for different lists of disks.
DBT8017E	Listing the host machines in the file system cluster failed because of an SSH communication error.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. You can list the host machines in a file system cluster by issuing the db2cluster command with the following parameters: -cfs -list -host. This message is returned when the db2cluster utility is unable to list the host machines in the file system cluster because of an SSH error.	Troubleshoot and correct the configuration of SSH components on the system, and then reissue the db2cluster command.
DBT8018E	The db2cluster command failed because `optionName` were specified multiple times.	You can create a replicated file system by using the db2cluster command. This message is returned when the db2cluster command is invoked with duplicate parameters.	Enter the command again by specifying the parameter only once.
DBT8019I	The db2cluster command to prepare the disks in the file system for replication has completed successfully.	You can convert an existing non-replicated file system to a replicated file system by using the db2cluster command. The db2cluster command enables replication in the following sequence. Assigns the list of disks in the file system to a valid redundancy group ID. Re-balances data between the two redundancy groups. This message is displayed when step 1 is completed successfully.	No response is required
DBT8020I	The db2cluster command to enable replication in the file system has completed successfully. Adding disks to redundancy group 2 may be required, replication of file system may also be required. An alert may be raised if file system rebalance is recommended. Issue 'db2instance -list' to determine if this alert has been raised.	You can convert an existing non-replicated file system to a replicated file system by using the db2cluster command. Use the following steps to complete replication: 1. Add disks to redundancy group 2 and the file system tiebreaker group. 2. If there are data in the file system prior to the conversion, use the "-replicate" option to replicate data. Depending on the placement of data on disks prior to the conversion, an alert may be raised if a file system rebalance is recommended by GPFS. Use "db2instance -list" to determine if this alert is raised. Note that both replication and rebalance of a file system are I/O intensive commands and are recommended to run at off-peaked hours only. This message is displayed for your information only.	1. If there are data in the file system prior to the conversion, use the "-replicate" option to replicate data. 2. Determine whether any alerts were raised by issuing the following command: db2instance -list 3. View the details for any alerts. db2instance -list -verify 4. If there is an 'unbalanced' alert, use the "-rebalance" option to rebalance data.
DBT8021I	Started the disks in the file system. This action may take some time to complete.	This message is returned for your information only.	No response is required
DBT8022I	The db2cluster command to start the disks in the file system has completed successfully.	This message is returned for your information only.	No response is required.
DBT8023E	The db2cluster command to start the disks in the file system has failed.	The db2cluster command failed to start the disks in the filesystem because of an internal error.	Contact IBM support to determine the reason for the failure.
DBT8024E	An invalid file system was specified.	The db2cluster command failed because the specified file system does not exist or is invalid.	Enter the command again using valid values.
DBT8025E	The db2cluster command failed because the specified file system already has replication enabled.	You can convert an existing non-replicated file system to a replicated file system by using the db2cluster command. This message is displayed when replication is already enabled in the specified file system.	No response is required.
DBT8026E	The db2cluster command failed to add disks without redundancy group id specification to the replicated file system.	You can add disks to a replicated file system by using the db2cluster command. This message is displayed when an attempt to add a disk without redundancy group id specification to a replicated file system was made.	Enter the command again to add disks into the file system by specifying '-rdncy_grp_id' option.
DBT8027I	The db2cluster command has successfully associated the redundancy group id to the specified member or CF.	This message is returned for your information only.	No response is required.
DBT8028I	The db2cluster command has successfully removed the redundancy group id `ID` from the specified member or CF.	This message is returned for your information only.	No response is required.
DBT8029E	The db2cluster command failed to add the redundancy group id to the specified member or CF. Reason code: `StringToken`.	You can add the redundancy group id to a member or CF in a Geographically Dispersed pureScale Cluster (GDPC) by using the db2cluster command. This message is displayed when an error occurs because of one of the following reasons: 1. The member or CF is already associated with a redundancy group id. 2. Invalid redundancy group id was specified. 3. Internal system error.	Perform according action for the displayed reason code: 1. Run "db2cluster -list -rdncy_grp_id" to list the current association. 2. Redundancy group id must be 1 or 2, specify the appropriate value and re-issue the command. 3. Contact IBM support to determine the reason for the failure.
DBT8030E	The db2cluster command failed to change the redundancy group id of the specified member or CF. Reason code: `StringToken`.	You can change the existing redundancy group id of a member or CF in a Geographically Dispersed pureScale Cluster (GDPC) by using the db2cluster command. This message is displayed when an error occurs because of one of the following reasons: 1. The specified member or CF does not have a redundancy group id associated to it. 2. Invalid redundancy group id was specified. 3. Internal system error.	Perform according action for the displayed reason code: 1. Use '-add' option to associate the specified member or CF to a redundancy group id. 2. Redundancy group id must be 1 or 2, specify the appropriate value and re-issue the command. 3. Contact IBM support to determine the reason for the failure.
DBT8031E	The db2cluster command failed to remove the redundancy group id `ID` from the specified member or CF. Reason code: `StringToken`.	You can remove the redundancy group id of a member or CF in a Geographically Dispersed pureScale Cluster(GDPC) by using the db2cluster command. This message is displayed when an error occurs while removing disks from the file system. The specified reason code indicates one of the following errors occurred: 1. The specified member or CF does not have a redundancy group id associated to it. 2. Internal system error.	1. Run "db2cluster -list -rdncy_grp_id" to list the current association. 2. Contact IBM support to determine the reason for the failure.
DBT8032I	The db2cluster command has successfully replicated the file system. Rebalance may be required, if it is required, an alert will be generated automatically. Issue 'db2instance -list' to determine if alert has been raised.	You can replicate a file system by issuing the db2cluster command with the -replicate option. This message is returned after the db2cluster utility successfully replicates the specified file system.	1. Determine whether any alerts were raised by issuing the following command: db2instance -list 2. View the details for any alerts. db2instance -list -alert 3. If there is an 'unbalanced' alert, rebalance the file system by issuing the following command: db2cluster -cfs -rebalance Filesystem-name
DBT8033E	The db2cluster command to replicate the file system has failed.	The db2cluster command failed to replicate the files system because of an internal error.	Correct the error displayed on screen and re-issue the command.
DBT8034I	File system replication is in progress. This operation may take some time to complete.	This informational message indicates that file system is being replicated between the redundancy groups.	No action is required.
DBT8035W	Addition of disks to the file system is in progress. This operation may need you to replicate data and rebalance the file system.	You can add disks to the file system by using the db2cluster command. If a new redundancy group is created by adding disks to the file system, you may need to replicate data between the redundancy groups. Adding disks to your file system may also need you to rebalance your file system. You can perform both replication and rebalancing operations by using the db2cluster command.	Perform replication and/or rebalancing operations as required. Because both the operations are file input and output intensive, it is recommended that you run them when there is lower system activity in the cluster.
DBT8036I	The db2cluster command has successfully added disks to the file system `FSname`. Replication of file system may be required if the file system has non-replicated data prior to this operation. Rebalance may also be required after replication is completed. If it is required, an alert will be generated. Issue 'db2instance -list' to determine if this alert has been raised.	You can add disks to a replicated file system by using the db2cluster command. This message is returned after the db2cluster utility successfully adds the device into the specified file system.	1. Use -replicate option to replicate data 2. Determine whether any alerts were raised by issuing the following command: db2instance -list 3. View the details for any alerts. db2instance -list -verify 4. If there is an 'unbalanced' alert, rebalance the file system by issuing the following command: db2cluster -cfs -rebalance Filesystem-Name Note that both replication and rebalance of a file system are I/O intensive commands and are recommended to run at off-peaked hours only.
DBT8037W	Removal of disks from the file system is in progress. This operation may need you to replicate data and rebalance the file system.	You can remove disks from the file system by using the db2cluster command. If the removal of the disk has made some replica data inaccessible you may need to restore all replicated files in the file system to their designated degree of replication. Removing disks from your file system may also need you to rebalance your file system. You can perform both replication and rebalancing operations by using the db2cluster command.	Perform replication and/or rebalancing operations as required. Because both the operations are file input and output intensive, it is recommended that you run them when there is lower system activity in the cluster.
DBT8038I	The db2cluster command has successfully removed the disk from the file system `Filesystem-Name`. Replication of file system may be required to restore all replicated files in the file system to their optimal degree of replication in case the removal of the disk has made future replication impossible. Rebalance may also be required after replication is completed. If it is required, an alert will be generated. Issue 'db2instance -list' to determine if this alert has been raised.	You can remove disks from a replicated file system by using the db2cluster command. This message is returned after the db2cluster utility successfully removes the disk from the specified file system.	1. Use -replicate option to restore all replicated files in the file system to their optimal degree. 2. Determine whether any alerts were raised by issuing the following command: db2instance -list 3. View the details for any alerts. db2cluster -list -alert 4. If there is an 'unbalanced' alert, rebalance the file system by issuing the following command: db2cluster -cfs -rebalance Filesystem-Name Note that both replication and rebalance of a file system are I/O intensive commands and are recommended to run at off-peaked hours only.
DBT8039E	The option `StringToken` provided to the command is invalid.	This message is returned when the usage of one of the options in the command is invalid.	Run 'db2cluster -help' for correct usage and enter the command again by specifying valid options.
DBT8040E	The db2cluster command failed to list the redundancy group id of the specified member or CF.	You can list the redundancy group id of a member or CF in a Geographically Dispersed pureScale Cluster (GDPC) by using the db2cluster command. This message is displayed when an error occurs while retrieving redundancy group id of the specified member or CF.	Contact IBM support to determine the reason for the failure.
DBT8041E	This command cannot be specified with -cm or -cfs option.	You can add, change, remove, or list the redundancy group id of a member or CF in a Geographically Dispersed pureScale Cluster (GDPC) by using the db2cluster command. This message is displayed when option '-cm' or '-cfs' is specified.	Enter the command again without specifying '-cm' or '-cfs' option.
DBT8042E	The db2cluster command to remove the disk from the specified filesystem has failed. reason code: `Reason-code`	You can remove disks from the file system by using the db2cluster command. This message is displayed when an error occurs while removing the disk from the file system. The specified reason code indicates one of the following errors occurred: 1. Error detected during the process of rebalancing and fixing file system failure group. 2. Access to the specified disk denied. 3. Invalid parameter detected in the command. 4. No free space on the file system is available. 5. Internal system error, check diagnostic log for more information.	Check diagnostic log for more information.
DBT8043E	The db2cluster command failed to add disks with redundancy group specification to the non-replicated file system.	You can add disks to a replicated file system by using the db2cluster command. This message is displayed when an attempt to add a disk with redundancy group specification to a non-replicated file system was made.	Enter the command again to add disks into the file system without specifying '-rdncy_grp_id' option.
DBT8044E	Creating the file system failed because of a problem with the disk. File system name: `file-system-ID`. Disk name: `disk-ID`. Disk problem reason code: `reason-code`.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to create a clustered file system, but there is a problem with the specified disk. The reason code indicates more specifically what the underlying problem is: 1 There was a general disk error. 2 The disk does not support SCSI-3 Persistent Reserve technology. 3 The disk is not directly attached to all the hosts in the shared file system cluster. 4 The disk is already in use by another GPFS file system, the OS file system, the OS itself, or something other than this GPFS file system. 5 The disk was not found. 6 The disk is already in use as a device container for a table space in a database. 7 The disk is already in use by a GPFS file system. A concurrent create file system or add disk to file system may have been run with the same disk. 8 The disk was not found in the partition block allocation file, /proc/partitions.	Perform the following troubleshooting steps: Verify the state and configuration of the disk and then reissue the command specifying a disk that is ready for use. Review related error information in the diagnostic (db2diag) log files. Additional user response corresponding to particular reason codes: 4 To determine where the disk is being used and to remove it: Locate which system is using the disk: If the disk is in use by another GPFS cluster file system, it will be in the disk list of one of the file systems on one of the clusters, which can be determined by running, on a host on each GPFS cluster, db2cluster -cfs -list -filesystem to get a list of file systems for that cluster and db2cluster -cfs -list -filesystem `file-system-ID` on each file system listed in that cluster. If the disk is in use by (mounted on) the OS file system, then it will be listed in the list of mounts on the OS: Linux: /proc/mounts HP, SUN: /etc/mnttab AIX: mntctl() NT: GetLogicalDriveStrings() Otherwise the disk is in use by the OS and is not suitable for use. Remove it from that system, if it is safe to do so. If the disk is in use by another GPFS file system, run db2cluster -cfs -remove -disk `disk-ID` -filesystem `file-system-ID` on a host of the cluster containing that file system. If the disk is in use by (mounted on) the OS file system, unmount it if it is safe to do so. 5 Ensure the disk is at the given disk path and is listed in /proc/partitions. 6 See the db2diag.log for more information as to which instances and databases are using the disk. If it is safe to do so, run drop db `database-ID` on each database mounted on the disk path to stop the disk from being used as a device container for table spaces in those databases. 7 To determine where the disk is being used and to remove it, on a host on each GPFS cluster: Run db2cluster -cfs -list -filesystem to get the list of file systems in the cluster. Run db2cluster -cfs -list -filesystem `file-system-ID` -disk on each file system listed to determine which file system the disk is in. 8 Ensure the input for -disk is a valid disk and can be found in /proc/partitions.
DBT8045E	The target host `Hostname1` cannot be accessed from the current host `Hostname2`.	This operation requires access from the current host to the target host with either the instance user or DB2 cluster services administrator user. In some cases, both are required. Failure can be caused by remote access setup incorrectly or the remote host is unavailable.	1. Ensure the remote host is accessible from the current host. 2. The instance user and the DB2 cluster services administrator user can execute commands remotely from the current host to the remote host.
DBT8046E	Removing the disk from the file system failed because of a problem with the disk. Disk name: `disk-ID`. File system: `file-system-ID`. Reason code: `reason-code`.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to remove a disk from the file system, but there is a problem with the specified disk. The reason code indicates more specifically what the underlying problem is: 1 There was a general disk error. 2 The disk is in use by another GPFS file system, the OS file system, the OS itself, or something other than this GPFS file system. 3 The disk was not found. 4 The disk is already in use as a device container for a table space in a database. 5 The disk was not found in the partition block allocation file, /proc/partitions.	Perform the following troubleshooting steps: Verify the state and configuration of the disk and then reissue the command specifying a disk that is ready for use. Review related error information in the diagnostic (db2diag) log files. Additional user response corresponding to particular reason codes: 2 To determine where the disk is being used and to remove it: Locate which system is using the disk: If the disk is in use by another GPFS cluster file system, it will be in the disk list of one of the file systems on one of the clusters, which can be determined by running, on a host on each GPFS cluster, db2cluster -cfs -list -filesystem to get a list of file systems for that cluster and db2cluster -cfs -list -filesystem `file-system-ID` on each file system listed in that cluster. If the disk is in use by (mounted on) the OS file system, then it will be listed in the list of mounts on the OS: Linux: /proc/mounts HP, SUN: /etc/mnttab AIX: mntctl() NT: GetLogicalDriveStrings() Otherwise the disk is in use by the OS and is not suitable for use. Remove it from that system, if it is safe to do so. If the disk is in use by another GPFS file system, run db2cluster -cfs -remove -disk `disk-ID` -filesystem `file-system-ID` on a host of the cluster containing that file system. If the disk is in use by (mounted on) the OS file system, unmount it if it is safe to do so. 3 Ensure the disk is at the given disk path and is listed in /proc/partitions. 4 See the db2diag.log for more information as to which instances and databases are using the disk. If it is safe to do so, run drop db `database-ID` on each database mounted on the disk path to stop the disk from being used as a device container for table spaces in those databases. 5 Ensure the disk is actually a disk and can be found in /proc/partitions.
DBT8047E	The db2cluster command failed because the '-rdncy_grp_id' option is missing for one of the disk lists.	You can create a replicated file system by using the db2cluster command. This message is returned when '-rdncy_grp_id' option is missing in one of the disk lists.	Check 'db2cluster -help' and enter the command again with correct usage.
DBT8048E	The shared file system cluster `file-system-ID` was successfully created, but the GPFS ready script was not available. The cluster cannot be started until the script is copied to the local host at /var/mmfs/etc/gpfsready.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to create a shared file system cluster, but the gpfsready script was not found.	To start the shared file system cluster you must copy the gpfsready script to /var/mmfs/etc/ and run db2cluster -cfs -start -all
DBT8049E	The shared file system cluster `file-system-ID` was successfully created, but the disk `disk-ID` provided was invalid. Reason code: `reason-code`.	You can manage your DB2 cluster using the db2cluster utility. The database product installer invokes the db2cluster command to perform some install and instance management operations too. This message is returned when an attempt is made to create a clustered file system, but there is a problem with the specified disk. The reason code indicates more specifically what the underlying problem is: 4 The disk is already in this GPFS file system. 6 The disk was not found. 9 The disk was not found in the partition block allocation file, /proc/partitions.	Perform the following troubleshooting steps: Verify the state and configuration of the disk and then reissue the command specifying a disk that is ready for use. Review related error information in the diagnostic (db2diag) log files. Additional user response corresponding to particular reason codes: 4 To remove the disk, run db2cluster -cfs -remove -disk `disk-ID` -filesystem `file-system-ID`. 6 Ensure the disk is at the given disk path and is listed in /proc/partitions. 9 Ensure the disk is actually a disk and can be found in /proc/partitions.
DBT8050E	Disk `disk-ID` could not be accessed from this host. Ensure that user `user-ID` has read and write permission.	The user does not have sufficient ID permissions to access the disk.	1 Ensure your user ID is root or is the same as the user ID of the owner of the disk. 2 Rerun the command.
DBT8051E	The db2cluster command failed to create the log directory: `directory-name`. Reason code: `Reason-code`.	The db2cluster -verify command creates a directory within the DIAGPATH or ALT_DIAGPATH directory to dump the log files generated during its execution. This message is displayed when the command fails to create such a directory. The specified reason code indicates one of the following errors occurred: 1 Access denied to the directory. 2 The disk quota has been exhausted. 3 An input/output error occurred. 4 The length of the file name exceeds the maximum size. 5 A directory component in the path does not exist. 6 No free space on the file system. 7 A component of the path is not a directory. 8 The file is part of a read-only file system. 9 Too many symbolic links. 10 File is on a remote system and the link to that system is not active. 11 Internal error occurred.	The action corresponding to the reason code is: 1 Provide the current user read and write permissions to the directory or run the command from a userid that has read and write permissions to the directory. 2 Clean up the disk or add more space to the disk. 3 Fix the hard drive or any hardware problem caused elsewhere. 4 Either allocate a greater file name limit to your shell or use a shorter name. 5 Check if the path specified is valid. 6 Allocate more space on the file system. 7 Check if the path specified is valid. 8 Provide write permission on the file system. 9 Fix this issue as per the respective OS specifications. 10 Ensure that the file in question can be accessed. 11 This is an internal error. Check the db2diag.log and contact IBM Support.
DBT8052E	The db2cluster command to verify the state of the cluster failed to get information about the instance. Reason code: `Reason-code`.	The db2cluster -verify command creates a directory within the DIAGPATH or ALT_DIAGPATH directory to dump the log files generated during execution. This new directory needs to be instance user owned. This message is displayed when the command fails to get the instance user ID or instance group ID. The specified reason code indicates one of the following errors occurred: 1 No instance available. 2 DB2PATH is not set. 3 An internal error occurred.	The action corresponding to the reason code is: 1 Check the state of the pureScale instance. 2 Set the DB2PATH environment variable to the directory where the DB2 database product is installed. This is usually required on Windows 32-bit operating systems. 3 This is an internal error. Check the db2diag.log and contact IBM Support.
DBT8053E	The `db2-command` command failed because the directory `directory-name` is not accessible.	This message is returned when a directory is either missing or inaccessible.	Check the ownership and permissions of the directory and its parent directories and make sure they are accessible by the current user. If this problem persists, check the db2diag.log or contact IBM Support.
DBT8054W	Host `host-name` has successfully entered file system maintenance mode. However, the GPFS kernel module cannot be unloaded. The host must be rebooted before exiting maintenance mode to return to normal operation.	This message is returned when the GPFS kernel module cannot be unloaded when entering maintenance mode. This can be caused by unfinished processing or strayed processes holding on to resources allocated in the module. A reboot is required to remove the GPFS module from system memory before GPFS can be restarted. Attempting to restart GPFS before a reboot can lead to unexpected result such as system crash or operating system kernel panic.	Perform a reboot before exiting maintenance mode and return GPFS to normal operation.
DBT8055E	Validation of `string-token` failed because directory /var/db2/db2ssh does not exist.	You can issue validation check of db2locssh and db2scp command using db2cluster -verify utility. This message is returned when mandatory directory of db2ssh cannot be found at /var/db2/db2ssh.	Search for the topic db2locssh in IBM Knowledge Center or contact IBM software support for assistance
DBT8056E	Validation of `string-token` failed because the non-root user id `db2sshid-id` has different GID and UID on host `host-name1` and host `host-name2`.	You can issue validation check of db2locssh and db2scp command using db2cluster -verify utility. In order for the successful execution of db2locssh and db2scp, a non-root user id for db2ssh must be created with same GID and UID among all hosts. This message is returned when the non-root user id used for db2ssh is not created with same GID and UID.	1 Check /etc/passwd and /etc/group to ensure that the db2sshid is created with same UID and GID on each host. 2 Search for the topic db2locssh in IBM Knowledge Center or contact IBM software support for assistance.
DBT8057E	Validation of `string-token` failed because error is returned from the execution of `string-token`.	You can issue validation check of db2locssh and db2scp command using db2cluster -verify utility. This message is returned because execution command of db2locssh or db2scp reported error.	Check system log for further diagnostics or contact IBM software support for assistance
DBT8058E	Validation of `string-token` failed because db2locssh is not associated with a non-root db2sshid.	You can issue validation check of db2locssh and db2scp command using db2cluster -verify utility. This message is returned when db2locssh has not yet associated with a non-root db2sshid on the current host.	Search for the topic db2locssh in IBM Knowledge Center or contact IBM software support for assistance
DBT8059E	Validation of db2ssh failed, refer to the following log and trace for further diagnostics: `Log-path`	You can validate the setup of db2locssh and db2scp using the db2cluster -verify utility. This message is returned when the execution of validation failed, you can find more detail and explanation in the log and trace paths displayed on the screen for further diagnostics	1 Check the given log and trace for more details and diagnostics 2 Search for the topic db2locssh in IBM Knowledge Center and verify the current db2locssh setup is correct 3 Contact IBM software support for assistance
DBT8060W	db2cluster has detected Storage Scale is configured with `string-token` as its remote shell command and `string-token` as its remote copy command.	You can validate the setup of db2locssh and db2scp using the db2cluster -verify utility. This warning message is returned when a mix configuration of db2locssh and scp or ssh and db2scp is detected in the current Storage Scale cluster. For the best practice, mix configuration of db2locssh/db2scp and ssh/scp is not suggested.	1 Issue mmlscluster command to check the current configuration of Storage Scale 2 Search for the topic db2locssh in IBM Knowledge Center and verify the current db2locssh setup is correct 3 Contact IBM software support for assistance.
DBT8061E	The command failed because one or more hosts in the CFS cluster are still active.	This message is returned when current operation requires all hosts in the CFS cluster to be offline.	Stop all hosts in the cluster with the command 'db2cluster -cfs -stop -all'. Re-issue the failed command after all hosts in the CFS cluster have been stopped. If the failure persists, contact IBM software support for assistance.
DBT8062E	The command failed because one or more hosts in the CFS cluster are not active.	This message is returned when current operation requires all hosts in the CFS cluster to be online.	Start all hosts in the cluster with the command 'db2cluster -cfs -start -all'. Re-issue the failed command after all hosts in the CFS cluster are in active state. If the failure persists, contact IBM software support for assistance.
DBT8063E	The db2cluster command failed because cluster configuration repository cannot be enabled.	This message is returned when cluster configuration repository in the CFS cluster cannot be enabled.	Cluster configuration repository requires the gpfs.gskit package to be installed and all hosts in the cluster to be online. Verify that the gpfs.gskit package is installed properly on all hosts first. After that, run 'db2cluster -cfs -list -host -state' to ensure all hosts are in STARTED state. If any host is in a non-STARTED state, try restarting them all with the 'db2cluser -cfs -start -all' command before re-attempting the original failed db2cluster command. If the failure persists, contact IBM software support for assistance.
DBT8064W	Validation of replicated file system failed because at least one disk in the file system `fs-name` is associated with redundancy group ID 3.	You can validate the configuration of replicated file system using the db2cluster -verify utility. This warning message is returned when at least one disk in the file system is associated with redundancy group ID 3.	1 Verify if any disk is associated with redundancy group ID 3 in the file system by running command 'db2cluster -cfs -list -filesystem fs-name -disk'. 2 Search for the topic 'Post-upgrade task for cluster using GPFS replication' in IBM Knowledge Center to convert the redundancy group ID associated with the disk. 3 Contact IBM software support for assistance.
DBT8065E	File system `fs-name` can not be deleted because the associated mount resource exists in the resource model.	You can remove a file system in Storage Scale using db2cluster utility. This message is returned when the file system mount record has been found in the resource model.	1 Ensure the target file system is no longer in use by DB2 2 Contact IBM software support for assistance.
DBT8066E	Unable to enter maintenance mode on host `host-name`. Reason code = `reason-code`.	1 Another host is in the process of entering maintenance. 2 Unsupported quorum type detected for peer domain. 3 Unable to get the path to the sqllib_shared directory.	1 Re-issue this command once the command on the other host has completed. 2 Re-issue this command after changing the peer domain tiebreaker to disk or majority via the db2cluster command. 3 Re-issue this command after verifying that DB2INSTANCE is set to valid value and the shared filesystem is accessible on the host.
DBT8067E	Re-issue the same `command` command with `debug-option` option to gather additional diagnostic data.	This message is returned to gather additional information that would be helpful in diagnosing the root cause. The location of the log file will be printed on the screen.	Contact IBM support with the generated logs to determine the reason for the failure.
DBT8068E	Error occurred while exiting maintenance mode on host `host-name`. Reason code = `reason-code`.	1 Unable to enable current host as a quorum node in the peer domain. 2 Unable to enable current host as a quorum node in the Storage Scale cluster. 3 Internal error has been detected.	1 Collect db2support -purescale and contact IBM support for assistance. 2 Collect /var/adm/ras/mmfs.log.* logs on the specified host and contact IBM support for assistance. 3 Contact IBM support with the generated log for assistance.
DBT8069E	Error occurred while verifying the maintenance state of hosts in the cluster. Reason code = `reason-code`.	1 Internal error has been detected. 2 You can only verify the maintenance state of the hosts in the cluster by running the db2cluster command as root user.	1 Contact IBM support with the generated log for assistance. The maintenance state of individual hosts can be checked by running 'db2cluster -cm -verify -maintenance' command locally on each host. 2 Rerun the command as root user.
DBT8070E	Database `database-name` could not be found in the cluster.	This message is returned when the database name or alias specified in the command is not an existing database.	Ensure the database specified in the command exists in the system database directory. If this problem persists, check the db2diag.log or contact IBM Support.
DBT8071E	No start database manager command was issued.	This message is returned when the start database manager command has not been processed.	Issue a start database manager command and resubmit the current command.
DBT8072E	The `db2-command` command failed because the file `file-name` is not accessible.	This message is returned when a file is either missing or inaccessible.	Check the ownership and permissions of the file and make sure they are accessible by the current user. If this problem persists, check the db2diag.log or contact IBM Support.
DBT8200E	Ethernet resource could not be created. Reason code = `reason-code`.	This message is returned when a network interface resource could not be created. 1 The host specified is not a member of the cluster. 2 The network interface specified does not exist. 3 The resource attempted to be created already exists. 4 Passwordless SSH is not configured with the destination host. 5 Internal error has been detected.	1 Run the 'db2cm -list' command and check under 'Node Information' to verify whether the specified host exists. If the host exists, rerun the command with the correct host. 2 Please verify the network interface specified and retry with the corrected value. 3 Run the 'db2cm -list' command and check under 'Resource Information' to verify if the resource exists already. 4 Please configure passwordless SSH with the destination host and retry the command. 5 Please collect db2support and engage IBM Support. If issues still persist, please collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8201E	Ethernet resource could not be deleted. Reason code = `reason-code`.	This message is returned when a network interface resource could not be deleted. 1 The host specified is not a member of the cluster. 2 The resource attempted to be deleted does not exist. 3 Internal error has been detected.	1 Run the 'db2cm -list' command and check under 'Node Information' to verify whether the specified host exists. If the host exists, rerun the command with the correct host. 2 Run the 'db2cm -list' command and check under 'Resource Information' to verify if the resource actually exists. 3 Please collect db2support and engage IBM Support. If issues still persist, please collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8202E	Database resource could not be created. Reason code = `reason-code`.	This message is returned when a database resource could not be created. 1 The specified HADR database resource already exists. 2 The Db2 instance specified does not exist on the local host. 3 The HADR database specified is not in PEER state. 4 The HADR_PEER_WINDOW db configuration parameter needs to be at least 60 seconds. 5 The specified HADR database does not exist. 6 Network interface resources need to be configured for both hosts before creating a database resource. 7 An internal error occurred.	1 Run the 'db2cm -list' command to verify whether the HADR database resource already exists. If the resource already exists, delete the resource and rerun the 'db2cm -create -db' command. 2 Verify whether the specified instance exists on the local host. If the instance exists, rerun the 'db2cm -create -db' command. 3 Run the db2pd -hadr -db DB_NAME command to verify the HADR state of the database. 4 Update the HADR_PEER_WINDOW db configuration parameter to at least 60 seconds and then rerun the 'db2cm -create -db' command. 5 Run the db2pd -hadr -db DB_NAME command to verify whether the database exists and is activated. If the database is not activated, activate the database and then rerun the 'db2cm -create -db' command. 6 Run the 'db2cm -list' command to verify whether a network interface resource is configured for both hosts. If it is not configured on either host, create the network resource first and then rerun the 'db2cm -create -db' command. 7 Collect db2support and engage IBM Support. If issues still persist, please collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8203E	Database resource could not be deleted. Reason code = `reason-code`.	This message is returned when a database resource could not be deleted. 1 The HADR database resource that you are attempting to delete does not exist. 2 An internal error occurred.	1 Run the 'db2cm -list' command to verify whether the HADR database resource exists. 2 Collect db2support and engage IBM Support. If issues still persist, please collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8204E	Instance resource could not be created. Reason code = `reason-code`.	This message is returned when an instance resource could not be created. 1 The Db2 instance specified does not exist on the host. 2 The hostname specified is not a member of the cluster. 3 The instance resource attempted to be created already exists. 4 Passwordless SSH is not configured with the destination host. 5 An internal error occurred.	1 Make sure a Db2 instance exists on the host provided. 2 Run the 'db2cm -list' command to verify whether the host exists. 3 Run the 'db2cm -list' command to verify whether the instance resource already exists. 4 Configure passwordless SSH with the destination host and retry the command. 5 Collect db2support and engage IBM Support. If issues still persist, please collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8205E	Instance resource could not be deleted. Reason code = `reason-code`.	This message is returned when an instance resource could not be deleted. 1 The hostname specified is not a member of the cluster. 2 The instance resource attempted to be deleted does not exist. 3 Passwordless SSH is not configured with the destination host. 4 An internal error occurred.	1 Run the 'db2cm -list' command to verify if the host exists. 2 Run the 'db2cm -list' command to verify if the instance resource exists. 3 Configure passwordless SSH with the destination host and retry the command. 4 Collect db2support and engage IBM Support. If issues still persist, please collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8206E	Invalid command syntax. Refer to db2cm log or run 'db2cm -help' for more details. Reason code = `reason-code`.	This message is returned when a syntax error is made in the db2cm command. 1 More than two hosts have been specified. Please specify only two hosts. 2 Input parameter must not exceed the maximum length. Please specify a new value. 3 Invalid arguments and value parameters specified inside the command line input. 4 The command line input is not a valid db2cm command. 5 The specified command is not applicable to the current HA model of the cluster. 6 Internal error has been detected.	1 Specify no more than two hosts inside the command. Syntax can be checked in db2cm documentation or using 'db2cm -help'. 2 Verify that the input parameter is within the maximum length. Refer to the db2cm log or check the db2cm documentation for more details. 3 Check the command syntax against db2cm documentation or using 'db2cm -help'. 4 Check the command syntax against db2cm documentation or using 'db2cm -help'. 5 Please specify a command that is applicable to the current HA model of the cluster. 6 Please collect db2support and engage IBM Support. If issues still persist, please collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8207E	Instance type could not be determined. Reason code = `reason-code`.	This message is returned when the instance type could not be determined. 1 DB2INSTANCE has not been specified while running under root user. 2 The instance specified does not exist. 3 Internal error has been detected.	1 Set the DB2INSTANCE environment variable to the instance owner. 2 Verify that the instance specified exists on the local host and try again. 3 Please collect db2support and engage IBM Support. If issues still persist, please collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8208E	Failed to disable resource `resource` on host `host`. Reason code: `reason-code`.	This message is returned when an attempt to disable a resource has failed. 1 The instance resource specified does not exist. 2 The host specified is not a member of the cluster. 3 Passwordless SSH is not configured with the destination host. 4 Unable to run db2cm on the remote host. 5 Unable to disable one or more databases. 6 Internal Error.	1 Run the 'db2cm -list' command to verify if the instance resource exists. If the resource is found, try to disable the resource by using the correct instance name. 2 Run the 'db2cm -list' command and check under 'Node Information' to verify whether the specified host exists. If the host exists, rerun the command with the correct host. 3 Ensure passwordless SSH is configured with the destination host and retry the command. 4 An error has occurred while running db2cm on the remote host. Check the diagnostic log (/tmp/db2cm/db2cm.log.*) for more information. 5 Ensure the HADR database is properly configured by ensuring the database is activated on both primary and standby instances. 6 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8209E	Failed to enable resource `resource` on host `host`. Reason code: `reason-code`.	This message is returned when an attempt to enable a resource has failed. 1 The instance resource specified does not exist. 2 The host specified is not a member of the cluster. 3 Passwordless SSH is not configured with the destination host. 4 Unable to run db2cm on the remote host. 5 An instance attempting to be enabled has not been started.Unable to enable an instance resource because the corresponding Db2 instance has not been started. 6 Unable to enable one or more databases. 7 Internal Error.	1 Run the 'db2cm -list' command to verify if the instance resource exists. If the resource is found, try to enable the resource by using the correct instance name. 2 Run the 'db2cm -list' command and check under 'Node Information' to verify whether the specified host exists. If the host exists, rerun the command with the correct host. 3 Ensure passwordless SSH is configured with the destination host and retry the command. 4 An error has occurred while running db2cm on the remote host. Check the diagnostic log (/tmp/db2cm/db2cm.log.*) for more information. 5 Run db2start on the instance attempting to be enabled to ensure it has started. 6 Ensure the HADR database is properly configured by ensuring: - The database is activated on both primary and standby instances. - At least one instance associated with the database is started and managed - Run db2pd -db DB_NAME -hadr and confirm: - HADR_CONNECT_STATUS=CONNECTED - HADR_STATE=PEER 7 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8210E	Failed to disable database resource `database`. Reason code = `reason-code`.	This message is returned when an attempt to disable a database resource has failed. 1 The host specified is not a member of the cluster. 2 Unable to disable the database resource corresponding to the database name specified. 3 Internal Error.	1 Run the 'db2cm -list' command and check under 'Resource Information' to verify if the database resource exists and retry with the correct resource. 2 Ensure the HADR database is properly configured by ensuring the database is activated on both primary and standby instances. 3 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8211E	Failed to enable database resource `database`. Reason code = `reason-code`.	This message is returned when an attempt to enable a database resource has failed. 1 The host specified is not a member of the cluster. 2 Unable to enable the database resource corresponding to the database name specified 3 Internal Error.	1 Run the 'db2cm -list' command and check under 'Resource Information' to verify if the database resource exists and retry with the correct resource. 2 Ensure the HADR database is properly configured by ensuring: - The database is activated on both primary and standby instances. - At least one instance associated with the database is started and managed - Run db2pd -db DB_NAME -hadr and confirm: - HADR_CONNECT_STATUS=CONNECTED - HADR_STATE=PEER 3 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8212E	VIP resource could not be created. Reason code = `reason-code`.	This message is returned when a VIP resource could not be created. 1 The VIP resource attempted to be created already exists. 2 The Db2 instance resource does not exist on the host. 3 The database does not exist. 4 The IP address provided is already pingable. 5 The database resource does not exist. 6 Passwordless SSH is not configured with the destination host. 7 The IP address provided is not in the correct form. 8 The netmask provided is not in the correct form. 9 The VIP address is not within the same subnet as the host IP. 10 The Db2 partition resource does not exist. 11 The Db2 partition number provided is invalid. 12 An internal error has been detected.	1 Run the 'db2cm -list' command and check under 'Resource Information' to verify if the resource exists. If the resource needs to be recreated, delete it first and reissue the command. 2 Verify that the instance specified exists on the local host and try again. 3 Run db2pd -hadr -db DB_NAME to verify that the db exists and is activated. If the db is not activated, activate the db and retry the command. 4 Ensure that the IPv4 address provided is not pingable. 5 Run the 'db2cm -list' command and check under 'Resource Information' to verify if the database resource actually exists. 6 Ensure passwordless SSH is configured with the destination host and retry the command. 7 Ensure that the IPv4 address provided is in the correct format. - is x.x.x.x, where x is a value between 0 and 255. 8 Ensure that the netmask provided is in one of the two the correct formats: - CIDR format. - is x.x.x.x, where x is a value between 0 and 255. 9 Ensure that the VIP address is within the same subnet as the host IP. 10 Run the 'db2cm -list' command and verify under 'Resource Information' that the Db2 partition resource actually exists. 11 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8213E	VIP resource could not be deleted. Reason code = `reason-code`.	This message is returned when a VIP resource could not be deleted. 1 The resource attempted to be deleted does not exist. 2 The database resource does not exist. 3 The partition number provided does not exist. 4 The instance specified does not exist. 5 The database has multiple VIP resources. 99 An internal error has been detected.	1 Run the 'db2cm -list command and check under 'Resource Information' to verify if the resource exists. 2 Run the 'db2cm -list' command and check under 'Resource Information' to verify if the database resource exists. 3 Ensure that the partition number provided is associated with an existing partition. 4 Ensure that the instance name used is correct and verify that it exists. 5 Re-run the delete VIP command and specify the IP address to be deleted. 99 Collect db2support and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8214E	Failed to create the domain. Reason code: `reason-code`.	This message is returned when an attempt to create domain has failed. 1 A domain already exists on the current host. 2 Failed to start cluster manager services. 3 The number of partitions running on a host exceeds the set capacity limit. 4 A standby host has a Db2 partition defined on it. 5 The watchdog service is not set up on all hosts in the cluster. 6 An active host does not have a Db2 partition defined on it. 7 A given active host or standby host belongs to another domain. 8 The given domain name is already used. 9 Failed to find the specified Db2 instance for the cluster domain on the current host. 10 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that no other domain exists. 2 Check error messages in the system logs for further details. For Pacemaker, services are: pacemaker, pacemaker_remote, corosync 3 Balance the number of partitions per host, so that partitions are evenly distributed among active hosts. 4 Choose a standby host that does not have a Db2 partition defined on it. 5 Ensure that a watchdog service is set up on all hosts in the cluster. For more information, see the IBM documentation. 6 Choose an active host that has a Db2 partition defined on it. 7 Choose hosts that do not belong to another domain. 8 Specify a domain name that has not been used by another domain. 9 Create the domain on an existing instance node in your DPF Db2 cluster. 10 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8215E	Failed to delete the domain. Reason code: `reason-code`.	This message is returned when an attempt to delete domain has failed. 1 The domain specified does not exist. 2 Failed to stop cluster manager services. 3 The command for running remote operations is not configured between the current host and all cluster hosts. 4 The command for running remote operations is not configured between the current host and the quorum device. 5 The domain contains resources. 6 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Check error messages in the system logs for further details. For Pacemaker, services are: pacemaker, pacemaker_remote, corosync 3 Configure passwordless SSH as root with all cluster hosts. Refer to IBM documentation on how to configure passwordless ssh or db2locssh. 4 Verify that root passwordless SSH or db2locssh is configured correctly between the current host and the quorum device host. On all hosts, populate the known_hosts file by authenticating connectivity to both the long and short qualified host names for each host. Ensure all hosts are pingable. Once verified, rerun the command. Alternatively, run the 'db2cm -delete -domain <domainName> -force' command to skip cleaning up the quorum device host. 5 Delete the resources from the domain before deleting the domain. 6 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8216E	Failed to add host. Reason code: `reason-code`.	This message is returned when an attempt to add a CF has failed. 1 A domain does not exist. 2 The host is already part of the domain. 3 The command for running remote operations must be configured. 4 Failed to start cluster manager services. 5 The command must run from a quorum node in the domain. 6 Failed to configure the quorum device for the new host. 7 The command for running remote operations is not configured between the current host and all cluster hosts, including the current host, nor between the current host and the quorum device host. 8 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Run 'db2cm -list -host' command to verify the host specified is not already part of the domain. 3 Configure passwordless SSH as root with the specified host or specify a remote command via -remote_cmd and -remote_scp option. 4 Check error messages in the system logs for further details. For Pacemaker, services are: pacemaker, pacemaker_remote, corosync 5 Run the command from a quorum node in the domain. 6 The quorum device must be removed by running the 'db2cm -delete -qdevice -force' command. Rerun the 'db2cm -add -host <hostname>' command to add the desired host. Run the 'db2cm -create -qdevice <hostname>' command with the quorum device host name to recreate the quorum device. 7 Verify that root passwordless SSH or db2locssh is configured correctly between the current host and all cluster hosts, including the current host, and between the current host and the quorum device host. On all hosts, populate the known_hosts file by authenticating connectivity to both the long and short qualified host names for each host. Ensure all hosts are pingable. Once verified, rerun the command. 8 Collect db2support and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8217E	Failed to add member host. Reason code: `reason-code`.	This message is returned when an attempt to add a member host has failed. 1 A domain does not exist. 2 The host is already part of the domain. 3 The remote execution command must be configured. 4 Failed to start cluster manager services. 5 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Run 'db2cm -list -host' command to verify the host specified is not already part of the domain. 3 Configure passwordless SSH as root with the specified host or specify a remote command via -remote_cmd and -remote_scp option. 4 Check error messages in the system logs for further details. For Pacemaker, services are: pacemaker, pacemaker_remote, corosync 5 Collect db2support and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8218E	Failed to delete host. Reason code: `reason-code`.	This message is returned when an attempt to delete a host has failed. 1 A domain does not exist. 2 The host is not part of the domain. 3 Delete operation cannot run on the host specified. 4 A delete CF host command can only be issued from another CF host in the domain. 5 The command for running remote operations must be configured. 6 Failed to stop cluster manager services. 7 The host contains resources. 8 Failed to remove quorum device information for the host that is being removed. 9 The command for running remote operations is not configured between the current host and all cluster hosts, including the current host, nor between the current host and the quorum device host. 10 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Run 'db2cm -list -host' command to verify the host specified is not already part of the domain. 3 The command must be executed from another host. 4 The command must be executed from another CF host. 5 Configure passwordless SSH as root with the specified host or specify a remote command via -remote_cmd and -remote_scp option. 6 Check error messages in the system logs for further details. For Pacemaker, services are: pacemaker, pacemaker_remote, corosync 7 The resources must be removed before the host can be removed from the domain. 8 The quorum device must be removed by running the 'db2cm -delete -qdevice -force' command. Rerun the 'db2cm -remove -host <hostname>' command to remove the desired host. Run the 'db2cm -create -qdevice <hostname>' command with the quorum device host name to recreate the quorum device. 9 Verify that root passwordless SSH or db2locssh is configured correctly between the current host and all cluster hosts, including the current host, and between the current host and the quorum device host. On all hosts, populate the known_hosts file by authenticating connectivity to both the long and short qualified host names for each host. Ensure all hosts are pingable. Once verified, rerun the command. 10 Collect db2support and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8219E	Failed to create the fence agent. Reason code: `reason-code`.	This message is returned when an attempt to create the fence agent has failed. 1 A domain does not exist. 2 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Collect db2support and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8220E	Failed to delete the fence agent. Reason code: `reason-code`.	This message is returned when an attempt to delete the fence agent has failed. 1 A domain does not exist. 2 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Collect db2support and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8221E	Failed to create resources. Reason code: `reason-code`.	This message is returned when an attempt to create resources has failed. 1 A domain does not exist. 2 The resource model is already populated. 3 An internal error occurred. 4 Partitions are stopped. 5 The network interface configuration on host `hostname` is inconsistent with the CFS subnet configuration.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Delete the existing resources in the domain before attempting to recreate them. 3 Collect db2support and engage IBM Support. 4 All partitions must be started. Start any partitions that are stopped and retry the command. 5 Check that there is a network interface on host `hostname` that is on the same subnet as the configured CFS subnet: `subnet` as shown in the output mmlsconfig. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8234E	Failed to delete resources. Reason code: `reason-code`.	This message is returned when an attempt to delete resources has failed. 1 A domain does not exist. 2 Delete resource action is denied because of a mismatch of cluster topology detected between the db2nodes.cfg file and Db2 Instance Information Registry. It is commonly caused by a cluster currently with restart light process animated for one or more members. 3 Resources are not in the expected state. 4 An internal error occurred. 5 'db2cm -delete -resources -force' was attempted, but failed.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 If the failed member persists in a WAITING_FOR_FAILBACK state, determine and rectify the issue. Ensure the member fails back to its home host successfully prior to reissuing the command. 3 Verify that all Db2 member, idle, CF, CF control, and CF primary resources are offline. If they are not offline, run db2stop to put all member, idle, CF, CF control, and CF primary resources into offline state. If this issue persists, collect db2support data and engage IBM support. 4 Collect db2support data and engage IBM Support. 5 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8235E	Userid `user-name` does not have sufficient permission. Reason code: `reason-code`.	The user does not have sufficient permission to perform the cluster operation. 1 User does not have System Administrator privilege. 2 User does not have Cluster Administrator privilege.	1 Log on as a system administrator (root on UNIX) and rerun the command. 2 Log on as a user that has Cluster Administrator privilege or using the 'db2cm -grant -adminUser' command to grant the user Cluster Administrator privilege. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8236E	Userid `user-name` does not have sufficient permission to access instance `instance-name`. Obtain SYSADM, SYSMAINT, or SYSCTRL authority for this instance and reissue the command.	The user does not have sufficient permission to access the instance.	Obtain SYSADM, SYSMAINT, or SYSCTRL authority for this instance and reissue the command. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8237E	The db2cm command encountered an unexpected error during authorization check.	The db2cm command encountered an unexpected error during authorization check.	Collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8238E	Failed to grant Cluster Administrator privilege to user `user-name` on host `host-name`. Reason code:`reason-code`.	An attempt to grant the Cluster Administrator privilege to the user failed, as indicated by these reason codes: 1 The Cluster Administrator privilege has already been granted to the user. 2 An invalid userid was specified. 3 An invalid host name was specified. 4 An unexpected error occurred.	1 No further action is needed. 2 Rerun the command using a valid userid. 3 Rerun the command using a valid host name. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8239E	Failed to revoke Cluster Administrator privilege from user `user-name` on host `host-name`. Reason code:`reason-code`.	An attempt to revoke the Cluster Administrator privilege from the user failed, as indicated by these reason codes: 1 The Cluster Administrator privilege has already been revoked from the user. 2 An invalid userid was specified. 3 An invalid host name was specified. 4 An unexpected error occurred.	1 No further action is needed. 2 Rerun the command using a valid userid. 3 Rerun the command using a valid host name. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8240E	The environment variable DB2INSTANCE is not defined or is invalid, or the instance directory is not accessible.	Failed to determine the Db2 instance owner. The environment variable DB2INSTANCE is not defined , is invalid, or the instance directory is not accessible.	Ensure that the environment variable DB2INSTANCE is set to a valid Db2 instance name. Also, verify that the instance directory is accessible. For commands that do not require access to the instance directory, such as "db2cm -dump", rerun the command as the root user. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8242E	Failed to retrieve cluster information on host. Reason code: `reason-code`.	This message is returned when an attempt to list cluster information on host fails. 1 The current node is not online in the cluster manager domain. 2 An internal error occurred.	1 Start the cluster manager services on the current host and rerun the command. 2 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8243E	Failed to add mount point to the exception list. Reason code: `reason-code`.	This message is returned when an attempt to add mount point to the exception list has failed. 1 The specified mount point is already in the exception list. 2 The specified mount point is not a directory. 3 An internal error occurred.	1 No action required. 2 Check the specified mount point is a directory or not. 3 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8244E	Failed to remove mount point from the exception list. Reason code: `reason-code`.	This message is returned when an attempt to remove mount point from the exception list has failed. 1 The specified mount point is not in the exception list. 2 An internal error occurred.	1 No action required. 2 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8245E	Failed to add mount resources for database `database-name`. Reason code: `reason-code`.	Attempt to add mount resources for the database failed, as indicated by these reason codes: 1 A domain does not exist. 2 The database is not found in the database directory. 3 The database cannot be activated on some nodes. 4 The filesystem type is not supported. 5 The Db2 partition resource does not exist in the resource model. 5 The instance specified does not exist. 7 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Ensure the database name is correct and catalogued in the database directory, then rerun the command. 3 Ensure that the database can be activated on all nodes, then rerun the command. 4 Refer to the IBM Knowledge Center for the list of supported filesystem types. 5 Verify that the specified partition number is correct. 6 Run the 'db2cm -list' command to verify that the specified instance exists. 7 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8246E	Failed to remove mount resources for database `database-name`. Reason code: `reason-code`.	Attempt to remove mount resources for the database failed, as indicated by these reason codes: 1 A domain does not exist. 2 There is no mount resource for the database. 3 Cannot delete mount resources for a catalogued database. 4 The Db2 partition resource does not exist in the resource model. 5 The instance specified does not exist. 6 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Ensure the database name specified is correct and that there are mount resources created for the database, then rerun the command. 3 Use the UNCATALOG DATABASE command to un-catalog the database and re-issue the command. 4 Verify that the specified partition number is correct. 5 Run the 'db2cm -list' command to verify that the specified instance exists. 6 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8247E	There is no active domain on the current host.	There is no active cluster manager domain on the current host.	Run 'db2cm -list -domain' to verify that the domain exists.
DBT8248E	Failed to enable all resources. Reason code = `reason-code`.	This message is returned when an attempt to enable resources has failed. 1 There are no resources in the cluster. 2 One or more resources failed to be enabled. 3 The system is in an inconsistent state. 4 Internal error.	1 Run the 'db2cm -list' command to verify that resources exist in the cluster. 2 Run 'db2cm -verify -resources' to ensure the cluster is configured correctly and try again. 3 Run 'db2cm -repair -resources' to restore the cluster. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8249E	Failed to disable all resources. Reason code = `reason-code`.	This message is returned when an attempt to disable resources has failed. 1 There are no resources in the cluster. 2 One or more resources failed to be disabled. 3 The system is in an inconsistent state. 4 Internal error.	1 Run the 'db2cm -list' command to verify that resources exist in the cluster. 2 Run 'db2cm -verify -resources' to ensure the cluster is configured correctly and try again. 3 Run 'db2cm -repair -resources' to restore the cluster. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8250E	Failed to enable partition `partition-number` on instance `instance-name`. Reason code = `reason-code`.	This message is returned when an attempt to enable a partition has failed. 1 The partition specified does not exist. 2 The partition resource failed to be enabled. 3 The system is in an inconsistent state. 4 Internal error.	1 Run the 'db2cm -list' command to verify that resources related to the partition exist in the cluster. 2 Run 'db2cm -verify -resources' to ensure the cluster is configured correctly and try again. 3 Run 'db2cm -repair -resources' to restore the cluster. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8251E	Failed to disable partition `partition-number` on instance `instance-name`. Reason code = `reason-code`.	This message is returned when an attempt to disable a partition has failed. 1 The partition specified does not exist. 2 The partition resource failed to be disabled. 3 The system is in an inconsistent state. 4 Internal error.	1 Run the 'db2cm -list' command to verify that resources related to the partition exist in the cluster. 2 Run 'db2cm -verify -resources' to ensure the cluster is configured correctly and try again. 3 Run 'db2cm -repair -resources' to restore the cluster. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8252E	Mount resource could not be created. Reason code: `reason-code`.	This message is returned when an attempt to create a mount resource has failed. 1 An online domain does not exist. 2 The partition number is invalid. 3 The Db2 partition resource does not exist in the resource model. 4 Unable to perform passwordless ssh to the specified partition's host. 5 The mount path does not exist or the mount point is unmounted on the specified partition's host. 6 The mount path is nested mounted on another mount point. 7 The mount path has mount monitoring set to no. 8 The mount path is hosted on a filesystem whose type is not supported. 9 The mount path has auto mount enabled. 10 The mount resource attempted to be created already exists. 11 The instance specified does not exist. 12 The mount path configuration is not identical on all hosts. 13 The mount path specified is already being used by another mount resource. 14 An internal error has occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists and is online. 2 Verify that the specified partition number is correct. 3 Verify that the Db2 partition resource specified exists in the resource model. 4 Setup passwordless ssh between the local host and the specified partition's host or re-run the command on the specified partition's host. 5 Verify that the spelling of the specified mount path is correct and the associated mount point is mounted on the specified partition's host. 6 Verify that the specified mount path is not nested mounted on another mount point. 7 Enable mount monitoring for the specified mount path by running 'db2cm -set -option mountMonitoring <mount path> -value yes'. 8 Search for "Db2 Recommended file systems" in IBM documentation to see a list of supported mount types for the given High Availability configuration. 9 Disable the auto mount setting for the specified mount path. 10 Verify that the mount resource does not already exist in the resource model. 11 Run the 'db2cm -list' command to verify that the specified instance exists. 12 Ensure the instance mount path is configured identically in /etc/fstab on all hosts. 13 Verify that the mount path is not already used in the resource model. 14 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8253E	Mount resource could not be deleted. Reason code: `reason-code`.	This message is returned when an attempt to delete a mount resource has failed. 1 An online domain does not exist. 2 The partition number is invalid. 3 The Db2 partition resource does not exist in the resource model. 4 Unable to perform passwordless ssh to the specified partition's host. 5 The mount path does not exist or the mount point is unmounted on the specified partition's host. 6 The mount resource does not exist. 7 The partition number is not associated with the specified mount. 8 The instance specified does not exist. 9 The mount path corresponds to the instance mount of partition resource and cannot be deleted. 10 An internal error has occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists and is online. 2 Verify that the specified partition number is correct. 3 Verify that the Db2 partition resource specified exists in the resource model. 4 Setup passwordless ssh between the local host and the specified partition's host or re-run the command on the specified partition's host. 5 Verify that the spelling of the specified mount path is correct and the associated mount point is mounted on the specified partition's host. 6 Verify that the mount resource exists in the resource model. 7 Verify that the partition number specified is associated with the mount resource in the resource model. 8 Run the 'db2cm -list' command to verify that the specified instance exists. 8 Run the 'db2cm -delete -partition' command to delete both the partition resource and the corresponding instance mount resource. 10 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8254E	Failed to set automatic failback policy. Reason code: `reason-code`.	This message is returned when an attempt to set automatic failback policy has failed as indicated by these reason codes: 1 The option value must be either "ON" or "OFF". 2 Internal error.	1 Re-submit the command using an option value of either "ON" or "OFF". 2 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8255E	Failed to get automatic failback policy. Reason code: `reason-code`.	This message is returned when an attempt to get the current automatic failback policy has failed as indicated by these reason codes: 1 The current failback policy setting is either invalid or not initialized. 2 Internal error.	1 Run the 'db2cm -set -option autofailback' command to set the member failback policy to either "ON" or "OFF". 2 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8256E	Failed to set remote command. Reason code: `reason-code`.	This message is returned when an attempt to set remote command has failed as indicated by these reason codes: 1 Either DB2CM_REMOTE_SHELL or DB2CM_REMOTE_COPY environment variable is not set. 2 At least one of the path(s) specified in the environment variables is invalid or not executable. 3 An internal error occurred.	1 Set both environment variables DB2CM_REMOTE_SHELL and DB2CM_REMOTE_COPY to the correct values and rerun the command. 2 Verify path(s) specified in the environment variables is valid or executable. 3 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8257E	Unable to enter maintenance mode on host `hostname`. Reason code: `reason-code`.	This message is returned when an attempt to enter maintenance mode has failed, as indicated by these reason codes: 1 Another host in the cluster is in the process of entering maintenance mode. 2 Majority quorum cannot be maintained because there are too few online hosts. 3 The cluster will lose quorum if the host enters maintenance mode. Only one cluster caching facility (CF) can be in maintenance mode at any one time. 4 The current host is in an inconsistent state. 5 The current host is in maintenance mode. 6 One or more Db2 members or cluster caching facilities (CFs) are still active on the current host. 7 The Db2 instance is still active on the current host. 8 An internal error has occurred.	1 Reissue this command when the command that is running on the other host has completed. 2 Bring back any offline host so that quorum can be maintained. 3 Exit maintenance mode on the other cluster caching facility (CF) to enter maintenance mode on this CF host. You can also exit maintenance on all hosts and use the '-all' option to put the entire cluster into maintenance mode. 4 Run the 'db2cm -exit -maintenance -force' command and then run the 'db2cm -verify -maintenance' command to confirm that the host is ready for maintenance. 5 The current host is already in maintenance mode. No further action required. 6 Run the db2stop command to stop the pureScale cluster caching facility (CF) or member. 7 To stop the Db2 instance on the current host, run the db2stop instance command for the current host. 8 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8258E	Failed to exit maintenance mode on local host. Reason code: `reason-code`.	This message is returned when an attempt to exit maintenance mode has failed, as indicated by these reason codes: 1 The host is not in maintenance mode. 2 The host is in an inconsistent state. 3 The cluster is in maintenance mode. 4 An internal error occurred.	1 The host is not in maintenance mode. Run the 'db2cm -cm -verify -maintenance' command to check the maintenance status of the host. 2 Run the 'db2cm -cm -exit -maintenance -force' command and then check maintenance status with the 'db2cm -cm -verify -maintenance' command to check the maintenance status of the host. 3 Run the 'db2cm -cm -exit -maintenance -all' command to exit cluster maintenance. 4 Collect db2support and engage IBM support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8259E	Failed to verify maintenance. Reason code: `reason-code`.	This message is returned when an attempt to verify maintenance has failed, as indicated by these reason codes: 1 A host in the cluster is running the DPF maintenance command. 2 Internal error.	1 Wait for the currently running DPF maintenance command to complete before rerunning. 2 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8260E	Failed to get CF preferred primary host. Reason code:`reason-code`.	This message is returned when an attempt to get CF preferred primary host has failed as indicated by these reason codes: 1 The CF primary resource does not exist 2 There is no location constraint defined for the CF primary resource 3 An internal error occurred.	1 Run 'db2cm -verify -resources' to verify the resource model. 2 Run 'db2cm -verify -resources' to verify the resource model. 3 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8261E	Failed to move one or more partitions. Reason code: `reason-code`.	This message is returned when an attempt to move one or more partitions failed as indicated by these reason codes: 1 A domain does not exist on the local host. 2 The target host is not online. 3 One or more of the specified partition numbers is invalid. 4 The logical port 0 partition in any host of a DPF cluster must be the only partition left on the host before moving the partition to a different host. 5 Moving the partition(s) to the target host exceeds the maximum number of partitions supported on the target host. 6 One or more partition numbers specified does not exist on the cluster, is unmanaged, is disabled, is offline or running on the target host already. 7 The value for -partition must be 'all' when specifying a host for -from. 8 The current configuration does not support single partition move operation. 9 The instance specified does not exist. 10 No partitions to move from the specified host. 11 One or more hosts specified are not in the local domain. 12 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists. 2 Run the 'db2cm -list' command to verify the status of the specified host. 3 Validate the partition number(s) specified in the Db2 nodes configuration file. 4 Verify in the Db2 nodes configuration file that other partitions exist that are non-logical port zero on the source or local host. If partitions exist that are non-logical port zero, run the 'db2cm -move' command to move the partitions to the target host before moving the logical port zero partition. The logical port zero partition requires a separate 'db2cm -move' command to be run if there are non-logical port zero partitions on the same host. 5 Run the 'db2cm -list' command to verify that there is enough capacity for the number of partitions to be moved to the target host. 6 Run the 'db2cm -list' command to verify the state of the partition number(s) specified. 7 Rerun 'db2cm -move' command with 'all' as the value for '-partition'. 8 Rerun the move operation with 'all' as the target partition. 9 Run the 'db2cm -list' command to verify that the specified instance exists. 10 Rerun 'db2cm -move' command with a non-standby host as the value for '-from'. 11 Re-run the move operation with hosts in the local domain. 12 If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8262E	Overlay IP resource could not be created. Reason code = `reason-code`.	This message is returned when an Overlay IP resource could not be created. 1 The Overlay IP resource that you are attempting to create already exists. 2 The Db2 instance resource does not exist on the host. 3 The Db2 partition resource does not exist on the host. 4 The database name that you provided does not exist. 5 The IP address that you provided is already in use on the network. 6 The database resource does not exist. 7 Passwordless SSH is not configured with the destination host. 8 The IP address that you provided is not in the correct form. 9 The AWS CLI is not installed on one or more hosts. 10 The installed AWS CLI version is below the minimum supported version. 11 The curl command is not installed. 12 The IMDSv2 metadata service is unavailable on one or more hosts. 13 The 'default' or provided AWS profile does not exist. 14 A prerequisite IAM policy is not configured. 15 The route associated with the provided IP address does not have a cluster host or interface as its destination. 16 The provided address is within the VPC's subnet. 17 The route table entry for the provided IP address does not exist. 18 The provided route table does not exist. 19 The EC2 instances are in different VPCs. 20 An internal error has been detected.	1 Run the 'db2cm -list' command and check under 'Resource Information' to verify that the resource exists. If the resource needs to be recreated, delete it first and reissue the command. 2 Run the 'db2cm -list' command to verify that the instance specified is on the local host and exists in the resource model under the 'Resource Information' section. Then rerun the db2cm command. 3 Run the 'db2cm -list' command to verify that the partition specified is on the local host and exists in the resource model under the 'Resource Information' section. Then rerun the db2cm command. 4 Run db2pd -hadr -db DB_NAME to verify that the database exists and is activated. If the database is not activated, activate the database and retry the command. 5 Ensure that the IPv4 address provided is not pingable. 6 Run the 'db2cm -list' command and check under 'Resource Information' to verify that the database resource exists. 7 Ensure passwordless SSH is configured with the destination host and retry the command. 8 Ensure that the IPv4 address provided is in dot-decimal format. 9 Ensure the AWS CLI is installed on all hosts in the cluster before attempting to retry the command. The AWS CLI should either be installed directly under /usr/bin/, or there should be a symbolic link from /usr/bin/ to the AWS CLI executable. 10 Ensure the AWS CLI installed meets the minimum supported version. 11 Install curl and retry the db2cm command.. 12 The AWS Overlay IP is only supported on AWS EC2 instances with IMDSv2 enabled. Ensure the IMDSv2 instance metadata services is enabled for each host in the cluster before rerunning the command. 13 Ensure the default AWS CLI profile has been configured using 'aws configure', or if using a profile other than 'default', rerun this command while specifying the profile name with the -profile option. 14 Ensure an IAM role containing all required policies is attached to each EC2 instance in the cluster. Examine the db2cm run log for error messages indicating which specific IAM policies are missing before rerunning the command. 15 Ensure the provided route is not already in use by another system or application, and that traffic is being directed to one of the hosts or interfaces in the cluster. 16 Choose an IP address that exists outside the VPC subnet and rerun the command. 17 Ensure the provided IP address has an existing route defined within the provided route table, and that the destination is set to one of the hosts or interfaces within the cluster. 18 Ensure the provided route table ID belongs to an existing route table. 19 Configuration of the AWS Overlay IP is only supported between cluster hosts that all belong to the same VPC. 20 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8263E	Overlay IP resource could not be deleted. Reason code = `reason-code`.	This message is returned when an Overlay IP resource could not be deleted. 1 The resource attempted to be deleted does not exist. 2 The database resource does not exist. 3 The partition resource does not exist. 4 The instance resource does not exist. 5 An internal error has been detected.	1 Run the 'db2cm -list' command and check under 'Resource Information' to verify that the Overlay IP resource exists. 2 Run the 'db2cm -list' command and check under 'Resource Information' to verify that the database resource exists. 3 Run the 'db2cm -list' command and check under 'Resource Information' to verify that the partition number provided is associated with an existing partition resource. 4 Run the 'db2cm -list' command and check under 'Resource Information' to verify that there is an existing instance resource for the specified instance name. 5 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8264E	Failed to display alerts. Reason code:`reason-code`.	This message is returned when an attempt to display alerts has failed as indicated by these reason codes: 1 An online domain does not exist. 2 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists and is online. 2 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8265E	Failed to clear alerts. Reason code:`reason-code`.	This message is returned when an attempt to clear alerts has failed as indicated by these reason codes: 1 An online domain does not exist. 2 The specified host does not exist. 3 The specified member or CF number is not valid. 4 An internal error occurred.	1 Run 'db2cm -list -domain' to verify that the domain exists and is online. 2 Rerun the command with a valid host name. 3 Rerun the command with a valid member or CF number. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8266E	Failed to repair resources. Reason code:`reason-code`.	This message is returned when an attempt to repair resources has failed as indicated by these reason codes: 1 An online domain does not exist. 2 There are online Db2 resources. 3 Unable to repair the resources because there is no Db2 Instance Information Registry. 4 The network interface configuration on host `hostname` is inconsistent with the CFS subnet configuration. 5 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify whether the domain exists and is online. 2 Stop the Db2 instance and re-issue this command. 3 Run the 'db2cm -create -resources' command to create the Db2 instance resources and the Db2 Instance Information Registry. 4 Check that there is a network interface on host `hostname` that is on the same subnet as the configured CFS subnet: `subnet` as shown in the output mmlsconfig. 5 Collect db2support data and engage IBM Support. If the issue persists, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8267E	Failed to start host: `host`. Reason code:`reason-code`.	This message is returned when an attempt to start hosts within a cluster has failed. 1 Cluster manager services on the current host are not active. 2 The remote execution command is not configured. 3 The specified host cannot be found within the cluster. 4 An internal error occurred.	1 Rerun the executed command on another host within the cluster where the cluster manager is active. 2 Configure passwordless SSH as root with the specified host. Refer to IBM documentation on how to configure passwordless ssh or db2locssh. 3 Run the 'db2cm -list -host' command to verify whether the specified host exists and then retry with the correct host. 4 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8268E	Failed to stop host. Reason code:`reason-code`.	This message is returned when an attempt to stop a host within a cluster has failed. 1 More than one host has been specified. Specify only one host. 2 Cluster manager services on the current host are not active. 3 The remote execution command is not configured. 4 The specified host cannot be found within the cluster. 5 One or more Db2 members or cluster caching facilities (CFs) are still active on the specified host. 6 The Db2 instance is still active on the specified host. 7 The host cannot be stopped. Stopping the host results in quorum loss within the cluster manager domain. 8 The host cannot be stopped. Stopping the host results in quorum loss within the shared file system domain. 9 An internal error occurred.	1 Specify no more than one host inside the command. Check the command syntax in the db2cm documentation or by using 'db2cm -help'. 2 Rerun the executed command on another host within the cluster where the cluster manager is active. 3 Configure passwordless SSH as root with the specified host. Refer to IBM documentation on how to configure passwordless ssh or db2locssh. 4 Run the 'db2cm -list -host' command to verify whether the specified host exists and then retry with the correct host. 5 To stop member and CF resources, run either the db2stop member command or the db2stop cf command on the specified host. 6 To stop the Db2 instance on the specified host, run the db2stop instance command for the specified host. 7 Maintain quorum by starting the other cluster caching facility (CF) host. 8 Before attempting to rerun this command, maintain quorum by starting a host that is currently offline or by configuring a tie-breaker (if one is not already configured). 9 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8269E	Failed to list host(s). Reason code:`reason-code`.	This message is returned when an attempt to list host(s) within a cluster has failed. 1 Cluster manager services on the current host are not active. 2 The hosts that are in the cluster manager domain do match the hosts that are in the shared file system cluster. 3 An internal error occurred.	1 Rerun the executed command on another host within the cluster where the cluster manager is active. 2 Run the 'db2cm -cm -list -host [-state]' command and the 'db2cm -cfs -list -host [-state]' command to list the hosts within the cluster manager domain and within the shared file system cluster, respectively. Alternatively, run the 'db2cm -list -host -state' command to show all hosts within both the cluster manager domain and the shared file system cluster. 3 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8270E	Failed to enable all resources. Reason code: `reason-code`.	This message is returned when an attempt to enable resources has failed. 1 There are no resources in the cluster. 2 One or more resources failed to be enabled. 3 Passwordless SSH is not configured across all hosts in the cluster. 4 Internal error.	1 Run the 'db2cm -list' command to verify that resources exist in the cluster. 2 Run 'db2cm -verify -resources' to ensure the cluster is configured correctly and try again. 3 Ensure passwordless ssh is configured across all hosts and retry the command. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8271E	Failed to disable all resources. Reason code: `reason-code`.	This message is returned when an attempt to disable resources has failed. 1 There are no resources in the cluster. 2 One or more resources failed to be disabled. 3 Passwordless SSH is not configured across all hosts in the cluster. 4 Internal error.	1 Run the 'db2cm -list' command to verify that resources exist in the cluster. 2 Run 'db2cm -verify -resources' to ensure the cluster is configured correctly and try again. 3 Ensure passwordless ssh is configured across all hosts and retry the command. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8272E	Failed to execute db2cm commands. Reason code:`reason-code`.	This message is returned when an attempt to execute db2cm commands fails, as indicated by the following reason codes: 1 Local host is in maintenance mode. 2 The cluster manager is inactive. 3 An online domain does not exist. 4 An internal error occurred.	1 Run the 'db2cm -exit -maintenance' command to exit maintenance mode on the local host. 2 Start the cluster manager manually. 3 Run the 'db2cm -list -domain' command to verify whether the domain exists and is online. 4 Collect db2support data and engage IBM Support. If the issue persists, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8273E	Failed to add quorum device to the cluster. Reason code: `reason-code`.	An attempt to add the quorum device in the cluster failed. 1 An active domain does not exist. 2 There are an odd number of hosts on this system. A quorum device is not required. 3 The quorum device parameter that was passed-in is not valid. Make sure the input corresponds to a valid hostname and that the host is not one of the existing cluster nodes. 4 The command for running remote operations is not configured between the current host and all cluster hosts, including the current host, nor between the current host and the quorum device host. 5 This cluster already has a quorum device configured. 6 This quorum device host is being used by another cluster with the same domain name. 7 The quorum disk provided does not exist. 8 The quorum disk provided is not a valid tiebreaker. 9 The quorum disk provided is already in use. 99 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists. 2 No action required, quorum device setup is not required for this cluster. 3 Re-run the command with a valid hostname for the quorum device that is not one of the existing cluster nodes. 4 Verify that root passwordless SSH or db2locssh is configured correctly between the current host and all cluster hosts, including the current host, and between the current host and the quorum device host. On all hosts, populate the known_hosts file by authenticating connectivity to both the long and short qualified host names for each host. Ensure all hosts are pingable. Once verified, rerun the command. 5 If you want to use a different quorum device, first delete the current quorum device using the 'db2cm -cm -set -tiebreaker -majority' command and then rerun the original command. 6 If the other cluster domain is no longer available, navigate to /etc/corosync/qnetd/nssdb on the quorum device host, delete the file name 'cluster-<domainName>.crt' and re-run the 'db2cm -cm -set -tiebreaker -host <hostName>' command. If the other cluster domain is available, run the 'db2cm -cm -set -tiebreaker -host <hostName>' command with a different quorum device host. 7 Ensure the quorum disk exists on the local host. 8 Ensure the quorum disk supports either SCSI3 or NVMe reservation. 9 Verify that the disk is not in use. For more information, see "Troubleshooting the Db2 Disk Tiebreaker feature" in the IBM documentation. 99 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8274E	Failed to delete quorum device from the cluster. Reason code: `reason-code`.	An attempt to remove the quorum device from the cluster has failed. 1 An active domain does not exist. 2 There is no quorum device configured in the cluster. 3 The cluster consists of only two nodes. This increases the risk of a split brain scenario if the quorum device is removed. 4 The command for running remote operations is not configured between the current host and all cluster hosts, including the current host, nor between the current host and the quorum device host. 99 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists. 2 No action required. This command can only be run on a cluster that already has a quorum device configured. 3 If you still want to delete the quorum device against the recommendation, run the following command: 'db2cm -cm -set -tiebreaker -majority -force'. 4 Verify that root passwordless SSH or db2locssh is configured correctly between the current host and all cluster hosts, including the current host, and between the current host and the quorum device host. On all hosts, populate the known_hosts file by authenticating connectivity to both the long and short qualified host names for each host. Ensure all hosts are pingable. Once verified, rerun the command. 99 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8275E	Failed to set up fencing in the cluster. Reason code: `reason-code`.	An attempt to set up fencing on the cluster has failed. 1 The watchdog service is not set up on all hosts in the cluster. 2 The cluster does not have a Quorum device. 3 An internal error occurred.	1 Ensure that the watchdog service is set up on all hosts in the cluster. For more information, see the IBM documentation. 2 Fencing can be set up only if the cluster has a Quorum device. Configure a Quorum device and then retry setting up fencing. 3 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8276E	Failed to remove fencing configuration. Reason code: `reason-code`.	An attempt to remove fencing from the cluster has failed. 1 Fencing is not set up on the cluster. 2 An internal error occurred.	1 Ensure that fencing is set up in the cluster before attempting to remove it 2 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8277E	Failed to stop domain. Reason code: `reason-code`.	An attempt to stop the domain from the host has failed. 1 The Db2 instance is still active. 2 There is no active cluster manager domain on the current host. 3 The host is not a CF host. 4 An internal error occurred.	1 Run the db2stop instance on <host name> command to stop the db2 instance. 2 Run the 'db2cm -list -domain' command to verify that the domain exists and is online. 3 Run the command from a CF host. 4 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8278E	Failed to start domain. Reason code: `reason-code`.	An attempt to start the domain from the host has failed. 1 An active domain exists. 2 The host is not a CF host. 3 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain is offline. 2 Run the command from a CF host. 3 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8279E	The cluster manager resource model is inconsistent. Reason code:`reason-code`.	A call to verify resources discovered an inconsistent resource model. 1 Resources for the cluster manager domain are inconsistent. 2 The resource model version found does not match the expected version.	1 Run the 'db2cm -repair -resources' command to repair the resources. 2 Run the 'db2cm -repair -resources' command to repair the resource model. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8280E	Failed to verify resources. Reason code:`reason-code`.	An attempt to verify resources within a cluster has failed. 1 An online domain does not exist. 2 The resource model is not populated. 3 No Db2 Instance Information Registry was found. 4 One or more hosts within the domain are not online. 5 The network interface configuration on host `hostname` is inconsistent with the CFS subnet configuration. 6 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify whether the domain exists and is online. 2 Run the 'db2cm -create -resources' command to create resources before attempting to verify resources. 3 Run the 'db2cm -create -resources' command to create the Db2 instance resources and the Db2 Instance Information Registry. 4 Run the 'db2cm -list -host -state' command to verify that all hosts are online. If any hosts are offline, verify that those hosts are reachable and run the 'db2cm -start -host <host[,host]...>' command to start each offline host. 5 Run the 'db2cm -repair -resources' command to repair the resources. 6 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8281E	Export failed. Reason code:`reason-code`.	Exporting the cluster configuration file has failed. 1 The specified file already exists. 2 Failed to create the cluster configuration export file. 3 The cluster manager domain is not active on the current host. 4 An internal error occurred.	1 Specify a target file that does not already exist. 2 Check the ownership and permissions of the target file path directory and its parent directories and make sure they are accessible by the current user. 3 Activate the cluster manager domain on the current host. Run the 'db2cm -list -domain' command to verify the cluster manager domain state. 4 Run the 'db2cm -list' command to verify that the cluster is in a healthy state. Rerun the command when the cluster is healthy. If the cluster continues to fail, collect db2support and contact IBM support. Collect db2support data and engage IBM Support.
DBT8282E	Import failed. Reason code:`reason-code`.	Importing the cluster configuration file has failed. 1 The specified import file could not be accessed. 2 There is an active domain present. 3 The input file version is incompatible with the current Db2 release. 4 The input file format contains errors. 5 The resulting backup configuration cannot be deployed on a new set of hosts where any of the following values are different from the original cluster: - Hostnames - Domain name - Network interface names - Instance names - Database names - Database mount paths - Primary/Standby virtual IP addresses - Qdevice host 6 An internal error occurred.	1 Rerun the command with a valid import file. 2 Remove the active domain and rerun the command. 3 Export the cluster configuration file by using a supported Db2 release and then retry the import command. If the error persists, collect db2support logs and engage IBM Support. 4 Verify that the cluster has been rolled back successfully. If the issues persist, collect db2support and engage IBM Support. 5 Export the cluster configuration again and then re-run the import command. For the export operation, use the values that were used previously for the following parameters: - Hostnames - Domain name - Network interface names - Instance names - Database names - Database mount paths - Primary/Standby virtual IP addresses - Qdevice host 6 Verify that any cluster creation resources were rolled back successfully. If the issues persist, collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command.
DBT8283E	Failed to verify maintenance. Reason code: `reason-code`.	This message is returned when an attempt to verify maintenance has failed, as indicated by these reason codes: 1 The current host is in an inconsistent state. 2 The cluster manager is not active on the current host and the current host is not in maintenance. 3 An internal error occurred.	1 Check the diagnostic log (/tmp/db2cm/db2cm.log.*) for more information. 2 Start the cluster manager on the current host and rerun the command. 3 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8284E	Database partition resource could not be created. Reason code: `reason-code`.	An attempt to create a database partition resource has failed. 1 An active domain does not exist. 2 The instance specified does not exist. 3 The partition resource already exists. 4 Network interface resources does not exists. 5 The mount path does not exist or is unmounted. 6 The mount path specified is already being used by another mount resource. 7 The mount path specified is nested. 8 The mount path has mount monitoring set to 'no'. 9 The mount path is hosted on an unsupported file system. 10 The mount path has automount enabled. 11 The mount path configuration is not identical on all hosts. 12 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists and is online. 2 Run the 'db2cm -list' command to verify that the specified instance exists. 3 The partition resource is already created. No further action is required. 4 Run the 'db2cm -list' command to verify that network interfaces have been created. If not, run the 'db2cm -create -publicEthernet' command to create network interface resources. 5 Verify that the mount path is mounted on the host of the specified partition. 6 Verify that the mount path is not already used in the resource model. 7 Verify that the mount path is not nested on another mount point. 8 Enable mount monitoring for the instance mount by running the command 'db2cm -set -option mountMonitoring <mount path> -value yes'. 9 Search for "Db2 Recommended file systems" in IBM documentation to see a list of supported mount types for the given High Availability configuration. 10 Disable the auto mount setting for the instance mount. 11 Ensure the instance mount path is configured identically in /etc/fstab on all hosts. 12 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8285E	Database partition resource could not be deleted. Reason code: `reason-code`.	An attempt to delete a database partition resource has failed. 1 An active domain does not exist. 2 The instance specified does not exist. 3 The database partition resource specified does not exist. 4 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists and is online. 2 Run the 'db2cm -list' command to verify that the specified instance exists. 3 Run the 'db2cm -list' command to verify that the specified database partition resource exists. 4 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8286E	Mismatch in domain configuration found. Reason code:`reason-code`.	There is a mismatch in the domain configuration. 1 One or more domain configurations is invalid. 2 One or more hosts within the cluster have inconsistent domain configuration files. 3 An internal error occurred.	1 Run the 'db2cm -repair -domain' command to repair the invalid domain configuration. 2 Run the 'db2cm -delete -domain' command to delete the domain, and then run the 'db2cm -create -domain' command to recreate the domain. 3 Collect db2support data and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8287E	Failed to verify domain. Reason code:`reason-code`.	An attempt to verify the domain has failed. 1 An online domain does not exist. 2 The remote execution command is not configured. 3 An invalid domain topology exists. 4 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify whether the domain exists and is online. 2 Configure passwordless SSH as root with the specified host. Refer to IBM documentation on how to configure passwordless ssh or db2locssh. 3 Refer to the IBM documentation "Db2 DPF supported topology" to find a supported domain topology. 4 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8288E	Failed to collect db2cm dump. Reason code: `reason-code`.	An attempt to collect the output from a 'db2cm -dump' operation has failed. 1 The diagnostic path specified by the database manager configuration parameter is not accessible. 2 The specified output path is not accessible. 3 The time window is more than 30 days. 4 An internal error occurred.	1 Ensure that the diagnostic path is accessible and then rerun the 'db2cm -dump' command. 2 Ensure that the specified path is accessible and then rerun the 'db2cm -dump' command. 3 Rerun the 'db2cm -dump' with a time window that is less than or equal to 30 days. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8289E	Failed to verify maintenance mode for the mount "`mount-path`". Reason code: "`reason-code`".	An attempt to verify mount maintenance has failed, as indicated by these reason codes: 1 The specified mount point is not a database-level mount. 2 The specified mount point does not exist. 3 An internal error has occurred.	1 Ensure that the specified mount point is a database-level mount and then rerun the command. 2 Run the 'db2cm -list -mount' command to verify the mount resource exists. 3 Collect the results from running the 'db2support -purescale' command and contact IBM software support for assistance. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8290E	Failed to enter maintenance mode for the mount "`mount-path`". Reason code: "`reason-code`".	An attempt to enter mount maintenance mode has failed, as indicated by these reason codes: 1 The specified mount point is already in maintenance mode on the current host. The operation is not allowed. 2 The specified mount point is in host-level maintenance mode on at least one host in the cluster. The operation is not allowed. 3 The specified mount point cannot enter maintenance mode on all member hosts as at least one host is offline in the cluster. 4 The enter-mount-maintenance-mode operation can be run on a member host. 5 The specified mount point is not a database-level mount. 6 The specified mount point does not exist. 7 The current host is in the progress of rolling update. 8 The specified mount point is busy and unavailable for the unmount operation. 9 An internal error has occurred.	1 Run the 'db2cm -verify -maintenance -mount' command to verify the maintenance state for this mount point. 2 Run the 'db2cm -verify -maintenance -mount' command to verify the maintenance state for this mount point. Enter host-level mount maintenance mode on the remaining hosts, or exit host-level mount maintenance mode on all associated hosts and then enter cluster-wide mount maintenance mode. 3 Run the 'db2cm -list -member' command to verify that all member hosts are online in the cluster. 4 Run the command from a member host. 5 Ensure that the specified mount point is a database-level mount and then rerun the command. 6 Run the 'db2cm -list -mount' command to verify the mount resource exists. 7 Ensure that the current host is not in the process of rolling update. 8 Ensure that the specified mount point is not in use. 9 Collect the results from running the 'db2support -purescale' command and contact IBM software support for assistance. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8291E	Failed to exit maintenance mode for the mount "`mount-path`". Reason code: "`reason-code`".	An attempt to exit mount maintenance mode has failed, as indicated by these reason codes: 1 The specified mount point is not in maintenance mode on the current host. The operation is not allowed. 2 The specified mount point is not in maintenance on all hosts. The operation is not allowed. 3 The specified mount point cannot exit maintenance mode on all member hosts as at least one host is offline in the cluster. 4 The exit-mount-maintenance-mode operation can be run on a member host. 5 The specified mount point is not a database-level mount. 6 The specified mount point does not exist. 7 The current host is in the progress of rolling update. 8 An internal error has occurred.	1 Run the 'db2cm -verify -maintenance -mount' command to verify the maintenance state for this mount point. 2 Run the 'db2cm -verify -maintenance -mount' command to verify the maintenance state for this mount point. Exit host-level mount maintenance mode on the associated hosts. 3 Run the 'db2cm -list -member' command to verify that all member hosts are online in the cluster. 4 Run the command from a member host. 5 Ensure that the specified mount point is a database-level mount and then rerun the command. 6 Run the 'db2cm -list -mount' command to verify the mount resource exists. 7 Ensure that the current host is not in the process of rolling update. 8 Collect the results from running the 'db2support -purescale' command and contact IBM software support for assistance. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8292E	Failed to repair cluster manager domain. Reason code: `reason-code`.	An attempt to repair the cluster manager domain has failed. 1 The DB2INSTANCE environment variable is not set to the instance user. 2 The provided domain name does not exist. 3 The command must run from a CF host. 4 One or more hosts are not reachable. 5 Hosts within the domain are in maintenance mode. 6 One or more resources are not offline. 7 The command for running remote operations is not configured between the current host and the quorum device. 8 A mismatch of cluster topology was detected between the db2nodes.cfg file and the Db2 Instance Information Registry. 9 Failed to reconfigure the quorum device. 10 An internal error occurred.	1 Set the DB2INSTANCE environment variable to the correct instance name. 2 To repair the current domain, reissue the 'db2cm -repair -domain' command without specifying a domain name. 3 The command must be run from a CF host. 4 Configure passwordless SSH as root with all cluster hosts within the db2nodes.cfg file. Refer to IBM documentation on how to configure passwordless ssh or db2locssh. If this issue persists, ensure that all hosts are online. 5 Run the 'db2cm -verify -maintenance' command on all cluster hosts to identify which hosts are in maintenance mode. Run the 'db2cm -exit -maintenance' command on all hosts that are in maintenance mode to remove them from maintenance. Reissue the 'db2cm -repair -domain' command. If hosts are unable to be brought out of maintenance mode, reissue the 'db2cm -repair -domain' command with the '-force' option. 6 Verify that all Db2 member, idle, CF, and CF primary resources are offline by running the 'db2cm -list -resources' command. If any of these resources are still online, run 'db2stop' to put all member, idle, CF, and CF primary resources in an offline state. If resources are unable to be brought offline, reissue the 'db2cm -repair -domain' command with the '-force' option. 7 Verify that root passwordless SSH or db2locssh is configured correctly between the current host and the quorum device host. On all hosts, populate the known_hosts file by authenticating connectivity to both the long and short qualified host names for each host. Ensure all hosts are pingable. Once verified, rerun the command. Alternatively, run the 'db2cm -repair -domain <domainName> -force' command to repair the domain without setting up the quorum device host. 8 Reissue the 'db2cm -repair -domain' command with the '-force' option. 9 The quorum device must be removed by running the 'db2cm -delete -qdevice -force' command. Run the 'db2cm -repair -resources' command to restore the resource model. Run the 'db2cm -create -qdevice <hostname>' command with the quorum device host name to recreate the quorum device. 10 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8293E	Unable to enter maintenance mode on the cluster.`reason-code`.	An attempt to enter maintenance mode has failed, as indicated by the following reason codes: 1 Another host in the cluster is in the process of entering maintenance mode. 2 The cluster is already in maintenance mode. 3 One or more hosts in the cluster are unreachable. 4 One or more hosts in the cluster are in maintenance mode. 5 One or more Db2 members or cluster caching facilities (CFs) are still active in the cluster. 6 One or more nodes in the cluster still have an active Db2 instance. 7 An internal error has occurred.	1 When the command that is running on the other host is completed, rerun the 'db2cm -cm -enter -maintenance -all' command to enter maintenance mode. 2 No further action required. 3 Ensure that all hosts in the cluster are online and can be pinged, and then rerun the 'db2cm -cm -enter -maintenance -all' command. 4 Run the 'db2cm -cm -exit -maintenance -force' command on all hosts that are in maintenance mode and then run the 'db2cm -verify -maintenance -all' command to confirm that the cluster is ready for maintenance. 5 Run the 'db2stop' command to stop all cluster caching facilities (CFs) and members across the cluster. 6 Run the 'db2stop instance on hostname' command on each active Db2 instance. 7 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command.
DBT8294E	Unable to exit maintenance mode on the cluster.`reason-code`.	An attempt to exit maintenance mode has failed, as indicated by the following reason codes: 1 Unable to exit maintenance mode for this cluster because the current host was put into maintenance mode individually. 2 One or more hosts in the cluster are unreachable. 3 The cluster is not in maintenance mode. 4 The cluster is in inconsistent state. 5 The command was run with '-force' option from a member host. 6 An internal error has occurred.	1 Rerun the command without the '-all' option to remove the host from maintenance mode. 2 Ensure all hosts in the cluster are online and pingable, and then rerun the command. Ensure that all hosts in the cluster are online and can be pinged, and then rerun the 'db2cm -cm -exit -maintenance -all' command. 3 No further action required. 4 Rerun the 'db2cm -cm -exit -maintenance' command with the '-force' option from a CF host to take the cluster out of inconsistent state. 5 Run the command with the '-force' option from a CF host. 6 Collect the results from running a 'db2support' operation and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command.
DBT8295E	Failed to verify DPF resources. Reason code: "`reason-code`".	An attempt to verify DPF resources within a cluster has failed, as indicated by these reason codes: 1 An online domain does not exist. 2 The resource model is not populated. 3 No high availability(HA) resource metadata was found. 4 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify whether the domain exists and is online. 2 Run the 'db2cm -create -resources' command to create resources before attempting to verify resources. 3 Run the 'db2cm -delete -domain' command to delete the domain, and then run the 'db2cm -create -domain' command to recreate the domain. Run the 'db2cm -create -resources' to recreate resources. 4 Collect db2support logs and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8296E	The Azure fence resource could not be created. Reason code = `reason-code`.	The Azure fence resource could not be created, as indicated by these reason codes: 1 The Azure fence resource that you are trying to create already exists. 2 The credentials for the Service Principal might not be correct. 3 The Azure CLI is not installed on one or more hosts. 4 The Azure Fence Agent configured with a Service Principle failed to run on one or more hosts. 5 Curl is not installed on one or more hosts. 6 The Azure Fence Agent configured with a Managed Identity failed to run on one or more hosts. 7 No Managed Identity is assigned on one or more hosts. 8 One of the required environment variables was not defined. 9 An internal error has been detected.	1 Run the 'db2cm -list' command and check under Fencing Information to verify if the resource exists. If the resource needs to be recreated, delete the resource and the rerun the command. 2 Ensure that the credentials DB2_AZURE_SP_LOGIN and DB2_AZURE_SP_PASSWD for the Service Principal are correct, and then rerun the 'db2cm' command. 3 Ensure that the Azure CLI is installed in /usr/bin/az on all hosts and then rerun the 'db2cm' command. 4 Ensure that the following command can run successfully on all hosts: "fence_azure_arm -l $DB2_AZURE_SP_LOGIN -p $DB2_AZURE_SP_PASSWD --tenantId=[TENANT_ID] -o list". If the 'fence_azure_arm' command fails, ensure that the following conditions exist and then rerun the 'db2cm' command: - The Azure Fence agents are installed. - The Service Principal has the correct role attached. - The version of the python package azure-mgmt-compute is compatible with the fencing agent. 5 Install Curl and then rerun the 'db2cm' command. 6 Ensure that the 'fence_azure_arm --msi -o list' command can run successfully on all hosts. If the 'fence_azure_arm' command fails, ensure that the following conditions exist and then rerun the 'db2cm' command: - The Azure Fence agents are installed. - The Managed Identity has the correct role attached. - The version of the python package azure-mgmt-compute is compatible with the fencing agent. 7 Assign a Managed Identity with the required permissions to all hosts in the cluster domain. 8 If configuring fencing with Service Principals, ensure that the environment variables DB2_AZURE_SP_LOGIN and DB2_AZURE_SP_PASSWD are defined before creating the fence resource, and then rerun the 'db2cm' command. 9 Collect the results from running the 'db2support' command and contact IBM software support for assistance. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8297E	Failed to repair resources. Reason code: `reason-code`.	An attempt to repair the Cluser Manager resource model has failed. 1 An active domain does not exist. 2 An internal error occured.	1 Run the 'db2cm -list -domain' command to verify that the domain exists and is online. 2 Collect db2support and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8298E	The AWS fence resource could not be created. Reason code = `reason-code`.	The AWS fence resource could not be created, as indicated by these reason codes: 1 The AWS fence resource that you are trying to create already exists. 2 An unsupported quorum type exists for the cluster domain. 3 Neither Curl nor the AWS CLI is installed on one or more hosts. 4 The AWS Fence Agent is not installed on one or more hosts. 5 An alternate fencing device is already configured. 6 A prerequisite IAM policy is not configured. 7 An internal error has been detected.	1 Run the 'db2cm -list' command and check under Fencing Information to verify whether the resource exists. If the resource needs to be recreated, delete the resource and then rerun the 'db2cm' command. 2 Run the 'db2cm -list' command and check under Quorum Information to verify whether the Quorum type is Two Node. If the Quorum type is Two Node, rerun the 'db2cm' command. 3 Ensure that the AWS CLI is installed in /usr/bin/aws and that Curl is installed in /usr/bin/curl on all hosts. When the command line tools are installed, rerun the 'db2cm' command. 4 Ensure that the AWS fence agents are installed on all hosts, and then rerun the 'db2cm' command. 5 Run the 'db2cm -list' command and check under Fencing Information to verify whether an alternate fencing resource exists. If the fencing resource needs to be replaced, delete the resource and then rerun the 'db2cm' command. 6 Ensure that an IAM role containing all the required policies is attached to each EC2 instance in the cluster. Review the db2cm run log for error messages that indicate which specific IAM policies are missing before rerunning the command. 7 Collect the results from running the 'db2support' command and contact IBM software support for assistance. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8299E	The load balancer resource could not be created. Reason code = `reason-code`.	Your attempt to create a load balancer resource failed, as indicated by the following reason codes: 1 The load balancer resource already exists. 2 The Db2 instance resource does not exist on the host. 3 The partition number that you provided does not exist or is invalid. 4 The database resource does not exist. 5 The HADR database does not exist. 6 The port for the load balancer is not valid. 7 An internal error has been detected.	1 Run the 'db2cm -list' command and check under 'Resource Information' to determine whether the resource exists. If the resource exists but needs to be recreated, delete it first and then reissue the command. 2 Run the 'db2cm -list' command and to determine whether the specified Db2 instance is on the local host and that it exists in the resource model under the 'Resource Information' section. If the resource does not exist on the host, rerun the db2cm command. 3 Run the 'db2cm -list' command and to verify that the partition specified is on the local host and exists in the resource model under the 'Resource Information' section. If the partition does not exist, rerun the db2cm command. 4 Run the 'db2cm -list' command and check under 'Resource Information' to verify if the database resource exists. If the resource does not exist, rerun the db2cm command. 5 Run the 'db2pd -hadr -db DB_NAME' command to determine whether the database exists and is activated. If the database is not activated, activate the database and then rerun the dbcm command. 6 Ensure that the port that is specified for the load balancer is valid and between 1 - 65535, then rerun the db2cm command. 7 Collect the results from running the 'db2support' command and contact IBM software support for assistance. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8300E	Load Balancer resource could not be deleted. Reason code = `reason-code`.	This message is returned when a load balancer resource could not be deleted. 1 The resource attempted to be deleted does not exist. 2 The database resource does not exist. 3 The partition number provided does not exist or is invalid. 4 The Db2 instance specified does not exist. 5 An internal error has been detected.	1 Run the 'db2cm -list' command and check under 'Resource Information' to determine whether the resource exists. 2 Run the 'db2cm -list' command and check under 'Resource Information' to determine whether the database resource exists. 3 Run the 'db2cm -list' command and check under 'Resource Information' to determine whether the partition resource exists. 4 Ensure that the Db2 instance exists on the host and then rerun the db2cm command. 5 Collect the results from running the 'db2support' command and contact IBM software support for assistance. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8301E	Failed to enable CPU scheduling. Reason code = `reason-code`.	The CPU scheduling cannot be enabled. 1 A domain does not exist. 2 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists. 2 Collect the results from running the 'db2support' command and contact IBM software support for assistance. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8302E	Failed to disable CPU scheduling. Reason code = `reason-code`.	The CPU scheduling cannot be disabled. 1 A domain does not exist. 2 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists. 2 Collect the results from running the 'db2support' command and contact IBM software support for assistance. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8303E	Failed to verify CPU scheduling. Reason code = `reason-code`.	The CPU scheduling cannot be verified. 1 A domain does not exist. 2 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists. 2 Collect the results from running the 'db2support' command and contact IBM software support for assistance. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8304E	The db2cm -verify -req command failed. Reason code: `reason-code`.	An error occured while verifying OS status: 1 The cluster manager is not active. 2 A remote command failed to run. 3 Hostname given on command line was invalid or not a member of the domain. 4 An internal error occurred.	1 Run the 'db2cm -status' command to check if the cluster manager is active, if it is not bring it online or rerun the command on host where it is active. 2 Verify that passwordless ssh is set up between all cluster members and to themselves. 3 Run 'db2cm -list', verify the host name, and run the command again with a corrected hostname. 4 Collect db2support data and engage IBM Support. If the issue persists, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8305W	Failed check. Reason Code: `reason-code`.	A host failed the db2cm -verify -req check: 1 Failed to meet OS level. 2 Failed to meet kernel level. 3 Failed to meet C/C++ runtime level. 4 Failed to meet Linux distribution level. 5 Failed to meet kernel bitwidth. 6 Missing InfiniBand Support Package. 7 Missing HPN Package. 8 Missing libxcrypt-compat package. 9 Other.	1 Upgrade the Operating System to a supported level. 2 Install a supported kernel level. 3 See the requirement verify log on the host and install a supported version of the package(s) that is missing or an unsupported version. 4 Upgrade to a supported Linux Distribution. 5 Ensure the kernel running on the host is 64 bit. 6 See the requirement verify log on the host and install a supported version of the package(s) that is missing or an unsupported version. 7 See the requirement verify log on the host and install a supported version of the package(s) that is missing or an unsupported version. 8 See the requirement verify log on the host and install a supported version of the package(s) that is missing or an unsupported version. 9 See the requirement verify log on the host and correct the issues it mentions. If the issue persists, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8306W	A host has failed requirement verification.	'db2cm -verify -req' did not pass on at least one host.	Run 'db2cm -varify -req -host' for each of the hosts that failed verification or collect the indicated log file from the host(s).
DBT8307W	A host was offline while running requirement verification.	'db2cm -verify -req' could not check at least one host in the cluster because it was offline or unreachable.	Bring the host online and rerun OS Verification.
DBT8308W	A quorum device has been removed where the cluster consists of only two nodes.	The cluster consists of only two nodes. This increases the risk of a split brain scenario if the quorum device is removed.	Create a quorum device to prevent a split brain scenario.
DBT8309E	The Google Cloud fence resource cannot be created. Reason code = `reason-code`.	The Google Cloud fence resource cannot be created, as indicated by these reason codes: 1 The Google Cloud fence resource that you are trying to create already exists. 2 The specified service account might not be correct. 3 An unexpected error occurred when attempting to create the Google Cloud fence primitive. 4 The Google Cloud project cannot be retrieved. 5 The Google Cloud CLI gcloud is not installed on one or more hosts. 6 Curl is not installed on one or more hosts. 7 The fencing executable cannot be found on one or more hosts. 8 The zone of the host cannot be retrieved.	1 Run the 'db2cm -list' command and check under Fencing Information to verify if the resource exists. If the resource needs to be recreated, delete the resource and the rerun the command. 2 Ensure that the following command is run successfully on all hosts: "gcloud auth activate-service-account --key-file=[service account key file]" If this 'gcloud' command fails, ensure that the service account is set up and that the key file is specified correctly. 3 Collect the results from running the 'db2support' command and contact IBM software support for assistance. 4 Ensure that the following command is run successfully on all hosts: "gcloud config get-value project" If this gcloud command fails, ensure that the Google Cloud CLI gcloud is installed correctly. 5 Ensure that the Google Cloud CLI gcloud is installed on all hosts and then rerun the 'db2cm' command. 6 Install Curl and then rerun the 'db2cm' command. 7 Ensure that the following command is run successfully on all hosts: "/usr/sbin/fence_gce --zone=[zone name] --serviceaccount=[service account file] --project=[project name] --action=status --plug=[hostname]" If the 'fence_gce' command fails, ensure that the following conditions exist and then rerun the 'db2cm' command: - The Google Cloud fence agents are installed. - The service account is correct. - The project name is correct. - The hostname is correct and used in the option plug. 8 Ensure that the following command is run successfully on all hosts: "curl -s -H Metadata-Flavor:Google --fail http://169.254.169.254/computeMetadata/v1/instance/zone" If this curl command fails, ensure that the curl is installed. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8310E	Failed to get the host failure detection time. Reason code: `reason-code`.	An error occurred when attempting to get the host failure detection time. 1 There is no active cluster manager domain. 2 The host failure detection time is inconsistent across the cluster. 3 The cluster manager and the shared file system cluster host failure detection times are not in sync. 4 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists and is online. 2 As the root user, run the command db2cm -set -option HostFailureDetectionTime -value %1' as root to set the detection time. 3 As the root user, run the command db2cm -set -option HostFailureDetectionTime -value %1' as root to set the detection time. 4 Collect db2support data and engage IBM Support. If the issue persists, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8311E	Failed to set host failure detection time to "`time`" seconds. Reason code: `reason-code`.	An error occurred when attempting to set the host failure detection time. 1 An invalid value has been specified. 2 There are online Db2 resources 3 There is no active cluster manager domain. 4 One or more hosts in the cluster are unreachable. 5 An internal error occurred.	1 Specify a valid value range from 3 to 60 seconds. 2 Stop the Db2 instance and then rerun the command. 3 Run the 'db2cm -list -domain' command to verify that the domain exists and is online. 4 Ensure that all hosts in the cluster are online and can be pinged, and then rerun the command. 5 Collect db2support data and engage IBM Support. If the issue persists, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8312E	Failed to verify the host failure detection time. Reason code: `reason-code`.	An error occurred when attempting to verify the host failure detection time. 1 There is no active cluster manager domain. 2 The host failure detection time is inconsistent across the cluster. 3 The cluster manager and the shared file system cluster host failure detection times are not in sync. 4 An internal error occurred.	1 Run the 'db2cm -list -domain' command to verify that the domain exists and is online. 2 As the root user, run the command db2cm -set -option HostFailureDetectionTime -value %1' as root to set the detection time. 3 As the root user, run the command db2cm -set -option HostFailureDetectionTime -value %1' as root to set the detection time. 4 Collect db2support data and engage IBM Support. If the issues persist, collect db2support data and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8313E	Failed to validate whether the cluster manager vendor packages are installed on the cluster. Reason code = `reason-code`.	The vendor packages are needed for the cluster manager operations to work. 1 One or more of the specified hosts do not have the vendor packages installed. 2 An internal error occurred.	1 Verify with the Db2 installation logs that the vendor packages were installed correctly. 2 Collect the results from running the 'db2support' command and contact IBM software support for assistance. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8314N	The tiebreaker policy is set on the cluster.	The tiebreaker policy is configured on the cluster. When set to 'preferPrimary', the node that is running the HADR PRIMARY database is favored during split-brain scenarios.	No action is required. Related information: db2cm - Manage Db2 cluster services command
DBT8315E	Failed to set tiebreaker policy. Reason: `reason`.	The tiebreaker policy can not be set on the cluster, as indicated by these reason codes (reason codes vary by command): 1 No database resource was found. 2 Multiple databases were found. Use the -db parameter to specify the database. 3 The tiebreaker policy is already configured on this cluster. 4 A Quorum Device is not configured on this cluster. 5 The specified database resource was not found. 6 The tiebreaker policy is not configured on this cluster. 99 An internal error occurred.	1 Run the 'db2cm -list' command to verify whether the database resource already exists. If the resource does not exist, create it using the 'db2cm -create -db' command. 2 Multiple databases exist. Specify which database to use with the -db parameter: 'db2cm -set -option tiebreakerPolicy -value preferPrimary -db dbName'. 3 Tiebreaker policy is already configured. No action needed, or remove existing configuration first using 'db2cm -set -option tiebreakerPolicy -value none'. 4 Configure a Quorum Device first using 'db2cm -create -qdevice' command. 5 Run the 'db2cm -list' command to verify whether the database resource exists and the database name is correct. 6 The tiebreaker policy has not been set. Use 'db2cm -set -option tiebreakerPolicy -value preferPrimary' to configure it first. 99 Collect db2support data and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8316E	The AWS Route 53 resource cannot be created. Reason code = `reason-code`.	This message is returned when an AWS Route53 resource could not be created. 1 The AWS Route53 resource that you are trying to create already exists. 2 The Db2 instance specified does not exist. 3 The database specified does not exist. 4 The full name of the AWS Route53 resource cannot be pinged. 5 The database resource does not exist. 6 The AWS CLI command is not installed under /usr/bin/. 7 The installed version of the AWS CLI command is below the minimum supported version. 8 Curl is not installed on one or more hosts. 9 The local EC2 configuration metadata server is unavailable. 10 The 'default' or provided profile does not exist. 11 The specified hosted zone does not exist or is not accessible. 12 The specified full name for the AWS Route53 resource does not exist in the hosted zone. 13 An internal error has been detected.	1 Run the 'db2cm -list' command and check under the 'Full List of Resources' section to verify if the resource exists. If the resource needs to be recreated, delete the resource and the rerun the command. 2 Run the 'db2cm -list' command to verify that the instance specified is both on the local host and included in the resource model under the 'Resource Information' section. When you have verified this information, rerun the db2cm command. 3 Run the 'db2cm -list' command and check under 'Resource Information' to verify that the database resource exists. 4 Ensure that the fully-qualified domain name that is provided can be pinged. 5 Run the 'db2cm -list' command and check under 'Resource Information' to verify that the database resource exists. 6 Ensure that the AWS command line tool (CLI) is installed on all hosts in the cluster before attempting to retry the command. The AWS CLI must be installed directly under '/usr/bin' or there must be a symbolic link from '/usr/bin/' to the AWS CLI executable. 7 Ensure that the installed version of the AWS CLI meets the minimum supported requirements. 8 Install curl and retry the db2cm command. 9 The IMDSv2 metadata service is unavailable on one or more hosts. 10 Ensure that the default AWS CLI profile has been configured by using 'aws configure', or, if using a profile other than 'default', rerun this command while specifying the profile name with the '-profile' option. 11 Ensure that the following command is run successfully on all hosts: 'awscli route53 list-resource-record-sets --hosted-zone-id [hosted zone ID] --profile [profile name]' replacing [fullname] by the fullname in the hosted zone. If this 'awscli' command fails, ensure that the hosted zone is set up correctly. 12 Ensure that the following command is run successfully on all hosts: 'awscli route53 list-resource-record-sets --hosted-zone-id [hosted zone ID] --query ResourceRecordSets[?Name=='[fullname]'].Name --output text --profile [profile name]' If this 'awscli' command fails, ensure that the fullname specified is set up correctly within the hosted zone specified. 13 Collect db2support and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command
DBT8317E	The AWS Route 53 resource cannot be deleted. Reason code = `reason-code`.	This message is returned when an AWS Route53 resource cannot be deleted. 1 The resource to be deleted does not exist. 2 The instance resource does not exist. 3 The database resource does not exist. 4 An internal error has been detected.	1 Run the 'db2cm -list' command and check under 'Resource Information' to verify that the Route53 resource exists. 2 Run the 'db2cm -list'command and check under 'Resource Information' to verify that the instance resource exists. 3 Run the 'db2cm -list'command and check under 'Resource Information' to verify that the database resource exists. 4 Collect db2support and engage IBM Support. If the issues persist, collect db2support and engage IBM Support. Related information: db2cm - Manage Db2 cluster services command