DBT1000-1999

DBT Message ID Message Explanation User Response

DBT1000I

 The tool completed successfully.

The tool's processing completed without any errors.

No further action is required.

DBT1001N

 The syntax of the DB2INIDB tool is incorrect.

The DB2INIDB tool has the following syntax:

 db2inidb <database_alias> 
  AS < SNAPSHOT | STANDBY | MIRROR >
   [ RELOCATE USING config_file ]

Resubmit the command using the correct syntax.

DBT1002N

 Database name database-name is invalid.

The database name specified in the command is not valid. The database name must contain 1 to 8 characters and all of the characters must be from the database manager base character set.

Resubmit the command using a valid database name.

DBT1003N

 Unable to find program program-name.

An attempt to execute the specified program failed because it could not be found.

Ensure that the specified program exists and verify that the program's path exists in the PATH environment variable. Correct the problem and resubmit the command.

DBT1004N

 Unable to execute program program-name.

An error occurred while attempting to execute the specified program.

Ensure that the specified program exists and that it contains the appropriate file permissions. Correct the problem and resubmit the command.

DBT1005N

 The file file-name1 could not be copied to file-name2.

An error occurred when attempting to duplicate the specified file. The command could not be processed successfully.

Ensure that the specified source file exists and that it contains the appropriate file permissions, and ensure that the specified target file does not already exist. Correct the problem and resubmit the command.

DBT1006N

 The file-device-name file or device could not be opened.

An error occurred during an attempt to open the specified file or device.
  1. Ensure that the file or device exists and that its permissions are correct.
  2. Reissue the command.

DBT1007N

 An error occurred during an attempt to perform the operation-name operation on the file-device-name file or device.

An attempt to perform the specified operation on the specified file or device was unsuccessful.
  1. Correct the problem. Possible solutions include increasing the disk space or correcting the file permissions.
  2. Reissue the command.
  3. If the problem persists, contact your technical service representative.

DBT1008N

 Database database-name is not a split mirror image.

An attempt was made to use the DB2INIDB tool on a database that is not a split mirror image.

A split mirror image is a mirrored copy of a database that is taken while I/O writes are suspended. I/O writes can be suspended using the following command while being connected to the database:

   SET WRITE SUSPEND FOR DATABASE

Once the split mirror image has been taken, I/O writes on the primary database can be resumed with the following command:

   SET WRITE RESUME FOR DATABASE

Before the split mirror image can be used, the DB2INIDB tool must be run in order to remove its suspended state and initialize it by either performing crash recovery or placing it in rollforward pending state.

Resubmit the command using a split mirror image database.

DBT1009N

 Database database-name is not a recoverable database.

An attempt was made to use the STANDBY or MIRROR option of the DB2INIDB tool with a non-recoverable split mirror image database. The STANDBY and MIRROR options require the split mirror image to be recoverable.

A split mirror image is a mirrored copy of a database that is taken while I/O writes are suspended. I/O writes can be suspended using the following command while being connected to the database:

   SET WRITE SUSPEND FOR DATABASE

Once the split mirror image has been taken, I/O writes on the primary database can be resumed with the following command:

   SET WRITE RESUME FOR DATABASE

Before the split mirror image can be used, the DB2INIDB tool must be run in order to remove its suspended state and initialize it by either performing crash recovery or placing it in rollforward pending state.

The purpose of the STANDBY and MIRROR options are to place the split mirror image in rollforward pending state to permit logs from the primary database to be applied. The primary database must retain the log records for them to be available to the split mirror image database.

Resubmit the command using a split mirror image of a recoverable database. To enable the database for rollforward recovery, set the database configuration parameter logarchmeth1 or logarchmeth2 to a value other than OFF, disconnect all existing applications from the database, and perform an offline backup of the database.

DBT1010N

 The split mirror image database database-name has been previously initialized as a snapshot.

An attempt was made to use the STANDBY or MIRROR option of the DB2INIDB tool on a split mirror image that was previously initialized with the SNAPSHOT option. The STANDBY and MIRROR options can no longer be used to rollforward the log files from the primary database because the SNAPSHOT option caused this split mirror image to start a new log chain.

A split mirror image is a mirrored copy of a database that is taken while I/O writes are suspended. I/O writes can be suspended using the following command while being connected to the database:

   SET WRITE SUSPEND FOR DATABASE

Once the split mirror image has been taken, I/O writes on the primary database can be resumed with the following command:

   SET WRITE RESUME FOR DATABASE

Before the split mirror image can be used, the DB2INIDB tool must be run in order to remove its suspended state and initialize it by either performing crash recovery or placing it in rollforward pending state.

Resubmit the command with a new split mirror image database.

DBT1011N

 Unable to restart database database-name with the WRITE RESUME option. SQLCODE = sqlcode.

An attempt to restart the specified database with the WRITE RESUME option failed.

Verify the specified SQLCODE, correct the problem and resubmit the command.

DBT1012N

 Unable to perform operation operation-name on the database directory.

An attempt to perform the specified operation on the database directory was unsuccessful.

Possible reasons include:
  • The database manager could not process the request due to an insufficient amount of memory in the system.
  • No database entries were found in the system database directory.
  • The database does not exist in the system database directory.
Possible solutions include:
  • Ensure that there are sufficient system resources available.
  • Ensure that the database is cataloged correctly.

Correct the problem and resubmit the command.

DBT1013N

 The database database-name could not be found.

The specified database is not an existing database or the database could not be found in the local or system database directories.

Ensure that the specified database name exists in the system database directory. If the database name does not exist in the system database directory, then the database either does not exist or the database name has not been cataloged.

If the 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.

DBT1014N

 The instance name could not be determined.

An attempt to determine the current instance name was unsuccessful.

Ensure that the DB2INSTANCE environment variable is set to the current instance name. Correct the problem and resubmit the command.

DBT1015N

 Unable to allocate memory.

During processing, there was not enough memory to continue processing.
Possible solutions include:
  • Ensure that your system has sufficient real and virtual memory.
  • Remove background processes.

DBT1016N

 Table space files file-name1 and file-name2 are different sizes.

The two specified table space files have a different size even though they are supposed to be identical.
Contact your technical service representative with the following information:
  • Problem description
  • Contents of the table space catalog table
  • Table space files

DBT1017N

 The syntax of the DB2RELOCATEDB tool is incorrect.

The DB2RELOCATEDB tool has the following syntax:


db2relocatedb -f <config_file>

Where <config_file> is the name of file containing configuration information.

File format is:


DB_NAME=oldName,newName
DB_PATH=oldPath,newPath
INSTANCE=oldInst,newInst
DBPARTITIONNUM=dbPartitionNumber
LOG_DIR=oldDirPath,newDirPath
CONT_PATH=oldContPath1,newContPath1
CONT_PATH=oldContPath2,newContPath2
MIRRORLOG_PATH=newDirPath
FAILARCHIVE_PATH=newDirPath
LOGARCHMETH1=newDirPath
LOGARCHMETH2=newDirPath
OVERFLOWLOG_PATH=newDirPath
...

Notes:

  • Database name, database path, and instance name are all required fields. If one of these fields is not changing then it is not necessary to list the old and new value for it, just give the old/current one.
  • If you have settings for any of the following database configuration parameters, you can specify the corresponding keyword in the configuration file:
    • mirrorlogpath
    • failarchpath
    • logarchmeth1
    • logarchmeth2
    • overflowlogpath
  • Blank lines or lines beginning with a comment character (#) will be ignored.

Resubmit the command using the correct syntax.

DBT1018N

 field-name is a required field in the configuration file.

The specified field is a required field and does not exist in the configuration file.

Add the specified field information to the configuration file and then resubmit the command.

DBT1019N

 Invalid database path specified in the configuration file.

The specified database path in the configuration file is invalid.

On Windows, the database path must include the drive letter followed by a colon character. On other platforms, the database path must be absolute and end with a path separator.

Correct the erroneous database path and resubmit the command.

DBT1020N

 The configuration file contains an invalid entry at line line-number. Reason code = reason-code.

You cannot relocate with the DB2RELOCATEDB tool until the following condition indicated by the reason code is resolved:

1

The specified line is longer than the maximum number of characters.

2

A field was specified but no values follow it.

3

A field has been specified more than once.

4

Either the old or new database name contains too many characters.

5

Either the old or new database path name contains too many characters.

6

Either the old or new instance name contains too many characters.

7

An invalid node number has been specified in the DBPARTITIONNUM entry.

8

Either the old or new log directory path contains too many characters.

9

Either the old or new container name contains too many characters.

10

A duplicate container name in a CONT_PATH entry has been found.

11

The specified line is invalid.

12

Incorrect usage of the wildcard character (*).

13

Either the old or the new storage path name contains too many characters.

14

A duplicate storage path in a STORAGE_PATH entry has been found.

15

The new directory indicated for mirrorlogpath has too many characters.

16

The new directory indicated for failarchpath has too many characters.

17

The new directory indicated for logarchmeth1 has too many characters.

18

The new directory indicated for logarchmeth2 has too many characters.

19

The new directory indicated for overflowlogpath has too many characters.

The action corresponding to the reason code is:

1

Ensure that the specified line contains at most 1000 characters.

2

Ensure that the necessary values are specified for the field in question.

3

Ensure that the field in question is only specified once.

4

Ensure that the old and new database names contain no more than 8 characters.

5

Ensure that the old and new database path names contain no more than 215 characters.

6

Ensure that the old and new instance names contain no more than 8 characters.

7

Ensure that the node number contains no more than 4 digits.

8

Ensure that the old and new log directory paths contain no more than 242 characters.

9

Ensure that the old and new container names contain no more than 256 characters.

10

Ensure that each container name is only specified once in a CONT_PATH entry.

11

Verify the validity of the line in question.

12

The wildcard character must be the last character in both the old and new paths.

13

Ensure that the old and new storage path names contain no more than 190 characters.

14

Ensure that each storage path name is only specified once in a STORAGE_PATH entry.

15

Ensure that the new directory indicated for mirrorlogpath does not exceed the maximum length allowed.

16

Ensure that the new directory indicated for failarchpath does not exceed the maximum length allowed.

17

Ensure that the new directory indicated for logarchmeth1 does not exceed the maximum length allowed.

18

Ensure that the new directory indicated for logarchmeth2 does not exceed the maximum length allowed.

19

Ensure that the new directory indicated for overflowlogpath does not exceed the maximum length allowed.

Correct the problem and resubmit the command.

DBT1021N

 The total size of all container names is too large.

The total space required to store the list of containers exceeds the space allotted for a given table space in the table space file.
Try one or more of the following:
  • Use symbolic links, mounted file systems, etc. to shorten the new container names.
  • Back up the table space and then use the database administration utility to reduce the number and/or name lengths of the containers. Restore the table space to the new containers.

Correct the problem and resubmit the command.

DBT1022N

 The DB2RELOCATEDB tool must be run under instance instance-name.

An attempt has been made to run the DB2RELOCATEDB tool from an incorrect instance. If the instance is changing then the tool should be run from the new instance.

Resubmit the command using the correct instance.

DBT1023N

 The database release release-number is invalid.

The tool that is being used is from a different release than the database's current release. The command cannot be processed.

Ensure that the correct version of the tool is being used. Correct the problem and resubmit the command.

DBT1024N

 Change in database name has resulted in duplicate names in the local database directory.

An attempt to rename a database failed because an entry in the local database directory already existed with the same name.

Either change the database name to one that doesn't already exist or uncatalog the database if it no longer exists. Correct the problem and resubmit the command.

DBT1025N

 Neither old nor new database name were found in the database directory.

An attempt to determine the database token necessary to find the database path failed because neither the old nor new database names could be found in the database directory.

Ensure the database with the old database name exists and that it is cataloged properly. Correct the problem and resubmit the command.

DBT1026N

 Replacement of the new database path database-path in container name container-name will exceed length restrictions.

An attempt to rename the database path failed because it exceeds container name length restrictions when appended to the front of the specified container name.

Rename the database path and/or container name such that they do not exceed length restrictions when appended together. Correct the problem and resubmit the command.

DBT1027N

 Replacement of the new database path database-path in log directory path log-path will exceed length restrictions.

An attempt to rename the database path failed because it exceeds log directory path length restrictions when appended to the front of the specified log directory path.

Rename the database path and/or log directory path such that they do not exceed length restrictions when appended together. Correct the problem and resubmit the command.

DBT1028N

 Unable to copy table space files.

An attempt to duplicate the table space file SQLSPCS.1 failed.

Ensure there is sufficient disk space for the duplicate table space file. Correct the problem and resubmit the command.

DBT1029N

 Unable to copy buffer pool files.

An attempt to duplicate the buffer pool file SQLBP.1 failed.

Ensure there is sufficient disk space for the duplicate buffer pool file. Correct the problem and resubmit the command.

DBT1030N

 Unable to copy local database directory files.

An attempt to duplicate the local database directory file failed.

Ensure there is sufficient disk space for the necessary duplicate local database directory file. Correct the problem and resubmit the command.

DBT1031N

 An error occurred during an attempt to update the log control files.

The following log control files exist for each member:

  • The SQLOGCTL1.LFH primary log control file
  • The SQLOGCTL2.LFH secondary log control file

The following global log control files exist for each database partition:

  • The SQLOGCTL.GLFH.1 primary log control file
  • The SQLOGCTL2.GLFH.2 secondary log control file

The secondary log control file is a copy of the primary log control file for use in the event that there is a problem with the primary log control file.

This error was returned because the database manager could not update the primary log control files or the secondary log control files. Two of the possible reasons are as follows:

  • The log control files do not exist in the database directory.
  • The file permission settings prevent read or write access.
  1. Identify why the database manager could not update the log control files by reviewing the diagnostic (db2diag) log files.
  2. Correct the problem, for example, by taking the following steps:
    • Ensure that both the primary and secondary log control files exist in the database directory.
    • Change the permission settings of the files.
  3. Reissue the command.

DBT1032N

 The instance is not currently active.

The tool requires the instance to be active before it can perform any processing.

Issue a db2start before issuing the command.

DBT1033N

 Unable to attach to instance instance-name. SQLCODE = sqlcode.

An attempt to attach to the specified instance failed.

Verify the specified SQLCODE, correct the problem and resubmit the command.

DBT1034N

 Replacement of the string string-one with string-two for container container-name will exceed length restrictions.

An attempt to rename a container path using wildcards failed because the resulting path length is too long.

The maximum length for a container path is 256 characters. Modify the container path to conform to the length restriction and reissue the command.

DBT1035N

 Unable to set the HADR database role to standard for database database-name. SQLCODE = sqlcode.

An attempt to set the HADR database role to standard failed.

Verify the specified SQLCODE, correct the problem and resubmit the command.

DBT1036N

 Unable to refresh the directory cache after a successful relocation of database database-name. SQLCODE = sqlcode.

An attempt to perform a necessary refresh of the directory cache was unsuccessful.

Restart the instance on the current node and rerun the DB2INIDB tool without specifying the RELOCATE USING option. If the problem persists, contact your technical service representative.

DBT1037N

 CONT_PATH entries cannot be specified for an automatic storage table space.

An attempt has been made to relocate container paths for an automatic storage table space.

Remove the CONT_PATH entries that correspond to automatic storage table space. Only STORAGE_PATH entries can be used to relocate automatic storage table space.

DBT1038N

 A storage group has not been defined for the database.

An attempt has been made to relocate storage paths for a database that contains no storage groups.

Remove the STORAGE_PATH entries from the configuration file.

DBT1039N

 Unable to copy storage group files.

An attempt to duplicate the storage group file SQLSGF.1 has failed.

Ensure that there is sufficient disk space for the duplicated storage group file. Correct the problem and resubmit the command.