DBT8000-9999

DBT8000E

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

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

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

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:

1. Determine in which domain the host machine is ONLINE by issuing the lsrpdomain command.
2. Bring the host machine offline in the other domain by issuing the stoprpnode command.
3. Reissue the db2cluster command.

DBT8006E

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

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

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

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

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

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:

1. 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.
2. 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

1. See the db2diag.log for more information as to which instances and databases are using the disk.
2. 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:

1. Run db2cluster -cfs -list -filesystem to get the list of file systems in the cluster.
2. 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

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

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

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

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

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

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

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

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.

1. Assigns the list of disks in the file system to a valid redundancy group ID.
2. Re-balances data between the two redundancy groups.

This message is displayed when step 1 is completed successfully.

No response is required

DBT8020I

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

This message is returned for your information only.

No response is required

DBT8022I

This message is returned for your information only.

No response is required.

DBT8023E

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

The db2cluster command failed because the specified file system does not exist or is invalid.

Enter the command again using valid values.

DBT8025E

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

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

This message is returned for your information only.

No response is required.

DBT8028I

This message is returned for your information only.

No response is required.

DBT8029E

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

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

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

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 failed to replicate the files system because of an internal error.

Correct the error displayed on screen and re-issue the command.

DBT8034I

This informational message indicates that file system is being replicated between the redundancy groups.

No action is required.

DBT8035W

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

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

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

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

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

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

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

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

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

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:

1. 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.
2. 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

1. See the db2diag.log for more information as to which instances and databases are using the disk.
2. 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:

1. Run db2cluster -cfs -list -filesystem to get the list of file systems in the cluster.
2. 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

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

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:

1. 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.
2. 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

1. See the db2diag.log for more information as to which instances and databases are using the disk.
2. 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

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

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

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

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 -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 doesn't 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 -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

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

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

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

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

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

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

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

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 Spectrum 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 Spectrum 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

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

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

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

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

You can remove a file system in Spectrum 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

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

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

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 Spectrum 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

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

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

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

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.