Command Line Process Could Not Continue Processing
Messages Reference
Chapter 7. DB2 Messages
Each message has a message identifier that consists of a prefix (DB2) and a message number. Messages are listed in numeric sequence based on the message number. These messages are generated by the command line processor to alert you when a warning or error condition occurs. Messages are displayed directly on the screen interface. The command line processor returns DB2 and SQL messages.
For more information about SQL messages, see Chapter 10. "SQL Messages" in this guide.
DB20000I The "<command>" command completed successfully.
Cause: No errors were encountered during the execution of this command.
Action: No action required.
DB21001E The option "<option-letter>" specified after the 'db2' command or in the DB2OPTIONS variable is incorrect.
Cause: 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 -o Display output -p Display db2 interactive prompt -r Save output report to file -s Stop execution on command error -t Set statement termination character -v Echo current command -w Display FETCH/SELECT warning messages -z Save all output to file
The command cannot be processed.
Action: 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.
Cause: 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 character to 'x' -z<filename> Save all output to file <filename>
Action: Resubmit the command with the valid option and parameter.
DB21003E The value "<value>" in "<environment-variable>" is not valid.
Cause: The value for DB2BQTRY must be between 0 and 4294967295. The value for DB2BQTIME, DB2RQTIME or DB2IQTIME must be between 1 and 4294967295.
Action: Set the environment variable with the correct value and resubmit the command.
DB21004E You cannot specify both an input file and a command when invoking the command line processor.
Cause: You cannot specify both the -f option and a command line command when invoking the command line processor.
Action: Correct the error and issue the command again.
DB21005E An error occurred while accessing the file "<filename>".
Cause: The following could have caused the error:
- file permissions do not allow file access
- the file does not exist
Action: Correct the error and try again.
DB21006E The input command is too long. The maximum length is "<length>".
Cause: The input command cannot exceed the length specified.
Action: Correct the error and resubmit the command.
DB21007E End of file reached while reading the command.
Cause: The last command was not executed because end of file was reached. Terminate the last command with a ';' (or your defined termination character) if the -t option was used. Remove the '\' from the last line in the command if the +t option was used.
Action: Correct the error and resubmit the command.
DB21008E Commands can only be entered from the command line processor interactive mode or file input mode.
Cause: The user attempted to enter a command line processor command from the DOS prompt.
Action: Use command line processor interactive mode or file input mode.
DB21010I Help given for "<help-command-phrase>".
Cause: This message only appears in the history file specified with the -l option.
Action: No action required.
DB21011I In a partitioned database server environment, only the table spaces on the current node are listed.
Cause: Only the table spaces on the current node are visible to the LIST TABLESPACES command.
Action: To list the table spaces on another node, you must issue the LIST TABLESPACES command on that node.
DB21015E The command line processor back-end process request queue or input queue was not created within the timeout period.
Cause: Either the values for the DB2BQTRY and DB2BQTIME environment variables need to be increased or the command line processor back-end program "db2bp" cannot be started. The "db2bp" program must reside in the correct database manager install path and users must have execute permission on the file.
Action: Correct the error and resubmit the command.
DB21016E The command line processor encountered a system error while sending the command to the back-end process.
Cause: One of the following could have happened:
- The backend process was abnormally terminated.
- A system error occurred when reading from or writing to the back-end process queues.
- A system error occurred when reading from the front-end process output queue.
Action: Resubmit the command. If the error occurs again, get help from your system administrator.
DB21017E The command line processor encountered a system error with the front-end process output queue. Reason code = <reason code>.
Cause: A system error occurred while creating or reading from the front-end process output queue.
If the reason code is -2499, the command line processor output queue conflicts with an existing queue.
Action: Resubmit the command. If the error occurs again, record the message number and reason code, and get help from your system administrator.
DB21018E A system error occurred. The command line processor could not continue processing.
Cause: One of the following caused the system error:
- 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.
- Command line processor received one of the following program termination signals:
- SIGILL
- SIGTRAP
- SIGEMT
- SIGBUS
- SIGSEGV
- SIGSYS
Action: 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>".
Cause: The following could have caused the error:
- directory permissions do not allow access
- the directory does not exist
Action: Correct the error and resubmit the command.
DB21020E Unable to create the default message file "<file>".
Cause: To properly process this command, CLP needs a file where the messages issued during processing are saved before they are displayed on the console. It attempted to create such a file in a directory normally used for that purpose (such as /tmp on UNIX platforms or ...\TMP on OS/2), but the attempt failed because the directory does not exist.
Action: Correct the error and resubmit the command.
DB21021E No Administration Server instance is defined. The command failed.
Cause: You issued a command that needs to use an Administration Server instance, but no such instance is defined.
Action: Define an Administration Server instance and resubmit the command.
DB21022E Unable to switch to Administration Server instance "<instance-name>".
Cause: You issued a command that needs to use an Administration Server instance. Command line processor tried to switch to Administration Server instance "<instance-name>" but failed. The possible reasons may be:
- The Administration Server instance is not set correctly.
- Command line processor was already attached to a DB2 instance.
- Command line processor was connected to a database.
Action: Check that a valid Administration Server instance is set up before using this command. Also, you may need to issue the DETACH, or CONNECT RESET, or TERMINATE command before trying your request again.
DB21023E The command is not valid when executed from Administration Server.
Cause: You issued one of the following commands: GET DBM CONFIGURATION, RESET DBM CONFIGURATION, or UPDATE DBM CONFIGURATION, but these commands cannot be executed from Administration Server.
Action: Issue one of the following commands that are valid on Administration Server: GET ADMIN CONFIGURATION, RESET ADMIN CONFIGURATION, or UPDATE ADMIN CONFIGURATION.
DB21024I This command is asynchronous and may not be effective immediately.
Cause: This message is displayed after a FORCE command with the ASYNC clause.
Action: No action required.
DB21025I Client changes will not be effective until the next time the application is started or the TERMINATE command has been issued. Server changes will not be effective until the next DB2START command.
Cause: Changes to the database manager configuration parameters become effective only after they are loaded into memory. This typically occurs after a DB2START on a server and after the application restarts on a client.
Action: For the new database manager configuration parameters to become effective, 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 For most configuration parameters, all applications must disconnect from this database before the changes become effective.
Cause: The database configuration command has been successfully processed. However, except for some configuration parameters such as MINCOMMIT, the active database configuration cannot be changed until all applications have disconnected from the database. After the applications disconnect from the database, the first connection to the database will cause the changes to become effective.
Action: Ensure that all applications disconnect from the database and issue a db2 connect to command. Also, you may want to rebind your packages after the new configuration parameters take effect so that the new values will be used during the bind.
DB21027E Isolation level may not be changed while connected to a database.
Cause: The user attempted to change the isolation level while connected to a database. The command is ignored.
Action: If a change in isolation level is necessary, disconnect from the current database, then set the isolation level and re-connect to the database.
DB21028E The cursor "<cursor-name>" has not been declared.
Cause: The specified cursor needs to be declared before issuing an OPEN, FETCH, or CLOSE SQL statement.
Action: Declare the cursor and resubmit the command.
DB21029E The cursor "<cursor-name>" has already been declared and opened.
Cause: The user attempted to declare a cursor that is open.
Action: Close the cursor and resubmit the open command.
DB21030E The cursor "<cursor-name>" has not been opened.
Cause: The specified cursor needs to be opened.
Action: Open the cursor and resubmit the command.
DB21031E The SQL statement using the cursor "<cursor-name>" ("<internal-cursor>") returned:
Cause: This message shows the internal cursor name for the user defined cursor. Some SQL error messages may show the internal cursor name. This message is displayed before the SQL message.
Action: Correct the SQL error and resubmit the command.
DB21032E You have already declared the maximum number of cursors.
Cause: Command line processor supports 100 cursors declared with the WITH HOLD attribute and 100 cursors declared without the WITH HOLD attribute.
Action: Re-declare one of the existing cursors and resubmit the command.
DB21033E The command is not valid for databases that reside on DRDA hosts.
Cause: The following commands are not supported for databases that reside on DRDA host servers:
- LIST TABLES
- LIST PACKAGES
- REORGCHK
Action: 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:
Cause: This message is displayed before the SQL error message. The error may be caused by a syntax error in a non-SQL command.
Action: Correct the error and resubmit the command.
DB21035E The maximum number of items in the "<list-name>" list has been exceeded. The maximum number is "<number>".
Cause: The number of items in the list cannot exceed the maximum specified. This error may be caused by an invalid range specification.
Action: Correct the error and resubmit the command.
DB21036E The "<command>" command failed.
Action: 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.
Action: There were no ODBC data sources found of the type (USER or SYSTEM) that you specified. Retry the command by specifying the other type (SYSTEM or USER).
DB21040E "<number>" is not a valid in-doubt transaction number.
Cause: "<number>" is not one of the listed in-doubt transaction numbers.
Action: Select one of the listed transaction numbers and resubmit the command.
DB21041W <number> indoubt transaction(s) not shown.
Cause: Command line processor could not display all the in-doubt transactions. The number of transactions not displayed is "<number>".
Action: Finish processing the current list of indoubt transactions in order to reduce the total number of indoubt transactions in the system. Next, reissue the list indoubt transactions command.
DB21042E You must specify a transaction number.
Cause: A transaction number must be specified with the commit (c), rollback (r), or forget (f) in-doubt transaction subcommands.
Action: Reissue the command with the appropriate transaction number.
DB21043E "<subcommand>" is not a valid request.
Cause: The in-doubt transaction subcommand specified is not valid. Valid subcommands are:
Subcommand Description ---------- ----------------------------- c <number> Heuristically commit the in-doubt transaction <number>. r <number> Heuristically rollback 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. NOTE: The "f <number>" command is not available in DB2 Extended Enterprise Edition.
Action: Correct the error and resubmit the command.
DB21044E Cannot COMMIT transaction number "<number>".
Cause: The transaction must be in a prepared state (i) when you issue the commit (c) subcommand.
Action: Issue another command.
DB21045E Cannot ROLLBACK transaction number "<number>".
Cause: The transaction must be in a prepared (i) or idle (e) state. when you issue the rollback (r) subcommand.
Action: Issue another command.
DB21046E Cannot FORGET transaction number "<number>".
Cause: The transaction must be in a heuristically committed (c) or heuristically rolled-back (r) state when you issue the forget (f) command.
Action: Issue another command.
DB21050E "<state>" is not a valid SQLSTATE.
Cause: The sqlstate specified is not valid or could not be found. Valid states are numerical and two or five digits in length.
Action: Resubmit the command using a different state.
DB21051E The command is not supported for this environment.
Cause: The command requested is currently not supported by the command line processor in the environment being used.
Action: Resubmit the command on a different platform or within a different environment.
DB21052I "<command>" has been submitted for execution.
Cause: The command line processor is attempting to execute the indicated command. It will be unable to determine whether the command has completed successfully.
Action: If the command appears unsuccessful, submit it from outside the command line processor.
DB21053W Automatic escalation will occur when you connect to a database that does not support <isolation-level>.
Cause: Isolation levels are database dependent. Some, like NC, are only supported by specific databases. If you select an isolation level that is not supported by the database you are connecting to, it will automatically escalate to a supported level.
Action: Connect to a database that supports the isolation level you have selected, or select a different isolation level.
DB21054E The command line processor encountered a system error with the <command> command. Reason code = <reason code>.
Cause: The command line processor was unable to get enough memory to process your command. A system error occurred while processing it.
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 ... Action: Correct the error and resubmit the command.
DB21055W Command not valid for type 2 connections.
Cause: The information returned by the GET CONNECTION STATE command does not apply to type 2 connections.
Action: Issue QUERY CLIENT to verify CONNECT = 1.
DB21056W Directory changes may not be effective until the directory cache is refreshed.
Cause: If directory caching (DBM CFG dir_cache) is enabled, database, node, and DCS directory files are cached in memory. Directory changes may not become effective until the directory cache is refreshed. Refer to the dir_cache configuration parameter in the ADMIN guide for a description on directory caching.
Action: To refresh CLP's directory cache, issue a db2 TERMINATE. To refresh the directory information for another application, stop and restart that application. To refresh the directory information for the database, stop (db2stop) and restart (db2start) the database.
DB21057E Invalid tape device specified.
Cause: The tape device passed to the operating system was not accepted. On Windows NT it must be of the form "\\.\TAPEx" where x represents the drive number (0 is the first).
Action: Reissue the command specifying a valid tape device.
DB21058E Invalid tape position specified.
Cause: The tape mark position specified is not valid. On Windows NT the first tape position to which a backup is record is 1. Subsequent backup images begin at tape mark 2 and so on.
Action: Reissue the command specifying a valid tape position.
DB21059E Invalid tape blocksize specified.
Cause: The tape mark blocksize specified is not in the range supported by the tape device. In addition, for backup/restore to work it must also be a factor of or multiple of 4096.
Action: Reissue the command specifying a valid tape size.
DB21060E General tape failure.
Cause: An unexpected return code was returned from the tape operation.
Action: Resubmit the command. If the error occurs again, get help from your system administrator.
DB21061E Command line environment not initialized.
Cause: You have tried to invoke the command line processor from a command window that was not started by db2cmd.exe.
Action: Issue DB2CMD to start a command window that has the command line processor environment initialized.
DB21080E No previous RESTORE DATABASE command with REDIRECT option was issued for this database alias, or the information about that command is lost.
Cause: You have tried to run the RESTORE DATABASE command with the CONTINUE or ABORT option. However, either you didn't previously issue a RESTORE DATABASE command with the REDIRECT option, or you did issue such a command but for a different database alias than the one specified on the failing command. Another possible cause for this message could be that the information about a correctly issued previous RESTORE DATABASE ... REDIRECT command was lost. This can happen if the CLP back-end process terminates abnormally, or if you issue the TERMINATE command.
Action: Restart the whole redirected restore process by issuing the RESTORE DATABASE ... REDIRECT command and SET TABLESPACE CONTAINERS commands again. Then issue the RESTORE DATABASE ... CONTINUE command.
DB21081E No sections were found in the db2cli.ini file.
Cause: You have tried to list CLI parameters in the db2cli.ini file by using the GET CLI CONFIGURATION command, but the file is empty. There are no sections in that file.
Action: To update the db2cli.ini file, use the UPDATE CLI CONFIGURATION command.
DB21082E You don't have enough authority to run the UPDATE CLI CONFIGURATION command.
Cause: You need to have SYSADM authority to run this command.
Action: Obtain the necessary authority from your database administrator, then issue the command again.
DB21083E Section <section> not found.
Cause: Section <section> was not found in the db2cli.ini file.
Action: Specify an existing section and issue the command again.
DB21084E NEW and CONFIRM passwords not the same.
Cause: You were using the ATTACH or CONNECT command and specified that you wanted to change your password. The new password needs to be specified twice, by using the NEW and CONFIRM clauses, or by responding to the prompts. The two passwords you specified as your new password were different.
Action: Specify the same password twice.
DB21085I Instance "<instance_name>" uses DB2 code release "<rel_ver_mod>" with level identifier "<level_id>" and informational tokens "<build_id1>", "<build_id2>" and "<build_id3>".
Cause: This message is the output of the db2level command and provides detailed information about the code level of a given DB2 instance. The information may be request by DB2 service personnel to aid in resolving problems.
Action: Record all displayed information to provide to DB2 service personnel.
The db2level executable should not be copied from one machine to another. Only DB2 installation and service maintenance programs should manipulate this file.
The db2level executable will not display information about private test fixes that the customer has received from DB2 service personnel and installed on top of an officially supported service level.
DB21600N The "<command>" command did not complete successfully.
Cause: Errors were encountered during the execution of this command.
Action: Contact your technical service representative. Information in the db2diag.log file will enable your service representative to determine the cause of the failure.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books | Search the DB2 Books ]
Source: https://www.columbia.edu/sec/acis/db2/db2m0/db2db2.htm
0 Response to "Command Line Process Could Not Continue Processing"
Post a Comment