DBT3000-3999

DBT3007I

The db2IdentifyType1 command found type-1 indexes and updated the specified output command file with the appropriate REORG INDEX statements required to convert the indexes into type-2 indexes.

The file-name command file can be used only in Version 9.5 or earlier releases.

To convert the type-1 indexes to type-2, perform the following actions:

1. Verify that the file-name command file contains REORG statements for all the indexes that you want to convert.
2. [Optional] Remove from the file-name command file the REORG statements for any indexes that you want to convert later.
3. Convert type-1 indexes that are listed in the command file that the db2IdentifyType1 utility created to type-2 indexes by executing the commands in the command file using the command line processor:

    db2 -tvf <file_name> 

DBT3008I

The db2IdentifyType1 command did not detect any type-1 indexes and did not create a command file. Type-1 indexes might still exist because the db2IdentifyType1 command cannot detect whether type-1 or type-2 indexes exist in typed tables and ignores them during its processing.

No further action is required for Version 9 databases.

Perform the following steps to determine whether type-1 indexes and typed tables exist and to manually run the REORG INDEXES ALL commands for these tables:

1. Generate a list of all the root tables for typed tables by issuing the following query:

    SELECT DISTINCT H.ROOT_SCHEMA, H.ROOT_NAME,     T.TBSPACEID, T.TABLEID   FROM SYSCAT.TABLES T, SYSCAT.INDEXES I,      SYSCAT.HIERARCHIES H,      SYSCAT.NAMEMAPPINGS N WHERE T.TYPE = 'H' AND       T.TABSCHEMA = I.TABSCHEMA AND       T.TABNAME = I.TABNAME AND       H.METATYPE='U' AND       H.ROOT_SCHEMA=N.LOGICAL_SCHEMA AND       H.ROOT_NAME=N.LOGICAL_NAME  AND       T.TABSCHEMA=N.IMPL_SCHEMA AND       T.TABNAME=N.IMPL_NAME 

2. Decide whether to run REORG INDEXES ALL commands for all the typed tables regardless of the index type associated with them or for only the subset of typed tables with type-1 indexes. When deciding, evaluate the amount of time and resources required to manually determine the subset of typed tables. Running the REORG INDEXES ALL command with the CONVERT clause against tables with type-2 indexes has no effect.
3. To process only the subset of typed tables with type-1 indexes,use the INSPECT and the db2inspf commands, as follows:

    db2 INSPECT CHECK TABLE      NAME root_table_name RESULTS     KEEP sample.log       db2inspf      $INSTHOME/sqllib/db2dump/sample.log     sample.out 

   Use the index type for each root table to match the values for TBSPACEID and TABLEID from the query that generated the list of root tables to the Object and Tablespace identifiers in the formatted output from the db2inspf command, as shown in the following output:

    Table phase start (ID Signed: 4, Unsigned: 4;  Tablespace ID: 3) :    Data phase start. Object: 4  Tablespace: 3   The index type is 1 for this table.    Traversing DAT extent map, anchor 96.    Extent map traversal complete.    DAT Object Summary: Total Pages 20 - Used  Pages 20       - Free Space 2 %   Data phase end.    Index phase start. Object: 4  Tablespace: 3    Traversing INX extent map, anchor 160.    Extent map traversal complete.    INX Object Summary: Total Pages 17 - Used  Pages 17       Index phase end.     Table phase end.   Tablespace phase end. 

4. Run REORG INDEXES ALL commands for all the root tables or for the subset of tables with type-1 indexes, as shown in the following example:

    db2 REORG INDEXES ALL      FOR TABLE root_table_name      ALLOW WRITE ACCESS CONVERT 

DBT3009I

No output was generated because there are no indexes on the tables inspected by the db2Identify Type1 command.

Since there are no indexes on the inspected tables, you do not need to do any index conversion.

DBT3101E

The db2IdentifyType1 command requires a database name so that it can establish a database connection.

The basic syntax for the command is as follows: db2IdentifyType1 -d database_name -o file_name. When these two parameters are not specified correctly, the command cannot run.

Refer to the Command Reference for more information about the db2IdentifyType1 command or type db2IdentifyType1 -h to display help information.

Specify a database name using the correct syntax, and run the command again.

DBT3102E

The db2IdentifyType1 command requires the name of a file to which it can write its output.

The basic syntax for the command is as follows: db2IdentifyType1 -d database_name -o file_name. When these two parameters are not specified correctly, the command cannot run.

The file name can be qualified with a full or relative path, and it cannot exceed 246 characters.

Refer to the Command Reference for more information about the db2IdentifyType1 command or type db2IdentifyType1 -h to display help information.

Specify a valid file name using the correct syntax, and run the command again.

DBT3103E

A parameter was specified without a value. Refer to the Command Reference for more information about the db2IdentifyType1 command or type db2IdentifyType1 -h to display help information.

Specify a value for the parameter, and run the command again.

DBT3104E

The db2IdentifyType1 command can process only one database, table, or schema at a time. Multiple database names, table names and schema names are not supported.

Refer to the Command Reference for more information about the db2IdentifyType1 command or type db2IdentifyType1 -h to display help information.

Remove the duplicate parameter, and run the command again.

DBT3105E

The values for the parameters of the db2IdentifyType1 command follow the DB2 naming rules for database names, table names, and schema names. The length of the output file name, including the path, cannot exceed 246 characters.

Provide a value that complies with the name length restrictions, and run the command again.

DBT3106E

The db2IdentifyType1 command does not recognize the parameter that was provided.

Refer to the Command Reference for more information about the db2IdentifyType1 command or type db2IdentifyType1 -h to display help information.

Specify a valid parameter and run the command again.

DBT3107E

Refer to the Command Reference for more information about the db2IdentifyType1 command or type db2IdentifyType1 -h to display help information.

Remove the additional values and run the command again.

DBT3108I

The db2IdentifyType1 command can only inspect Version 8 or later databases.

Migrate the database to Version 8 or later, then run the command again.

DBT3109E

The db2IdentifyType1 command could not find the schema that was specified.

Schema name identifiers must be specified as they appear in the system catalog tables, using uppercase. Delimited schema name identifiers must be enclosed in double quotation marks.

Specify a valid schema name using the correct syntax, and run the command again.

DBT3110E

The db2IdentifyType1 command could not find the table that was specified.

Table name identifiers must be specified as they appear in the system catalog tables, using uppercase. Delimited table name identifiers must be enclosed in double quotation marks.

Specify a valid table name using the correct syntax, and run the command again.

DBT3201E

The db2IdentifyType1 command was unable to allocate an environment handle. This error could occur if the environment for the database manager instance was not set up correctly.

Before running the db2IdentifyType1 command again, you need to set up the database manager instance environment. Using the ID that owns the instance, you can open a new login window or run one of the following commands:

For Bourne or Korn shell

. $HOME/sqllib/db2profile

For C shell

source $HOME/sqllib/db2cshrc

where $HOME represents the home directory of the user ID that owns the instance.

DBT3202E

The db2IdentifyType1 command was unable to allocate a connection handle. Troubleshooting information was logged in the db2IdentifyType1.err file that is located in the same path specified for the -o parameter.

Review the content of the db2IdentifyType1.err file. Correct the problem and run the command again.

DBT3203E

There was a database connection problem that stopped the processing of the db2IdentifyType1 command.

The following situations might have caused the database connection error:

• The name specified for the database does not exist.
• The DB2 user ID and password are incorrect.
• The database is not available.

Troubleshooting information was logged in the db2IdentifyType1.err file that is located in the same path specified for the -o parameter.

Review the content of the db2IdentifyType1.err file. Correct the problem and run the command again.

DBT3204E

The db2IdentifyType1 command was unable to determine whether the user ID has the correct authorization for running the command. Either SYSADM or DBADM authority is required. Troubleshooting information was logged in the db2IdentifyType1.err file that is located in the same path specified for the -o parameter.

Review the content of the db2IdentifyType1.err file. Correct the problem and run the command again.

DBT3205E

The db2IdentifyType1 command must be run by a user ID with DBADM or SYSADM authority. No output was generated.

Run the command again with a user ID that has DBADM or SYSADM authority.

DBT3206E

A database connection problem caused the db2IdentifyType1 command to stop running.

Troubleshooting information might have been logged in the db2IdentifyType1.err file that is located in the same path specified for the -o parameter.

Ensure that the database is still accessible and run the command again.

DBT3207E

The db2IdentifyType1 command was unable to write its output to the file specified. One of the following conditions might have caused this error:

• The disk might be full or have inadequate space to complete the operation.
• The user ID might not have the correct privileges to write to the file directory.
• The file location might not have been mounted.

Correct the problem and run the command again.

DBT3208E

The db2IdentifyType1 command was unable to allocate a statement handle. Troubleshooting information was logged in the db2IdentifyType1.err file that is located in the same path specified for the -o parameter.

Review the content of the db2IdentifyType1.err file. Correct the problem and run the command again.

DBT3209E

An error occured when attempting to load a module that is required by the db2IdentifyType1 command. This can happen if the named module is not found or a resource error occurs.

Ensure that the named module exists in the same directory as the db2IdentifyType1 program or correct the error indicated by the sqlcode, then run the db2IdentifyType1 command again.

DBT3500E

You can verify installation prerequisites using the db2prereqcheck utility.

You can define the releases of DB2 database for which you want to verify installation prerequisites in an XML resource file. This message is returned when the db2prereqcheck utility cannot find the specified XML resource file or the default XML resource file.

Perform one of the following actions:

• Specify the XML resource file using the -f parameter with the db2prereqcheck command.
• If you did not specify the XML resource file using the -f parameter, check to see if the default XML resource file exists in the default installation directory.

DBT3501E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot open a file during normal processing. Because the db2prereqcheck utility runs with the same privileges as the user who ran the db2prereqcheck command, this message can be returned when the user who ran the db2prereqcheck command does not have read and write permission for the named file.

Respond to this message in one of the following ways:

• Modify the permissions of the named file so that your user id has read and write permission for the file.
• Log in to your system with a user ID that has read and write permission on the file.
• Ask someone who has read and write permission on the file to run the db2prereqcheck command.

DBT3502E

You can verify installation prerequisites using the db2prereqcheck utility.

You can define the releases of DB2 database for which you want to verify installation prerequisites in an XML resource file. This message is returned when an invalid version is specified in the XML resource file.

Correct the XML resource file and run the db2prereqcheck command again.

DBT3503E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when an invalid parameter is specified with the db2prereqcheck command.

1. Review the db2prereqcheck command syntax.
2. Run the db2prereqcheck command again, specifying valid parameters.

DBT3504E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot determine the current level of the operating system.

Perform one of the following actions:

• Review operating systems that are supported with DB2 database and the db2prereqcheck utility.
• Manually retrieve or look up the operating system level.

DBT3505E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot determine the distribution level of the current Linux operating system. There are several reasons why the utility might be unable to determine the distribution level. For example, the utility might be unable to determine the distribution level if the utility cannot find or read the system file called /etc/issue.

The db2prereqcheck utility cannot perform all of the the necessary prerequisite verification steps without knowing the distribution level of the current Linux operating system. In order for the db2prereqcheck utility to be used to verify installation prerequisites, the problem that prevented the utility from determining the distribution level must be resolved.

To enable the db2prereqcheck utility to determine the distribution level of the current Linux operating system, perform the following actions:

• Ensure that the system file called /etc/issue exists.
• Ensure that the system file called /etc/issue contains distribution level details.
• Run the db2prereqcheck command as a user who has read permission for the system file called /etc/issue.

DBT3506E

You can verify installation prerequisites using the db2prereqcheck utility.

While verifying installation prerequisites, the db2prereqcheck utility uses the Resource Package Manager utility. This message is returned when the db2prereqcheck utility call the rpm command and that rpm command fails.

1. Determine the cause of the rpm failure by reviewing diagnostic information in the db2prereqcheck report file.
2. Resolve the cause of the rpm failure.
3. Call the db2prereqcheck command again.

DBT3507E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot find the named package or file while the utility is verifying installation prerequisites.

To review the diagnostic report file, run db2prereqcheck with -o option. By default, prerequisite validation is displayed on screen.

DBT3508E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility encounters an error that the utility cannot classify or resolve.

1. Run with db2prereqcheck -o option.
2. Identify the cause of the problem by reviewing diagnostic information in the db2prereqcheck report file.
3. Resolve the cause of the problem.
4. Run the db2prereqcheck command again.

DBT3509E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility needs to determine the version of a package to verify installation prerequisites, but the utility cannot determine the version of the package.

Review the list of operating systems and software that are supported with DB2 database manually.

DBT3510E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot find a library file that is required to verify installation prerequisites.

Manually verify that the installation prerequisites are met.

DBT3511E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot find a map file that is required to verify installation prerequisites.

Verify manually whether installation prerequisites are met.

DBT3512W

You can verify installation prerequisites using the db2prereqcheck utility.

The current system might meet installation prerequisites even if the db2prereqcheck utility cannot determine the version of the C++ standard library that is installed.

Manually verify that the system has the required version of C++ standard library.

DBT3513W

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility uses several different methods for determining the current version of the C++ standard library. This message is returned when the db2prereqcheck utility attempts to determine the version of the currently-install C++ standard library using the ldconfig utility.

The current system might meet installation prerequisites even if the db2prereqcheck utility cannot determine the version of the C++ standard library that is installed.

Manually verify that the system has the required version of C++ standard library.

DBT3514W

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot find the 32-bit version of a required library file. If the named file is missing, 32-bit database applications might not function properly.

Respond to this message in one of the following ways:

• If you do not intend to use 32-bit applications with DB2 database, then no response is required.
• If you do intend to use 32-bit applications with DB2 database, ensure that the named 32-bit library file exists on the system before installing DB2 database.

DBT3515E

You can verify installation prerequisites using the db2prereqcheck utility.

Verify manually whether installation prerequisites are met.

DBT3516E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility attempts to execute a command to verify installation prerequisites, but the command fails.

Verify manually whether the installation prerequisites are met.

DBT3517E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot read a file during normal processing. Because the db2prereqcheck utility runs with the same privileges as the user who ran the db2prereqcheck command, this message can be returned when the user who ran the db2prereqcheck command does not have read and write permission for the named file.

Respond to this message in one of the following ways:

• Modify the permissions of the named file so that your user id has read and write permission for the file.
• Log in to your system with a user ID that has read and write permission on the file.
• Ask someone who has read and write permission on the file to run the db2prereqcheck command.

DBT3518E

You can verify installation prerequisites using the db2prereqcheck utility.

Manually verify that the system has the required AIX service pack level.

DBT3519E

You can verify installation prerequisites using the db2prereqcheck utility.

Manually verify that the system has the required AIX Technology Level (TL).

DBT3520E

You can verify installation prerequisites using the db2prereqcheck utility.

Verify manually whether the installation prerequisites are met.

DBT3521E

You can verify installation prerequisites using the db2prereqcheck utility.

Verify manually whether the prerequisites are met.

DBT3522E

You can verify installation prerequisites using the db2prereqcheck utility.

Verify manually whether the installation prerequisites are met.

DBT3523E

You can verify installation prerequisites using the db2prereqcheck utility.

Verify manually whether installation prerequisites are met.

DBT3524E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility determines that the version of the currently-install Windows operating system is not supported by one or more versions of DB2 database that were specified in the db2checkprereq XML resource file.

To install DB2 database, change the Windows operating system to a version that is supported by DB2 database.

DBT3525E

You can verify installation prerequisites using the db2prereqcheck utility.

You can define the releases of DB2 database for which you want to verify installation prerequisites in an XML resource file. This message is returned when the db2prereqcheck utility cannot process the contents of the specified XML resource file or the default XML resource file.

Correct the contents of the XML resource file and then run the db2prereqcheck command again.

DBT3526E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility produces an output, report file that contains a log of the prerequisites checked and the success of the verification. There is a default report file name, but you can also specify the name of the report file using the -o parameter with the db2prereqcheck command.

This message is returned when the value specified with the -o parameter is not valid for a file name. For example, this message can be returned when the value specified with the -o parameter is not in a format that is valid for a file name.

Respond to this message in one of the following ways:

• Run the db2prereqcheck command again, specifying a valid file name with the -o parameter.
• Use the default report file name by runing the db2prereqcheck command again, without specifying the -o parameter.

DBT3527E

You can verify installation prerequisites using the db2prereqcheck utility.

You can specify a version using the -v parameter with the db2prereqcheck command.

This message is returned when a value is specified for the -v parameter with the db2prereqcheck command, but the specified value does not match any valid versions of DB2 database defined in the resource XML file.

Call the db2prereqcheck command again, specifying a valid version with the -v parameter.

DBT3528E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility reads information about which prerequisites to check from an input XML resource file. There is a default XML resource file name, but you can also specify the name of the XML resource file using the -f parameter with the db2prereqcheck command.

This message is returned when the file specified with the -f parameter is not in valid XML file or its content is not in the format recognized by db2prereqcheck tool.

Respond to this message in one of the following ways:

• Call the db2prereqcheck command again, specifying a valid XML resource file with the -f parameter.
• Use the default XML resource file by calling the db2prereqcheck command again, without specifying the -f parameter.

DBT3529E

You can verify installation prerequisites using the db2prereqcheck utility.

You can control what kinds of tests the db2prereqcheck utilty performs and the output format by specifying various parameters with the db2prereqheck command.

This message is returned when mutually exclusive parameters are specified with the db2prereqcheck command.

Call the db2prereqcheck command again, specifying valid parameters.

DBT3530E

You can verify installation prerequisites using the db2prereqcheck utility.

You can specify a version using the -v parameter with the db2prereqcheck command.

If you use an XML resource file that lists one or more versions of DB2 database, you can cause the db2prereqcheck utility to verify the installation prerequisites for only the latest version that is specified in the XML resource file by specifying the -i parameter with the db2prereqcheck command.

This message is returned when the -i parameter is specified with the db2prereqcheck command, but the db2prereqcheck utility failed to determine what the latest version is that is specified in the XML resource file contents. There are multiple reasons for which the db2prereqcheck utility might be unable to retrieve the latest version from the XML resource file, including the following reasons:

• No DB2 database versions are specified in the XML resource file.
• The format of the XML resource file is not valid.
• The DB2 database versions that are specified in the XML resource file are not valid.

1. Perform the following troubleshooting steps:
   • Ensure that the format of the XML resource file is valid.
   • Ensure that one or more versions of DB2 database are correctly specified in the XML resource file.
2. Call the command again in one of the following ways:
   • Verify prerequisites for the latest version that is defined in the resource XML file by calling the db2prereqcheck command with the -i option.
   • Verify prerequisites for all DB2 database versions that are defined in the resource XML file by calling the db2prereqcheck command without the -i option.

DBT3531E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility produces a report file that contains information about the installation prerequisites that were verified on the current system.

This message is returned when an error occurs while db2prereqcheck is attempting to print information to the report file.

1. Verify that the user has a write permission to the report file.
2. Review the information in the message that could not be printed to the report file, and then consider that information when you review the information that is in the report file.

DBT3532E

You can verify installation prerequisites using the db2prereqcheck utility.

To install this database product, use a 64-bit operating environment.

DBT3533I

You can verify installation prerequisites using the db2prereqcheck utility.

No response is required.

DBT3535W

On Linux operating systems on an InfiniBand network or a 10 Gigabit Ethernet (10GE) RoCE network, specific InfiniBand Support packages are required. For a list of required packages, see the DB2 pureScale Feature installation prerequisites for Linux topic.

To install the required InfiniBand software, run a group installation of the InfiniBand Support package using the yum command.

DBT3536E

On Linux operating systems on a 10 Gigabit Ethernet (10GE) RoCE network, specific High Performance Networking (HPN) packages are required. For a list of required packages, see the DB2 pureScale Feature installation prerequisites for Linux topic.

To install the required HPN packages, run a group installation of the InfiniBand Support package using the yum command.

DBT3537W

On Linux operating, specific remote direct memory access (RDMA) packages are required.

Install the required RDMA packages.

DBT3538E

You can verify installation prerequisites using the db2prereqcheck utility.

You can specify the type of network configuration for which the db2prereqcheck utility should verify prerequisites using the -t parameter. There are four valid values for the -t parameter:

• SINGLE_IB_PORT_CLUSTER
• MULTI_IB_PORT_CLUSTER
• SINGLE_ROCE_PORT_CLUSTER
• MULTI_ROCE_PORT_CLUSTER

This message is returned when an invalid value is specified for the -t parameter.

Call the db2prereqcheck command again, specifying a valid value with the -t parameter.

DBT3539E

You can verify installation prerequisites using the db2prereqcheck utility.

You can verify installation prerequisites specifically for the DB2 pureScale environment by specifying the -p parameter. If you specify that the db2prereqcheck utility should verify the prerequisites for the DB2 pureScale environment, you can also specify the type of network configuration for which the db2prereqcheck utility should verify prerequisites using the -t parameter.

If you do not specify the -p parameter, the -t parameter must not be specified.

Respond to this error in one of the following ways:

• If you are verifying installation prerequisites for a DB2 pureScale environment, call the db2prereqcheck command again, specifying the -p parameter with or without the -t parameter.
• If you are not verifying installation prerequisites for a DB2 pureScale environment, call the db2prereqcheck command again without specifying the -t parameter.

DBT3540E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility requires the following minimum operating system levels:

• AIX 6.1
• HP-UX 11iv3
• Solaris 10

Run the db2prereqcheck command on a system with a supported operating system level.

DBT3541E

The database manager performs a variety of system validation steps, including using the db2prereqcheck utility, before installing the database product and before creating or managing database manager instances.

This message is returned when an unhandled error is encountered by the db2prereqcheck utility as part of those larger install or instance management operations.

Contact IBM support for help with resolving this problem.

DBT3542E

The database manager performs a variety of system validation steps, including using the db2prereqcheck utility, before installing the database product and before creating or managing database manager instances.

The reason code indicates a specific reason for the error:

1

The database manager or the db2prereqcheck utility failed to open the file called "/etc/hosts".

2

The database manager or the db2prereqcheck utility failed to determine the IP address of the machine on which the cluster caching facility is located.

Respond to this error by performing troubleshooting steps according to the given reason code:

Reason code 1

Ensure the system file called "/etc/hosts" exists, is accessible, and that the file contents are standard for a hosts file.

Reason code 2

Ensure that the host machines in the DB2 cluster are up and running, and the the network in the cluster is functioning normally.

DBT3543E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the utility encounters an error while printing a message in the current user language.

The failure to print one message might not affect the usefulness of the db2prereqcheck utility. However, if this error happens multiple times, this might indicate a problem with the installation of the db2prereqcheck utility.

Respond to this error in one or more of the following ways:

• Run the db2prereqcheck utility in English by setting the locale to English and then calling the db2prereqcheck command.
• Download a new copy of the db2prereqcheck utility.

DBT3544E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility uses the system command, "uname", to determine the level of the current operating system. There are multiple reasons that the db2prereqcheck utility might be unable to determine the operating system level by using the uname command, including the following examples:

• The call to the uname system command failed.
• The output of the uname system command is not what the db2prereqcheck utility was designed to expect.

Manually determine the version of the operating system and verify whether the current operating system version is supported with the database product being installed.

DBT3545E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility fails to open a temporary file while performing the prerequisite verification.

Run the db2prereqcheck utility again.

DBT3546E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility is unable to perform the prerequisites validation because the utility cannot find the given file or package.

Manually verify prerequisites for the database product.

DBT3547E

You can verify installation prerequisites using the db2prereqcheck utility.

Verify manually whether installation prerequisites are met.

DBT3548E

You can verify whether a system meets the prerequisites for database product releases and fix packs that are defined in a resource XML file. You can cause the db2prereqcheck utility to read from a specified resource XML file by using the -f parameter with the db2prereqcheck command, or you can allow the db2prereqcheck utility to use a default resource XML file.

This message is returned when the db2prereqcheck utility fails to open the resource XML file, either a file specified with the -f parameter, or the default file.

Call the db2prereqcheck command again, specifying a resource XML file that the db2prereqcheck utility can access.

DBT3549E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies system details by using system commands and examining various system configuration files. This message is returned when the db2prereqcheck utility is unable to extract necessary information from the output of a system command or the contents of a system configuration file.

Verify manually whether installation prerequisites are met.

DBT3550E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies system details by using system commands and examining the contents of system configuration files. This message is returned when the db2prereqcheck utility fails to extract the necessary package information from the output of the lslpp command.

Verify manually whether installation prerequisites are met.

DBT3551E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies system details by using system commands and examining the contents of system configuration files. This message is returned when the db2prereqcheck utility fails to extract the necessary package information from the output of the lslpp command.

Verify manually whether installation prerequisites are met.

DBT3552E

You can verify installation prerequisites using the db2prereqcheck utility.

Verify manually whether installation prerequisites are met.

DBT3553I

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies system details using system commands and system configuration files. This message is returned when the db2prereqcheck utility successfully loads a system file.

No user response is required.

DBT3554W

You can verify installation prerequisites using the db2prereqcheck utility.

The Input/Output Completion Port (IOCP) is required by the database server.

To successfully run a database server, install and configure IOCP manually.

DBT3555E

You can verify installation prerequisites using the db2prereqcheck utility.

No response is required

DBT3556W

You can verify installation prerequisites using the db2prereqcheck utility.

No response is required.

DBT3557E

You can verify installation prerequisites using the db2prereqcheck utility.

No user response is required.

DBT3558E

You can verify installation prerequisites using the db2prereqcheck utility.

The -c, -u, -g, and -p parameters are mutually exclusive.

Call the db2prereqcheck command again, specifying only one of the parameters -c, -u, -g, or -p.

DBT3559E

You can verify installation prerequisites using the db2prereqcheck utility.

Call the db2prereqcheck command again, specifying a valid value with the -a parameter.

DBT3560I

You can verify installation prerequisites using the db2prereqcheck utility.

No response is required.

DBT3561E

You can verify installation prerequisites using the db2prereqcheck utility.

Manually verify installation prerequisites.

DBT3562E

You can verify installation prerequisites using the db2prereqcheck utility.

Because some requirements, such as General Parallel File System (GPFS), are not compatible with Security-Enhanced Linux (SELinux) enabled, the db2prereqcheck utility attempts to determine whether SELinux is enabled. This message is returned when the db2prereqcheck utility is unable to determine whether SELinux is enabled.

Manually verify installation prerequisites.

DBT3563E

You can verify installation prerequisites using the db2prereqcheck utility.

DB2 database requires a General Parallel File System (GPFS.) However, GPFS is not supported with Security-Enhanced Linux (SELinux) enabled.

Disable SELinux and then proceed with the database product installation.

DBT3564E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility is unable to perform the prerequisites validation because the utility cannot find the given file or package on the given host machine.

Manually verify prerequisites for the database product.

DBT3565E

You can verify installation prerequisites by using the db2prereqcheck utility.

In versions of DB2 database earlier than DB2 Version 10.5, passwordless remote root login must be enabled to install DB2 database. This message is returned when passwordless remote root login needs to be enabled but the db2prereqcheck utility determined that passwordless remote root login is not currently enabled on the named host machine.

Enable passwordless remote root login on all host machines on which the DB2 database install will be performed, and then perform the installation operation.

DBT3566E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility attempts to determine whether all system services that are required for successfully installing DB2 database are enabled. This message is returned when the db2prereqcheck utility detects that a required system service is not enabled.

Manually verify installation prerequisites.

DBT3567E

You can verify installation prerequisites by using the db2prereqcheck utility.

To install and configure DB2 pureScale, one of the following communication methods must be configured for all host machines in the DB2 cluster:

• db2locssh
• Passwordless SSH

This message is returned when the db2prereqcheck utility determines that neither db2locssh nor passwordless SSH is enabled between the named host machines.

Respond to this error in one of the following ways:

• Configure db2locssh.
• Enable passwordless SSH on all host machines on which the DB2 database install will be performed.

Then perform the installation operation.

DBT3568E

You can verify installation prerequisites by using the db2prereqcheck utility.

The input/output Completion Port (IOCP) is required by the database server.

This message is returned when the db2prereqcheck utility detects that no input/output completion ports are installed on the given host machine.

Manually install and configure IOCP on the named host machine.

DBT3569E

You can verify installation prerequisites by using the db2prereqcheck utility.

The input/output Completion Port (IOCP) is required by the database server.

This message is returned when the db2prereqcheck utility detects that no input/output completion ports are enabled on the given host machine.

Manually install and configure IOCP on the named host machine.

DBT3570W

You can verify installation prerequisites by using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot determine either the physical volume identifier (PVID) or the worldwide identifier (WWID) for the specified device path. This information is useful for verifying disk and network prerequisites.

If the db2prereqcheck utility is unable to determine the PVID or WWID, the db2prereqcheck can still successfully perform prerequisite checking. However, if the device path is used for install or instance management runtime operations in the future, the underlying problem that prevented the db2prereqcheck utility from determining the PVID or WWID might also cause errors with install or instance management utilities.

To prevent potential future errors with install or instance management tasks, configure an identifier for the specified device.

DBT3571E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database.

This message is returned when the db2prereqcheck utility determined that there is insufficient space in the named directory on the given host machine for the installation of the database product to proceed successfully.

Respond to this message in one of the following ways:

• Allocate more space in the given directory on the given host machine.
• Specify a different directory that has more available space.

DBT3572W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck is unable to successfully use the ping command to test connectivity and network response time from the given host machine to the given cluster interconnect netname.

Configure the network so that the specified netname is accessible on the network from the host machine.

DBT3573W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck finds that TCP/IP has been configured incorrectly for the named host machine.

Configure TCP/IP for the named host machine.

DBT3574E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the /etc/hosts file has not been configured correctly on the named host machine.

Configure the /etc/hosts file on the host machine.

DBT3575W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the /etc/hosts file has not been configured correctly on the named host machine.

Configure the /etc/hosts file on the host machine.

DBT3576W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the /etc/hosts file has not been configured correctly on the named host machines.

Configure the /etc/hosts file on the listed host machines.

DBT3577E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

In the dat.conf file on the host machine, add an entry for the library.

DBT3578E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

In the dat.conf file on the host machine, configure an entry for the netname.

DBT3579E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

Configure only one dat.conf file on the host machine.

DBT3580E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

Configure a dat.conf file on the host machine.

DBT3581E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. For example, one of the tests that the db2prereqcheck utility performs is to run the simple command "ls <user-id>" to determine whether there is a home directory for the user.

This message is returned when the db2prereqcheck utility encounters a problem with a required user account on a host machine:

• An account for the user does not exist on the host machine
• The db2prereqcheck utility cannot find a home directory for the user on the host machine

Create the required user accounts on the host machine.

DBT3582E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that a required user id does not exist on all required host machines.

Create the required user accounts on all host machines.

DBT3583E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that a required user id does not exist on all required host machines.

Create the required user accounts on all host machines.

DBT3584E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that a required user id does not exist on the host machine.

Create the required user accounts on all host machines.

DBT3585E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility is unable to perform the prerequisites validation because the utility cannot find the given file or package.

Manually verify prerequisites for the database product.

DBT3586E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility finds two packages are installed that are not supported together.

Remove either the HPN package or the Mellanox package.

DBT3587E

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility is unable to perform the prerequisites validation.

Manually verify prerequisites for the database product.

DBT3588W

In DB2 pureScale environments, the Mellanox HCA driver mlx4_core parameter named log_mtts_per_seg must be configured in the modprobe configuration file, modprobe.conf, on host machines where any cluster caching facility (CF) resides. If this configuration parameter is not set appropriately, errors could occur when the database manager is started with the db2start command.

This message is returned when the db2prereqcheck utility is unable to validate the setting of log_mtts_per_seg on the given host machine for the reason indicated by the reason code:

1

The db2prereqcheck utility cannot find the file modprobe configuration file on the host machine.

2

The db2prereqcheck utility cannot find an entry for the log_mtts_per_seg parameter in the modprobe configuration file in the host machine.

• If there is no CF on the host machine, no user response is required.
• If there is a CF on the host machine, manually verify the configuration of the log_mtts_per_seg parameter.

DBT3589W

Configuring I/O completion ports (IOCPs) on AIX servers is not required for the installation of DB2 for Linux, UNIX, and Windows software. However, this configuration step is recommended for performance purposes.

Optional: Manually configure IOCP.

DBT3590W

You can verify installation prerequisites using the db2prereqcheck utility.

Part of the prerequisite verification that the db2prereqcheck utility performs includes verifying whether storage prerequisites have been met.

In DB2 pureScale environments, because the DB2 pureScale Feature requires the use of a storage area network (SAN), the db2prereqcheck utility attempts to determine whether a disk on a host machine is a member of a SAN.

• If you are not using the DB2 pureScale Feature, no response is required.
• If you are using the DB2 pureScale Feature, manually verify whether the disk is a part of a SAN.

DBT3591E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

Manually verify the contents of the dat.conf file on the host machine.

DBT3592E

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck finds that TCP/IP has been configured incorrectly for the named host machine.

Configure TCP/IP for the named host machine.

DBT3593W

In pureScale environments, the Mellanox HCA driver mlx4_core parameter named log_mtts_per_seg must be configured in the modprobe configuration file, modprobe.conf, on host machines where any cluster caching facility (CF) resides.

This message is returned when the log_mtts_per_seg parameter is not configured to the recommended value of "7" on the host machine.

• If there is no CF on the host machine, no user response is required.
• If there is a CF on the host machine, manually configure the log_mtts_per_seg parameter to the recommended value.

DBT3594W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database.

This message is returned when the db2prereqcheck utility determines that there is less than the recommended amount of space in the named directory on the given host machine, but that installing the database product could proceed successfully.

Note that although having less than the recommended amount of space on the directory named in the run time token directory-name might not prevent installing the database product from succeeding, having less than the recommended amount of space could cause run time performance problems or other errors in the future.

[Optional] Respond to this message in one of the following ways:

• Allocate more space in the given directory on the given host machine.
• Specify a different directory that has more available space.

DBT3595W

One prerequisite for the DB2 pureScale Feature is that Intel TCO WatchDog Timer Driver modules must be blacklisted with modprobe.

Installing DB2 database might succeed if the Intel TCO WatchDog Timer Driver modules are not blacklisted. However, you will encounter runtime errors creating database manager instances if these modules are not blacklisted.

Blacklist the module by adding an entry in the appropriate configuration file under the /etc/modprobe.d directory.

DBT3596W

You can verify that prerequisites for installing DB2 database by using the db2prereqcheck utility.

One requirement for installing the DB2 pureScale Feature is that all machines in the cluster are using the same operating system.

This message is returned when db2prereqcheck determines that not all machines in the cluster are running the same operating system.

Install the same operating system on all host machines in the cluster.

DBT3597W

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies many prerequisites, including space requirements.

This message is returned when the db2prereqcheck tool determines that there is less than the recommended amount of free space available for one or both of the following paths:

• The default installation path (/opt)
• The instance home directory path (/home)

Optional:

1. Review space requirements for the product in your environment.
2. Make the recommended amount of space available on /opt and /home.

DBT3598W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility detects an Interface Adapter (IA) that is not configured in the /etc/hosts and direct access transport file, dat.conf, on the host machine.

If the adapter supports Remote Direct Memory Access(RDMA), configure the adapter in the /etc/hosts file and the dat.conf file on the host machine.

DBT3599W

You can verify installation prerequisites by using the db2prereqcheck utility.

You can cause the db2prereqcheck utility to verify communication between all hosts in RDMA over Converged Ethernet (RoCE) and InfiniBand networks by specifying a list of netnames in the network. This message is returned when the the db2prereqcheck utility is unable to verify one of the specified netnames, because the netname is not listed in the etc/hosts file or is not configured in the direct access transport file, dat.conf.

To verify the netname, configure the netname in the etc/hosts file and the dat.conf file and then run the db2prereqcheck command again.

DBT3600W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility detects an invalid IP address for an Interface Adapter in an /etc/hosts file.

Update the /etc/hosts file on each of the hosts in the cluster so that for each host in the planned DB2 pureScale environment, the file includes all the IP addresses of all the communication adapter ports for all hosts in the planned environment.

DBT3601W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. The db2prereqcheck utility uses the libstdc++ and xlc libraries to perform some of the verification of Interface Adapters. This message is returned when the db2prereqcheck is unable to use one of these libraries.

Install the libstdc++ and xlc libraries and then run the db2prereqcheck command again.

DBT3602W

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility detects an interface adapter that is not configured in the /etc/hosts and direct access transport file, dat.conf, on the host machine.

If the adapter supports Remote Direct Memory Access(RDMA), configure the adapter in the /etc/hosts file and the dat.conf file on the host machine.

DBT3603E

You can verify installation prerequisites using the db2prereqcheck utility.

On Windows operating systems, before verifying prerequisites, the db2prereqcheck utility copies some files from the database product install image directory to the temporary directory configured by the %TEMP% environment variable.

This message is returned when the db2prereqcheck utility fails to copy one of those files to the temporary directory.

Perform the following troubleshooting steps:

• Issue the db2prereqcheck command as a user with write access to %TEMP%.
• Make 15MB of free space available in %TEMP% and then issue the db2prereqcheck command again.

DBT3604E

In a DB2 pureScale environment, the RDMA is supported through the User Direct Access Programming Library (uDAPL) interface.

This message is returned when the db2prereqcheck utility detects that the level of uDAPL that is currently installed is not supported with the current operating system level.

Ensure that uDAPL is installed and configured at the level specified for your system in the software prerequisites.

DBT3605E

You can verify installation prerequisites for the database product as well as feature-specific prerequisites, such as requirements for the DB2 pureScale Feature, by using the db2prereqcheck utility.

The DB2 pureScale Feature requires one or more raw devices to be configured for storing files that are shared by the DB2 members and cluster caching facilities (CFs). You can verify the shared devices that will be used by your DB2 pureScale instance by issuing the db2prereqcheck command, and specifying the devices with the -dl parameter.

This message is returned when the db2prereqcheck utility determines that one or more of the devices that were specified with the -dl parameter is not a raw device or is not configured with the same physical volume identifier (PVID) on all the host machines in the cluster.

Configure one or more raw devices that are shared between all the host machines in the DB2 cluster and then issue the db2prereqcheck command.

DBT3606E

You can verify installation prerequisites for the database product as well as feature-specific prerequisites, such as requirements for the DB2 pureScale Feature, by using the db2prereqcheck utility.

When you are configuring network settings for a planned DB2 pureScale environment, entries in the /etc/hosts file on each host machine in the cluster must be formatted in the following way:

 <IP-address> <full-domain-host-name> <alias> 

When verifying DB2 pureScale requirements, the db2prereqcheck utility returns this error message if the /etc/hosts file is not formatted in the required way on all host machines in the cluster.

On every host machine in the cluster, correct the entries in the /etc/hosts file so the entries are in the required format.

DBT3607E

You can verify installation prerequisites for DB2 database by using the db2prereqcheck utility.

You can use the db2prereqcheck utility to verify communication between all hosts in RDMA over Converged Ethernet (RoCE) and InfiniBand networks by specifying a list of netnames, hostnames and adapternames in the network.

This message is returned when the db2prereqcheck is unable to successfully ping all of the netname using RDMA to test connectivity between all the given host machine and cluster interconnect netnames. For more details refer the log file.

However, if these set of hostname and netname are for used for install or instance management runtime operations in the future, the underlying problem that prevented the db2prereqcheck utility from pinging netname might also cause errors with install or instance management utilities.

To verify the netname, configure the netname in the etc/hosts file and the dat.conf file and then run the db2prereqcheck command again.

DBT3608E

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility found a software package that is not at the required minimum level for the operating system level.

Install the required version of the software package and then run the db2prereqcheck command again.

DBT3609E

You can issue db2ssh validation check using db2prereqcheck utility by entering "db2prereqcheck -db2ssh_test" command.

This message is returned when the execution of validation failed, you can find the more detail and explanation in the given log path.

1

Check the given log 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.