DBT5000-5999

DBT5000I

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility did not find any database objects or features in the specified database that are not supported in a DB2 pureScale environment.

Optional: review the contents of the output log file.

You can now convert your instance to a DB2 pureScale instance type.

DBT5001W

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility found some database objects or features in the specified database that are not supported in a DB2 pureScale environment which will be automatically converted or disabled when you convert the instance to a DB2 pureScale instance type.

1. Review the contents of the db2checkSD output log file.
2. Investigate any issues identified in the db2checkSD output log file that are of concern to you.
3. Convert the instance to a DB2 pureScale instance type.

DBT5002N

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility found some database objects or features in the specified database that are not supported in a DB2 pureScale environment and which cannot be automatically converted or disabled when you convert the instance to a DB2 pureScale instance type.

1. Review the contents of the db2checkSD output log file.
2. Convert or disable any unsupported database objects or features that db2checkSD identified.
3. Run the db2checkSD utility again.

DBT5003N

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when an invalid parameter was passed to the db2checkSD command.

Run the db2checkSD command again, specifying valid parameters.

DBT5004N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

You can pass the name of a specific database to be checked, or you can use the -e parameter to specify that the db2checkSD utility should check all databases in the current database manager instance. This message is returned when no database or databases were specified to be examined by the db2checkSD utility.

Run the db2checkSD command again, specifying which database or databases to check in one of the following ways:

• Specify one specific database.
• Pass the -e parameter to cause the db2checkSD utility to examine all databases in the current database manager instance.

DBT5005N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD creates an output log file that contains detailed information about the investigation of the database structure, metadata, objects, and features that the db2checkSD utility performed. You must specify the name of the output log file using the -l parameter.

This message is returned when no name for the db2checkSD output log file was specified using the -l parameter with the db2checkSD command.

Run the db2checkSD command again, specifying an output log file name using the -l parameter.

DBT5006N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when a parameter is passed to the db2checkSD command without a value.

Run the db2checkSD command again, specifying a value for the named parameter.

DBT5007N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when a parameter is passed to the db2checkSD command more than once.

Run the db2checkSD command again, specifying the named parameter only once.

DBT5008N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD creates an output log file that contains detailed information about the investigation of the database structure, metadata, objects, and features that the db2checkSD utility performed. You must specify the name of the output log file name using the -l parameter. The log file name cannot be longer than 256 characters.

This message is returned when an output log file name was specified using the -l parameter with the db2checkSD command that is longer than 256 characters.

Run the db2checkSD command again, specifying an output log file name that is not longer than 256 characters.

DBT5009N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility. The db2checkSD utility is supported with DB2 Version 9.7 for Linux, UNIX, and Windows and later.

This message is returned when an attempt is made to use the db2checkSD utility to examine a database that is older than DB2 Version 9.7.

1. Upgrade the database to DB2 Version 9.7 or later.
2. Run the db2checkSD command against the database again once the database is at Version 9.7 or higher.

DBT5010N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The following authority is required to run the db2checkSD command: SYSADM or higher. This message is returned when a user without SYSADM authority or higher attempts to run the db2checkSD command.

Respond to this message with one of the following actions:

• Request that your authorization be upgraded to SYSADM authorization or higher and then rerun the db2checkSD command.
• Request that a user with SYSADM authorization or higher run the db2checkSD command.

DBT5011N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility performs the following tasks:

1. The db2checkSD utility identifies database objects and features that are not supported in a DB2 pureScale environment by examining database structures and metadata, as well as running queries against the database.
2. The db2checkSD utility generates a user script that you can run to prepare the database to be upgraded to a DB2 pureScale environment.

This message is returned when the db2checkSD utility found some table spaces that are in a state other than 'NORMAL', which would prevent the database from being upgraded successfully to a DB2 pureScale environment.

1. Identify the table spaces that are not in 'NORMAL' state by running the user script that was generated by the db2checkSD utility.
2. Move the table spaces that are not in a 'NORMAL' state to a 'NORMAL' state.
3. Run the db2checkSD utility against the database again.
4. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5012N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility performs the following tasks:

1. The db2checkSD utility identifies database objects and features that are not supported in a DB2 pureScale environment by examining database structures and metadata, as well as running queries against the database.
2. The db2checkSD utility generates a user script that you can run to prepare the database to be upgraded to a DB2 pureScale environment.

This message is returned when the db2checkSD utility found some database objects or enabled features that are not supported in a DB2 pureScale environment.

1. Identify the table spaces that do not use automatic storage by running the user script that was generated by the db2checkSD utility.
2. Convert the table spaces that do not use automatic storage to use automatic storage.
3. Run the db2checkSD utility against the database again.
4. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5013N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility performs the following tasks:

1. The db2checkSD utility identifies database objects and features that are not supported in a DB2 pureScale environment by examining database structures and metadata, as well as running queries against the database.
2. The db2checkSD utility generates a user script that you can run to prepare the database to be upgraded to a DB2 pureScale environment.

This message is returned when the db2checkSD utility found some database objects that are not supported in a DB2 pureScale environment.

1. Identify the WLM CONCURRENTDBCOORDACTIVITIES thresholds that are not supported in a DB2 pureScale environment by running the user script that was generated by the db2checkSD utility.
2. If the thresholds were created as part of a work action set, drop the work action representing this threshold. Otherwise, if the threshold was explicitly created, drop the threshold.
3. Run the db2checkSD utility against the database again.
4. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.
5. After upgrading the database to a DB2 pureScale environment, recreate the thresholds that were dropped in step 2 by using either the CREATE THRESHOLD statement or the ALTER WORK ACTION SET (ADD WORK ACTION) statement, as required.

DBT5015N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility performs the following tasks:

1. The db2checkSD utility identifies database objects and features that are not supported in a DB2 pureScale environment by examining database structures and metadata, as well as running queries against the database.
2. The db2checkSD utility generates a user script that you can run to prepare the database to be upgraded to a DB2 pureScale environment.

This message is returned when the db2checkSD utility found some database objects or enabled features that are not supported in a DB2 pureScale environment.

1. Identify the index extensions by running the user script that was generated by the db2checkSD utility.
2. Drop the index extensions listed by the generated user script.
3. Run the db2checkSD utility against the database again.
4. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5017N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD command is run against a multi-partitioned database or a single database partition that is not 0.

1. Convert the database to a single-partitioned database numbered 0.
2. Run the db2checkSD utility against the database again.
3. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5018N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD command is run against a database which is using DB2 Text Search.

1. Disable DB2 Text Search using the DISABLE DATABASE FOR TEXT command.
2. Run the db2checkSD utility against the database again. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5020N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD command is run against a database which is using Net Search Extender.

1. Disable Net Search Extender for the database using the DISABLE DATABASE command.
2. Run the db2checkSD utility against the database again.
3. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5022N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

You can pass the name of a specific database to be checked, or you can use the -e parameter to specify that the db2checkSD utility should check all databases in the current database manager instance.

Run the db2checkSD command again, specifying which database or databases to check in one of the following ways:

• Specify one specific database.
• Pass the -e parameter to cause the db2checkSD utility to examine all databases in the current database manager instance.

DBT5023N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD command is run against a database or databases which are using block-based buffer pools.

1. Modify or remove the block-based buffer pools by taking one of the following actions:
   • Run the ALTER BUFFERPOOL statement to change the number of pages identified by NUMBLOCKPAGES to 0.
   • Drop the block-based buffer pools.
2. Run the db2checkSD utility against the database again.
3. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5024N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility found some database objects or enabled features that are not supported in a DB2 pureScale environment.

1. Move all table space containers onto a GPFS by performing the following steps:
   1. Identify all of the table spaces in the database by running the following query:

       select CONTAINER_NAME from SYSIBMADM.SNAPCONTAINER 

   2. Move any table space containers that are not already on a GPFS onto a GPFS. One way to do this is to use a redirected restore operation.
2. Move all storage paths onto a GPFS by performing the following steps:
   1. Identify all of the storage paths in the database by running the following query:

       select DB_STORAGE_PATH from SYSIBMADM.SNAPSTORAGE_PATHS 

   2. Move any storage paths that are not already on a GPFS onto a GPFS.
3. Set database log paths to directories that are on a GPFS by performing the following steps:
   1. Determine the values of the following database configuration parameters using the GET DATABASE CONFIGURATION command: LOGPATH and NEWLOGPATH.
   2. If the directory named in either of the LOGPATH or NEWLOGPATH database configuration parameters is not on a GPFS, set LOGPATH and NEWLOGPATH to a directory that is on a GPFS.
4. Run the db2checkSD utility against the database again.
5. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5025N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility. The db2checkSD utility identifies these unsupported database objects and features by examining database structures and metadata, and running queries against the database.

This message is returned in the following situations, among others:

• An attempt was made to run the db2checkSD command from a computer that is configured to run only a cluster caching facility (CF).
• The db2checkSD utility was unable to connect to one or more of the databases.
• The db2checkSD utility encountered an unexpected error condition while running queries against the database.

Respond to this message in one of the following ways:

• Verify that you can connect to the database successfully.
• If the db2checkSD command was issued on a computer that is configured to run only a CF, run the command from any computer that is configured to run a DB2 member instead.
• If the db2checkSD command was not issued on a computer that is configured to run only a CF, perform the following procedure:
  1. Collect the following files:
     • The output log file created by the db2checkSD utility
     • The generated user script created by the db2checkSD utility
     • The db2diag log
  2. Contact IBM support to investigate the problem.

DBT5026I

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned after the db2checkSD utility has finished checking each database, when it is invoked with the -e option to check all databases in the instance.

Optional: Review the contents of the log file when the db2checkSD utility has finished checking all databases in the instance.

DBT5027W

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility identifies these unsupported database objects and features by examining database structures and metadata, as well as running queries against the database. This message is returned when the db2checkSD utility found an empty database directory or when the db2checkSD utility could not find a local database directory.

1. Catalog the databases that you want to check using the db2checkSD utility.
2. Run the db2checkSD command again.

DBT5028N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD command is run against a database or databases which are using HADR.

1. Stop HADR on the primary database using the STOP HADR command.
2. Run the db2checkSD utility against the database again.
3. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5029N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility generates the following files:

• An output log file that you can review for details about the db2checkSD utility's investigations
• A user script that you can use to identify database objects or features that must be removed or disabled before upgrading the database or databases to a DB2 pureScale environment

This message is returned when the db2checkSD utility was unable to create the output log file or the generated user script.

1. Give the db2checkSD utility write permission for the path where you want the db2checkSD utility to create the output log file and the generated user script.
2. Run the db2checkSD utility again.

DBT5030N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility performs the following tasks:

1. The db2checkSD utility identifies database objects and features that are not supported in a DB2 pureScale environment by examining database structures and metadata, as well as running queries against the database.
2. The db2checkSD utility generates a user script that you can run to prepare the database to be upgraded to a DB2 pureScale environment.

This message is returned when the db2checkSD utility found some database objects or enabled features that are not supported in a DB2 pureScale environment.

1. Identify the MDC and ITC tables by running the user script that was generated by the db2checkSD utility.
2. Move the data from the MDC and ITC tables into non-MDC and non-ITC tables.
3. Drop the MDC and ITC tables.
4. Run the db2checkSD utility against the database again.
5. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5032N

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility performs the following tasks:

1. The db2checkSD utility identifies database objects and features that are not supported in a DB2 pureScale environment by examining database structures and metadata, as well as running queries against the database.
2. The db2checkSD utility generates a user script that you can run to prepare the database to be upgraded to a DB2 pureScale environment.

This message is returned when the db2checkSD utility found some database objects or enabled features that are not supported in a DB2 pureScale environment.

1. Identify the range-clustered tables by running the user script that was generated by the db2checkSD utility.
2. Move the data from the range-clustered tables into non-range-clustered tables.
3. Drop the range-clustered tables.
4. Run the db2checkSD utility against the database again.
5. If the db2checkSD utility succeeds, you can upgrade the database to a DB2 pureScale environment.

DBT5033W

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility found some database objects or features in the specified database that are not supported in a DB2 pureScale environment which will be automatically converted or disabled when you upgrade the database to a DB2 pureScale environment.

1. Review the contents of the db2checkSD output log file.
2. Investigate any issues identified in the db2checkSD log that are of concern to you.
3. Upgrade the database to a DB2 pureScale environment.

DBT5034I

The db2checkSD utility has already been run for the database and all checks were successful. The checks were not performed again.

No further action is needed.

DBT5035N

You can verify that a given database can be used in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility is not able to open the database manager configuration file.

Use commands such as db2 get dbm configuration to get more information about the error that occurs when the database manager attempts to read the database manager configuration file.

DBT5036N

You can verify that a given database can be used in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility is not able to open the database configuration file.

Respond to this error by performing the following troubleshooting steps:

• Verify that you can connect to the database.
• Get more information about the error that occurs when the database manager attempts to read the database configuration file by performing one or both of the following actions:
  • Connect to the database
  • Run the GET DATABASE CONFIGURATION command for the database

DBT5037N

The db2checkSD utility verifies that a database can be used in a DB2 pureScale environment. An HADR standby database must be dropped before the instance is converted to a DB2 pureScale instance and reinitialized in the DB2 pureScale environment.

Drop the standby database, convert both instances to DB2 pureScale instances, then reinitialize the standby database.

DBT5038N

The db2checkSD utility verifies that a database can be used in a DB2 pureScale environment. The database configuration parameter HADR_SSL_LABEL is not supported in DB2 pureScale environment.

Set HADR_SSL_LABEL to NULL.

DBT5500N

The db2ckupgrade command is used to verify if a database can be upgraded.

The following authority is required to run the db2ckupgrade command: SYSADM or higher. This message is returned when a user with insufficient authority attempts to run the db2ckupgrade command.

The command failed.

Do one of the following:

1. Request that your authorization be upgraded to SYSADM authorization or higher and then rerun the db2ckupgrade command.
2. Request that a user with SYSADM authorization or higher run the db2ckupgrade command.

DBT5501N

The db2ckupgrade command is used to verify if a database can be upgraded.

The db2ckupgrade utility generates an output log file that you can review for details about the processing done by the utility.

This message is returned when the db2ckupgrade utility was unable to open or write to the output log file.

• Give the db2ckupgrade utility write permission for the path where you want the db2ckupgrade utility to create the output log file.
• Run the db2ckupgrade utility again.

DBT5502N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the number of parameters specified is incorrect.

Run the db2ckupgrade command again, specifying valid parameters.

DBT5503N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when an invalid parameter was passed to the db2ckupgrade command.

The command failed.

Run the db2ckupgrade command again, specifying valid parameters.

DBT5504N

The db2ckupgrade command is used to verify if a database can be upgraded.

You can pass the name of a specific database to be checked, or you can use the -e parameter to specify that the db2ckupgrade utility should check all databases in the current database manager instance. This message is returned when no database or databases were specified to be examined.

Run the db2ckupgrade command again, specifying which database or databases to check in one of the following ways:

• Specify one database name.
• Pass the -e parameter to cause the db2ckupgrade utility to examine all databases in the current database manager instance.

DBT5505N

The db2ckupgrade command is used to verify if a database can be upgraded.

The db2ckupgrade creates an output log file that contains detailed information about the investigation that the db2ckupgrade utility performed. You must specify the name of the output log file name using the -l parameter.

This message is returned when no name for the db2ckupgrade output log file was specified.

Run the db2ckupgrade command again, using the -l parameter, to specify an output log file name.

DBT5506N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when a parameter is passed to the db2kupgrade command without a value.

Run the db2ckupgrade command again, specifying a value for the named parameter.

DBT5507N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when a parameter is passed to the db2ckupgrade command more than once.

Run the db2ckupgrade command again, specifying the named parameter only once.

DBT5508I

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility verifies that all upgrade conditions are met. You can now upgrade the database.

1. Optional: Review the contents of the output log file.
2. You can now upgrade the database.

DBT5509N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility is unable to connect to the specified database.

The command failed.

1. Ensure that the specified database name is correct
2. Ensure that the database manager is running.
3. Try the command again.

DBT5510W

You can verify that a given database can successfully be upgraded to a later version using the db2ckupgrade utility.

This message is returned when the db2ckupgrade utility finds database objects which are not supported in the version to which you are upgrading. Specifically, this message is returned when the following database objects are in a database being checked:

• Global variables of type XML
• Compiled SQL functions that use parameters of type XML or that return XML types

If you proceed to upgrade the database to the target version, these objects will be invalidated during database upgrade. You will be unable to use these database objects until you upgrade to a version that supports those database objects.

To be able to use the database objects that are invalidated during upgrade, upgrade to a release and fix pack of DB2 database that supports XML global variables and compiled SQL functions that use XML parameters or that return XML types. When you upgrade to a fixpack that supports those database objects, the objects will be automatically revalidated the first time they are referenced after the database has been upgraded.

DBT5511N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when one of the parameters passed to the db2ckupgrade utility is longer than the maximum allowed length for that parameter.

Run the db2ckupgrade command again, specifying the parameter with the correct length.

DBT5512E

Some workload management objects are assigned default, system-reserved identifiers (ID).

This message is returned when the db2ckupgrade utility determines that an existing workload management object has an ID that happens to fall in the range of default, system-reserved IDs. The database cannot be upgraded while the workload management object with the conflicting ID exists in the database.

1. Extract the DDL statements that would reproduce your workload management objects by using the db2look utility, specifying the -wlm option.
2. Drop all of the workload management objects from the database.
3. Verify whether the database can be upgraded by using the db2ckupgrade utility, and resolve any other problems that are blocking the database from being upgraded.
4. After the db2ckupgrade utility determines that the database can be upgraded, perform the following steps:
   1. Upgrade the database.
   2. Recreate the workload management objects in the upgraded database by running the DDL statements that the db2look utility generated.

DBT5513N

The db2ckupgrade command is used to verify if a database can be upgraded.

Typically, amount of free space defined by SYSCATSPACE should be at least the same as the current amount of used space.

This message is returned when SYSCATSPACE has less than 50% free pages left.

• Increase the size of existing containers. You can also add additional containers although this might trigger data rebalancing.
• Optional: You can reduce the size of the containers after upgrade.

DBT5514N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the database being checked is found to be in a restore pending state.

Complete the restore and run the db2ckupgrade command again.

DBT5515N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the database being checked is in the process of having a backup taken to provide a starting point for roll-forward recovery, but is still in a backup pending state.

Wait until the backup has completed and run the db2ckupgrade command again.

DBT5516N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the database being checked is enabled for roll-forward recovery and it has been restored but not rolled forward.

1. Roll forward the database or indicate that you do not wish to roll forward by using the ROLLFORWARD command. Note that if you do not roll forward the database, the records written since the last backup of the database will not be applied to the database.
2. Run the db2ckupgrade command again.

DBT5517N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the database being checked is found to be in an inconsistent state.

The possible causes of this inconsistent state include

• The database is online and SQL has been issued which modified data in the database.

1. Perform a clean shutdown of the database.
2. Re-issue the db2ckupgrade command.

DBT5518W

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility completes with one or more warnings but the database can still be upgraded

1. Optional: Review the contents of the output log file.
2. You can now upgrade the database.

DBT5519N

The db2ckupgrade command is used to verify if a database can be upgraded.

The db2ckupgrade command attempts to deactivate the specified database and stop all necessary database services. This message is returned when the db2ckupgrade utility failed to deactivate the database.

Perform the following:

1. Review the SQLCODE to determine the reasons why the database could not be deactivated and take corrective action.
2. Run the db2ckupgrade command again.

DBT5520N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility attempted to set the DB2_QP_BYPASS_COST variable but failed.

Perform the following:

1. Review the SQLCODE and take corrective action.
2. Run the db2ckupgrade command again.

DBT5521N

While upgrading your database product to a higher version, you can verify whether the databases are ready to be upgraded by using the db2ckupgrade utility.

The db2ckupgrade command must be invoked from the higher version product install media or installation path.

This message is returned when the version of the db2ckupgrade utility is not higher than the database being tested, which could happen in different scenarios:

• The db2ckupgrade command was invoked from the same product as the database being tested, instead of being invoked from the higher version product.
• The database was upgraded to the higher version, and then db2ckupgrade was run against the already-upgraded database.

To verify whether a database at a lower DB2 version, X, can be upgraded to a higher DB2 version, Y, invoke the db2ckupgrade command from the higher version Y product install media or installation path.

DBT5522N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when a previous LOAD attempt on one or more tables in the database did not complete successfully. The upgrade cannot proceed until the LOAD operation is restarted or terminated.

Restart or terminate the previously failed LOAD operation on this table by issuing LOAD with the RESTART or TERMINATE option respectively.

To find out what tables are in a load pending state run the following command:

 select tabname from SYSIBMADM.ADMINTABINFO     where load_status is not NULL 

DBT5523N

The db2ckupgrade command is used to verify if a database can be upgraded.

This messages is returned when the REDISTRIBUTE utility has not completed for one or more tables in the database. The upgrade cannot proceed until the REDISTRIBUTE is finished.

Perform one of the following:

1. If the REDISTRIBUTE utility is in progress, wait until it completes. You can use the LIST UTILITIES command to monitor the progress of the REDISTRIBUTE utility.
2. If a previous REDISTRIBUTE operation failed and left the table in redistribute pending state, issue the REDISTRIBUTE utility again with the CONTINUE or ABORT option and let it complete.

DBT5524N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility determines that the database to be upgraded is enabled for VARCHAR2 support. Upgrading from DB2 Version 9.5 with VARCHAR2 is not supported.

No action is needed. The database cannot be upgraded.

DBT5525N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned in the following situations, among others:

• An attempt was made to run the db2ckupgrade command from a computer that is configured to run only a cluster caching facility (CF).
• The db2ckupgrade utility encountered an unhandled error condition while examining database structures and metadata, and running queries against the database.

Respond to this message in one of the following ways:

1. If the db2ckupgrade command was issued on a computer that is configured to run only a CF, run the command from any computer that is configured to run a DB2 member instead.
2. If the db2ckupgrade command was not issued on a computer that is configured to run only a CF, collect the output log file created by the db2ckupgrade utility, the generated user script created by the db2ckupgrade utility, and the db2diag log. Then contact IBM support to investigate the problem.

DBT5526W

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility finds an empty database directory or when the db2ckupgrade utility could not find a local database directory.

Perform the following actions:

• Catalog the databases that you want to check using the db2ckupgrade utility.
• Run the db2ckupgrade command again.

DBT5527N

The db2ckupgrade command is used to verify if a database can be upgraded.

The db2ckupgrade command must start the database manager in order to perform the verifications. This message is returned when db2ckupgrade is unable to start the database manager.

The token sqlcode contains the sqlcode that was returned from the underlying start database manager call.

The command failed.

1. Determine the cause of the failure by referring to the SQL message for the returned sqlcode.
2. Resolve the underlying problem.
3. Invoke the db2ckupgrade command again.

DBT5528N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility cannot operate because I/O writes are suspended for the database.

If write operations for the database are in the process of being suspended, monitor the state of the database using the suspend_io configuration parameter, and wait until the SET WRITE SUSPEND operation completes before you continue, then reissue the db2ckupgrade command again.

DBT5529N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility has completed but not all upgrade conditions were met. The database cannot be upgraded.

1. Review the contents of the output log file and fix any issues.
2. Run the db2ckupgrade command again.

DBT5530N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned then the db2ckupgrade utility attempted to access a table space which is in an invalid state, for which the intended access is not allowed.

The possible causes of the inconsistent state include:

• The database is online and SQL has been issued which modified data in the database.
• The database is online and HADR has been enabled.

Perform the following actions:

1. Perform a clean shutdown of the database.
2. After shutdown, if HADR has been enabled on the database, issue the STOP HADR command on the database.
3. Re-issue the db2ckupgrade command.

DBT5531W

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the -e parameter is specified but the db2ckupgrade utility is unable to find any local databases.

The command failed.

Check whether any database names exist in the system database directory. If there are no database names in the system database directory, then either no databases exist or the database names have not been cataloged.

If a database name appears in the system database directory and the entry type is INDIRECT, ensure that the database exists in the specified local database directory

DBT5532N

The db2ckupgrade command is used to verify if a database can be upgraded.

This messages is returned when the db2ckupgrade utility finds MQTs that depend on system views. During database upgrade all system views will be recreated, so any MQTs that depend on the system views will be automatically dropped.

Perform the following actions:

• Generate and backup the DDL needed to create the MQTs
• Drop the MQTs
• Upgrade the database
• Recreate the MQTs

DBT5533N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility could not perform the verification because it failed to activate the database.

1. Review the SQLCODE to determine the reasons why the database could not be activated and take corrective action.
2. Run the db2ckupgrade command again.

DBT5534W

Some system built-in routines such as table functions, views, or stored procedures, are discontinued in the target version of the database upgrade due to the introduction of new functionality or changes to the existing functionality.

The database upgrade to that target version drops any system built-in routines that are discontinued. To continue to use database objects that have a dependency on these system built-in routines, you have to alter these database objects and remove the dependency before the database upgrade.

This message is returned when the db2ckupgrade command detects a database object such as a view, trigger, or a user-defined stored procedure, that has a dependency on system built-in routines that are discontinued in the target version of the database upgrade.

Perform one of the following actions:

• If you no longer need the database object which depends on system built-in routines that are discontinued, drop this object.
• Alter the database object so that the object does not depend on system built-in routines that are discontinued. Use the replacement routines provided for system built-in routines that are discontinued.

DBT5535N

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the HADR primary's log shipping position does not match some HADR standby's log replay position.

Before the upgrade process can begin all data produced on the primary database must be shipped and replayed by each standby database configured in the cluster.

Using HADR monitoring tools, verify that the primary database is properly connected to all standby databases configured in the HADR_TARGET_LIST and that log shipping and log replaying functionality is healthy.

If multiple standby databases are configured and some standby's log replay position is not able to catch up to the primary's log shipping position, either attempt to resolve the issue blocking the shipping or replaying from proceeding or remove the standby from the HADR_TARGET_LIST. This standby can be re-initialized from a backup image post-upgrade.

Once all possible issues have been addressed re-issue the db2ckupgrade command.

If the problem cannot be resolved then issue STOP HADR on the primary database to change the database role back to standard then re-issue the db2ckupgrade command. The standby database(s) will have to be re-initialized from a backup image post-upgrade.

DBT5536W

You can verify whether a database can be upgraded by using the db2ckupgrade utility. Before upgrading to a new version, you can identify any database objects or features in the database that are not supported in the new version using the db2ckupgrade utility.

The security administrator uses audit policies to configure the audit facility to gather information about a database. This message is returned when the db2ckupgrade utility finds audit policies that are associated with a database (entries in the SYSCAT.AUDITUSE catalog view with a blank OBJECTTYPE), but none of the entries is associated with the current database. There is no entry that has an OBJECTNAME that matches the current database name.

An audit policy is not required to upgrade the database.

Optional:

1. Audit the database using the following command:

    AUDIT DATABASE USING POLICY <policy-ID> 

2. Run the db2ckupgrade command again.

If you do not audit the database and rerun db2ckupgrade, the SYSCAT.AUDITUSE catalog view will be cleared when the database is upgraded.

DBT5537I

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned after the db2ckupgrade utility has finished checking each database, when it is invoked with the -e option to check all databases in the instance.

Optional: Review the contents of the log file when the db2ckupgrade utility has finished checking all databases in the instance.

DBT5538N

The db2ckupgrade command is used to verify if a database can be upgraded. When upgrading from DB2 V9.8 the database upgrade moves certain table space files to a new location. If the table space containers use an unexpected mount point configuration the table space data cannot be moved by the upgrade processing.

Contact IBM support. If possible, have the details from the log file associated with the db2ckupgrade command available.

DBT5539N

The db2ckupgrade command is used to verify if a database can be upgraded. When upgrading from DB2 9.8 the files under /MEMBERnnnn/sqldbdir are consolidated to a single location. If the files in /sqldbdir are not identical on all members the upgrade processing cannot consolidate them.

Contact IBM support. If possible, have the log file associated with the db2ckupgrade command available.

DBT5540I

You can verify whether a database is ready to be upgraded by issuing the db2ckupgrade command. If the database is ready to be upgraded, the db2ckupgrade utility puts the database in "upgrade pending" state. When a database is in upgrade pending state, all connections are blocked.

There are two ways to bring a database out of upgrade pending state:

• Upgrade the database
• Issue the db2ckupgrade command with the -resetUpgradePending parameter

This message is returned when the db2ckupgrade utility has successfully reset the upgrade pending state of the database. No upgrade conditions were checked. Applications may connect to the database.

No user response is required.

DBT5541N

You can verify whether a database is ready to be upgraded by issuing the db2ckupgrade command. If the database is ready to be upgraded, the db2ckupgrade utility puts the database in "upgrade pending" state. When a database is in upgrade pending state, all connections are blocked.

There are two ways to bring a database out of upgrade pending state:

• Upgrade the database
• Issue the db2ckupgrade command with the -resetUpgradePending parameter

This message is returned when the db2ckupgrade utility fails to reset the upgrade pending state of the database because of the error given in the runtime token sqlcode.

1. Review the message for the underlying sqlcode.
2. Correct the source of the underlying problem.
3. Reissue the db2ckupgrade command with "-resetUpgradePending" parameter.

DBT5542I

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility.

The db2iupgrade utility internally calls db2ckupgrade. If the database is ready to be upgraded, the database is put into upgrade pending state. When a database is in upgrade pending state, attempts to connect to the database are blocked.

This message is returned when the db2ckupgrade command is issued internally by the db2iupgrade utility and the database has been put in upgrade pending state. The database can be upgraded.

Respond in one of the following ways:

• You can now upgrade the database.
• If you will not be upgrading the database immediately, and if you want applications to be able to continue to connect to the database, you can reset the state of the database by issuing the db2ckupgrade command with the "-resetUpgradePending" parameter.

DBT5543N

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility. The db2iupgrade utility internally calls db2ckupgrade.

If the db2ckupgrade utility determines that the database is ready to be upgraded, the db2ckupgrade utility puts the database into upgrade pending state.

This message is returned when the db2ckupgrade utility is called internally by the db2iupgrade utility, and an error occurs when the db2ckupgrade utility attempts to put the database into upgrade pending state. The database cannot be upgraded.

Issue the db2iupgrade command again.

DBT5544W

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when incompatible input parameters were passed to the db2ckupgrade command.

Reissue the db2ckupgrade command, specifying valid parameters.

DBT5545I

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility. The db2iupgrade utility calls the db2ckupgrade command internally.

If the db2ckupgrade utility determines that the database is ready to be upgraded, the db2ckupgrade utility puts the database in upgrade pending state.

This message is returned when the db2ckupgrade command is issued to verify a database that is already in upgrade pending state.

You can upgrade the database.

Upgrade the database.

DBT5546W

The db2ckupgrade command is used to verify if a database can be upgraded. The db2ckupgrade utility requires an exclusive database connection to run all upgrade condition checks.

It tries to get exclusive database connection, but if it fails, it gets shared database connection. Under such a circumstance, it does not check all upgrade conditions.

This message is returned when the db2ckupgrade utility verifies the upgrade condition under shared database connection.

1. Stop all applications.
2. Run the db2ckupgrade command again.
3. To enforce running in exclusive database connection, issue db2ckupgrade with -allChecks parameter.

DBT5547I

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility.

The db2ckupgrade utility can also be used to perform some operations other than verifying whether a database is ready to be upgraded. For example: -resetUpgradePending parameter.

This message is returned when the db2ckupgrade utility successfully ran one of those operations and no upgrade conditions were checked.

Optional: Review the contents of the output log file.

DBT5548N

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility.

The db2ckupgrade utility can also be used to perform some operations other than verifying if a database can be upgraded. For example: resetting upgrade pending state.

This message is returned when the db2ckupgrade utility successfully run those operations, which does no upgrade condition checks.

Review the contents of the output log file.

DBT5549N

You can verify whether or not a database is ready to be upgraded by using the db2ckupgrade utility.

You can control which verification tests the db2ckupgrade utility performs by specifying different command parameters with the db2ckupgrade command. For example, specifying the -allChecks parameter causes the db2ckupgrade utility to perform all tests.

When the -allChecks parameter is specified with the db2ckupgrade command, the db2ckupgrade utility requires an exclusive database connection.

This message is returned when the -allChecks parameter is specified with the db2ckupgrade command but the db2ckupgrade utility failed to get an exclusive database connection.

1. Review the contents of the output log file.
2. Stop all applications.
3. Run the db2ckupgrade command again.

DBT5550W

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility. The db2ckupgrade utility requires an exclusive database connection to run all upgrade condition checks.

If the db2ckupgrade utility fails to get an exclusive connection, the utility will fall back to using a shared connection. When the db2ckupgrade utility uses a shared connection, it does not test all upgrade conditions.

This message is returned when the db2ckupgrade utility tests only some upgrade conditions because it could only use a shared database connection.

To test all upgrade conditions, perform the following steps:

1. Stop all applications.
2. Run the db2ckupgrade command again, specifying the -allChecks parameter.

DBT5551I

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when database upgrade on an HADR primary database is not supported. In order to proceed with the upgrade procedure, the db2ckupgrade command must stop HADR services and change the HADR role back to STANDARD.

Proceed to continue with the upgrade procedure. The standby database(s) will have to be re-initialized from a backup image post-upgrade.

DBT5552W

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when on the HADR standby database a table space is in an invalid or error state. This can be a result of a container or disk problem. A decision must be made how this impacts the upgrade procedure.

A table space error may or may not interfere with the upgrade procedure. Using the DB2 diagnostics log on the standby database, determine what table space is in an invalid state and what error condition exists. Assess whether this table space error will affect your upgrade procedure.

It is possible to proceed with the upgrade procedure but once in the new DB2 version the table space in error cannot be recovered. Post upgrade the table space in error must be dropped and re-created.

Alternatively, issue STOP HADR on the primary database to change the database role back to standard and proceed with the upgrade procedure. The HADR environment will have to be reinitialized post upgrade.

DBT5553N

DBT5554N

DBT5556W

DBT5557N

The db2ckupgrade command is used to verify if a database can be upgraded.

Typically, amount of free space defined by SYSTEMP should be at least the same as the current amount of used space.

This message is returned when SYSTEMP has less than 50% free pages left.

• Increase the size of existing containers. You can also add additional containers although this might trigger data rebalancing.
• Optional: You can reduce the size of the containers after upgrade.