DB20000 - DB29999

DB20000I The `command` command completed successfully.

Explanation

No errors were encountered during the execution of this command.

User response

No action required.

DB21001E The option `option-letter` specified after the 'db2' command or in the DB2OPTIONS variable is incorrect.

Explanation

The option specified is not supported. The supported options are:

Option Description
------ -------------------------------
-a  Display SQLCA
-c  Auto-commit
-e  Display SQLCODE/SQLSTATE
-f  Read from input file
-l  Log commands in history file
-n  Remove new line character
-o  Display output
-p  Display interactive prompt
-r  Save output report to file
-s  Stop execution on cmd error
-t  Set stmt termination character
-v  Echo current command
-w  Display FETCH/SELECT warnings
-x  Suppress printing of column
    headings
-z  Save all output to file

The command cannot be processed.

User response

Resubmit the command with a valid option.

DB21002E The parameter for option `option-letter` specified after the 'db2' command or in the DB2OPTIONS variable is missing or incorrect.

Explanation

The following lists the options with parameters:

Option      Description
------      --------------------------
-ec         Display SQLCODE
-es         Display SQLSTATE
-f<filename> Read from input
            file
            <filename>
-l<filename> Log commands in
            history file
            <filename>
-r<filename> Save output report
            to file <filename>
-td<x>       Set termination
            char to 'x'
-z<filename> Save all output to
            file <filename>

file permissions do not allow file access
the file does not exist

Too much data is being output to the screen. Pipe the output to a file that you can view once processing is complete.
Command line processor did not successfully install its interrupt signal handler.
Command line processor did not successfully open the back-end process queues.
Command line processor did not successfully start up the back-end process.
The back-end process was abnormally terminated.
The front-end process did not successfully allocate or free memory.
The front-end and/or back-end process did not successfully dynamically load a library.
Command line processor received one of the following program termination signals:
- SIGILL
- SIGTRAP
- SIGEMT
- SIGBUS
- SIGSEGV
- SIGSYS

User response

Retry the command. If the problem persists, record the DB2 message number. If the trace was active, save the trace information and contact your technical support with the following information:

Problem description
DB2 message number
SQLCA if possible
Trace file if possible

DB21019E An error occurred while accessing the directory `directory`.

Explanation

The following could have caused the error:

directory permissions do not allow access
the directory does not exist

The Administration Server instance is not set correctly.
Command line processor was already attached to a database manager instance.
Command line processor was connected to a database.

User response

To see which parameter changes took effect dynamically and which ones did not, retrieve the database manager configuration parameters and display details using the following command:

DB2 GET DBM CFG SHOW DETAIL

Changes to database manager configuration parameters can only take effect dynamically if you are attached to the instance. Not all configuration parameters support dynamic update. To see which parameters can be changed dynamically, refer to the Administration Guide.

If several parameters were submitted in a group, submit the parameters individually. In those cases where a configuration parameter could not change dynamically, do one or more of the following:

for user applications: stop and start the application
for CLP: TERMINATE and reconnect
for a server: issue DB2STOP and DB2START

DB21026I One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, all applications must disconnect from this database before the changes become effective.

Explanation

The database configuration command has been successfully processed. However, not all changes were processed right away. After the applications disconnect from the database, the first connection to the database will cause the changes to become effective.

User response

To see which parameter changes took effect dynamically and which ones did not, retrieve the database configuration parameters and display the parameter details using the following command:

DB2 GET DB CFG FOR
   <database-alias> SHOW DETAIL

Changes to database configuration parameters can only take effect dynamically if you are connected to the database. Not all configuration parameters support dynamic update. To see which parameters can be changed dynamically, refer to the Administration Guide.

If several parameters were submitted in a group, submit the parameters individually. In those cases where a configuration parameter could not change dynamically, do one or more of the following:

Ensure that all applications disconnect from the database and issue a db2 connect to command
Rebind your packages after the new configuration parameters take effect so that the new values will be used during the bind.
Use the FLUSH PACKAGE CACHE command to invalidate dynamic statements in the SQL cache.

DB21033E The command is not valid for this database server.

Explanation

The following commands are supported only when accessing a DB2 for Linux, UNIX, or Windows database server:

LIST TABLES
LIST PACKAGES
REORGCHK
INGEST

User response

Do not issue the command for this database.

DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:

Explanation

You can execute database utilities, SQL statements, and online help using the DB2 command line processor (CLP). You can use the CLP in interactive mode, in command mode (where each command must be prefixed by "db2"), or in batch mode.

This message is displayed in the following scenarios:

Text is passed to the CLP and it is not a valid CLP command.
An error occurs when the CLP passes the text to the database manager to process as an SQL statement. When this scenario happens, this message is returned, followed by the error message that was returned by the database manager.

This error can be caused by the following kinds of problems with the specified command or SQL statement:

Text is passed to the CLP in command mode or in batch mode and there are special characters, such as quotes, in the text that are not identified with an escape character.
There is a syntax error.

User response

Respond to this error in one of the following ways:

If there are special characters, such as quotes, in the command, use an escape character, such as the backslash character, to cause the operating system shell to ignore those special characters.
Correct the syntax error by performing the following steps:
1. Review the full text of the error returned by the database manager to determine the cause of that error.
2. Modify the command to correct the cause of the problem.
3. Resubmit the command.

DB21035E The maximum number of items in the `list-name` list has been exceeded. The maximum number is `number`.

Explanation

The number of items in the list cannot exceed the maximum specified. This error may be caused by an invalid range specification.

User response

Correct the error and resubmit the command.

DB21036E The `command` command failed.

User response

Retry the command with the trace active. If the problem persists, save the trace information and contact your technical support with the following information:

Problem description
DB2 message number
Trace file

DB21037W No data sources found.

Subcommand Description
---------- ---------------------------
c <number> Heuristically commit
           the in-doubt transaction
           <number>.
r <number> Heuristically roll-
           back the in-doubt
           transaction <number>.
f <number>  Heuristically forget
           the in-doubt transaction
           <number>.
l <number>  List all in-doubt
           transactions or the in-
           doubt transaction
           <number>.
q          Exit LIST INDOUBT
           TRANSACTION prompting.

While processing the portion of the command indicated by the reason code, the command line processor was unable to get enough memory.

Reason
code Description    Syntax
---- -------------- ------------------
1   Data file      LOAD FROM
                   file/pipe/dev...
2   Lob data       LOBS FROM
                   lob-path...
3   Directory      USING directory...
4   Source         FROM dir/dev...
5   Target         TO dir/dev...
6   Tablespace     TABLESPACE
                   tblspace-name...
7   Tblspace-def   MANAGED BY...
8   Container data USING (PATH...,
                   PATH...)
                   or
                   USING (
                   {FILE|DEVICE}...,
                   {FILE|DEVICE}...)
9   Log path       log-directory ...,
                   log-directory ...
10  Node list      node-number ...,
                   node-number ...
11  Partitioned    [PARTITIONED DB CONFIG]
    load option    partitioned-db-option
                 [{partitioned-db-option}...]
  
12  Storage path   ON drive/path,
                   drive/path...
17  Ingest field  ($field-name field-type, ...)
    definition 
18  SQL statement  INSERT ..., UPDATE ...,
    on the INGEST  MERGE..., or DELETE ... 
    command
19  Column name   any column name in the statement
    in the SQL 
    statement on the 
    INGEST command
20  Field name    any field name in the statement
    in the SQL 
    statement on 
    the INGEST command

User response

You might be able to avoid the error by one of the following:

Specify a larger value for one of the database manager configuration parameters that control heap or memory size.
Modify the portion of the command indicated by the reason code to contain fewer elements. For example, if the reason code is 17, remove some field definitions from the INGEST command.

DB2 GET DBM CFG SHOW DETAIL

DB21085I This instance or install (instance name, where applicable: `instance-name`) uses `32-or-64` bits and DB2 code release `release` with level identifier `level`.

Explanation

This message is the output of the db2level command and provides detailed information about the code level of a given database product. The information might be requested by IBM software support to aid in resolving problems.

When the db2level command is run with a database product that does not have a database manager instance, such as the IBM Data Server Driver Package or the IBM Data Server Driver for ODBC and CLI, the value of the first run-time token, instance-name, will be "*".

User response

Record all displayed information to provide to IBM software support.

The db2level executable should not be copied from one machine to another.

The db2level executable may not display all information about private test fixes that have been provided by DB2 software support and installed on top of an officially supported service level.

DB21086I The incremental RESTORE operation of this backup image completed successfully, but there are additional backup images that must be restored to complete the entire incremental RESTORE operation.

Explanation

To complete an incremental RESTORE operation, every incremental backup image in its restore chain must be restored. The current operation succeeded, but there are additional backup images that must be restored before the overall RESTORE operation is complete.

User response

Restore the next backup image.

DB21089I

DB2 Administration Server `server-name` uses DB2 code release
`ver-rel-mod`
with level identifier `level-id`.
Informational tokens are `build-id1`, `build-id2`, and Fix Pack `FixPak-number`.
Product is installed at `install-path`.

Explanation

This message is the output of the db2daslevel command and provides detailed information about the code level of a given DB2 Administration Server. The information may be requested by DB2 service personnel to aid in resolving problems.

Explanation

For CLP commands REGISTER XMLSCHEMA, REGISTER XSROBJECT, ADD XMLSCHEMA DOCUMENT, COMPLETE XMLSCHEMA, or DECOMPOSE XML DOCUMENT, some possible reason codes include:

1: The file size is zero.
2: The file cannot be found.
3: Access to the file was denied. The user does not have permission to open the file.
4: Unexpected end of file encountered while reading from the file.
5: Access to the file was denied. The file is in use.
6: A media error was encountered while accessing the file.
7: The size of the document exceeds the maximum size supported by the command.

User response

Fix any errors and rerun the application.

DB21108E The request cannot be executed because the database server version does not support this functionality.

Explanation

Some new functionality is not supported against older database server versions.

User response

Execute the request against a database server where the latest database server version has been installed, or upgrade the server to the latest database server version.

DB21109E The syntax is incorrect for the `directive` directive. Reason Code: `reason-code`.

Explanation

The new terminator cannot be set, because of a problem with the --#SET TERMINATOR syntax fragment in the directive. The terminator has not been changed. One of the following reason codes may apply:

Reason codes:

1: An invalid terminator was specified. A valid terminator contains one or two characters, but cannot contain a space or a tab.
2: The directive does not include a new terminator.
3: There must be a space after the words --#SET TERMINATOR.

User response

Revise the syntax of your directive, and then reissue the directive.

DB21500I The DB2MSCS command completed successfully.

Explanation

The user request was successfully processed.

User response

No action required.

DB21501E The db2mscs command failed because the following invalid option was specified: `option-name`

Explanation

You can create the infrastructure for DB2 failover support with Microsoft Cluster Server (MSCS) using the db2mscs utility.

Valid arguments for the db2mscs command are:

-f InputFileName Specifies the DB2MSCS.CFG input file to be used by the MSCS utility. If this parameter is not specified, the DB2MSCS utility reads the DB2MSCS.CFG file that is in the current directory.
-d TraceFileName Turns on debug tracing and specifies the name of the trace output file.
-u InstanceName Undo the DB2MSCS operation for the instance.
-l Username Specifies the user name of the domain account for the DB2 service (specified as domain\user).
-p Password Specifies the password of the domain account for the DB2 service.

User response

Enter the command again with valid parameters.

DB21502E Cannot open the configuration file `file-name`.

Explanation

A configuration file could not be opened. Depending on the filename in the message text, this error can be explained as follow:

If the filename in the message text was the name of the input file specified for the DB2MSCS command, then input file can not be found.
If the filename was "db2systm", then the database manager configuration file for target instance is missing.
If the filename was "db2mscs.bak", then the backup configuration file could not be created in the instance directory.
If the filename was "db2mscs.bak" and an undo operation was performed, then the backup configuration file from the instance directory could not be opened when performing the undo operation.

User response

Depending on the file that was in error, the problem may be corrected as follow:

If the filename in the message text was the name of the input file specified for the DB2MSCS command, then ensure that the file exists in the current directory, or that a fully qualified filename is specified for the command.
If the database manager configuration file for target instance is missing, then drop and recreate the instance.
If the backup configuration file could not be created in the instance directory, then ensure that the instance profile directory exists and that the current logon account has write access to the directory.
If the backup configuration file from the instance directory could not be opened when performing the undo operation, then ensure that the MSCS disk that contains the instance profile directory is online on the current machine and retry the operation.

After all the required MSCS resources had been created, the DB2MSCS utility failed to migrate the database manager instance to run in a clustered environment because of an internal error. During an instance migration, the utility performs the following steps:

Copy the instance directory to the location specified by the INSTPROF_DISK or INSTPROF_PATH keyword.
Move the DB2 registry profile variables from the machine registry to the cluster registry.
Set the DB2INSTPROF registry variable to point to the new instance profile location.
Set the DB2CLUSTERLIST to the name of the current machine.

User response

Before running the DB2MSCS utility, ensure that:

On the current machine, the instance can be started and stopped successfully from the command line.
On other cluster node(s), the same instance must be stopped and optionally dropped.
All the disk resources are active on the current machine and can be moved back and forth successfully between the cluster nodes.
The current logon user has sufficient access to the local machine registry and the cluster registry.
If the problem persists, contact your IBM Service Representative and provide both the DB2MSCS traces and DB2 traces.

DB21534E An error occurred during addition of MSCS node to the database manager instance, rc = `error-code`.

Explanation

The utility failed to add the other MSCS node to the database manager instance. During this operation, the utility will do the followings:

Update the DB2 cluster machine list by adding the name of the target machine to the DB2CLUSTERLIST registry variable.
Create the DB2 service and the registry instance profile for the current database manager instance on the target node.

User response

Before running the DB2MSCS utility, ensure that:

On the current machine, the instance can be started and stopped successfully from the command line.
On other cluster node(s), the same instance must be stopped and optionally dropped.
All the disk resources are active on the current machine and can be moved back and forth successfully between the cluster nodes.
The current logon user has sufficient access to the target machine registry and the cluster registry.
If the problem persists, contact your IBM Service Representative and provide both the DB2MSCS traces and DB2 traces.

Stop and drop the database manager instance.
Remove all DB2 resources and their dependent resources from the Cluster Administrator window.

DB22000E Error: The syntax of the DB2LSWTCH command is incorrect.

Explanation

The local switcher promotes or demotes the DB2 copy it is installed under:

db2lswtch.exe -db2 -promote
db2lswtch.exe -client -promote
db2lswtch.exe -all -promote

db2lswtch.exe -db2 -demote
db2lswtch.exe -client -demote
db2lswtch.exe -all -demote

The command options are:

-db2 -promote to promote the current copy to the default DB2 copy.
-client -promote to promote the current copy to the default IBM database client interface copy.
-all -promote to promote the current copy to the default DB2 copy and IBM database client interface copy.

-db2 -demote to demote the current default DB2 copy.
-client -demote to demote the current default IBM database client interface copy.
-all -demote to demote the current default DB2 copy and IBM database client interface copy.

The db2swtch utility can display the DB2 copies or IBM data server driver copies installed on the system, and set the default DB2 copy or default IBM database client interface copy. This utility can also be used to redirect the references in machine.config between common IDS .NET data provider and SQLI IDS .NET data provider:

db2swtch [-db2|-client]
         [-d {name of DB2 copy or IBM data
              server driver copy}]
         [-l]
         [-IDS common|SQLI]
         [-h|-?]

The command options are:

(no arguments): launches the utility in graphical mode
-d {name of DB2 copy}: sets the default DB2 copy and default IBM database client interface copy to the name specified
-db2 -d {name of DB2 copy}: sets the default DB2 copy to the name specified
-client -d {name of DB2 copy or IBM data server driver copy}: sets the default database client interface copy to the name specified
-l: displays the list of DB2 copies and IBM data server driver copies on the system
-IDS common: redirects the IDS .NET data provider reference in machine.config to common IDS .NET data provider
-IDS SQLI: redirects the IDS .NET data provider reference in machine.config to SQLI IDS .NET data provider
-h|-?: displays help

DB29526E You cannot drop this table; it does not exist. Please select a job that has results, and try again, or select a recurring job that is scheduled and try again.

Explanation

A request was made to drop a result table for a job which did not have an associated result table.

User response

Select a job that has a results or select a recurring job that is scheduled and try again.

DB29527W Are you sure you want to cancel job #`param-1`?

DB29528W Are you sure you do NOT want to display job #`param-1`?
WARNING: If you select this option this job will never be displayed again.

DB29530W This option will remove confirmation messages from actions like 'cancel' and 'hide'. Is this something you really want to do?

DB29537E Unknown Type: `param-1`

DB29542E

Connection SQL error: `param-1`
Error Number: `param-2`
Error Message: `param-3`

DB29545E Name invalid: Query Name can only be 20 characters or less in length. Please change the name accordingly and retry.

Explanation

A name for a query was specified which was longer than 20 characters.

User response

Specify a query name that has at most 20 characters.

DB29546E Name invalid: Query Name can only contain alphanumeric characters and spaces...( "a..z", "A..Z", "0..9" ). Please change the name accordingly and retry.

Explanation

A name for a query was specified which contained non-alphanumeric characters.

User response

Specify a query name composed of only alphanumeric characaters.

DB20000 - DB29999

DB20000I The command command completed successfully.

Explanation

User response

DB21001E The option option-letter specified after the 'db2' command or in the DB2OPTIONS variable is incorrect.

Explanation

User response

DB21002E The parameter for option option-letter specified after the 'db2' command or in the DB2OPTIONS variable is missing or incorrect.

Explanation

User response

DB21003E The value value in environment-variable is not valid.

Explanation

User response

DB21004E You cannot specify both an input file and a command when invoking the Command Line Processor.

Explanation

User response

DB21005E An error occurred while accessing the file filename.

Explanation

User response

DB21006E The input command is too long. The maximum length is length.

Explanation

User response

DB21007E End of file reached while reading the command.

Explanation

User response

DB21008E Commands can only be entered from the command line processor interactive mode or file input mode.

Explanation

User response

DB21009E This command must be launched from a command window running with full administrative privileges.

Explanation

User response

DB21010I Help given for help-command-phrase.

Explanation

User response

DB21011I In a partitioned database server environment, only the table spaces on the current node are listed.

Explanation

User response

DB21015E The Command Line Processor backend process request queue or input queue was not created within the timeout period.

Explanation

User response

DB21016E The Command Line Processor encountered a system error while sending the command to the backend process.

Explanation

User response

DB21017E The Command Line Processor encountered a system error with the front-end process output queue. Reason code = reason-code.

Explanation

User response

DB21018E A system error occurred. The command line processor could not continue processing.

Explanation

User response

DB21019E An error occurred while accessing the directory directory.

Explanation

User response

DB21020E Unable to create the default message file file.

Explanation

User response

DB21021E No Admin Server instance is defined. The command failed.

Explanation

User response

DB21022E Unable to switch to Administration Server instance instance-name.

Explanation

User response

DB21023E The command is not valid when executed from Administration Server.

Explanation

User response

DB21024I This command is asynchronous and may not be effective immediately.

Explanation

User response

Explanation

User response

DB21026I One or more of the parameters submitted for immediate modification were not changed dynamically. For these configuration parameters, all applications must disconnect from this database before the changes become effective.

Explanation

User response

DB21027E Isolation level may not be changed while connected to a database.

Explanation

User response

DB21028E The cursor cursor-name has not been declared.

Explanation

User response

DB21029E The cursor cursor-name has already been declared and opened.

Explanation

DB20000I The `command` command completed successfully.

DB21001E The option `option-letter` specified after the 'db2' command or in the DB2OPTIONS variable is incorrect.

DB21002E The parameter for option `option-letter` specified after the 'db2' command or in the DB2OPTIONS variable is missing or incorrect.

DB21003E The value `value` in `environment-variable` is not valid.

DB21005E An error occurred while accessing the file `filename`.

DB21006E The input command is too long. The maximum length is `length`.

DB21010I Help given for `help-command-phrase`.

DB21017E The Command Line Processor encountered a system error with the front-end process output queue. Reason code = `reason-code`.

DB21019E An error occurred while accessing the directory `directory`.

DB21020E Unable to create the default message file `file`.

DB21022E Unable to switch to Administration Server instance `instance-name`.

DB21028E The cursor `cursor-name` has not been declared.

DB21029E The cursor `cursor-name` has already been declared and opened.

DB21030E The cursor `cursor-name` has not been opened.

DB21031E The SQL statement using the cursor `cursor-name` (`internal-cursor`) returned:

DB21035E The maximum number of items in the `list-name` list has been exceeded. The maximum number is `number`.

DB21036E The `command` command failed.

DB21040E Transaction number `number` is not a valid indoubt transaction number.

DB21041W The following amount of indoubt transactions was not displayed: number `number`

DB21043E `subcommand` is not a valid request.

DB21044E Cannot COMMIT transaction number `number`.

DB21045E Cannot ROLLBACK transaction number `number`.

DB21046E Cannot FORGET transaction number `number`.

DB21050E `state` is not a valid SQLSTATE.

DB21052I `command` has been submitted for execution.

DB21053W Automatic escalation will occur when you connect to a database that does not support `isolation-level`.

DB21054E The command line processor encountered a system error with the `command` command. Reason code = `reason-code`.