Explanation

This is the normal termination message.

Explanation

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

The command cannot be processed.

Explanation

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

The command cannot be processed.

Explanation

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

The command cannot be processed.

Explanation

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

The command cannot be processed.

Explanation

The command cannot be processed.

Explanation

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.

Explanation

The indicated decimal field could not be converted.

The command cannot be processed.

Explanation

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

The command cannot be processed.

Explanation

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

The command cannot be processed.

Explanation

The file being processed has more than 255 data columns.

The command cannot be processed.

Explanation

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

Only the SQLQMF facility SQLQMFDB supports graphic data types.

The command cannot be processed.

Explanation

Too many parameters were specified with the command.

The command cannot be processed.

Explanation

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.

Explanation

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

The command cannot be processed.

Explanation

The keyword parameter indicator (“/”) was followed by a value that is not a keyword.

The command cannot be processed.

Explanation

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.

Explanation

The database IMPORT operation terminated with warning or error messages.

The command has left its work files allocated.

Explanation

The S/370 filename is a required parameter.

The command cannot be processed.

Explanation

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

The command cannot be processed.

Explanation

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

The command has terminated.

Explanation

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

Explanation

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

The command cannot be processed.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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:

• 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).

Explanation

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.

Explanation

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.

Explanation

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

This message is returned with reason code 4 for the following reasons:

• The specified value for DBPARTITIONNUM is not defined in the db2nodes.cfg file in the sqllib directory.
• The specified value for DBPARTITIONNUM or MEMBER is outside of the valid range. The valid range is: 0 - 999.
• The specified value for the db2iupdt command parameter -mid is outside of the valid range. The valid range is: 0 - 127.

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 QUIESCE option is specified.

9

The hostname and port parameters must be specified when using the ADD DBPARTITIONNUM option.

10

Cannot update the db2nodes.cfg file in the sqllib directory for the ADD DBPARTITIONNUM 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 database manager instance id (/etc/services file on UNIX-based systems).

14

The port value is not in the valid port range defined for your database manager 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_<ver>_<rel> /$DB2INSTANCE.

20

This message is returned with reason code 20 for the following reasons:

• The number specified with the ADD DBPARTITIONNUM option already exists in the db2nodes.cfg file or has been already been added since the last stop database manager command was issued.
• The member number specified with the db2iupdt command -mid parameter already exists in the db2nodes.cfg file

21

The tablespace type specified with the ADD DBPARTITIONNUM option is not valid.

22

The tablespace specified with the ADD DBPARTITIONNUM option is out of range.

23

The computer name parameter must be specified for the ADD DBPARTITIONNUM option.

24

The user name parameter must be specified for the ADD DBPARTITIONNUM 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.

31

The cluster interconnect netname parameter is not valid.

32

A database manager call to the cluster manager failed.

33

The identifier does not match the type that is defined in the db2nodes.cfg file in the sqllib directory.

34

The value specified for the QUIESCE option is not valid.

35

The member parameter must be specified when the QUIESCE option is used.

36

You can recover from a failed ADD or DROP operation in the DB2 pureScale environment using the db2iupdt command with the -fixtopology parameter. This reason code is returned when the db2iupdt command is called with the -fixtopology parameter but the cluster caching facility does not detect any failed ADD or DROP operations. Because there are no topology fixes required, when the db2iupdt utility tried to stop the database, the stop command failed.

37

The transport type of the new member or CF specified does not match the transport type used by existing members and CFs, as defined in the netname field in the db2nodes.cfg file.

38

Starting a DB2 member failed because of uDAPL configuration problems or uDAPL runtime errors.

39

The setting of CF_NUM_CONNS is not valid for the number of members in the cluster. This can happen if CF_NUM_CONNS is set to a fixed value that is too high.

40

Add member cannot be issued from a host that is not in the DB2 pureScale cluster.

41

An online add member operation cannot be performed on a host machine where a CF is currently running or where a CF is in the process of restarting.

42

A DB2 member or CF was not started because the /proc file system directory is not mounted on the host machine where the member or CF resides.

43

An online add CF operation cannot be performed on a host machine where a member is currently running or where a member is in the process of restarting.

Explanation

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 dbpartitionnum value at line line of the db2nodes.cfg file in the sqllib directory is not valid.

6

The dbpartitionnum value at line line of the db2nodes.cfg file in the sqllib directory is out of sequence.

7

The dbpartitionnum 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 database manager 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 database manager 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.

15

The computer name at line line of the db2nodes.cfg file in the sqllib directory is not valid.

16

The hostname at line line of the db2nodes.cfg file in the sqllib directory conflicts with the value of DB2FCMCOMM registry variable.

21

The type value at line line of the db2nodes.cfg file in the sqllib directory is not valid.

22

The instance defined in the db2nodes.cfg file in the sqllib directory is not a valid DB2 pureScale instance.

31

The cluster interconnect netname at line line of the db2nodes.cfg file in the sqllib directory is not valid.

32

The nodenum value at line X of the db2nodes.cfg exceeds the maximum member number specified by the FCM_MAX_MEMBERS_OVERRIDE setting on the DB2_FCM_SETTINGS registry variable.

33

The outbound port range is not defined for your database manager instance id in the services file (/etc/services on UNIX-based systems).

34

The nodenum value at line X of the db2nodes.cfg maps to a port outside the outbound port range defined for your database manager instance id in the services file (/etc/services on UNIX-based systems).

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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

The utility stops processing.

Explanation

An attempt was made to assign a null value to partitioning column column-number, which is not nullable.

The utility stops processing.

Explanation

No FCM buffer is available.

The statement cannot be processed.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

The data type and data length are not supported for a partitioning key.

The utility stops processing.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

There are two log control files:

• Primary log control file SQLOGCTL1.LFH
• Secondary log control file SQLOGCTL2.LFH

  The secondary log control file is a mirror copy of the primary log control file for use in the event that there is a problem with the primary log control file.

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.

Explanation

There are two log control files:

• Primary log control file SQLOGCTL1.LFH
• Secondary log control file SQLOGCTL2.LFH

  The secondary log control file is a mirror copy of the primary log control file for use in the event that there is a problem with the primary log control file.

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.

Explanation

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.

Explanation

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.

Explanation

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 32 768.

2

The number of values in the distribution file is not 32 768.

3

The data in the distribution file is not in a valid format.

4

The database partition 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 database partition number that is not defined in SYSCAT.DBPARTITIONGROUPDEF for the specified database partition group.

7

The specified target partition map is not valid.

Explanation

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

The ROLLFORWARD DATABASE processing stops.

Explanation

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

The ROLLFORWARD DATABASE processing stops.

Explanation

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

1

The database partition group specification is not legal. The resulting database partition group after redistribution would not contain any database partitions.

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 ABORT.

5

No data redistribution is performed because the data in the database partition group is already distributed as specified.

6

The REDISTRIBUTE DATABASE PARTITION GROUP command was not submitted from the catalog database partition.

7

The REDISTRIBUTE DATABASE PARTITION GROUP command is not available nor applicable in this non-partitioned version of the product.

8

Redistribution is not allowed if there are user temporary table spaces in the database partition group with existing created temporary tables or declared temporary tables.

9

The REDISTRIBUTE DATABASE PARTITION GROUP command is not allowed if there are table spaces in the database partition group with tables not in FULL access mode (ACCESS_MODE='F' in SYSCAT.TABLES).

10

The REDISTRIBUTE DATABASE PARTITION GROUP command is not allowed if there are table spaces in the database partition group with tables having attached partition (SYSCAT.DATAPARTITIONS.STATUS = 'A').

11

The REDISTRIBUTE DATABASE PARTITION GROUP command is not allowed if there are table spaces in the database partition group with tables having detached partitions and there are dependent tables that need to be incrementally maintained with respect to these detached partitions (SYSCAT.DATAPARTITIONS.STATUS = 'D').

12

The REDISTRIBUTE DATABASE PARTITION GROUP command is not allowed if there are table spaces in the database partition group with tables having detached partitions pending index cleanup (SYSCAT.DATAPARTITIONS.STATUS = 'I').

13

The REDISTRIBUTE DATABASE PARTITION GROUP command is not allowed if there are table spaces in the database partition group with tables in the set integrity pending state (SYSCAT.TABLES.STATUS='C').

14

The REDISTRIBUTE DATABASE PARTITION GROUP command is not allowed if there are MDC tables in the database partition group which contain rolled out blocks that are pending cleanup.

15

The NOT ROLLFORWARD RECOVERABLE keywords have not been specified in the REDISTRIBUTE DATABASE PARTITION GROUP command.

16

The REDISTRIBUTE DATABASE PARTITION GROUP command is not allowed if there are table spaces in the database partition group with tables having logically detached partitions (SYSCAT.DATAPARTITIONS.STATUS = 'L').

This reason code is returned when the ALTER TABLE statement was previously executed, specifying the DETACH PARTITION clause, against one or more of the tables in this database partition group and that asynchronous detach operation is not complete.

17

A restriction was encountered during an attempt to resolve a previously failed data redistribution operation:

• If you begin or continue a data redistribution operation and the operation fails, you may not subsequently abort the redistribute operation while any tables are in redistribute-pending state.
• If you abort a data redistribution operation and the operation fails during the abort, you may not subsequently continue the redistribute operation while any tables are in redistribute-pending state.

19

The operation could not be performed on the table because a dictionary for the table is currently being created in a background process.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.)

Explanation

An error occurred during data redistribution.

The utility stops processing.

Explanation

The command or the utility cannot be processed.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

Explanation

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

Explanation

The operation failed with the specified SQLCODE.

Explanation

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:

• QUIESCE INSTANCE
• UNQUIESCE INSTANCE
• STOP DATABASE MANAGER (db2stop)
• STOP DATABASER MANAGER DBPARTITIONNUM
• START DATABASE MANAGER (db2start)
• START DATABASE MANAGER DBPARTITIONNUM
• START DATABASE MANAGER with restart options

The following database-level commands or operations are not compatible with the add or drop database partition server operation:

• CREATE DATABASE
• DROP DATABASE
• QUIESCE DATABASE
• UNQUIESCE DATABASE
• ACTIVATE DATABASE
• DEACTIVATE DATABASE
• A Z lock on a database object
• A single-system view backup of all database partitions
• Restoring a database

The following table-space-level statements and operations are not compatible with the add or drop database partition server operation:

• CREATE TEMPORARY TABLESPACE
• Altering a temporary table space
• Dropping a temporary table space
• Updating automatic storage paths

The following storage-group-level statements and operations are not compatible with the add or drop database partition server operation:

• CREATE STOGROUP
• ALTER STOGROUP
• DROP STOGROUP
• RENAME STOGROUP

Explanation

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.

Explanation

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.

Explanation

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

Explanation

The db2stop DROP DBPARTITIONNUM procedure could not access the catalog node for database dbname.

Explanation

The db2stop DROP DBPARTITIONNUM command was stopped before it began processing.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

An unexpected utility error occurred.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

Either the data was not split with db2split or the db2split operation was not successful.

Explanation

The partitioning columns specified in the db2split configuration file were not correct. The data was not correctly split.

Explanation

Explanation

The db2split configuration file is not correct.

Explanation

The requested change is not made.

Explanation

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:

4

An attempt was made to update MAX_COORDAGENTS or MAX_CONNECTIONS to a value that would have caused these two configuration parameters to be incompatible with each other.

5

An attempt was made to set SSL_SVCENAME equal to the current value of SVCENAME, or to set SVCENAME equal to the current value of SSL_SVCENAME.

6

A value that is not a fully qualified path was specified for one of the following database manager configuration parameters:

• SSL_SVR_KEYDB
• SSL_SVR_STASH
• SSL_CLNT_KEYDB
• SSL_CLNT_STASH

7

An invalid value was specified for the database manager configuration parameter SSL_VERSIONS.

8

An invalid value was specified for the database manager configuration parameter SSL_CIPHERSPECS.

9

The procedure that was specified for the database configuration parameter CONNECT_PROC is not a valid connect procedure.

10

The string value that was specified for the database configuration parameter CONNECT_PROC is invalid for one of the following reasons:

• The string contains an invalid character
• The string does not include both the schema name and the procedure name like this: [schema-name].[procedure-name]

11

The requested update to the database configuration parameter CONNECT_PROC requires a connection to the database, but no database connection exists.

12

An attempt to update the CONNECT_PROC database configuration parameter failed because the DEFERRED parameter was specified with the UPDATE DATABASE CONFIGURATION command.

13

An attempt was made to update AUTHENTICATION or ALTERNATE_AUTH_ENC to a value that would have cause these two configuration parameters to be incompatible with each other.

14

An attempt was made to update the database configuration parameter ENCRLIB or ENCROPTS when not connected to the target database.

15

An attempt was made to update the database configuration parameter ENCRLIB or ENCROPTS by a user that does not have SECADM authority on the target database.

16

An attempt was made to update KEYSTORE_TYPE or KEYSTORE_LOCATION to a value that results in an incompatibility between these two configuration parameters.

17

An attempt was made to update AUTHENTICATION to an authentication type that requires encryption, but the encryption facility is not available.

18

An attempt to update the HADR_SSL_LABEL database configuration parameter failed because this feature is not supported in a DB2 pureScale environment.

Explanation

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.

Explanation

Database name has to be specified in the load command.

Explanation

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.

Explanation

The output node list specification is not valid.

Explanation

The partitioning database partition list specification is not valid.

Explanation

Either the table is not defined, or it is not defined in an MPP environment.

Explanation

Checking level (parameter: check_level) can be either CHECK or NOCHECK. The default is CHECK.

Explanation

If input data files are remote, they will be transferred to a local pipe. If this local pipe already exists, the process will fail.

Explanation

The program can not create temporary input pipes for the splitter processes.

Explanation

The program needs a temporary working directory at local non-NFS space of all partitioning and loading partitions.

Explanation

The program can not create temporary output pipes for the partitioning agent at partition partition-num.

Explanation

The program can not create temporary input pipes for the merging agent at partition partition-num.

Explanation

The program can not create temporary input pipe for the loading agent at partition partition-num.

Explanation

Either the file does not exist, or it is not readable.

Explanation

A CLP load command must be supplied in the configuration file.

Explanation

Either the database manager has not been started yet, or it encountered problems.

Explanation

Either the table is not defined, or it is not defined in an MPP environment.

Explanation

Valid record is between 1 to 32768.

Explanation

The running mode of this program can be: SPLIT_ONLY, LOAD_ONLY, SPLIT_AND_LOAD (default), or ANALYZE.

Explanation

The program can not create output pipes for the process, which generates the header information for split file.

Explanation

The program needs a configuration file.

Explanation

Path name for input data files in the load command is not allowed. There is a separate parameter (data_path) for this purpose.

Explanation

All partitions in the partitioning database partition list must have an entry in the node configuration file.

Explanation

All partition in the output partition list must be members of the partition list where the table is defined.

Explanation

Either the input data file was not found, or it is not readable.

Explanation

The current working directory is not writable.

Explanation

The partition where statistic data will be collected must be a member of the output partition list.

Explanation

If the BINARYNUMERICS or PACKEDDECIMAL modifier is specified in the load command, record length (reclen) must be specified in the load command as well.

Explanation

If a table is defined in a single node database partition group, the NOHEADER modifier must be specified in the load command.

Explanation

If the input file is a non-binary data file, float or double columns can not be defined as partitioning key.

Explanation

There are probably on-going loading processes. Make sure all previous loading processes are completed before another AutoLoader session can be started.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

If a table is defined in a single node database partition group, either partitioning or analyzing is not necessary.

Explanation

An AutoLoader process can not successfully open a file or pipe for reading.

Explanation

An AutoLoader process can not successfully open a file or pipe for writing.

Explanation

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.

Explanation

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.

Explanation

Valid file types are ASC (positional ASCII) or DEL (delimited ASCII).

Explanation

The file name and path for the partitioning map could not be opened. An error occurred.

Explanation

A filesystem error occurred when writing to the partitioning map file.

Explanation

The file name and path for a temporary file could not be opened. An error occurred.

Explanation

A filesystem error occurred when writing to a temporary file.

Explanation

The utility attempted to start a child process on a different database partition, but an error occurred.

Explanation

Explanation

An incomplete data record was found at the end of a data file provided to the utility by the user.

Explanation

The utility attempted to determine a default node number, but was unable to.

Explanation

The utility attempted to determine the current working directory and/or drive but encountered an error.

Explanation

The user specified a command line option for the AutoLoader utility which is either not supported, or obsolete.

Explanation

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.

Explanation

A node was specified as a target node for loading, but this node is apparently not a member of the node group being loaded.

Explanation

The utility attempted to retrieve the instance name but encountered an error.

Explanation

The utility attempted to retrieve the current user ID for the ID, but an error was encountered.

Explanation

The user supplied an explicit password to the utility, but the password is not valid.

Explanation

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.

Explanation

The LOAD command is missing from the AutoLoader configuration file. The parameter must be specified.

Explanation

An option parameter was specified multiple times inside the AutoLoader configuration file.

Explanation

The Load utility is now dispatching the request-type operation on each of the partitions.

Explanation

The AutoLoader is now issuing the split operation on each of the target split partitions.

Explanation

The AutoLoader is waiting for all splitters to complete.

Explanation

The Load utility is waiting for operations to complete.

Explanation

The LOAD operation has begun on the specified partition.

Explanation

The remote execution of the splitter utility on the specified partition has completed.

Explanation

This information is generated periodically to provide status to the user on the progress of large Load jobs.

Explanation

This message is written at the completion of the Load to indicate the total volume of user data that has been processed.

Explanation

Explanation

The ROWCOUNT option in the load command is not supported in the AutoLoader utility.

Explanation

RESTART/TERMINATE option in AutoLoader can only work with SPLIT_AND_LOAD or LOAD_ONLY mode.

Explanation

Users should not specify RESTART nor TERMINATE in the LOAD command. Instead, the RESTART and TERMINATE options of the AutoLoader should be used.

Explanation

AutoLoader has acknowledged that LOAD is restarting in either LOAD/BUILD/DELETE phase.

Explanation

AutoLoader has acknowledged that LOAD cannot be restarted on a given node.

Explanation

AutoLoader has acknowledged that LOAD does not need to be restarted on a given node.

Explanation

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.