DBT2000-2999

DBT Message ID Message Explanation User Response

DBT2002W

 Unable to write the end of tape marker. Reason: reason

Writing to the end of tape marker failed.

No further action is required.

DBT2006I

 db2tapemgr completed successfully.

Processing completed without any errors and warnings.

No further action is required.

DBT2007W

 db2tapemgr completed with warnings.

The db2tapemgr command completed without any errors, but warnings.

Refer to the output for more information.

DBT2008N

 db2tapemgr failed with errors.

db2tapemgr completed with errors.

Refer to the output for more information.

DBT2009N

 Internal error occurred. Reason: error.

An unexpected error occurred.

Refer to the reason text for further actions.

DBT2015W

 Log file log-file-name is not on disk.

The log file cannot be found.

If the log file was accidentally deleted, either restore the log file and reissue the command or update the location field for the missing log file in the history file.

DBT2016I

 No log files found for processing.

The history files do not contain information about log files.

No further action is required.

DBT2017N

 Label label-one is not inserted in the tape drive. The tape inserted in the drive has a label label-two.

Two different tapes cannot have the same name.

Confirm that the correct tape is in the tape drive. If the tape is unreadable, use the DELETE TAPE LABEL option to remove the information about this tape from the history file. If an existing tape label was specified, choose another label and reissue the command.

DBT2018N

 Invalid value value for variable variable.

The specified value is invalid.

Specify a valid value.

DBT2019N

 The tape has not expired. The tape will expire on expiration-date.

Unable to write to the tape as the tape has not expired. It is possible that the tape contains log files which may be required for database recovery.

Either reduce the value of DB2_TAPEMGR_TAPE_EXPIRATION or insert a different tape.

DBT2020N

 Log files on tape are from a different database database-name.

The log files on the tape are from a different database.

Insert another tape or specify the FORCE option.

DBT2021N

 Log files on tape are from a different database instance instance-name.

The log files on the tape are from a different database instance.

Insert another tape or specify the FORCE option.

DBT2022N

 Log files on tape are from a different database partition database-partition.

The log files on the tape are from a different database partition.

Insert another tape or specify the FORCE option.

DBT2027N

 Tape has not been used for storing log files before.

The contents of the tape are not recognized as a file which has been written by db2tapemgr.

No further action is required.

DBT2032W

 Only number-of-log-files log files fit on tape.

The selected number of log files do not fit on tape.

To avoid this warning, specify a maximum number of log files to write on tape using the n LOGS option.

DBT2036W

 Storing history file on tape failed. Reason: reason

The log files have already been written to tape successfully.

If the tape is full, limit the number of log files written to tape using the n LOGS option.

DBT2039I

 Clearing location in history for log files currently on tape tape-name.

The location field of the log file entries in the history file are cleared. An empty location field in a log file entry indicates that the log file has been deleted or overwritten and is no longer available for database recovery.

No further action is required.

DBT2047N

 Tape contains log files for database partition number db-partitionnum-1, however database partition number db-partitionnum-2.

The tape contains logs for a database partition that does not correspond to the database partition specified.

Specify the correct database partition number. If no value is specified, the value of DB2NODE is used.

DBT2048I

 Tape contains log files of database database-name1, however database database-name2 was specified.

The tape contains log files of another database.

Proceed only if you plan on performing a redirected restore operation.

DBT2049I

 Tape contains log files of instance instance1, however instance instance2 was specified.

The tape contains log files of another database instance.

Proceed only if you plan on performing a redirected restore operation.

DBT2050I

 The log file log-file is on disk.

The log file is already on disk and will not be retrieved from tape.

To retrieve the log file from tape again, delete the log file on disk and specify the RETRIEVE option. Otherwise, no further action is required.

DBT2051N

 No matching backup found in the history file.

The history file does not contain a backup.

Specify a different rollforward time and reissue the command. Otherwise, restore the log files manually using the ALL LOGS or LOGS n TO m option.

DBT2052I

 No required log file found.

The log files are required for rollforward operation.

If the history file is current, no further action is required. Otherwise the history file may not contain all information required for a rollforward operation. If this is the case, restore a history file from the newest tape using the RETRIEVE HISTORY FILE option and reissue the command with the USING HISTORY FILE option.

DBT2053I

 No required log file on tape.

The history file does not contain any entries specifying that a log file will need to be retrieved from tape for a rollforward operation.

If the history file is current, no further action is required. Otherwise the history file may not contain all information required for a rollfo rward operation. If this is the case, restore a history file from the newest tape using the RETRI EVE HISTORY FILE option and reissue the command with the USING HISTORY FILE option.

DBT2054I

 Log files required for backup taken at timestamp timestamp:

The log files are required for rollforward.

If the history file is up-to-date, no further action is required. Otherwise the history file may not contain all information required for a rollforward operation. If this is the case, restore a history file from the most recent tape using the RETRIEVE HISTORY FILE option and reissue the command with the USING HISTORY FILE option.

DBT2055I

 No tapes are required for the rollforward operation.

If your history file is up-to-date, no further action is required. Otherwise the history file may not contain all information required for a rollforward operation. If this is the case, restore a history file from the most recent tape using the RETRIEVE HISTORY FILE option and reissue the command with the USING HISTORY FILE option.

DBT2062I

 Working on database database-name.

The DATABASE option was not specified. The default value controlled by the DB2DBDFT variable is used.

To operate on another database, specify the DATABASE option.

DBT2063N

 The DATABASE option is not specified and the DB2DBDFT is not set.

Specify the DATABASE option or set the DB2DBDFT variable.

DBT2065I

 Using database partition partition-number.

The default value is either 0 or the value of the DB2NODE variable.

to change the database partition, specify the DATABASE option or set the DB2DBDFT variable.

DBT2067N

 No directory specified and the database configuration parameter OVERFLOWLOGPATH is not set.

Retrieve operations require that a destination directory is set.

Specify the TO option or set the OVERFLOWLOGPATH database configuration parameter.

DBT2068N

 The value value of database configuration parameter OVERFLOWLOGPATH is not a directory.

Ensure that the OVERFLOWLOGPATH directory exists.

DBT2069N

 Unable to double store to same tape.

Choose another tape for your double store operation.

DBT2071I

 Using the automatic generated tape-label label.

The format of the label is the current time followed by the database alias.

To specify a table label, use the TAPE LABEL option.

DBT2102N

 File name filename1 does not match filename2.

The file name does not match the expected file name. This may occur if another program has written files to the tape.

No further action is required.

DBT2103N

 Directory directory-name does not exist

The specified directory does not exist.

Create the specified directory.

DBT2104N

 File file-name found.

More than one file is found on this tape.

No further action is required.

DBT2106N

 Database database-name is remote.

The specified database is catalogued as remote database. The db2tapemgr can only be used on local databases.

Login locally and recall tool.

DBT2108N

 Database database-name not found in database directory.

The specified database is not found in the database directory.

Choose another database name or if the database exists, ensure that the database is catalogued.

DBT2109N

 Parameter parameter is expected.

The specified parameter is expected.

Reissue the command using the correct syntax.

DBT2110N

 Value value of parameter parameter is too long.

The specified value for this parameter is too long.

Reissue the command using the correct syntax.

DBT2111N

 Value value of parameter parameter is too short.

The specified value for this parameter is too short.

Reissue the command using the correct syntax.

DBT2112N

 Device device-name is not a tape device.

The specified device is not recognized as a tape device.

Specify a recognized tape device name like and reissue the command.

DBT2113N

 Device device-name is a rewind device.

The specified device is not recognized as a non-rewind tape device.

Specify a recognized tape device name like and reissue the command.

DBT2114N

 History file history-file does not exist.

The specified history file does not exist.

Check the path to the history file and Reissue the command.

DBT2115N

 History file history-file does not end with value.

The specified history file name does not end with db2rhist.asc.

Check the file name of the history file and reissue the command.

DBT2116N

 Value value of parameter parameter is not alphanumeric.

The value of the parameter needs to be alphanumeric.

Reissue the command using the correct syntax.

DBT2117N

 Value value of parameter parameter is out of range.

The value of the parameter is out of range.

Reissue the command using the correct syntax.

DBT2118N

 Parameter blocksize needs to be a multiple of 512.

Choose a multiple of 512 as blocksize and reissue the command.

DBT2119N

 Value value of parameter parameter is not numeric.

Reissue the command using the correct syntax.

DBT2120N

 No operation is specified.

The parameter which specifies the operation is not specified.

Reissue the command with the correct syntax.

DBT2121N

 Unknown operation operation is specified.

Reissue the command using the correct syntax.

DBT2122N

 Too many command arguments are specified following the command parameter: parameter.

Reissue the command using the correct syntax.

DBT2123N

 Invalid time format time-format.

The time format should conform to the following format: YYYY-MM-DD:HH:MM:SS.

Reissue the command with the correct time format syntax.

DBT2124N

 Unable to reduce number of log files.

Use the n LOGS option to limit the amount of log files to write on tape and reissue the command.

DBT2125N

 File file-name1 is not a tape header file. File file-name2 is found.

The tape contains other types of files. This may occur if another program has written files to the tape.

No further action is required.

DBT2126N

 Invalid tape header format.

The contents of the tape header are not recognized.

Attempt to retrieve the log files manually from tape.

DBT2127N

 Changes were made to history file during update.

Updating the history file failed because another process has updated the history file.

Reissue the command.

DBT2128N

 The maximum number of open scans has exceeded the limit.

Reading the history file failed because too many processes are accessing the history file.

Reissue the command.

DBT2129W

 Fixed damaged history file.

A damaged history file has been fixed automatically.

No further action is required.

DBT2130N

 History file cannot be fixed.

A damaged history file has been detected and it cannot be fixed.

Restore another version of the history file and reissue command.

DBT2131N

 The number of table spaces has changed in the history file.

The contents of the history file has been changed by another process.

Reissue the command.

DBT2132N

 A duplicate timestamp exists within the history file.

The history file contains entries with same timestamp.

Restore another version of the history file and reissue command.

DBT2138N

 The history file does not correspond to the current partition.

Specify a history file that corresponds to the ON DBPARTITIONNUM parameter that was specified when the utility started. If this parameter was not specified when the utility started, the value of DB2NODE is used.

DBT2150N

 db2relocatedb failed because of the value specified for the keyword keyword in the db2relocatedb configuration file. Reason code: reason-code.

You can use the db2relocatedb command to rename or relocate all or part of a database. The db2relocatedb takes the name of a configuration file as a parameter. In the configuration file, you can specify the configuration of the renamed or relocated database using keyword-value pairs.

This message is returned when there is a problem with the value specified for the given keyword keyword. The reason code indicates the nature of the problem:

1

The specified directory does not exist.

2

The db2relocatedb utility does not have permission to access the specified directory.

3

A value was specified for keyword keyword but the corresponding database configuration parameter is not set for the database that you are trying to relocate.

Respond to this error according to the reason code:

1

Create the new directory that you want to use and re-issue the db2relocatedb command again.

2

Grant the db2relocatedb utility and the database manager write permission on the new directory and re-issue the db2relocatedb command again.

3

Remove the keyword on the configuration file and re-issue the db2relocatedb command. After the command completes successfully, you can set the database configuration parameter using the UPDATE DATABASE CONFIGURATION command or the db2CfgSet API.

DBT2200E

 This option is not valid. Option: option-name

The specified option is not valid.

Specify a valid option and run the command again.