SQL6000-7999
| SQL Message ID | Message | Explanation | User Response |
|---|---|---|---|
|
SQL6000N |
DB2 Conversion of QMF Data. |
This is the normal termination message. |
No action is required. |
|
SQL6001N |
The abend is not in Database Manager. |
The user executed a module of the SQLQMF facility directly rather than using the SQLQMF facility command. The command cannot be processed. |
Use the provided SQLQMF facility command. |
|
SQL6002N |
Both the program name and CS:IP parameters must be specified. |
Communications Manager encountered an error during the download of the host file. The command cannot be processed. |
Review the Communications Manager message log. |
|
SQL6003N |
The CS:IP parameter is not valid. |
The computed row size (the sum of the computed column sizes) exceeds the maximum of 7000 bytes. The command cannot be processed. |
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. |
An unexpected error occurred during processing. The Communications Manager or DB2 may not be installed or configured correctly. The command cannot be processed. |
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. |
One of the following conditions was encountered:
The command cannot be processed. |
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. |
One of the following conditions was encountered:
Federated system users: there isn't enough space to hold the db2djlink output. Additional space is required for the temporary files that db2djlink creates and uses. The command cannot be processed. |
Check for sufficient disk space on the C: drive. Retry the command. Federated system users: increase the size of the file system where the federated server is installed. To estimate the amount of free space db2djlink needs on an AIX operating system, enter:
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. |
The indicated decimal field could not be converted. The command cannot be processed. |
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. |
The file specified by the filename parameter is not in the expected QMF format. The command cannot be processed. |
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. |
The downloaded QMF file has a column width greater than 4000 bytes. The command cannot be processed. |
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. |
The file being processed has more than 255 data columns. The command cannot be processed. |
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. |
The QMF file contains a column with data type that is not supported. The SQLQMF facility does NOT support the following data types:
Only the SQLQMF facility SQLQMFDB supports graphic data types. The command cannot be processed. |
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. |
Too many parameters were specified with the command. The command cannot be processed. |
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. |
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. |
Retry the command with a correct host filename syntax. |
|
SQL6014N |
Invalid command syntax, colon (':') should follow a keyword. |
Keyword parameters with operands require the keyword to be immediately followed by a “:” character and then the operand. The command cannot be processed. |
Verify the command syntax and retry the command. |
|
SQL6015N |
The keyword is not recognized. |
The keyword parameter indicator (“/”) was followed by a value that is not a keyword. The command cannot be processed. |
Retry the command using a different keyword value. |
|
SQL6016N |
Too many operands for the System/370 filename name. |
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. |
Retry the command using a different keyword value. |
|
SQL6017N |
More information may be contained in the Import message log name. |
The database IMPORT operation terminated with warning or error messages. The command has left its work files allocated. |
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. |
The S/370 filename is a required parameter. The command cannot be processed. |
Retry the command with a host filename. |
|
SQL6019N |
Communications short session ID ID is either too long or is invalid. |
The value provided for the communications short session ID is either longer than one byte or is not alphabetic. The command cannot be processed. |
Retry the command with a valid value. |
|
SQL6020N |
An import option was specified without also providing a database name. |
No database name was provided and an import option was specified. The command has terminated. |
Retry the command and include a database name. |
|
SQL6021N |
Data was successfully imported. |
This is a normal ending message when the SQLQMF facility imports data to a database. |
No action is required. |
|
SQL6022N |
System database directory is not shared by all nodes. |
All nodes should be accessing one physical copy of the system database directory. The command cannot be processed. |
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. |
The user attempted to retrieve partitioning information on the specified table without the appropriate authorization (either the DBADM authority or the CONTROL or SELECT privilege on the table). The utility stops processing. |
Do not attempt to run the Get Table Partitioning Information utility without appropriate authorization. Contact your security administrator for assistance with authorization. |
|
SQL6024C |
Table or index name is not defined on node node-number. |
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 utility stops processing. |
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. |
The backup image used for the restore is a backup of the database on a different node. |
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. |
In an environment that is not a DB2 pureScale environment, 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:
|
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. |
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. |
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. |
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. |
Reissue the command/API from a node where the database resides. |
|
SQL6030N |
START or STOP DATABASE MANAGER failed. Reason code reason-code. |
The reason code indicates the error. The statement cannot be processed.
|
The action corresponding to the reason code is:
|
|
SQL6031N |
Error in the db2nodes.cfg file at line number line. Reason code reason-code. |
The statement cannot be processed because of a problem with the db2nodes.cfg file, as indicated by the following reason codes:
|
The action corresponding to the reason code is:
|
|
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. |
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. |
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. |
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. |
Check the log file created in the log directory of the sqllib directory for the instance to see which nodes did not stop. |
|
SQL6034W |
Database partition database-partition is not being used by any databases. |
During DROP DBPARTITIONNUM VERIFY processing, all databases are scanned to verify that this node does not exist in the database partition groups of any database, and that no event monitor is defined on this node. |
This node can now be removed from the system by issuing the 'db2stop drop dbpartitionnum <db-partition-number>' command. |
|
SQL6035W |
Database partition partition-name is being used by database database. |
During DROP DBPARTITIONNUM VERIFY processing, databases are scanned to verify that this database partition does not exist in the database partition groups of any database, and that no event monitor is defined on this database partition. Database partition partition-name is being used by database database and cannot be dropped. |
You must do the following before dropping the database partition:
|
|
SQL6036N |
START or STOP DATABASE MANAGER command is already in progress. |
A START DATABASE MANAGER or a STOP DATABASE MANAGER command is already in progress on the system. |
Wait for the command in progress to complete, then try the request again. |
|
SQL6037N |
START or STOP DATABASE MANAGER timeout value was reached. |
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. |
Do the following:
|
|
SQL6038N |
No partitioning key is defined. |
The user attempted to use the Get Row Partitioning Information utility without specifying a partitioning key. The utility stops processing. |
Ensure that you specify a partitioning key, then try the request again. |
|
SQL6039N |
Partitioning column column-number is currently defined as not nullable. |
An attempt was made to assign a null value to partitioning column column-number, which is not nullable. The utility stops processing. |
Assign a non-null value or change the type of the partitioning column to be nullable. |
|
SQL6040C |
No FCM buffers are available. |
No FCM buffer is available. The statement cannot be processed. |
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. If FCM_NUM_BUFFER is already set to automatic, you should also check the overall memory consumption on your system to determine if other applications are using inappropriate amounts of memory, and preventing the allocation of FCM buffers. sqlcode: -6040 sqlstate: 57011 |
|
SQL6041C |
No FCM connection entries are available. |
No FCM connection entry is available. FCM is unable to increase the number of connection entries automatically because the maximum value has been reached. The statement cannot be processed. |
Try the request again after other processes have freed up some of this resource. sqlcode: -6041 sqlstate: 57011 |
|
SQL6042C |
No FCM message anchors are available. |
No FCM message anchor is available. FCM is unable to increase the number of message anchors automatically because the maximum value has been reached. The statement cannot be processed. |
Try the request again after other processes have freed up some of this resource. sqlcode: -6042 sqlstate: 57011 |
|
SQL6043C |
No FCM request blocks are available. |
No FCM request block is available. FCM is unable to increase the number of request blocks automatically because the maximum value has been reached. The statement cannot be processed. |
Try the request again after other processes have freed up some of this resource. sqlcode: -6043 sqlstate: 57011 |
|
SQL6044N |
The syntax of the string representation string with value of datatype datatype-value and length length is not correct. |
The specified string cannot be recognized as the target data type. (The Application Development Guide contains information on data types.) Either the syntax is not valid or the value is out of range. The utility stops processing. |
Ensure that the string representation or the data type is correct, then try the request again. |
|
SQL6045N |
The datatype datatype-value of length datatype-length is not supported. |
The data type and data length are not supported for a partitioning key. The utility stops processing. |
See the Administration Guide for information about data types. See the API Reference for information about the Get Row Partitioning Information API. |
|
SQL6046N |
The sqledrpn API call failed because an invalid value was specified for the Action parameter. |
You can verify whether a database partition server is being used by a database by calling the sqledrpn API. The only supported value for the Action parameter of the sqledrpn API is "SQL_DROPNODE_VERIFY". This message is returned when the sqledrpn API is called and a value other than "SQL_DROPNODE_VERIFY" is specified for the Action parameter. |
Call the sqledrpn API again, specifying the value "SQL_DROPNODE_VERIFY" for the Action parameter. |
|
SQL6047N |
Database partition group cannot be redistributed because table name does not have a partitioning key. |
At least one table in the single-partition database partition does not have a partitioning key. All tables in the single-partition database must have a partitioning key before the database partition group can be redistributed to a multiple-partition database partition group. The operation was not performed. |
Use the ALTER TABLE statement to specify partitioning keys for tables that do not have one. Then try the request again. Alternatively, omit the tables that do not have partitioning keys by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command. |
|
SQL6048N |
A communication error occurred during START or STOP DATABASE MANAGER processing. |
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 including the new node you attempted to add. This message can also be returned when a password has expired. |
Do the following:
|
|
SQL6049N |
The log control file for database database-name could not be found on the following database partitions: database-partition-list. |
There are two log control files:
The database manager could find neither the primary log control file nor the secondary log control file for the specified database in the database directory on the the specified database partitions. The database was not started. If ",..." is displayed at the end of the database partition list, see the syslog file for the complete list of database partitions. |
Either restore the database from a backup on the specified database partitions or re-create the database. |
|
SQL6050N |
An I/O error occurred while accessing the log control file for database database-name on the following database partitions: database-partition-list. |
There are two log control files:
This error was returned because the database manager could access neither the primary log control file nor the secondary log control file for the specified database on the specified database parititions. If the database manager can access neither of the log control files, you cannot use the database. If ",..." is displayed at the end of the database partition list, see the syslog file for the complete list of database partitions. |
Either restore the database from a backup on the specified database partitions, or re-create the database. |
|
SQL6051N |
Database name is not configured for roll-forward recovery on node(s) node-list. |
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. |
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. |
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. |
Do the following:
|
|
SQL6053N |
Error exists in file file. Reason code = reason-code. |
There is an error in the specified file as indicated by the reason code:
|
Perform the action that corresponds to the reason code:
|
|
SQL6054N |
The archive file name is not a valid log file for the database name on node node-number. |
An archive log file exists in the log directory on the specified node, but it is not valid. The ROLLFORWARD DATABASE processing stops. |
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. |
An archive log file in the log directory on the specified node does not belong to the specified database. The ROLLFORWARD DATABASE processing stops. |
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. |
|
SQL6056N |
The redistribution operation was not performed. Reason code: reason-code. |
The operation cannot be executed. The reason code indicates the error.
|
Respond according to the reason code:
|
|
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. |
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. |
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. |
|
SQL6058N |
Roll-forward recovery stopped because of error error while retrieving log file name for database name on node node-number. |
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. |
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. |
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. |
Do one of the following:
|
|
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. |
The Rollforward Database utility cannot find the necessary log file(s) in the logpath. |
Do one of the following:
|
|
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. |
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. |
Do one of the following:
|
|
SQL6063N |
Roll-forward recovery on database name has stopped on node(s) node-list due to a change in log file size. |
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.) |
Reissue the ROLLFORWARD command to continue. |
|
SQL6064N |
SQL error sqlcode occurred during data redistribution. |
An error occurred during data redistribution. The utility stops processing. |
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. |
One of the following conditions was encountered:
The command or the utility cannot be processed. |
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. |
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. |
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. |
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. |
Restore the database on the listed nodes. |
|
SQL6069N |
The ROLLFORWARD DATABASE command cannot be submitted on a non-catalog node. |
The ROLLFORWARD DATABASE command is only accepted on the catalog node. |
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. |
One of the following:
|
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. |
The node specified for restart is already active on the system. |
If necessary, issue a DB2STOP specifying the node to stop and issue the DB2START command again to restart the node. |
|
SQL6073N |
An add or drop operation of a database partition or DB2 member failed. SQLCODE = sqlcode. Database name = database_name. |
The operation failed with the specified SQLCODE. |
Take any required corrective action, then try the request again. |
|
SQL6074N |
The database partition server, DB2 member or CF cannot be added or dropped because one or more commands, statements, or operations that are not compatible with the online add or drop operation are in progress. |
In a DB2 pureScale environment, one or more commands, statements, or operations are in progress that are not compatible with the add or drop member or CF operation. For restrictions, see the Topology changes related link. In a database partition environment, one or more commands, statements, or operations are in progress that are not compatible with the add or drop database partition server operation. The following instance-level commands are not compatible with the add or drop database partition server operation:
The following database-level commands or operations are not compatible with the add or drop database partition server operation:
The following table-space-level statements and operations are not compatible with the add or drop database partition server operation:
The following storage-group-level statements and operations are not compatible with the add or drop database partition server operation:
|
To respond to this error, perform the following steps:
sqlcode: -6074 sqlstate: 55072 |
|
SQL6075W |
The Start Database Manager operation successfully added the database partition server. The database partition server is not active until all database partition servers are stopped and started again. |
The db2nodes.cfg file is not updated to include the new database partition server until all database partition servers are simultaneously stopped by the STOP DATABASE MANAGER (db2stop) command. Until the file is updated, the existing database partition servers cannot communicate with the new one. |
Issue db2stop to stop all the database partition servers. When all database partitions are successfully stopped, issue db2start to start all the database partition servers, including the new one. |
|
SQL6076W |
If you continue, this command will remove all database files for the specified database partition from the current instance. Before continuing, ensure that the specified database partition is not in use. |
In a partitioned database environment, you can drop a database partition from the current database manager instance by using the STOP DATABASE MANAGER command with the DROP DBPARTITIONNUM parameter. Alternatively, you can drop a database partition from the current database manager instance by using the db2InstanceStop API and specifying SQLE_DROP with the iStopOption parameter of the db2StopOptionsStruct data structure. When SQLE_DROP is specified, you can configure whether the db2InstanceAPI should continue or terminate after this message is returned by using the iCallerac parameter. When the STOP DATABASE MANAGER command is executed, this message is printed, and you are prompted to confirm whether to continue the drop database partition operation. |
Before dropping a database partition, perform the following steps:
When calling the db2InstanceStop API, use the iCallerac parameter in the db2StopOptionsStruct data structure to cause the application to continue or terminate after this message. |
|
SQL6077W |
The db2stop DROP DBPARTITIONNUM procedure ended successfully, but could not remove all the files. See the file file for details. |
The db2stop DROP DBPARTITIONNUM procedure ended successfully, but some user data files are still on the node. |
Information in file file will indicate the directory structure from which files could not be deleted. |
|
SQL6078N |
The db2stop DROP DBPARTITIONNUM procedure could not update the database information for database dbname. |
The db2stop DROP DBPARTITIONNUM procedure could not access the catalog node for database dbname. |
Try the request again. If the problem persists, contact your service representative. |
|
SQL6079W |
The db2stop DROP DBPARTITIONNUM command was cancelled successfully. |
The db2stop DROP DBPARTITIONNUM command was stopped before it began processing. |
None. |
|
SQL6080W |
The Start Database Manager operation successfully added the database partition server, but no database partitions have been created on the database partition server. The database partition server is not active until all database partition servers are stopped and started again. |
The db2nodes.cfg file is not updated to include the new database partition server until all database partition servers are simultaneously stopped by the STOP DATABASE MANAGER (DB2STOP) command. Until the file is updated, the existing database partition server cannot communicate with the new database partition server. |
Issue DB2STOP to stop all the database partition servers. When all database partition servers are successfully stopped, issue DB2START to start them all, including the new database partition server. When all database partition servers are successfully started, the database system can be used. |
|
SQL6081N |
A communication error caused a DB2STOP FORCE command to time out on this node. |
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. |
Do the following:
|
|
SQL6100N |
The partitioning map in the data file and the partitioning map for the database are not the same. |
The data to be loaded has either not been partitioned, or was partitioned with a partitioning map other than the current one for the database partition group to which the table belongs. The data cannot be loaded. |
If the data was not partitioned, use the db2split program to partition the data, then load the partitioned data. If the data was partitioned, do one of the following:
|
|
SQL6101N |
This data file contains data for node node-1 but the Load utility is connected to node node-2. |
The data to be loaded is associated with a node number that differs from the node number of the node to which the application is connected. The data cannot be loaded. |
Either find the data file associated with this node and try the request again with that data file, or connect to the node associated with this data file and issue the request at that node. |
|
SQL6102W |
The parameter name is reserved for future use. Its value should be set to default-value. |
A parameter reserved for future capabilities has been set to a value that is not its default value. It should be set to the default value to ensure future compatibility. |
Ensure that the parameter name is set to the value, default-value, then try the request again. |
|
SQL6103C |
An unexpected utility error occurred. Reason code = reason-code. |
An unexpected utility error occurred. |
Record the message number (SQLCODE) and reason code in the message. If trace was active, invoke the Independent Trace Facility at the operating system command prompt. See the Administration Guide for information on how to use this facility. Then contact your technical service representative with the following information:
|
|
SQL6104N |
The load utility does not support the creation of indexes. |
The load utility does not support the creation of indexes, but the table to be loaded has at least one index defined on it. The index may have been explicitly created with the CREATE INDEX statement or implicitly created when a primary key was defined for the table. |
Drop all indexes defined on the table with the DROP INDEX statement. Drop the primary key with the ALTER TABLE statement. Resubmit the command. Use CREATE INDEX and ALTER TABLE as required to recreate indexes and primary key after the load completes successfully. |
|
SQL6105W |
The Load utility has completed processing. A Rollforward done to a point in time after the load will not succeed. Take a database backup now if database recoverability is required. |
No logging is done by the Load utility. If you try to roll forward with a backup made before the load, the operation will fail when it encounters references to the data that was loaded. |
To ensure database recoverability after the load, do a backup before the data is modified. |
|
SQL6106N |
The filetype modifier "NOHEADER" was specified, but the database partition group on which the table is defined is not a single-node database partition group. |
The data to be loaded was specified as having no header information. However the target table specified is not a single-node table. The data cannot be loaded. |
The data must be split using db2split, then loaded without the "NOHEADER" option. |
|
SQL6107N |
The partitioning key information in the data file is not correct. |
Either the data was not split with db2split or the db2split operation was not successful. |
Use the db2split program to partition the data and then try the request again with the partitioned data. If the insert-column option is being used, ensure that all of the partitioning columns are specified in the column list. If the problem persists, contact your technical service representative with the following information:
|
|
SQL6108N |
The number of partitioning keys defined in the data file header(number-1) does not match the number of partitioning keys defined for the table (number-2). |
The partitioning columns specified in the db2split configuration file were not correct. The data was not correctly split. |
Do the following:
|
|
SQL6109N |
Utility expected partitioning column column-name-1, but found partitioning column column-name-2. |
In the db2split configuration file:
|
Do the following:
|
|
SQL6110N |
Utility expected partitioning column type column-type-1 for column column-name-1, but the data file lists it as type column-type-2. |
The db2split configuration file is not correct. |
Do the following:
|
|
SQL6111N |
Cannot create a subdirectory under the path specified by newlogpath. |
When the newlogpath parameter is updated, the system attempts to create a subdirectory under the specified path using the node name as the name of the subdirectory. One of the following operating system errors prevented the creation of the subdirectory:
The requested change is not made. |
Do one of the following, then try the request again:
If the problem persists, see your system administrator. |
|
SQL6112N |
The configuration parameter was not updated because the resulting configuration parameter settings would not be valid. Reason code reason-code. |
You can configure database manager functionality and database functionality by using configuration parameters. There are requirements and restrictions for what values are valid for every configuration parameter. This message is returned when an update to a configuration parameter fails because the specified value would result in a conflict with one of those requirements or restrictions for the specified configuration parameter. The value of the runtime token reason-code indicates the problem with the requested update:
|
Respond to this message according to the reason code:
|
|
SQL6500W |
RESTARTCOUNT in the load command may cause some problems. |
Since multiple loading processes for the same table are completely independent, it is almost impossible to have an identical restartcount for those multiple loading processes. |
Please make sure you have the correct load command. |
|
SQL6501N |
Database name was not given in the load command. |
Database name has to be specified in the load command. |
Please specify the database name and rerun the command. |
|
SQL6502N |
The path name (parameter: data_path) for data file was not specified. |
If the input data file is remote, the file will be transferred locally. The path to the file on the remote machine must be supplied. |
Please specify the path name to the remote data file and rerun the command. |
|
SQL6504N |
There are errors in the output node list specification (parameter: outputnodes) in the configuration file. |
The output node list specification is not valid. |
Check the sample configuration file, correct your output node list specification, and rerun the command. |
|
SQL6505N |
There are errors in the partitioning database partition list specification (parameter: PARTITIONING_DBPARTNUMS) in the load command. |
The partitioning database partition list specification is not valid. |
Correct your partitioning database partition list specification, and rerun the command. |
|
SQL6506N |
The program failed to extract partitioning key information for table table-name from the system catalog table. |
Either the table is not defined, or it is not defined in an MPP environment. |
Make sure you have the table properly defined. |
|
SQL6507N |
Checking level (parameter: check_level) in the configuration file is not valid. |
Checking level (parameter: check_level) can be either CHECK or NOCHECK. The default is CHECK. |
Correct the parameter in the configuration file, and rerun the command. |
|
SQL6508N |
The program failed to create the output pipe for the ftp process. |
If input data files are remote, they will be transferred to a local pipe. If this local pipe already exists, the process will fail. |
Please ensure your working space is clean. |
|
SQL6509N |
The program failed to create input pipes for the partitioning agents. |
The program can not create temporary input pipes for the splitter processes. |
Please ensure your working space is clean. |
|
SQL6510N |
The program failed to create the temporary directory at local non-NFS space of partition partition-num. |
The program needs a temporary working directory at local non-NFS space of all partitioning and loading partitions. |
Please ensure your working space is clean. |
|
SQL6511N |
Load failed to create output for the partitioning agent at partition partition-num. |
The program can not create temporary output pipes for the partitioning agent at partition partition-num. |
Please ensure your working space is clean. |
|
SQL6512N |
Load failed to create input pipes for the merging agent at partition partition-num. |
The program can not create temporary input pipes for the merging agent at partition partition-num. |
Please ensure your working space is clean. |
|
SQL6513N |
Load failed to create the input pipe for the loading agent at partition partition-num. |
The program can not create temporary input pipe for the loading agent at partition partition-num. |
Please ensure your working space is clean. |
|
SQL6514N |
The program can not read the node configuration file: node-cfg-file. |
Either the file does not exist, or it is not readable. |
Please check the existence and permissions of the node configuration file. |
|
SQL6515N |
The program failed to find a load command in the configuration file. |
A CLP load command must be supplied in the configuration file. |
Please specify a CLP load command in the configuration file. |
|
SQL6516N |
The program failed to connect to database db-name. |
Either the database manager has not been started yet, or it encountered problems. |
Check your database manager status. |
|
SQL6517N |
Load failed to extract the partition list, where the table tbl-name is defined, from the system catalog table. |
Either the table is not defined, or it is not defined in an MPP environment. |
Check how the table was defined in the database. |
|
SQL6518N |
The record length (reclen in the load command) is not valid. |
Valid record is between 1 to 32768. |
Please correct the record length, and rerun the command. |
|
SQL6519N |
The mode (parameter: mode) mode in the configuration file is not valid. |
The running mode of this program can be: SPLIT_ONLY, LOAD_ONLY, SPLIT_AND_LOAD (default), or ANALYZE. |
Please correct the mode in the configuration file. |
|
SQL6520N |
The program failed to create output pipes for the process, which generates the header information for split file. |
The program can not create output pipes for the process, which generates the header information for split file. |
Please ensure your working space is clean. |
|
SQL6521N |
The configuration file cfg-file for this program doesn't exist. |
The program needs a configuration file. |
Please create a configuration file. |
|
SQL6522N |
The program found a path name for the input data files in the load command. |
Path name for input data files in the load command is not allowed. There is a separate parameter (data_path) for this purpose. |
Please correct the configuration file. |
|
SQL6523N |
The element partition-num in the partitioning database partition list (parameter: PARTITIONING_DBPARTNUMS) is not defined in the node configuration (db2nodes.cfg) file. |
All partitions in the partitioning database partition list must have an entry in the node configuration file. |
Please correct your partitioning database partition list. |
|
SQL6524N |
The element partition-num in the output partition list (parameter: OUTPUT_DBPARTNUMS) is not a member of the partition list where the table is defined. |
All partition in the output partition list must be members of the partition list where the table is defined. |
Please correct your output partition list. |
|
SQL6525N |
The program can not read the input data file file-name. |
Either the input data file was not found, or it is not readable. |
Please check the existence and permissions of the input data file. |
|
SQL6526N |
The program can not write in current working directory cwd. |
The current working directory is not writable. |
Please check the permission of current working directory. |
|
SQL6527N |
The partition where statistic data will be collected, (parameter: RUN_STAT_DBPARTNUM), is not a member of the output partition list. |
The partition where statistic data will be collected must be a member of the output partition list. |
Please correct the RUN_STAT_DBPARTNUM parameter. |
|
SQL6528N |
Record length was not specified in the load command. |
If the BINARYNUMERICS or PACKEDDECIMAL modifier is specified in the load command, record length (reclen) must be specified in the load command as well. |
Please correct the load command. |
|
SQL6529N |
The No Header option (noheader) was not specified in the load command. |
If a table is defined in a single node database partition group, the NOHEADER modifier must be specified in the load command. |
Please correct the load command. |
|
SQL6530N |
The data type of one partitioning key is float or double. |
If the input file is a non-binary data file, float or double columns can not be defined as partitioning key. |
Supply a binary data file, or change the definition of your table. |
|
SQL6531N |
The program failed to reset tablespace quiesce. |
There are probably on-going loading processes. Make sure all previous loading processes are completed before another AutoLoader session can be started. |
Check the processes status on your machine. |
|
SQL6532N |
A savecount in the load command can not be set to non-zero. |
The savecount in the load command can not be set to non-zero if there are multiple partitioning nodes, the mode is PARTITION_AND_LOAD, and the command is either a REPLACE INTO or INSERT INTO load command. |
Please correct the load command. |
|
SQL6533N |
A restartcount in the load command can not be set to non-zero. |
Because multiple partitioning nodes produce random order of records for loading process(es), using RESTART INTO with a restartcount can not guarantee a successful recovery. |
Please correct the load command. |
|
SQL6534N |
There is an error in the netrc file netrc-file. |
Either the .netrc file could not be found, or there is no entry for remote host machine, or the permissions of the file are not correct. |
Please check the existence and permission of the .netrc file. |
|
SQL6535N |
The mode PARTITION_ONLY or ANALYZE is not valid. |
If a table is defined in a single node database partition group, either partitioning or analyzing is not necessary. |
Please change the mode to LOAD_ONLY or PARTITION_AND_LOAD. |
|
SQL6536N |
The program progname failed to open file filename for reading. |
An AutoLoader process can not successfully open a file or pipe for reading. |
Please ensure everything is correct in the configuration file. |
|
SQL6537N |
The program progname failed to open file filename for writing. |
An AutoLoader process can not successfully open a file or pipe for writing. |
Please ensure everything is correct in the configuration file. |
|
SQL6538N |
Load failed to read the partitioned file partitioned-file. |
When Load is invoked in LOAD_ONLY mode, the input data file must have already been partitioned, and all partitioned files must be readable by the Load. |
Check whether or not the input data file has been partitioned, and the access permissions of the resulting partitioned files. |
|
SQL6539N |
There is at least one command in cmd-list not found in the working environment. |
The execution of this program depends on a number of common Unix commands. The process fails if any one of them is not available in the working environment. |
Make sure you have all necessary commands properly installed on your system. |
|
SQL6540N |
File type file-type specified in the load command is not valid. |
Valid file types are ASC (positional ASCII) or DEL (delimited ASCII). |
Correct the load command in the configuration file. |
|
SQL6550N |
The partitioning map file map-file-name could not be opened for writing. |
The file name and path for the partitioning map could not be opened. An error occurred. |
Confirm that the partitioning map file name and file path were specified correctly and that the file can be opened for writing. |
|
SQL6551N |
An error occurred while attempting to write to the partition map file. |
A filesystem error occurred when writing to the partitioning map file. |
Check that the file path is correct, and that the target device has sufficient space to hold the partitioning map output. |
|
SQL6552N |
An error occurred while attempting to open a temporary configuration file filename for writing. |
The file name and path for a temporary file could not be opened. An error occurred. |
Confirm that the utility temporary file storage path was specified correctly and that the path allows for files to be opened for writing. |
|
SQL6553N |
An error occurred while attempting to write to a temporary configuration file filename. |
A filesystem error occurred when writing to a temporary file. |
Check that the file path is correct, and that the target device has sufficient space for the file data. |
|
SQL6554N |
An error occurred when attempting to remotely execute a process. |
The utility attempted to start a child process on a different database partition, but an error occurred. |
|
|
SQL6555N |
The load utility encountered an unexpected communications error. |
The utility encountered an error attempting one of the following operations:
|
|
|
SQL6556W |
An incomplete record was detected at the end of file filename. |
An incomplete data record was found at the end of a data file provided to the utility by the user. |
Examine the source data for syntactical correctness. |
|
SQL6557N |
Failed to retrieve the default node number. |
The utility attempted to determine a default node number, but was unable to. |
State source and target node numbers explicitly in the utility configuration file, or contact DB2 Service for assistance. |
|
SQL6558N |
The utility failed to determine the current working directory and/or drive. |
The utility attempted to determine the current working directory and/or drive but encountered an error. |
Contact DB2 Service for assistance. |
|
SQL6559N |
An invalid command line option was provided to the AutoLoader utility. |
The user specified a command line option for the AutoLoader utility which is either not supported, or obsolete. |
Refer to the AutoLoader documentation, or online help, for the supported options and features. |
|
SQL6560N |
Node node-number which is an execution node for partitioning does not appear in the db2nodes.cfg file. |
A node specified as an execution node for partitioning does not appear to be a member in the db2nodes.cfg file. The work intended to complete on this node can not be started. |
Add the node to the node list definition in the db2nodes.cfg file, or specify an alternate node for the partition operation which is a member of the node configuration. |
|
SQL6561N |
Target node node-number for load does not appear in the database partition group. |
A node was specified as a target node for loading, but this node is apparently not a member of the node group being loaded. |
Check the database partition group definition and confirm that the target node specified for loading is part of this database partition group. If the node is not part of the database partition group correct the utility target node specification to include the correct list of nodes. If the node is part of the database partition group, please contact DB2 Service for assistance. |
|
SQL6562N |
The utility is unable to retrieve the instance name. |
The utility attempted to retrieve the instance name but encountered an error. |
Confirm that the utility is running on a node with database product installed, and a valid instance is running. For additional help, please contact DB2 Service. |
|
SQL6563N |
Failed to retrieve the current user ID. |
The utility attempted to retrieve the current user ID for the ID, but an error was encountered. |
Contact DB2 Service. |
|
SQL6564N |
The password supplied is not valid. |
The user supplied an explicit password to the utility, but the password is not valid. |
Supply a valid password. |
|
SQL6565I |
Usage: db2xxld [-config config-file] [-restart] [-terminate] [-help] |
The AutoLoader configuration file is a user supplied file which contains the LOAD command to be executed, the target database, and several optional parameters that the user may specify. The sample configuration file, 'AutoLoader.cfg', supplied in the samples directory contains inline comments which describe the available options and their defaults. When running this program with '-restart' and '-terminate' option, user should not modify the configuration file from their last incomplete job. |
Refer to the documentation for further details about the AutoLoader utility. |
|
SQL6566N |
The LOAD command is missing from the AutoLoader configuration file. |
The LOAD command is missing from the AutoLoader configuration file. The parameter must be specified. |
Ensure that you have specified the correct configuration file for the AutoLoader, and that the LOAD command is specified inside. |
|
SQL6567N |
The option-name option appears multiple times in the AutoLoader configuration file. |
An option parameter was specified multiple times inside the AutoLoader configuration file. |
Correct the configuration file so that each option appears at most only once. |
|
SQL6568I |
The Load utility is now dispatching all request-type requests. |
The Load utility is now dispatching the request-type operation on each of the partitions. |
This is an informational message. |
|
SQL6569I |
The AutoLoader is now issuing all split requests. |
The AutoLoader is now issuing the split operation on each of the target split partitions. |
This is an informational message. |
|
SQL6570I |
The AutoLoader is waiting for all splitters to complete. |
The AutoLoader is waiting for all splitters to complete. |
This is an informational message. |
|
SQL6571I |
The Load utility is waiting for all operations to complete. |
The Load utility is waiting for operations to complete. |
This is an informational message. |
|
SQL6572I |
The LOAD operation has begun on partition node-number. |
The LOAD operation has begun on the specified partition. |
This is an informational message. |
|
SQL6573I |
The remote execution of the splitter utility on partition node-number finished with remote execution code code. |
The remote execution of the splitter utility on the specified partition has completed. |
This is an informational message. |
|
SQL6574I |
The utility has read MB-count megabytes from the source data. |
This information is generated periodically to provide status to the user on the progress of large Load jobs. |
This is an informational message. |
|
SQL6575I |
The utility has completed reading MB-count megabytes from the user data. |
This message is written at the completion of the Load to indicate the total volume of user data that has been processed. |
This is an informational message. |
|
SQL6576N |
The AutoLoader utility encountered a threading error. Reason code reason-code, return code ret-code. |
The following is an explanation of the reason code reason-code:
|
Ensure that you are running on an operating system which supports threaded applications, and that your thread limit per process is sufficient. The thread requirements are as follows:
|
|
SQL6577N |
The AutoLoader utility does not support the ROWCOUNT option in the load command. |
The ROWCOUNT option in the load command is not supported in the AutoLoader utility. |
Correct your load command in the AutoLoader configuration file, and resubmit your command. |
|
SQL6578N |
Invalid AutoLoader option. RESTART/TERMINATE option can only be specified with SPLIT_AND_LOAD or LOAD_ONLY mode. |
RESTART/TERMINATE option in AutoLoader can only work with SPLIT_AND_LOAD or LOAD_ONLY mode. |
Please check the AutoLoader configuration file or the autloader option flags. |
|
SQL6579N |
Invalid LOAD command in the AutoLoader configuration file. RESTART and TERMINATE options of the AutoLoader are used to perform LOAD RESTART and LOAD TERMINATE operation respectively. |
Users should not specify RESTART nor TERMINATE in the LOAD command. Instead, the RESTART and TERMINATE options of the AutoLoader should be used. |
Without modifying the AutoLoader configuration file, users should launch db2xxld with option RESTART or TERMINATE. |
|
SQL6580I |
LOAD is restarting on node node-num in phase restarting-phase. |
AutoLoader has acknowledged that LOAD is restarting in either LOAD/BUILD/DELETE phase. |
This is an informational message. |
|
SQL6581I |
Load cannot restart on node node-num. |
AutoLoader has acknowledged that LOAD cannot be restarted on a given node. |
This is an informational message. |
|
SQL6582I |
Restarting LOAD on node node-num is not required. |
AutoLoader has acknowledged that LOAD does not need to be restarted on a given node. |
This is an informational message. |
|
SQL6583N |
The partitioning key definition is incompatible with partitioned database load mode load-mode. |
An identity column was specified as part of the partitioning key definition, but the load mode specified was not PARTITION_AND_LOAD and the identityoverride modifier was not specified. |
Either change the load mode to PARTITION_AND_LOAD, specify the identityoverride modifier, or remove the identity column from the partitioning key definition. |
|
SQL7001N |
Unknown command command was requested. |
The command submitted to REXX could not be recognized. The command cannot be processed. |
Verify that the command is a valid SQL statement and rerun the procedure. Note that all commands must be in uppercase. |
|
SQL7002N |
The cursor name is invalid. |
The user specified an incorrect cursor name. The command cannot be processed. |
Verify that the cursor name is one of the form “c1” through “c100”. |
|
SQL7003N |
The statement name is invalid. |
The user has specified an incorrect statement name. The command cannot be processed. |
Verify that the statement name is of the form “s1” through “s100”. |
|
SQL7004N |
The syntax of the request is invalid. |
REXX was unable to parse the command string submitted. The command cannot be processed. |
Use proper command syntax. |
|
SQL7005W |
The cursor used by this OPEN statement has not been declared. |
An OPEN statement was attempted without a declaring a cursor. The command cannot be processed. |
Insert a DECLARE statement before the OPEN statement and rerun the procedure. |
|
SQL7006N |
Invalid keyword keyword given on request. |
The statement contains a not valid keyword keyword. The command cannot be processed. |
Specify the correct keyword format. |
|
SQL7007N |
REXX variable variable does not exist. |
A REXX variable that did not exist in the REXX variable pool was passed. The command cannot be processed. |
Verify that all variable names in the host-variable list are assigned before the command that failed. Then run the procedure again. |
|
SQL7008N |
REXX variable variable contains inconsistent data. |
A variable that contained inconsistent data was passed to REXX. The command cannot be processed. |
If the variable is an SQLDA, verify that the data and length fields have been assigned correctly. If it is a REXX variable, verify that the type of data is appropriate to the command where it is being used. |
|
SQL7009N |
Truncated REXX variable variable. |
The variable variable passed to REXX contained inconsistent data. The data string from variable was truncated. The command cannot be processed. |
Verify that the data length is consistent with the length given in the input SQLDA, and run the procedure again. |
|
SQL7010N |
Invalid scan ID ID. |
The scan ID variable passed to REXX did not exist or contained inconsistent or missing data. The command cannot be processed. |
Verify that the data contained in the scan ID has been assigned correctly, and run the procedure again. |
|
SQL7011N |
Required parameter parameter not given. |
The parameter parameter is required by REXX command syntax but was not specified. The command cannot be processed. |
Specify the required parameter value, and run the procedure again. |
|
SQL7012N |
Attempted ISL change while connected to a database. |
Isolation level (ISL) may not be changed while connected to a database. The command is ignored. |
If a change in isolation level is necessary, disconnect from the current database, then set the isolation level and connect to the database. |
|
SQL7013N |
Mismatched cursor and statement name or hold attribute. |
In REXX, the cursor and statement name form must be 'cnn' and 'snn,' where 'nn' is a number from 1 to 100. The numbers must be the same for a cursor and statement pair. Also, c1 through c50 are declared without hold and c51 through c100 with hold. The command is ignored. |
Verify that the cursor and statement numbers match and rerun the procedure. |
|
SQL7014N |
Incorrect number of host variable components. |
In REXX, the first component of a compound host variable lists a number which is not equal to the actual number of components defined. The command is ignored. |
Verify that the number in the first component matches the number of components actually defined and rerun the procedure. |
|
SQL7015N |
The variable name variable is not valid in REXX. |
The variable name specified is not valid in REXX. The name must conform to the language requirements. The command cannot be processed. |
Change the name to one that conforms to the REXX requirements and resubmit the command. |
|
SQL7016N |
Invalid syntax provided to the SQLDB2 interface. Related Error: db2-error. |
Invalid syntax was provided to the SQLDB2 interface, e.g. both an input file and a command were specified. |
Look up the related error code for more information. |
|
SQL7032N |
SQL procedure procedure-name not created. Diagnostic file is file-name. |
SQL Procedure procedure-name was not created. One of the following has occurred:
For UNIX platforms, the full path of the file that contains diagnostic information is: $DB2PATH/function/routine/sqlproc/ \ $DATABASE/$SCHEMA/tmp/file-name where $DATABASE represents the name of the database, and $SCHEMA represents the schema name of the SQL procedure. For Windows operating systems, the full path of the file that contains diagnostic information is: %DB2PATH%\function\routine\sqlproc\ \ %DATABASE%\%SCHEMA%\tmp\file-name where %DATABASE% represents the name of the database, and %SCHEMA% represents the schema name of the SQL procedure. |
Ensure that both a compatible C compiler and a DB2 Application Development Client are installed on the server. If a precompile or compile error occurred, refer to the messages from the precompiler or compiler in the diagnostic file file-name. Ensure that the DB2 registry variable DB2_SQLROUTINE_COMPILER_PATH is set to point to a script or batch file that sets up the C compiler environment. On a UNIX operating system, for example, you may create a script called “sr_cpath” in the /home/DB2INSTANCE/sqllib/function/routine directory. To set the DB2 registry variable DB2_SQL_ROUTINE_COMPILER_PATH accordingly, issue the following command:
sqlcode: -7032 sqlstate: 42904 |
|
SQL7035W |
The executable of the SQL procedure procedure-name is not saved in the database catalog. |
The executable of the SQL procedure exceeds the limit of 2 megabytes and therefore cannot be stored in the database catalog. It will not be recovered automatically at database restore time or on ROLLBACK of a DROP PROCEDURE statement. |
If the warning resulted from a CREATE PROCEDURE statement, ensure that you keep a backup of the executable associated with SQL procedure procedure-name. If the warning was issued during a restore operation or a ROLLBACK of a DROP PROCEDURE statement, then the executable associated with procedure-name must be manually synchronized with the SQL procedure that is defined in the catalog. sqlcode: +7035 sqlstate: 01645 |
|
SQL7099N |
Invalid error error has occurred. |
A REXX internal error has occurred. The command cannot be processed. |
Verify that REXX is installed properly and rerun the procedure. If the error continues, note the error number and call the dealer. |