Messages Reference

SQL6000 - SQL6099

SQL6000N DB2 Conversion of QMF Data.

Cause: This is the normal termination message.

Action: No action is required.

SQL6001N The prefix for the filename was not specified.

Cause: The user executed a module of the SQLQMF facility directly rather than using the SQLQMF facility command.

The command cannot be processed.

Action: Use the provided SQLQMF facility command.

SQL6002N Communications Manager encountered a download error.

Cause: Communications Manager encountered an error during the download of the host file.

The command cannot be processed.

Action: Review the Communications Manager message log.

SQL6003N The file exported from QMF contains rows that are too long. The row length is "<number>".

Cause: The computed row size (the sum of the computed column sizes) exceeds the maximum of 7000 bytes.

The command cannot be processed.

Action: Return to your QMF host session and run a query with fewer data columns selected. EXPORT the data again and then try the SQLQMF facility command again.

SQL6004N "<function>" returned the unexpected return code "<code>".

Cause: An unexpected error occurred during processing. The Communications Manager or DB2 may not be installed or configured correctly.

The command cannot be processed.

Action: Ensure that Communications Manager has been installed and the appropriate host communications session is active. Retry the command after checking for other errors. If the problem persists, contact your Communications Manager system administrator.

SQL6005N An error occurred while reading the downloaded QMF file.

Cause: One of the following conditions was encountered:

The file could not be opened.
The end of file was encountered prematurely.
There was an I/O error while reading the file.

The command cannot be processed.

Action: Review the Communications Manager message log. Retry the command. If the error continues, contact your Communications Manager system administrator.

SQL6006N An error occurred while writing to an output file.

Cause: One of the following conditions was encountered:

Not enough space exists on the C: drive to write the data.
An output file could not be opened.
An I/O error occurred while writing the file.
An I/O error occurred while closing the file.
The file is in use by another OS/2 process.

DataJoiner users: there isn't enough space to hold the djxlink output. Additional space is required for the temporary files that djxlink creates and uses.

The command cannot be processed.

Action: Check for sufficient disk space on the C: drive. Retry the command.

DataJoiner users: increase the size of the file system where DataJoiner is installed. To estimate the amount of free space djxlink needs on an AIX operating system, enter:

     ls -e /usr/lpp/djx*/lib/libdb2euni.a

This command returns the number of bytes used by the listed file. Multiply that number by 3. The result is an estimate of how much free space is needed on the file system. Increase the size of the file system as necessary and retry the command.

SQL6007N The decimal number in row "<row>", column "<column>" cannot be converted to ASCII.

Cause: The indicated decimal field could not be converted.

The command cannot be processed.

Action: Verify that the host column data type is DECIMAL. Retry the QMF EXPORT and then try the SQLQMF facility command again. If the error continues, rerun the QMF query without the named column.

SQL6008N The file specified in the command is not in QMF data format.

Cause: The file specified by the filename parameter is not in the expected QMF format.

The command cannot be processed.

Action: Verify that you have typed the name correctly. If correct, return to your QMF host session and issue the command EXPORT DATA TO filename again. Be sure to export using the QMF data format.

SQL6009N The file exported from QMF contains Column "<name>" with a width "<width>" that is too long. The maximum column width is 4000 bytes.

Cause: The downloaded QMF file has a column width greater than 4000 bytes.

The command cannot be processed.

Action: Return to your QMF host session, rerun the QMF query without the named column, and export the data again. Then run the SQLQMF facility command again.

SQL6010N The downloaded QMF file has more than 255 data columns.

Cause: The file being processed has more than 255 data columns.

The command cannot be processed.

Action: Return to your QMF host session and rerun a query, selecting 255 or fewer data columns. EXPORT the data again and then run the SQLQMF facility command again.

SQL6011N The data type "<number>" ("<type-text>") of column "<name>" (positioned at column "<number>") cannot be processed.

Cause: The QMF file contains a column with data type that is not supported.

The SQLQMF facility does NOT support the following data types:

LONG VARCHAR
LONG VARGRAPHIC.

Only the SQLQMF facility SQLQMFDB supports graphic data types.

The command cannot be processed.

Action: Return to your QMF host session and rerun the query without selecting the named column. Then run the SQLQMF facility command again.

SQL6012N Too many parameters were specified for the command.

Cause: Too many parameters were specified with the command.

The command cannot be processed.

Action: Retry the command with the correct number of parameters.

SQL6013N Host filename "<host filename>" is either too long or does not begin with an alphabetic character.

Cause: The host filename does not begin with an alphabetic character; or, if the host is a VM System, the host filename, filetype, or filemode are too long.

The command cannot be processed.

Action: Retry the command with a correct host filename syntax.

SQL6014N Invalid command syntax, colon (':') should follow a keyword.

Cause: Keyword parameters with operands require the keyword to be immediately followed by a ":" character and then the operand.

The command cannot be processed.

Action: Verify the command syntax and retry the command.

SQL6015N The keyword is not recognized.

Cause: The keyword parameter indicator ("/") was followed by a value that is not a keyword.

The command cannot be processed.

Action: Retry the command using a different keyword value.

SQL6016N Too many operands for the System/370 filename "<name>".

Cause: If the host is a VM System, the host file name contains more than three space-separate tokens. If the host is an MVS System, the host filename contains embedded blanks.

The command cannot be processed.

Action: Retry the command using a different keyword value.

SQL6017N More information may be contained in the Import message log "<name>".

Cause: The database IMPORT operation terminated with warning or error messages.

The command has left its work files allocated.

Action: Use the message preceding this message and the IMPORT message log, if it exists, to decide if the IMPORT was successful and to determine corrective action. If the import was successful, erase the DEL, CRE, COL, and IML files.

SQL6018N No S/370 filename was specified.

Cause: The S/370 filename is a required parameter.

The command cannot be processed.

Action: Retry the command with a host filename.

SQL6019N Communications short session ID "<ID>" is either too long or is invalid.

Cause: The value provided for the communications short session ID is either longer than one byte or is not alphabetic.

The command cannot be processed.

Action: Retry the command with a valid value.

SQL6020N An import option was specified without also providing a database name.

Cause: No database name was provided and an import option was specified.

The command has terminated.

Action: Retry the command and include a database name.

SQL6021N Data was successfully imported.

Cause: This is a normal ending message when the SQLQMF facility imports data to a database.

Action: No action is required.

SQL6022N System database directory is not shared by all nodes.

Cause: All nodes should be accessing one physical copy of the system database directory.

The command cannot be processed.

Action: Ensure that all nodes are accessing the system database directory that resides in the sqllib directory, then try the request again.

SQL6023N The user does not have the authority to run the Get Table Partitioning Information utility on table "<name>".

Cause: The user attempted to retrieve partitioning information on the specified table without the appropriate authorization (either the SYSADM or DBADM authority or the CONTROL or SELECT privilege on the table).

The utility stops processing.

Action: Do not attempt to call the Get Table Partitioning Information utility without appropriate authorization. Contact your system administrator for assistance.

SQL6024N Table or index <name> is not defined on node <node-number>.

Cause: The application is connected to node "<node-number>", and the table or index "<name>" is not defined.

The cause is one of the following:

The node to which the application is connected is not a member of the nodegroup in which the table or index was created.
The node is not in use by that nodegroup.

The utility stops processing.

Action: Connect the application to a node on which the table or index is defined. Determine the nodegroup in which the table was created and obtain the list of nodes in the nodegroup by selecting the appropriate rows from the NODEGROUPDEF catalog view. The nodes whose IN_USE value is set to Y are the ones on which the table or index is defined.

SQL6025N Database backed up on node "<node1>" cannot be restored to node "<node2>".

Cause: The backup image used for the restore is a backup of the database on a different node.

Action: Ensure that you have the correct backup image for the node, then try the request again.

SQL6026N Database with catalog node "<node1>" cannot be restored to a database with catalog node "<node2>".

Cause: The catalog node can exist on only one node and there is a discrepancy between the backup image and the node being restored to. This can occur in the following cases:

The backup image specified catalog node "<node1>" and the restore was attempted on an existing database whose catalog node is node "<node2>".
The restore was attempted to a new database and the catalog node has not been restored first. (Restore the catalog node first to create the database on all nodes).

Action: Verify that the correct backup image is being restored.

If you are restoring to an existing database and want to change the catalog node to "<node2>", the existing database must be dropped first.

If you are restoring to a new database, restore the catalog node "<node1>" first.

SQL6027N The path "<path>" for the database directory is not valid.

Cause: The path "<path>" specified for either the CREATE DATABASE or the CATALOG DATABASE command starts with the character '.' or contains the character string '/.'.

The command cannot be processed.

Action: Ensure that the specified path is a fully qualified path, does not start with the character '.', and does not contain the character string '/.'. Then try the request again.

SQL6028N Catalog database failed because database "<dbname>" was not found in the local database directory.

Cause: When cataloguing a local database into the system database directory, the command/API has to be issued from a node on the server where the database resides.

Action: Reissue the command/API from a node where the database resides.

SQL6030N START or STOP DATABASE MANAGER failed. Reason code "<reason-code>".

Cause: The reason code indicates the error. The statement cannot be processed.

(1): Cannot access the sqllib directory of the instance.
(2): The full path name added to the profile filename is too long.
(3): Cannot open the profile file.
(4): The nodenum parameter value is not defined in the db2nodes.cfg file in the sqllib directory.
(5): The nodenum parameter must be specified when a command option is specified.
(6): The port parameter value is not valid.
(7): The new couple hostname/port is not unique.
(8): The FORCE option cannot be specified when the NODENUM option is specified.
(9): The hostname and port parameters must be specified when using the ADDNODE option.
(10): Cannot update the db2nodes.cfg file in the sqllib directory for the ADDNODE or RESTART option.
(11): The hostname parameter value is not valid.
(12): The pointer to the sqledbstrtopt or sqledbstopopt structure is not valid.
(13): No port value is defined for your DB2 instance id (/etc/services file on UNIX-based systems).
(14): The port value is not in the valid port range defined for your DB2 instance id (/etc/services file on UNIX-based systems).
(15): A hostname value has no corresponding port 0 defined in the db2nodes.cfg file in the sqllib directory.
(16): The value specified for the command or option parameter is not valid.
(17): The DROP option cannot be specified when the NODENUM option is not specified.
(18): The value specified for the callerac parameter is not valid.
(19): Unable to create the UNIX socket directory /tmp/db2_<version>_<release>/$DB2INSTANCE.
(20): The node number specified with the ADDNODE option already exists in the db2nodes.cfg file or the node has been already been added since the last stop database manager command was issued.
(21): The tablespace type specified with the ADDNODE option is not valid.
(22): The tablespace node specified with the ADDNODE option is out of range.
(23): The computer name parameter must be specified for the ADDNODE option.
(24): The user name parameter must be specified for the ADDNODE option.
(25): The computer name is not valid.
(26): The user name is not valid.
(27): The password is not valid.
(28): The password is expired.
(29): The user account specified is either disabled, expired, or restricted.

Action: The action corresponding to the reason code is:

(1): Ensure that the $DB2INSTANCE userid has the required permissions to access the sqllib directory of the instance.
(2): Change the profile name to a shorter name so that the total length of the fully qualified path added to the profile name length is smaller than the SQL_PROFILE_SZ defined in the file sqlenv.h.
(3): Ensure that the profile file exists.
(4): Ensure that the nodenum value specified is defined in the db2nodes.cfg file in the sqllib directory and is between 0 and 999.
(5): Resubmit the command with the nodenum parameter specified.
(6): Ensure that the port value is between 0 and 999. If a value is not specified, the port value defaults to 0.
(7): Ensure that the new couple hostname/port is not already defined in the db2nodes.cfg file in the sqllib directory.
(8): Do not specify the FORCE option when you specify the NODENUM option.
(9): Ensure that the hostname and the port values are specified when you specify the ADDNODE option.
(10): Ensure that the $DB2INSTANCE username has write access to the sqllib directory of the instance, that there is sufficient disk space, and the file exists.
(11): Ensure that the specified hostname is defined on the system.
(12): Ensure that the pointer is not NULL and points to the sqledbstrtopt for the sqlepstr() API, or to the sqledbstopopt structure for the sqlepstp() API.
(13): Ensure that the services file (/etc/services on UNIX-based systems) contains an entry for your DB2 instance id.
(14): Ensure that you only use port values that are specified in the services file (/etc/services file on UNIX-based systems) for your instance.
(15): Ensure that all the hostname values have a port 0 defined in the db2nodes.cfg file in the sqllib directory including the restart option parameters.
(16): Ensure that the value specified for the option parameter is within the valid range.
(17): Specify the NODENUM option when you specify the DROP option.
(18): Ensure that the value specified for the callerac parameter is within the valid range.
(19): Check the permission of the /tmp filesystem to make sure all intermediate directories of /tmp/db2_<version>_<release>/$DB2INSTANCE can be created.
(20): Ensure that the correct node number is being specified. You must stop the database manager to update the db2nodes.cfg file with nodes that have been added to the system since the previous stop database manager command.
(21): Ensure that the value specified for the tablespace type is within the valid range.
(22): Ensure that the tablespace node value specified is defined in the db2nodes.cfg and is between 0 and 999.
(23): Specify the computer name of the system on which the new node is created using the COMPUTER option.
(24): Specify a valid domain account user name and password for the new node using the USER and PASSWORD options.
(25): Resubmit the command with a valid computer name.
(26): Resubmit the command with a valid user name.
(27): Resubmit the command with a valid password.
(28): Change/update the account password and resubmit the command.
(29): Resubmit the command with a valid user account.

SQL6031N Error in the db2nodes.cfg file at line number "<line>". Reason code "<reason code>".

Cause: The statement cannot be processed because of a problem with the db2nodes.cfg file, as indicated by the following reason codes:

(1): Cannot access the sqllib directory of the instance.
(2): The full path name added to the db2nodes.cfg filename is too long.
(3): Cannot open the db2nodes.cfg file in the sqllib directory.
(4): A syntax error exists at line "<line>" of the db2nodes.cfg file in the sqllib directory.
(5): The nodenum value at line "<line>" of the db2nodes.cfg file in the sqllib directory is not valid.
(6): The nodenum value at line "<line>" of the db2nodes.cfg file in the sqllib directory is out of sequence.
(7): The nodenum value at line "<line>" of the db2nodes.cfg file in the sqllib directory is not unique.
(8): The port value at line "<line>" of the db2nodes.cfg file in the sqllib directory is not valid.
(9): The hostname/port couple at line "<line>" of the db2nodes.cfg file in the sqllib directory is not unique.
(10): The hostname at line "<line>" of the db2nodes.cfg file in the sqllib directory is not valid.
(11): The port value at line "<line>" of the db2nodes.cfg file in the sqllib directory is not defined for your DB2 instance id in the services file (/etc/services on UNIX-based systems).
(12): The port value at line "<line>" of the db2nodes.cfg file in the sqllib directory is not in the valid port range defined for your DB2 instance id in the services file (/etc/services on UNIX-based systems).
(13): The hostname value at line "<line>" of the db2nodes.cfg file in the sqllib directory has no corresponding port 0.
(14): A db2nodes.cfg file with more than one entry exists, but the database manager configuration is not MPP.

Action: The action corresponding to the reason code is:

(1)

Ensure that the $DB2INSTANCE userid has the required permissions to access the sqllib directory of the instance.

(2)

Make the instance home directory path name shorter.

(3)

Ensure that the db2nodes.cfg file exists in the sqllib directory and is not empty.

(4)

Ensure that at least 2 values are defined per line in the db2nodes.cfg file and that the file does not contain blank lines.

(5)

Ensure that the nodenum value defined in the db2nodes.cfg file is between 0 and 999.

(6)

Ensure that all the nodenum values defined in the db2nodes.cfg file are in ascending order.

(7)

Ensure that each nodenum value defined in the db2nodes.cfg file is unique.

(8)

Ensure that the port value is between 0 and 999.

(9)

Ensure that the new couple hostname/port is not already defined in the db2nodes.cfg file.

(10)

Ensure the hostname value defined in db2nodes.cfg at line "<line>" is both defined on the system and operational.

(11)

Ensure that the services file (/etc/services on UNIX-based systems) contains an entry for your DB2 instance id.

(12)

Ensure that you only use port values that are specified in the services file (/etc/services file on UNIX-based systems) for your instance.

(13)

Ensure that the port value 0 has been defined for the corresponding hostname in the db2nodes.cfg file.

(14)

Perform one of the following actions:

Remove the db2nodes.cfg file.
Alter the db2nodes.cfg file to contain exactly one entry.
Install the DB2 Extended Enterprise Edition server.

SQL6032W Start command processing was attempted on "<total_number>" node(s). "<number_started>" node(s) were successfully started. "<number_already_started>" node(s) were already started. "<number_not_started>" node(s) could not be started.

Cause: The database manager did not start successfully on all the nodes. Not all of the data in the database may be accessible. Data on the nodes that started successfully or were already running is accessible.

Action: Check the log file created in the log directory of the sqllib directory for the instance to see which nodes did not start.

SQL6033W Stop command processing was attempted on "<total_number>" node(s). "<number_stopped>" node(s) were successfully stopped. "<number_already_stopped>" node(s) were already stopped. "<number_not_stopped>" node(s) could not be stopped.

Cause: The database manager did not stop successfully on all the nodes. The database manager is still active on the nodes that could not be stopped.

Action: Check the log file created in the log directory of the sqllib directory for the instance to see which nodes did not stop.

SQL6034W Node "<node>" is not being used by any databases.

Cause: During DROP NODE VERIFY processing, all databases are scanned to verify that this node does not exist in the nodegroups of any database, and that no event monitor is defined on this node.

Action: This node can now be removed from the system by issuing the 'db2stop drop nodenum <node>' command.

SQL6035W Node "<node>" is being used by database "<database>".

Cause: During DROP NODE VERIFY processing, databases are scanned to verify that this node does not exist in the nodegroups of any database, and that no event monitor is defined on this node. Node "<node>" is being used by database "<database>" and cannot be dropped.

Action: You must do the following before dropping the node:

Redistribute the data to remove it from the node using the REDISTRIBUTE NODEGROUP command. Use either the DROP NODE option of the REDISTRIBUTE NODEGROUP command or the ALTER NODEGROUP statement to drop the node from the nodegroup. This must be done for all nodegroups in which the node to be dropped is a member.
Drop any event monitors that are defined on the node.
Issue the 'db2stop drop nodenum <node>' command to drop the node.

SQL6036N START or STOP DATABASE MANAGER command is already in progress.

Cause: A START DATABASE MANAGER or a STOP DATABASE MANAGER command is already in progress on the system.

Action: Wait for the command in progress to complete, then try the request again.

SQL6037N START or STOP DATABASE MANAGER timeout value was reached.

Cause: The start_stop_time value defined in the database manager configuration was reached at the node. This value specifies the time, in minutes, in which a node must respond to a Start Database Manager, Stop Database Manager or Add Node command.

Action: Do the following:

Check the First Failure Service Log (db2diag.log) to see if an error message has been logged for the node which timed out. If an error has not been logged, and timeouts persist, you may need to increase the start_stop_time value specified in the database manager configuration file.
If the timeout occurred during a Start Database Manager command, you should issue a Stop Database Manager command for all nodes which timed out.
If the timeout occurred during a Stop Database Manager command, you should issue a Stop Database Manager command for all nodes which timed out or for all nodes. Any node which is already stopped will return with a message stating that the node is stopped.

SQL6038N No partitioning key is defined.

Cause: The user attempted to use the Get Row Partitioning Information utility without specifying a partitioning key.

The utility stops processing.

Action: Ensure that you specify a partitioning key, then try the request again.

SQL6039N Partitioning column "<column-number>" is currently defined as not nullable.

Cause: An attempt was made to assign a null value to partitioning column "<column-number>", which is not nullable.

The utility stops processing.

Action: Assign a non-null value or change the type of the partitioning column to be nullable.

SQL6040C No FCM buffers are available.

Cause: No FCM buffer is available.

The statement cannot be processed.

Action: Try the request again.

If the error persists, increase the number of FCM buffers (fcm_num_buffers) specified in the database manager configuration file, then try the request again.

sqlcode: -6040

sqlstate: 57011

SQL6041C No FCM connection entries are available.

Cause: No FCM connection entry is available.

The statement cannot be processed.

Action: Try the request again.

If the error persists, increase the number of FCM connection entries (fcm_num_connect) specified in the database manager configuration file, then try the request again.

sqlcode: -6041

sqlstate: 57011

SQL6042C No FCM message anchors are available.

Cause: No FCM message anchor is available.

The statement cannot be processed.

Action: Try the request again.

If the error persists, increase the number of FCM message anchors (fcm_num_anchors) specified in the database manager configuration file, then try the request again.

sqlcode: -6042

sqlstate: 57011

SQL6043C No FCM request blocks are available.

Cause: No FCM request block is available.

The statement cannot be processed.

Action: Try the request again.

If the error persists, increase the number of FCM request blocks (fcm_num_rqb) specified in the database manager configuration file, then try the request again.

sqlcode: -6043

sqlstate: 57011

SQL6044N The syntax of the string representation "<string>" with value of datatype "<datatype-value>" and length "<length>" is not correct.

Cause: The specified string cannot be recognized as the target datatype. (The Programming Reference contains information on datatypes.) Either the syntax is not valid or the value is out of range.

The utility stops processing.

Action: Ensure that the string representation or the datatype is correct, then try the request again.

SQL6045N The datatype "<datatype-value>" of length "<datatype-length>" is not supported.

Cause: The datatype and data length are not supported for a partitioning key.

The utility stops processing.

Action: See the Administration Guide for information about datatypes. See the API Reference for information about the Get Row Partitioning Information API.

SQL6046N Specified DROP NODE action is not valid.

Cause: The value specified for the action parameter of the DROP NODE command is not valid. Only the verify mode is supported for the DROP NODE command. The parameter must be set to the value SQL_DROPNODE_VERIFY.

The command cannot be processed.

Action: Ensure that the action is set to SQL_DROPNODE_VERIFY, then try the request again.

SQL6047N Nodegroup cannot be redistributed because table "<name>" does not have a partitioning key.

Cause: At least one table in the single-node nodegroup does not have a partitioning key. All tables in the single-node nodegroup must have a partitioning key before the nodegroup can be redistributed to a multiple-node nodegroup.

The operation was not performed.

Action: Use the ALTER TABLE command to specify partitioning keys for tables that do not have one. Then try the request again.

SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.

Cause: A TCP/IP communication error occurred while the START or STOP DATABASE MANAGER command was trying to establish connection with all the nodes defined in the sqllib/db2nodes.cfg file.

Action: Do the following:

Ensure that the node has the proper authorization defined in the .rhosts or the host.equiv files.
Ensure that the application is not using more than (500 + (1995 - 2 * total_number_of_nodes)) file descriptors at the same time.
Ensure all the DB2 Extended Enterprise Edition environment variables are defined in the profile file.
Ensure the profile file is written in the Korn Shell script format.
Ensure that all the host names defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.

SQL6049N The log control file for database "<name>" could not be found on node(s) "<node-list>".

Cause: The SQLOGCTL.LFH file for the database is not in the database directory on the specified node(s).

The database was not started.

If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.

Action: Either restore the database from a backup on the specified node(s), or re-create the database.

SQL6050N An I/O error occurred while accessing the log control file for database "<name>" on node(s) "<node-list>".

Cause: An error occurred while accessing the SQLOGCTL.LFH file for the database on the specified node(s).

The database cannot be used.

If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.

Action: Either restore the database from a backup on the specified node(s), or re-create the database.

SQL6051N Database "<name>" is not configured for roll-forward recovery on node(s) "<node-list>".

Cause: The specified database is not configured for roll-forward recovery on the specified node(s).

The database is not rolled forward on all nodes.

If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.

Action: Ensure that recovery is required on the specified node(s), then restore the most recent backup version of the database on these nodes.

SQL6052N Cannot roll forward database "<name>" because it is not in roll-forward pending state on node(s) "<node list>".

Cause: The specified database is not in the roll-forward pending state on the specified node(s). This may be because the database has not been restored, or was restored with the WITHOUT ROLLING FORWARD option, or roll-forward recovery is complete on these nodes.

The database is not rolled forward.

If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.

Action: Do the following:

Ensure that recovery is required on the specified node(s).
Restore a backup version of the database on these nodes.
Issue the ROLLFORWARD DATABASE command.

SQL6053N Error exists in file "<file>". Reason code = "<reason-code>".

Cause: There is an error in the specified file as indicated by the reason code:

(1): The number of values in the partitioning map file is not 1 or 4,096.
(2): The number of values in the distribution file is not 4,096.
(3): The data in the distribution file is not in a valid format.
(4): The node number in the partitioning map is not between 0 and 999.
(5): The sum of all the values in the distribution file is greater than 4,294,967,295.
(6): The specified target partition map contains a node number that is not defined in SYSCAT.NODEGROUPDEF for the specified nodegroup.

Action: The action corresponding to the reason code is:

(1): Ensure that the partitioning map file contains only a single value (if the resultant nodegroup is a single-node nodegroup) or exactly 4,096 values (if the resultant nodegroup is a multinode nodegroup).
(2): Ensure that the distribution file contains exactly 4,096 values, one per hash partition.
(3): Ensure that the values in the distribution file are integers greater than or equal to 0, and that the sum of all the distribution values is less than or equal to 4,294,967,295.
(4): Ensure that the node numbers are in the range of greater than or equal to 0 and less than or equal to 999.
(5): Ensure that the sum of all the distribution values for the 4,096 partitions is less than or equal to 4,294,967,295.
(6): Either issue ALTER NODEGROUP to add the missing node(s) or change the partitioning map file to exclude the node(s) not defined in sysibm.sysnodegroupdef.

SQL6054N The archive file "<name>" is not a valid log file for the database "<name>" on node "<node-number>".

Cause: An archive log file exists in the log directory on the specified node, but it is not valid.

The ROLLFORWARD DATABASE processing stops.

Action: To determine the correct archive log file, issue the ROLLFORWARD DATABASE command with the QUERY STATUS option. Move the correct archive log file to the database log directory or, if the database is in a consistent state, change the log path to point to the correct archive file and issue the ROLLFORWARD DATABASE command again.

SQL6055N The archive file "<name>" does not belong to database "<name>" on node "<node-number>".

Cause: An archive log file in the log directory on the specified node does not belong to the specified database.

The ROLLFORWARD DATABASE processing stops.

SQL6056N Nodegroup cannot be redistributed. Reason code = "<reason-code>".

Cause: The operation cannot be executed. The reason code indicates the error.

(1): The nodegroup specification is not legal. The resulting nodegroup after redistribution would not contain any nodes.
(2): A previous redistribution operation did not complete successfully.
(3): A redistribution operation is already in progress.
(4): There is no previously aborted redistribution command to CONTINUE or ROLLBACK.
(5): No data redistribution is performed because the data in the nodegroup is already distributed as specified.
(6): The REDISTRIBUTE NODEGROUP command was not submitted from the catalog node.
(7): The REDISTRIBUTE NODEGROUP command is not available nor applicable in this non-partitioned version of the product.

Action: The action corresponding to the reason code is:

(1): Do not drop all the nodes of the nodegroup during redistribution.
(2): Identify why the previous redistribution failed and take the required corrective action. Submit the REDISTRIBUTE NODEGROUP command using either the CONTINUE or ROLLBACK option. CONTINUE will complete the previously aborted redistribution operation and ROLLBACK will undo the effects of the previously aborted operation.
(3): Issue the next REDISTRIBUTION NODEGROUP command after the current one completes.
(4): You cannot invoke the CONTINUE or ROLLBACK option on a nodegroup that is not associated with a failed redistribution operation.
(5): Try using a different target partitioning map or distribution file. Otherwise, redistribution is not necessary.
(6): Issue the command again from the catalog node.
(7): Do not issue the REDISTRIBUTE NODEGROUP command using this version of the product.

SQL6057N Archive file "<name>" is not associated with the database "<name>" that was restored, or with the log file previously processed on node "<node-number>".

Cause: An archive log file is found in the log directory on the specified node, but does not belong to the specified database.

The ROLLFORWARD DATABASE processing stops.

SQL6058N Roll-forward recovery stopped because of error "<error>" while retrieving log file "<name>" for database "<name>" on node "<node-number>".

Cause: Roll-forward processing invokes the db2uexit to retrieve the log file for the database on the specified node. The error may have occurred in the db2uexit.

The ROLLFORWARD DATABASE processing stops.

Action: See the user exit documentation in the Administration Guide for a description of the error, and either resume or terminate the roll-forward recovery.

SQL6059N The point-in-time passed to the Rollforward utility must be greater than or equal to "<timestamp>", because database "<name>" on node(s) "<node-list>" contains information later than the specified time.

Cause: An advanced virtual timestamp is in the database backup.

If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.

Action: Do one of the following:

Issue the command again with a point-in-time that is greater than or equal to "<timestamp>".
Restore an earlier backup on node(s), then issue the ROLLFORWARD DATABASE command again.

SQL6061N Roll-forward recovery on database "<name>" cannot reach the specified stop point (end-of-log or point-in-time) because of missing log file(s) on node(s) "<node-list>".

Cause: The Rollforward Database utility cannot find the necessary log file(s) in the logpath.

Action: Do one of the following:

Use the ROLLFORWARD DATABASE command with the QUERY STATUS option to determine which log files are missing. When you find the log files, put them in the log path and resume forward recovery.
If you cannot find the missing log files, restore the database on all nodes, then do point-in-time recovery using a timestamp that is earlier than that of the earliest missing log file.

SQL6062N Roll-forward recovery on database "<name>" cannot complete because the log information on node(s) "<node-list>" does not match the corresponding record(s) on the catalog node.

Cause: The Rollforward utility processed all the log files found on each node, but the stop points on the specified nodes do not match the corresponding records on the catalog node. This can be caused by missing log files on either the catalog node or on the specified nodes, or the catalog node must be included in the list of nodes to be rolled forward.

The ROLLFORWARD DATABASE processing stops.

Action: Do one of the following:

Check if the catalog node needs to be rolled forward. If it does, submit the ROLLFORWARD command again and include the catalog node.
Use the ROLLFORWARD DATABASE command with the QUERY STATUS option to determine which log files are missing. When you find the log files, put them in the log path and resume forward recovery.
If you cannot find the missing log files, restore the database on all nodes, then do point-in-time recovery using a timestamp that is earlier than that of the earliest missing log file.

SQL6063N Roll-forward recovery on database "<name>" has stopped on node(s) "<node-list>" due to a change in log file size.

Cause: The Rollforward Database utility has stopped rolling forward because the log files have changed in size. It must be restarted to establish the new log file size.

If ",..." is displayed at the end of the node list, see the diagnostic log for the complete list of nodes.

Roll-forward recovery has stopped.

(Note : if you are using a partitioned database server, the node number(s) indicate which node(s) the error occurred on. Otherwise, it is not pertinent and should be ignored.)

Action: Reissue the ROLLFORWARD command to continue.

SQL6064N SQL error "<sqlcode>" occurred during data redistribution.

Cause: An error occurred during data redistribution.

The utility stops processing.

Action: Look at the SQLCODE (message number) in the message for more information. Make any required changes and try the request again.

SQL6065N An error occurred while writing to file "<file>".

Cause: One of the following conditions was encountered:

The file could not be opened.
An I/O error occurred while writing to the file.
An I/O error occurred while closing the file.

The command or the utility cannot be processed.

Action: Ensure that the file exists and that the file permissions allow write access. Try the command or the utility again.

SQL6067W ROLLFORWARD DATABASE QUERY STATUS command encountered sqlcode "<sqlcode>".

Cause: The ROLLFORWARD DATABASE QUERY STATUS command encountered an error with the sqlcode "<sqlcode>". The query might not be successful on some nodes for various reasons. The most severe error is indicated by "<sqlcode>". The roll-forward status is only returned for the successful nodes.

Action: Look up the sqlcode "<sqlcode>" in the DB2 Messages Reference, or online to determine the problems on the failed nodes. Take the required corrective actions, then continue the forward recovery on these nodes.

SQL6068W Rollforward operation was cancelled successfully. The database has to be restored on node(s) "<node-list>".

Cause: A Rollforward operation was cancelled before it successfully completed, and the database is left in an inconsistent state. The restore pending flag is on for the listed nodes.

If ",..." is displayed at the end of the node list, see the syslog file for the complete list of nodes.

Action: Restore the database on the listed nodes.

SQL6069N The ROLLFORWARD DATABASE command cannot be submitted on a non-catalog node.

Cause: The ROLLFORWARD DATABASE command is only accepted on the catalog node.

Action: Submit the command on the catalog node.

SQL6071N The requested operation cannot be processed because a new node has been added to the system. The system must be stopped and started again before the operation can be done.

Cause: One of the following:

The request was issued from the new node, and this node cannot communicate with other nodes.
A CREATE or DROP DATABASE operation was requested before all nodes were stopped and started again to include the new node.

Action: Issue db2stop to stop all the nodes. When all nodes are successfully stopped, issue db2start to start all the nodes, including the new node, then try the request again.

sqlcode: -6071

sqlstate: 57019

SQL6072N DB2START with the RESTART option cannot proceed because the specified node is already active.

Cause: The node specified for restart is already active on the system.

Action: If necessary, issue a DB2STOP specifying the node to stop and issue the DB2START command again to restart the node.

SQL6073N Add Node operation failed. SQLCODE = "<sqlcode>".

Cause: The Add Node operation failed with sqlcode "<sqlcode>".

Action: Check the message associated with the sqlcode that is returned in either the DB2 Messages Reference, or online.

Take any required corrective action, then try the request again.

SQL6074N Add Node operation failed because a Create or Drop Database operation is currently executing.

Cause: An Add Node operation cannot execute concurrently with a Create or Drop Database operation.

Action: Wait for the Create or Drop Database operation to complete, then try the request again.

SQL6075W The Start Database Manager operation successfully added the node. The node is not active until all nodes are stopped and started again.

Cause: The db2nodes.cfg file is not updated to include the new node until all nodes are simultaneously stopped by the STOP DATABASE MANAGER (db2stop) command. Until the file is updated, the existing nodes cannot communicate with the new node.

Action: Issue db2stop to stop all the nodes. When all nodes are successfully stopped, issue db2start to start all the nodes, including the new node.

SQL6076W Warning! This command will remove all database files on the node for this instance. Before continuing, ensure that there is no user data on this node by running the DROP NODE VERIFY command.

Cause: This procedure will remove all the database partitions from the specified node.

Action: Ensure that the DROP NODE VERIFY command was run before dropping this node. If using the API, ensure that the callerac parameter is specified correctly.

SQL6077W The db2stop DROP NODENUM procedure ended successfully, but could not remove all the files. See the file "<file>" for details.

Cause: The db2stop DROP NODENUM procedure ended successfully, but some user data files are still on the node.

Action: Information in "<file>" file will indicate the directory structure from which files could not be deleted.

SQL6078N The db2stop DROP NODENUM procedure could not update the database information for database "<dbname>".

Cause: The db2stop DROP NODENUM procedure could not access the catalog node for database "<dbname>".

Action: Try the request again. If the problem persists, contact your service representative.

SQL6079W The db2stop DROP NODENUM command was cancelled successfully.

Cause: The db2stop DROP NODENUM command was stopped before it began processing.

Action: None.

SQL6080W The Start Database Manager operation successfully added in the node, but no database partitions have been created on the node. The node is not active until all nodes are stopped and started again.

Cause: The db2nodes.cfg file is not updated to include the new node until all nodes are simultaneously stopped by the STOP DATABASE MANAGER (DB2STOP) command. Until the file is updated, the existing nodes cannot communicate with the new node.

Action: Issue DB2STOP to stop all the nodes. When all nodes are successfully stopped, issue DB2START to start all the nodes, including the new node. When all nodes are successfully started, the database system can be used.

SQL6081 A communication error caused a DB2STOP FORCE command to time out on this node.

Cause: A communication error occurred on one or more of the database nodes, causing the DB2STOP FORCE command to time out on the current node, or, DB2STOP FORCE terminated because a severe error occurred during FORCE on one or more nodes. Any node where the communication error occurred will receive the SQL6048N message.

Action: Do the following:

Correct the communication error on the node (or nodes) that received the SQL6048N message.
Issue a DB2START command and ensure that all nodes that received the SQL6048N message started successfully.
Issue the DB2STOP FORCE command again from any node.
Look at the db2diag.log file to find the error, correct it if possible, and reissue the DB2STOP FORCE command from any node.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]