SQL5000-5999

SQL5001N

authorization-ID does not have the authority to change the database manager configuration file.

The user attempted to update or reset the database manager configuration file without having SYSADM authority.

The requested change is not made.

Do not attempt to change the database manager configuration file without appropriate authorization. Contact a user with SYSADM authority if a change is required.

SQL5005C

The operation failed because the database manager failed to access either the database manager configuration file or the database configuration file.

The database product uses two types of configuration files:

Database manager configuration file

Created when a database manager instance is created, the database manager configuration file contains parameters that affect system resources at the instance level. There is also one database manager configuration file for each client installation, which contains information about the client enabler for a specific workstation. The database manager configuration file is named db2systm and is located in the instance directory.

Database configuration file

Created when a database is created, the database configuration file contains parameters that affect the use of that database. The database configuration file for each database is named SQLDBCONF, and stored along with other control files for that database in the directory named "SQLnnnnn" (where nnnnn is a number assigned when the database was created.)

This message is returned when a database utility (such as db2start, db2icrt, restore, or many others) requires that the database manager write to or read from either the database manager configuration file or the database configuration file, and the database manager was unable to access the configuration file.

There can be several reasons that the database manager was unable to access the configuration file, including the following reasons:

• After the database product installation has been upgraded or otherwise changed, some database applications are still trying to link to libraries from the previous installation
• After the database product installation has been upgraded or otherwise changed, operating system environment variables such as PATH, LIBPATH, or LD_LIBRARY_PATH still refer to paths from the previous installation
• The configuration file does not exist in the location where the database manager expects to find the file Operating system file permissions prevent the database manager from accessing the directory in which the configuration file is located
• Operating system file permissions prevent the database manager from writing to or reading from the configuration file or the directory in which the configuration file is located

In a DB2 pureScale environment, following a connect to database command, member database directory or database configuration file is not found or the member does not exist.

1. Determine the specific configuration file that the database manager attempted to access by reviewing diagnostic information in the db2diag log files.

   For example, search in the db2diag log files for the following strings:

   • SQLDBCONF
   • db2systm
2. Systematically eliminate possible reasons that the database manager was unable to access either the database manager configuration file or the database configuration file:
   • Ensure that operating system environment variables such as PATH, LIBPATH, and LD_LIBRARY_PATH include the correct paths for the current installation of the database product.
   • Locate the database manager configuration file and the database configuration files, and verify that the database manager has read and write permissions for the configuration files themselves as well as the directories in which those configuration files are located.

In a DB2 pureScale environment, either:

• Restore a database backup, or
• For members that do not exist re-create the configuration file by uncataloging the database and catalog the database again.

SQL5010N

The path name to the database manager configuration file is not valid.

An error occurred while determining the path for the database manager configuration file. The database manager directory structure may have been altered.

The command cannot be processed.

Resubmit the command. If the error continues, reinstall the database manager.

SQL5012N

Host variable host-variable is not an exact numeric data type.

The statement cannot be processed.

Change the host variable to be an exact numeric data type.

sqlcode: -5012

sqlstate: 42618

SQL5018N

The entry in the database manager configuration file for the maximum number of remote connections to the workstation (numrc) is not in the valid range.

The value for the maximum number of remote connections to the workstation must be between 1 and 255.

The requested change is not made.

Resubmit the command with a valid value for the maximum number of remote connections to the workstation.

SQL5020N

The entry in the database manager configuration file for the node name for the workstation (nname) is not valid.

The node name specified in the configuration command is not valid. The node name may be 1 to 8 characters. All the characters must be chosen from the database manager base character set.

The command cannot be processed.

Resubmit the command with a valid node name.

SQL5021N

The entry in the database manager configuration file for the index recreation parameter (INDEXREC) is not valid.

An invalid value was passed to Configuration Services for the Index Recreation parameter (INDEXREC) in the database manager configuration file. The invalid value may have been entered through the Command Line Processor or through a program API call. The valid values for the API call and for the command line processor are 1 (ACCESS), 2 (RESTART), 3 (RESTART_NO_REDO) and 4 (ACCESS_NO_REDO).

The update to the database manager configuration file is rejected.

Repeat the update request, entering one of the possible values.

SQL5022N

The entry in the database configuration file for the index recreation parameter (INDEXREC) is not valid.

An invalid value was passed to Configuration Services for the Index Recreation parameter (INDEXREC) in a database configuration file. The invalid value may have been entered through the Command Line Processor or through a program API call. The valid values for the API call and for the command line processor are 0 (SYSTEM), 1 (ACCESS), 2 (RESTART), 3 (RESTART_NO_REDO) and 4 (ACCESS_NO_REDO).

The update to the database configuration file is rejected.

Repeat the update request, entering one of the possible values.

SQL5025C

The database manager configuration file is not current.

The database manager configuration file has been updated since you connected to the database. It is not compatible with the configuration for the database to which you are connected.

No access is allowed to the database manager configuration file.

Wait until all applications disconnect from the databases. Issue the stop database manager command, and then issue the start database manager command.

If installing the sample database, drop it and install the sample database again.

SQL5030C

Command processing failed because of release number mismatch.

The release number in the database manager or database configuration file does not match the release number of the DB2 copy from which you issue the command.

If you are upgrading an instance or a database, the release number of the database manager or database is not supported for upgrade.

If you are updating an instance or a database, the release number of the database is not supported for update.

The command cannot be processed.

Verify that the release levels of your database or database manager and the DB2 copy from which you issue the command match:

• If you are upgrading an instance or a database:
  • The GET DBM CFG command to determine the release configuration parameter value of the database manager.
  • The db2level command to determine the release number of your DB2 copy.
• If you are updating an instance or a database:
  • The GET DB CFG command to determine the release configuration parameter value of the database.
  • The db2level command to determine the release number of your DB2 copy.
  • Consult the Db2 documentation for the minimum release level supported by your DB2 copy for update of a database.

If the release levels do not match, you can try one of the following actions:

• Issue the db2iupdt command to update the release level of the database manager.
• Restore the database from a backup.
• Follow the guidance in the Db2 documentation for updating the release level of a database.

If you are upgrading an instance or a database, the release number of the database or database manager is not supported for upgrade. You must upgrade to a release level that is supported for upgrade prior to upgrading to the release number of your Db2 copy.

If you are updating an instance or database, the release number of the database is not supported for update. You must update the release level of the database to a level that is supported for update prior to updating to the release number of your Db2 copy.

If the error occurred with the sample database, drop it and recreate it using the db2sampl command.

sqlcode: -5030

sqlstate: 58031

SQL5035N

The connection failed because the database product has been updated and the database needs to be upgraded

After you update the database product, sometimes databases must be upgraded before you can connect to them. This message is returned when the database product has been updated, and then an attempt is made to connect to a database that needs to be upgraded.

Issue the UPGRADE DATABASE command before attempting to access the database.

If you receive this message when you issued a database restore, drop the existing database before proceeding.

sqlcode: -5035

sqlstate: 55001

SQL5040N

One of the socket addresses required by the TCP/IP server support is being used by another process.

One of the socket addresses required by the server either is in use by another program, or has not been freed completely by the TCP/IP subsystem after the database manager has been stopped.

If you have just issued db2stop, wait for a couple of minutes so that the TCP/IP subsystem has enough time to clean up its resources. Otherwise, make sure no other programs on your workstation are using the port numbers reserved for your service name in the /etc/services file. The port number is a component of a socket address.

SQL5042N

One of the communication protocol server support processes failed to start up.

Due to system call failure, or a communication subsystem call failure, one of the communication protocol server support processes did not start up successfully.

SQL5043N

Support for one or more communications protocols specified in the DB2COMM environment variable failed to start successfully. However, core database manager functionality started successfully.

This message can be returned for the following types of reasons:

• Communication subsystem configuration error.
• Communication subsystem call failure.
• Database manager configuration error.
• System call failure.
• Database manager licensing error.
• Cluster manager call failure.

For example, one reason this message can be returned is that the SVCENAME database manager configuration parameter is not set correctly.

You can still connect to the server with communication protocols that did start successfully. Local clients can also connect to the server.

Perform the following troubleshooting steps:

• Verify that the SVCENAME database manager configuration parameter is set correctly by listing the settings for all database manager configuration parameters by using the following command:

  
  db2 get dbm cfg
  

• Look in the administration notification log for details on this error. The log will contain more information on the cause of the error and also which communication protocols did not start successfully.
• If the nicbinding.cfg file is in use, ensure that any specified host name or IP address is valid and that the port on any specified NICs is not owned by another process.

SQL5047C

Insufficient memory to execute this function.

There is not enough memory available to execute this function.

The function cannot be completed.

SQL5048N

The release level of the database client is not supported by the release level of the database server.

Database clients can only access database servers with a release level which is in the range of one level lower than the client to two levels higher than the client.

SQL5050C

The database manager encountered an error while processing the contents of the database manager configuration file.

The database manager configuration file, db2systm, is created when a database manager instance is created. The parameters in the database manager configuration file affect system resources at the instance level.

This message is returned when the database manager encounters an error reading information from or updating information in the database manager configuration file.

This error can be caused by different reasons, including the following examples:

• The database manager configuration file might have been altered by a text editor or a program other than the database manager.
• Environment variables (such as LIBPATH or LD_LIBRARY_PATH) might be set incorrectly, and that is preventing the database manager from finding the proper versions of libraries or other files.
• After the database product has been upgraded, processes (such as the monitoring process called kuddb2 or db2fmcd) or resources (such as old directories) that were associated with the previous version might be interfering with files the current database manager is accessing.

Perform one or more of the following troubleshooting steps:

• Verify that DB2 database-related environment variables are set correctly.
• Stop all database manager processes.
• Drop and recreate the database manager instance.
• Reinstall the database product.

SQL5051N

An object qualified by qualifier cannot be created in schema schema-name.

An object created in a CREATE SCHEMA statement is qualified by qualifier which is different from the schema name. All objects created in a CREATE SCHEMA statement must be either qualified by the schema name schema-name or not qualified. Unqualified objects are implicitly qualified by the schema name.

The statement cannot be processed.

Explicitly qualify the object in the schema with schema-name or remove qualifier from the object name.

sqlcode: -5051

sqlstate: 42875

SQL5055C

The content of the local or global database configuration file is not valid.

There is a database configuration file called SQLDBCONF. There can be two types of database configuration file:

• The global database configuration file in the partition-global directory contains configuration details that pertain to resources that must be consistent across the database.
• The local database configuration file in the DB2 member-specific directory contains configuration details that pertain to one DB2 member.

These database configuration files must not be altered by any programs other than the database manager.

This message is returned when either the global database configuration file or the DB2 member-specific database configuration file is invalid. This message can also be returned when there is an inconsistency between the global database configuration file and one or more of the DB2 member-specific database configuration files. The files might be invalid because they were altered by a text editor or a program other than the database manager.

Recreate the database or restore the database from a backup image.

sqlcode: -5055

sqlstate: 58031

SQL5060N

The configuration parameter token specified is invalid.

A token number specified in the sqlfupd structure passed to a Configuration Services API is not valid. It does not represent any of the supported configuration parameters. Alternatively, if an UPDATE was attempted, the token specified may be that of an unmodifiable configuration parameter.

Correct the sqlfupd structure and then rerun the program.

SQL5061N

An invalid pointer to structure sqlfupd was passed to Configuration Services.

The pointer to structure sqlfupd passed as a parameter to one of the Configuration Services APIs was invalid. It is either NULL, or does not point to an allocated block of memory of the size indicated by the count parameter.

Correct the code which invokes the Configuration Services API, and retry the API call.

SQL5062N

An invalid pointer was passed within the sqlfupd structure to Configuration Services.

The structure sqlfupd passed as a parameter to one of the Configuration Services APIs contained an invalid pointer. The pointer is either NULL, or does not point to an allocated block of memory. Each token passed in the structure must have a corresponding pointer to a field that is either passed in or out of the API.

Correct the code which invokes Configuration Services, and rerun the program.

SQL5065C

The nodetype value in the database manager configuration file is not valid.

The nodetype parameter in the database manager configuration file is not valid.

The command cannot be processed.

Reinstall the database manager.

SQL5066W

The database configuration parameter value for token token-name has been truncated.

The database configuration parameter value is larger than the specified token can contain.

A new token now represents this database configuration parameter value and should be used if the value is larger than can be contained by the old token.

Use the new token for this database configuration parameter.

SQL5070N

The count parameter in the configuration command is not valid. It must be greater than 0.

The count value passed as a parameter to a Configuration Services API must be greater than 0.

The command cannot be processed.

Correct the code which invokes Configuration Services, and rerun the program.

SQL5075N

The configuration utility was interrupted.

An interrupt was received by the configuration utility. The user may have pressed the interrupt key sequence.

The command was not processed. Any requested change is not made.

Resubmit the command.

SQL5076W

The update completed successfully. The current value of NOTIFYLEVEL will cause some health monitor notifications not to be issued to the notification log.

Health Monitor issues notifications to the notification log and to specified e-mail and page contacts. The current value of NOTIFYLEVEL is set too low to have notifications be issued for alarms and warnings. NOTIFYLEVEL must be set to 2 or higher for alarm notifications and 3 or higher for warning notifications.

Increase the value of the database manager configuration parameter NOTIFYLEVEL.

SQL5077N

The parameter parameter is not supported by the Configuration Advisor for this server release. Supported parameters include supported-parameters.

The parameter specified is not supported by this server release.

Reissue the command without the parameter or replace it with another supported parameter.

SQL5081N

The entry in the database configuration file for the size of the buffer pool (buffpage) is not in the valid range.

The minimum value for the size of the buffer pool is two times the maximum number of active processes (maxappls). The maximum value for the size of the buffer pool is 524288 (number of 4KB pages) and is operating system dependent. The maximum value under AIX is 51000 (204000 for Extended Server Edition) (4KB pages). Under HP-UX, the value must be between 16 and 150000 (4KB pages).

The requested change is not made.

Resubmit the command with a valid value for the size of the buffer pool.

SQL5083N

The entry in the database configuration file for the initial log file size (logfile) is not in the valid range.

The value for the initial log file size must be between 12 and (2**32 - 1).

The requested change is not made.

Resubmit the command with a valid value for the initial log file size.

SQL5091N

The entry in the database configuration file for the size of one log file extension (logext) is not in the valid range.

The value for the size of one log file extension must be between 4 and 256.

The requested change is not made.

Resubmit the command with a valid value for the size of one log file extension.

SQL5092N

The entry in the database configuration file for the maximum allowable number of log file extensions (logmaxext) is not in the valid range.

The value for the maximum allowable number of log file extensions must be between 0 and (2 * 10**6).

The requested change is not made.

Resubmit the command with a valid value for the maximum allowable number of log file extensions.

SQL5093N

The entry in the database manager configuration file for the size of the agent heap is not in the valid range.

The value for the size of the agent heap must be between 2 and 85.

The requested change is not made.

Resubmit the command with a valid value for the agent heap size.

SQL5098W

The default log file path has been changed to logfilepath.

The default log file path has been changed from the database directory to the global database directory.

Ensure that there is enough disk space in the new default log file path for the log files. If a disk or partition was mounted for the old default log file path, consider changing the mount point to the new default log file path.

SQL5099N

The value value indicated by the database configuration parameter parameter is not valid, reason code reason-code.

The value of the named parameter is not valid for one of the following reasons:

1

The path string is longer than 242 bytes.

2

The path does not exist.

3

The first directory in the path has a name in the form SQLNNNNN, where NNNNN is a value from 00001 to 99999.

4

A file with the correct name was found in the specified path, but is not a log file for this database.

5

The path is currently being used by another database.

6

The path is currently being used by the same database for another purpose.

7

The device specified by the path is not big enough to hold the log files.

8

A raw device cannot be specified as a NEWLOGPATH, MIRRORLOGPATH, OVERFLOWLOGPATH, FAILARCHPATH, LOGARCHMETH1, LOGARCHMETH2, or CTRL_FILE_RECOV_PATH.

9

The path cannot be accessed.

10

The path string is longer than 192 bytes.

11

When specifying DISK for a method, the target must be a directory.

12

When specifying VENDOR for a method, the target must be a directory.

13

LOGARCHMETH2 must be set to OFF if LOGARCHMETH1 is set to USEREXIT or LOGRETAIN.

14

When specifying DISK, VENDOR or DB2REMOTE, a valid target value must be specified.

15

A target value cannot be specified when setting the LOGARCHMETH1 configuration parameter to LOGRETAIN or USEREXIT.

16

Invalid method specified. Valid values include DISK, TSM, VENDOR, DB2REMOTE, USEREXIT, LOGRETAIN, and OFF.

17

Cannot switch to circular logging when database is rollforward pending.

19

The specified value for the configuration parameter is not valid. Neither USEREXIT nor LOGRETAIN are valid values for the database configuration parameter LOGARCHMETH2.

20

A remote storage path cannot be specified as a NEWLOGPATH, MIRRORLOGPATH, OVERFLOWLOGPATH, or FAILARCHPATH.

The requested change is not made.

Resubmit the command with a valid value for the named parameter.

sqlcode: -5099

sqlstate: 08004

SQL5100N

The entry in the database manager configuration file for the number of allowed concurrent databases is too large.

The requested change would cause (1) the number of allowed concurrent databases to be too large or (2) the number of segments allowed for the database manager to be too small.

segments >=
  ((number of databases * 5) + 1)

The requested change is not made.

SQL5102C

The edition-name edition of the product does not support the DB2 workload manager (WLM).

This edition of DB2 does not offer the WLM utility.

Purchase the license key for the DB2 Performance Optimization Feature from your IBM representative or authorized dealer. Then update your license using the db2licm command.

SQL5103N

The entry in the database configuration file for the size of the buffer pool (buffpage) is too small for the maximum number of active applications (maxappls).

  bufferpool_size >
    (number of active_processes * 2)

The requested change is not made.

SQL5104N

The statement failed because the data in HDFS cannot be mapped to the Hadoop table definition. Hadoop table name: table-name. Column index: column-index. Log entry identifier: log-entry-identifier. Reason: reason-string.

This error occurs when a statement is run against a Hadoop table and the data in HDFS cannot be mapped to the table definition. It also occurs when a statement runs against a Hadoop table and the input value cannot be mapped to HDFS. 

The token column-index specifies the ordinal position in the table definition of the column that is problematic (starting at 0 for the first column in the table). If the error relates to a partitioning column, "<column-index>" refers to the index of the column in the partitioning key definition.

The token "<log-entry-identifier>" identifies a log file that contains more information about the error that is returned. It is composed of three parts:

• A three-letter prefix that indicates which log file includes diagnostic details.
• A three-digit number that indicates on which database partition the log file resides.
• An identifier that is printed in the log file near the related diagnostic details.

1. Compare the data in HDFS with the table definition.
2. Change the data in HDFS or change the table definition so that the data in HDFS can be mapped to the table definition.
3. Run the statement again.

sqlcode: -5104

sqlstate: 530AC

Related information:

• LOG_ENTRY table function
• Data types

SQL5105N

The statement failed because a Big SQL component encountered an error. Component receiving the error: component-name. Component returning the error: component-name. Log entry identifier: log-entry-identifier. Reason: reason-string.

The statement failed because a Big SQL component or an open source component encountered an error. This message can be returned for many different scenarios and from many components.

The token log-entry-identifier identifies a log file that contains more information about the error that is returned. It is composed of three parts:

• A three-letter prefix that indicates which log file includes diagnostic details.
• A three-digit number that indicates on which database partition the log file resides.
• An identifier that is printed in the log file near the related diagnostic details.

The token reason-string provides a brief description of the issue and might help to identify the cause of the problem. This token might not always be returned.

1. Locate the diagnostic details in the appropriate log file by using the information in the log-entry-identifier runtime token.
2. Resolve the cause of the problem.
3. Submit the statement again.

sqlcode: -5105

sqlstate: 58040

Related information:

• LOG_ENTRY table function
• Overview of troubleshooting commands

SQL5106N

The statement failed because of a mismatch between meta data in the Hive metastore and the Hadoop table definition in the Big SQL catalog. Hadoop table name: table-name.

The meta data in the Big SQL catalog must be kept synchronized with the Hive metastore in order for objects in Hive to be available for Big SQL queries. Normally, this is done automatically, depending on the setting of the CATALOG_SYNC_MODE global variable.

This error is returned when there are changes to either the Hive metastore or the Big SQL catalog that cause them to become unsynchronized.

Synchronize the Hive metastore and the Big SQL catalog by using one of the following methods:

• Update the Big SQL catalog with information from the Hive metastore by using the HCAT_SYNC_OBJECTS procedure.
• Manually alter the Big SQL catalog by disabling automatic synchronizing with the CATALOG_SYNC_MODE variable and then issuing an ALTER TABLE statement.
• Cause the Big SQL catalog to be refreshed by using the HCAT_CACHE_SYNC function.

sqlcode: -5106

sqlstate: 530AD

Related information:

• CREATE TABLE statement

SQL5107N

A configuration file contains an invalid value for a property. Configuration file name: configuration-file-name. Property which has an invalid value: property.

You can configure components in your IBM InfoSphere BigInsights environment, such as the IBM Big SQL server, the Hadoop Distributed File System (HDFS), the IBM InfoSphere BigInsights Scheduler, or other components, by using configuration files. For example, you can configure IBM Big SQL server by using a configuration file called bigsql-conf.xml.

This message is returned when a component encounters an invalid configuration setting in the associated configuration file, given in the runtime token configuration-file-name.

Correct any invalid configuration properties in the given configuration file, and then synchronize the configuration of the component.

sqlcode: -5107

sqlstate: 560D9

SQL5108W

Loading of data to a Hadoop table or processing of data in an external table completed. Number of rows processed: processed-row-count. Number of source records: total-record-count. If the source was a file, number of skipped lines: line-count. Number of rejected source records: rejected-record-count. Job or file identifier: job-id.

You can issue a LOAD HADOOP statement to extract data from an external data source (such as a relational database or delimited file in an external or local file system) and load that data into a Hadoop table. You can issue SQL statements that reference an external table, which is based on a delimited file in an external or local file system.

When you do either of these things, the source data is processed one record at a time. This message is issued when data in at least one source record is invalid. Data is invalid when:

• The type of the data does not match the data type of the target column.
• The value of the data is not valid for the target column.
• The data is malformed.

If a record contains invalid data, the load utility or external table operation rejects the record.

If a LOAD HADOOP statement:

• Specifies the 'rejected.records.files.dir' property, rejected records are saved in the specified location
• Does not specify the 'rejected.records.files.dir' property, rejected records are saved in the bigsql.log log file

For an external table, a LOG file (containing information about the processing of the original statement) and a BAD file (containing the rejected records) are generated in the specified LOGDIR directory or in the default db2dump directory.

sqlcode: +5108

sqlstate: 01HN2

SQL5109N

The LOAD HADOOP statement was aborted and no data was loaded into the target table because the number of rejected source records exceeded the limit. Number of rejected source records: rejected-records-count. Rejection limit: rejected-records-limit. Job identifier:job-id.

You can extract data from external data sources, such relational databases or delimited files that are in an external or local file system, and load that data into a Hadoop table by using the LOAD HADOOP statement.

The source data is loaded one record at a time into the target table. If the data in a source record are invalid for the corresponding target columns, the load utility will reject the record. A value can be invalid for the corresponding target column for different reasons:

• The type of the data does not match the data type of the target column
• The value of the data is not valid for the target column
• The data is malformed

When a source record is rejected, the data in that record are not loaded into the target table:

• If the 'rejected.records.files.dir' property is specified with the LOAD HADOOP statement, rejected records are saved in the specified location.
• If the 'rejected.records.files.dir' property is not specified with the LOAD HADOOP statement, rejected records are saved in the bigsql.log log file.

This message is returned when the load operation fails and no data is loaded into the target table because too many source records were rejected:

• The number of rejected records exceeded the number that was specified with the 'max.rejected.records' property.
• The number of rejected records exceeded the default maximum number of rejected records allowed.

Details about rejected records are in the Hadoop task logs.

Resolve the reason that caused the records to be rejected and then perform the load operation again.

Optional: Increase the value given with the 'max.rejected.records' property.

sqlcode: -5109

sqlstate: 5U060

SQL5110N

The LOAD HADOOP statement was not processed because the load utility was unable to determine which column to use for splitting the source data.

You can extract data from external data sources, such relational databases or delimited files that are in an external or local file system, and load that data into a Hadoop table by using the LOAD HADOOP statement.

If the load utility is using more than one map task, the load utility distributes the work between the map tasks by splitting the source data into subsets and loading the data in parallel:

• If a column name is specified with the SPLIT COLUMN clause in the LOAD HADOOP statement, the load utility splits the data according to the specified column name.
• If the SPLIT COLUMN clause is not specified with the LOAD HADOOP statement, the load utility will attempt to select a column to split the source data:
  • If the source is an SQL query, the load utility will select one of the columns in the query.
  • If the source is a database table, the load utility will use the primary key of the source table.

This message is returned when the load utility cannot determine which column to use for splitting the source data.

To load the source data in parallel, specify which column to use for splitting the data in one of the following ways:

• Specify the SPLIT COLUMN clause in the LOAD HADOOP statement.
• If the source is a database table, define a primary key on the source table.

To load the data sequentially, set the 'num.map.tasks' property to 1.

sqlcode: -5110

sqlstate: 5U060

SQL5111N

The LOAD HADOOP statement failed because of an error with a component. Component name: component-name. Reason code: reason-code. Log entry identifier: log-entry-identifier. Job identifier: job-id.

You can extract data from external data sources, such relational databases or delimited files that are in an external or local file system, and load that data into a Hadoop table by using the LOAD HADOOP statement.

The reason code indicates the type of problem:

Reason code 1

Connection to the data source failed for one of the following reasons:

• Authentication failed for the given credentials
• The source database JDBC driver JAR files are not installed in the Sqoop directory

Reason code 2

The SQL query failed:

• If the FROM QUERY clause was specified, this message can be returned with reason code 2 if the specified query has a syntax error.
• If the FROM TABLE clause was specified, this message can be returned with reason code 2 when the load utility generates an invalid SQL query because of a problem with what was specified with the FROM TABLE clause:
  • The specified table name, or any column name is incorrect
  • The WHERE clause has a syntax error

Reason code 3

The data in the source does not match the target table definition.

Reason code 4

The job with identifier job-id failed to execute.

The log identifier in the token log-entry-identifier is composed of three parts:

1. A three-letter prefix that indicates which log file includes diagnostic details.
2. A three-digit number that indicates on which database partition the log file resides.
3. An identifier that is printed in the log file near the related diagnostic details.

Resolve the cause of the problem according to the reason code:

Reason code 1

• Correct the user or password in the URL string specified in the LOAD HADOOP statement.
• Copy the source database JDBC driver JAR files into the Sqoop directory.

Reason code 2

• If the FROM QUERY clause is being used, correct the syntax of the query.
• If the FROM TABLE clause is being used, correct the details specified: the table name, the column names, the WHERE clause.

Reason code 3

• Drop and recreate the target table to match the source data.
• Specify additional LOAD HADOOP options, such as the 'field.index' property, to map the source data to the target columns.

Reason code 4

Locate the diagnostic details in the appropriate log file by using the information in the log-entry-identifier runtime token, and then troubleshoot the cause of the failure.

sqlcode: -5111

sqlstate: 5U060

SQL5112N

The value of the configuration parameter parameter must be either 0 or 1.

The request is not completed because the value given for parameter is invalid.

Ensure that the value specified for parameter is either 0 or 1, then try the request again.

SQL5113N

ALT_COLLATE cannot be updated for a Unicode database.

The alternate collating sequence (ALT_COLLATE) database configuration parameter can only be updated for a non-Unicode database. In a Unicode database, all tables must be collated using the collating sequence specified when the database was created.

Do not update the ALT_COLLATE database configuration parameter for a Unicode database.

SQL5114N

The LOAD HADOOP statement was not processed because the specified source URL is invalid. Specified source URL: source-url.

You can extract data from external data sources, such relational databases or delimited files that are in an external or local file system, and load that data into a Hadoop table by using the LOAD HADOOP statement.

To load data from a file, you must specify a URL indicating the location of the file with the USING FILE clause in the LOAD HADOOP statement. The composition of the string that is specified as the URL must conform to one of four supported formats:

• FTP
• SFTP (secure FTP, enables using a credentials file)
• HDFS (for use with Hadoop Distributed File Systems)
• WEBHDFS (for use with remote HDFS sources)

This message is returned when a file URL is specified as a data source, and the specified URL does not conform to one of the supported formats.

Issue the LOAD HADOOP statement again, specifying a valid source URL.

sqlcode: -5114

sqlstate: 5U060

SQL5115N

The command or statement was not executed because the following functionality is not supported in the current environment: keyword.

In IBM Big SQL, there is a database manager underlying the SQL processing engine.

This message is returned when an attempt is made to perform an action directly against the database manager underlying the Big SQL processing engine, and that action is not supported in a Big SQL environment. The token keyword indicates which functionality is the source of the problem.

Remove the unsupported piece from the command or statement, and then issue the command or statement again.

SQL5120N

Old and new log parameters cannot both be modified at the same time.

The user is attempting to modify both the previous log parameters and the new parameters. The application should only support the parameters of the current release.

The request is denied.

Modify only the parameters of the current release and retry the command.

SQL5121N

The entry in the database configuration file for configuration options is not valid.

The value set for database options (SQLF_DETS) is not valid. Valid settings are between 0 and 15. The requested change is not made.

The requested change is not made.

Resubmit the command with a valid database options value.

SQL5122N

Access to the database was denied because of a machine dependent check.

The database and database configuration file cannot be accessed because of copy protection.

The user request is denied.

Have a user with SYSADM authority return to the original database, modify the configuration file to turn off the copy protection, and create a new backup, which can be used to restore the database. If the original database is no longer available, contact your service representative.

SQL5123N

Database name cannot be configured because an I/O error occurred while accessing the log control file.

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.

If the database manager can access neither of the log control files, you cannot use the database.

The requested change was not made.

Restore the database from a backup copy or recreate the database.

SQL5124N

DB2 failed to update or reset the database configuration on one or more partitions. Reason code reason-code.

DB2 uses fast communication manager (FCM) messages to broadcast an update or reset request. FCM communication can fail just after issuing the db2start command when it is not fully initialized.

Possible reason code values are:

1

The database configuration was not changed because the update or reset failed on at least one partition. See the db2diag log file for more details.

2

The database configuration is inconsistent among the nodes because the update or reset failed on at least one partition. See the db2diag log file for more details.

The user response corresponding to the reason code is as follows:

1

Make sure all partitions are up and running and resubmit the request.

2

Make sure all partitions are up and running. Resubmit the request or review the configuration updates and apply them manually on all partitions.

SQL5125N

The update operation on the global database configuration parameter parameter-name could not be applied on the specified member.

The values of global database configuration parameters are shared across an entire DB2 pureScale instance.

Global database configuration parameter values must be the same on all members. This error message is returned when an attempt is made to apply a value for a global database configuration parameter to a specific member using the UPDATE DB CFG command with the MEMBER clause.

Issue an update operation using the UPDATE DB CFG command without the MEMBER clause. This value applies to all members in the DB2 pureScale instance.

sqlcode: -5125

sqlstate: 5U053

SQL5126N

The UPDATE DATABASE MANAGER CONFIGURATION command failed because the specified database manager configuration parameter is not supported by the current instance node type. Database manager configuration parameter: parameter-name. Instance node type: instance-node-type.

Different database products are associated with different database manager instance node types. The current instance node type is indicated by the runtime token instance-node-type:

1

Database server with local and remote clients

2

Client

3

Database server with local clients

4

Partitioned database Server with local and remote clients

You can configure DB2 database functionality by setting database manager configuration parameters. Each instance node type supports only the database manager configuration parameters for the database products that are associated with that instance node type.

This message is returned when an attempt is made to update a database manager configuration parameter that is not supported by the current instance node type.

1. List the database manager configuration parameters that are supported by the current instance node type by using the GET DATABASE MANAGER CONFIGURATION command.
2. Perform one of the following actions:
   • Achieve the desired configuration by updating one or more database manager configuration parameters that are supported with the current instance node type.
   • If the functionality associated with the failed configuration attempt is supported by a different instance node type, update or upgrade the instance node type to a type that supports the functionality and then reissue the UPDATE DATABASE MANAGER CONFIGURATION command.

sqlcode: -5126

sqlstate: 5U001

SQL5130N

The value specified for the configuration parameter parameter is not in the valid range of start-of-range to end-of-range.

The request is not done because the value of parameter is not within the valid range.

Ensure that the value specified for parameter is within the valid range, then try the request again.

SQL5131N

The value specified for the configuration parameter parameter is not in the valid range. The valid range is "-1", or from start-of-range to end-of-range.

The request is not done because the value of parameter is not within the valid range.

Ensure that the value specified for parameter is within the valid range, then try the request again.

SQL5132N

The configuration parameter parameter is null or too long. The maximum length is maximum-length.

The configuration parameter is not set or too long.

Change the value of the configuration parameter to within the maximum length given.

SQL5133N

The configuration parameter was not updated because the specified value is not valid. Specified value: value. Configuration parameter name: parm.

You can configure the characteristics of your database manager instance or database by setting instance or database configuration parameters.

This message is returned when an attempt is made to set an instance configuration parameter or a database configuration parameter to an unsupported or invalid value.

Set the configuration parameter to a valid value.

SQL5134N

The configuration parameter tpname contains invalid characters.

Change the tpname and retry the command or function call.

SQL5135N

The settings of the maxlocks and maxappls configuration parameters do not use all of the locklist space.

maxappls * maxlocks >= 100

This ensures that all of the allocated locklist space can be used.

Increase the setting for maxappls, maxlocks, or both.

SQL5136N

The entry in the database manager configuration file for the default database path (dftdbpath) is invalid.

Change the dftdbpath and retry the command or function call.

SQL5137N

The entry in the database manager configuration file for the diagnostic directory path (diagpath) is invalid.

There are a number of reasons why the specified diagnostic directory path might be invalid:

• The specified path does not follow the supported operating system naming convention.
• The path does not exist.
• The path was set to the same path as the alternate diagnostic path.
• The path provided is read-only.

Change the diagpath and retry the command or function call.

SQL5138N

Diagnostic directory paths must contain at least one split-token in a Db2 pureScale environment.

In a Db2 purescale environment, the diagnostic directory path must be split using at least one of the following tokens:

• $h Resolves to HOST_hostname
• $n Resolves to NODEnumber
• $m Resolves to DIAGnumber. Note that DIAGnumber is used regardless of whether it refers to a database partition, a CF, or a member.

Add a split token to the diagpath and retry the command or function call.

Related information: DIAGPATH - Diagnostic data directory path

SQL5140N

The entry in the database manager configuration parameter "authentication" must be one of SERVER, CLIENT, DCE, KERBEROS, SERVER_ENCRYPT, DCE_SERVER_ENCRYPT, or KRB_SERVER_ENCRYPT.

The allowed values for the configuration parameter "authentication" are:

• SERVER = 0
• CLIENT = 1
• DCE = 3
• SERVER_ENCRYPT = 4
• DCE_SERVER_ENCRYPT = 5
• KERBEROS = 7
• KRB_SERVER_ENCRYPT = 8

The requested change is not made.

Resubmit the command with a valid value for "authentication".

SQL5141N

The configuration parameter avg_appls is out of range. The valid range is from 1 to the value of maxappls.

The allowable range for avg_appls is from 1 to the value of maxappls.

The requested change is not made.

SQL5142N

The configuration parameter agentpri is not in the valid range.

For example, the number 304 would correspond to a priority class of 3 (TIMECRITICAL), with a priority level of 4.

Change the value of the configuration parameter to a value within the valid range.

SQL5144W

The parameter update took effect but self tuning of the automatic parameters will not occur until the database configuration parameter SELF_TUNING_MEM is set to ON.

Self tuning of the AUTOMATIC memory parameters is not active when SELF_TUNING_MEM is set to OFF.

Update the database configuration parameter SELF_TUNING_MEM to ON to enable self tuning of the AUTOMATIC memory parameters.

SQL5145W

The parameter update took effect however tuning of the AUTOMATIC memory parameters was deactivated because an insufficient number of parameters or buffer pools are set to AUTOMATIC.

Self tuning of the AUTOMATIC memory parameters is active when 2 or more tunable parameters or buffer pools are set to AUTOMATIC and SELF_TUNING_MEM is ON. Self tuning was active but the configuration update caused its deactivation.

Self tuning of the AUTOMATIC memory parameters will resume when one or more tunable parameters or buffer pools are set to AUTOMATIC.

SQL5146W

Parameter_1 must be set to Parameter_3 when Parameter_2 is Parameter_3. Parameter_1 has been set to Parameter_3.

If Parameter_2 is AUTOMATIC then Parameter_1 must be set to AUTOMATIC as well. To this end, Parameter_1 was set to AUTOMATIC.

Parameter_1 was set to AUTOMATIC by DB2. To set this parameter to a different value, first set Parameter_2 to a value and then set Parameter_1 to a value using the MANUAL option of the db2 update database configuration command.

SQL5147N

Parameter_1 cannot be set to MANUAL if Parameter_2 is AUTOMATIC.

If Parameter_2 is AUTOMATIC then Parameter_1 needs to be AUTOMATIC as well.

To set Parameter_1 to another value, Parameter_2 must be set to a value other than AUTOMATIC first.

SQL5148W

The database configuration parameter config_param was successfully updated to AUTOMATIC but self tuning of config_param will not take effect until the database manager parameter SHEAPTHRES is set to 0.

Self tuning of the database configuration parameter config_param is only allowed when the database manager configuration parameter SHEAPTHRES is set to 0.

If you wish to enable self tuning of the database configuration parameter config_param set the database manager configuration parameter SHEAPTHRES to 0.

SQL5150N

The value specified for the configuration parameter parameter is less than the minimum allowable value of minimum-value.

The request is not completed because the value given for parameter is too low. parameter may not be less than minimum value

Ensure that the value specified for parameter is within the valid range, then try the request again.

SQL5151N

The value specified for the configuration parameter parameter is less than the minimum allowable value of minimum-value and is not -1.

The request is not completed because the value given for parameter is invalid. Except for an allowable value of -1, parameter may not be less than minimum value.

Ensure that the value specified for parameter is within the valid range, then try the request again.

SQL5152N

The value specified for the configuration parameter parameter is greater than the maximum allowable value of maximum-value.

The request is not completed because the value given for parameter is too high. parameter may not be greater than maximum value

Ensure that the value specified for parameter is within the valid range, then try the request again.

SQL5153N

The update cannot be completed because the following relationship would be violated: condition.

A valid configuration file must maintain the following relationship:

condition.

The update request could not be completed because the resulting configuration would violate that relationship.

Resubmit the request, ensuring that the relationship is satisfied.

SQL5154N

The requested combination of configuration values for "authentication" and parameter is not allowed. Reason code = reason-code.

The requested change is not made.

SQL5155W

The update completed successfully. The current value of SORTHEAP may adversely affect performance.

The value of SORTHEAP is currently greater than half the value of the sort threshold. The sort threshold is the value of the database manager configuration parameter SHEAPTHRES or, if SHEAPTHRES is set to 0, it is the value of the database configuration parameter SHEAPTHRES_SHR. This may cause performance to be less than optimal.

Increase the value of the sort threshold and/or decrease the value of SORTHEAP so that the sort threshold is at least twice as large as SORTHEAP.

A larger ratio is desirable in most cases. See the Administration Guide for recommendations on configuration parameter tuning.

SQL5156N

The value of the database manager configuration parameter "trust_allclnts" must be one of NO, YES, or DRDAONLY.

The requested change is not made.

Resubmit the command with a valid value for "trust_allclnts".

SQL5160N

Updates to parameter are currently disallowed. An operation is currently pending for this parameter. All applications must disconnect from the database and the database must be reactivated before new updates to this parameter can be applied.

In a cluster environment, this database configuration parameter can have only one pending operation. Upon database reactivation, cluster resources are updated to ensure consistency between the cluster manager and the database.

To allow another update to the database configuration parameter, ensure that all applications disconnect from the database and issue a DB2 CONNECT TO command. If the database was explicitly activated, deactivate and reactivate it.

SQL5161N

Updates to parameter are disallowed until the next DB2START command.

In a cluster environment, an update to the database manager configuration parameter can be performed when the previous resource has been deleted. Cluster resources are deleted when the database manager is restarted in order to maintain consistency.

To allow updates to the database manager configuration parameter issue DB2STOP and DB2START on the server.

SQL5162N

The db2dsdriver.cfg configuration file contains the parameter parameter1, which has the same value as the parameter parameter2, but these parameters cannot have the same value.

The db2dsdriver.cfg configuration file contains database information, and is used by the following drivers and clients:

• IBM Data Server Driver for ODBC and CLI
• IBM Data Server Driver Package
• For DB2 Version 9.7: for CLI and open source applications, the IBM Data Server Client and IBM Data Server Runtime Client

The information in the db2dsdriver.cfg file is similar to the information that is in the system database directory on an IBM Data Server Client or IBM Data Server Runtime Client.

The client driver configuration file cannot contain the same value for parameters. If true is specified for one parameter, false must be specified for the other.

1. Change the value of one of the parameters in the db2dsdriver.cfg file so that the two parameters do not have the same value.
2. Stop the application process and start it again for the new db2dsdriver.cfg file settings to take effect.

SQL5163N

A required configuration parameter parameter is missing from the db2dsdriver.cfg configuration file.

The db2dsdriver.cfg configuration file contains database information, and is used by the following drivers and clients:

• IBM Data Server Driver for ODBC and CLI
• IBM Data Server Driver Package
• For DB2 Version 9.7: for CLI and open source applications, the IBM Data Server Client and IBM Data Server Runtime Client

The information in the db2dsdriver.cfg file is similar to the information that is in the system database directory on an IBM Data Server Client or IBM Data Server Runtime Client.

The client driver configuration file must contain all required parameters.

1. Add the required configuration parameter to the db2dsdriver.cfg configuration file.
2. Stop the application process and start it again for the new db2dsdriver.cfg file settings to take effect.

SQL5164N

The db2dsdriver.cfg configuration file contains a configuration group group that requires at least one parameter, but no parameters are present.

The db2dsdriver.cfg configuration file contains database information, and is used by the following drivers and clients:

• IBM Data Server Driver for ODBC and CLI
• IBM Data Server Driver Package
• For DB2 Version 9.7: for CLI and open source applications, the IBM Data Server Client and IBM Data Server Runtime Client

The information in the db2dsdriver.cfg file is similar to the information that is in the system database directory on an IBM Data Server Client or IBM Data Server Runtime Client.

1. Add parameters to the configuration group in the db2dsdriver.cfg configuration file.
2. Stop the application process and start it again for the new db2dsdriver.cfg file settings to take effect.

SQL5165N

The value value indicated by the database configuration parameter parameter is not valid. Reason code=reason-code

The update of the indicated database configuration parameter failed. The explanation corresponding to the reason code is:

1

The hadr_target_list is invalid for one of the following reasons:

• The host entry is longer than 255 characters.
• The service entry is longer than 40 characters.
• The host entry contains invalid characters. Host entries can contain either alphanumerics, dashes, and underscores, or they can be in a numeric IPv4 or IPv6 address format.
• The values were not formatted correctly. The valid delimiters are: ":" "." "[" "]" "{" "}" "|"

2

The number of databases specified in hadr_target_list exceeds the maximum allowed (one in a DB2 pureScale environment and three in other environments).

4

The entries contained duplicate host:port pairs.

5

In a DB2 pureScale environment, each standby cluster specified in hadr_target_list must be enclosed with braces ("{...}"), even if the cluster only has one address listed.

6

In an environment other than DB2 pureScale, only one address is allowed for each standby database specified in hadr_target_list.

7

In a DB2 pureScale environment, a maximum of 128 addresses are allowed for each standby cluster specified in hadr_target_list.

The user response corresponding to the reason code is:

1

Update the hadr_target_list configuration parameter using a string with a valid length or set of characters. Check the db2diag.log for more details.

2

• If your HADR setup is in a DB2 pureScale environment, specify no more than one database in hadr_target_list.
• If your HADR setup is not in a DB2 pureScale environment, specify no more than three databases in hadr_target_list.

4

Update the hadr_target_list configuration parameter using unique host:port combinations.

5

Enclose the address list of each standby cluster with braces ("{...}").

6

List only one address for each standby database specified in hadr_target_list.

7

List no more than 128 addresses for each standby cluster specified in hadr_target_list.

SQL5180N

The database manager is unable to read the federation configuration file file-name.

The federated configuration file could not be found, or it could not be opened for reading.

Specify the federation configuration file in the DB2_DJ_INI registry variable. Be sure that the file exists and is readable. Ensure a fully qualified path is specified for the location of the file.

SQL5181N

The format of line line-number in the federation configuration file file-name is invalid.

The specified line is not in the correct format. Entries must follow the format <evname> = <value>, where <evname> is the name of the environment variable and <value> is the corresponding value.

Put the specified line in the format described in the preceding paragraph.

SQL5182N

A required environment variable, variable-name, has not been set.

In the federated configuration file db2dj.ini, the environment variable variable-name is unlisted, or it is listed but has no value.

Refer to the federation documentation for information about updating the federated configuration file.

SQL5185N

Pass-through to server-type data sources is not supported.

The Pass-Through facility cannot be used to access server-type data sources.

None required.

sqlcode: -5185

sqlstate: 428EV

SQL5186N

Configuring the Db2 environment failed because the specified Db2 environment variable, Db2 registry variable, Db2 configuration parameter, command option, or value of one of the preceding items is discontinued. Variable, parameter, option name or value: variable-or-parameter-name

This message is returned when an attempt is made to configure the Db2 environment by setting a Db2 environment variable, database manager configuration parameter, Db2 database configuration parameter, command option, or value of one of the preceding items that has been discontinued.

1. Use other variables or parameters to accomplish the same configuration objectives.
2. Update automated scripts and applications to use different variables or parameters to accomplish the same configuration objectives.

SQL5187N

The operation-type operation is not allowed for procedure procedure-name because a connection procedure with the same name is defined for the database.

Operations are restricted on any procedure with the same name as the connect procedure defined for a database using the database configuration parameter CONNECT_PROC. The connect procedure itself cannot be altered or dropped directly or as a result of CREATE OR REPLACE operation. A new procedure with the same name cannot be created, even if it has a different procedure signature.

If you are creating a new procedure, use a different name for the procedure name or a different schema. If the connect procedure that is currently in use needs to be altered or dropped, the value of CONNECT_PROC database configuration parameter must be changed to another procedure name or the empty string.

sqlcode: -5187

sqlstate: 429C8

SQL5188N

The statement failed because object name of type access-control-type is marked invalid.

The SQL statement could not be run as it required row or column access control be applied and either a column mask or row permission is currently marked invalid.

The statement cannot be processed.

A user with SECADM authority must either:

• drop the column mask or row permission then optionally recreate it,
• issue a CREATE or REPLACE statement to recreate the invalid object.

sqlcode: -5188

sqlstate: 560D0

SQL5189N

The alternate diagnostic directory path was not set because the specified path is invalid: alternate-diagpath

You specify an alternate diagnostic directory path with the alt_diagpath configuration parameter, so that diagnostic logging can continue even if the primary diagnostic path specified by the diagpath configuration parameter cannot be used. The alternate diagnostic path is switched to when the primary path is not available; logging resumes in the primary diagnostic path once that path is available again.

There are a number of reasons why the specified alternate diagnostic directory path might be invalid:

• The path does not exist.
• The path was set to the same path as the primary diagnostic path.
• The specified path does not follow the supported operating system naming convention.
• The path provided is read-only.

Verify that the alternate diagnostic directory path you want to use is available and set the path. For greater resiliency, the diagpath and alt_diagpath configuration parameters should always use different file systems.

SQL5190I

The primary diagnostic directory path and the alternate diagnostic directory path use the same file system.

You specify an alternate diagnostic directory path with the alt_diagpath configuration parameter, so that diagnostic logging can continue even if the primary diagnostic directory path specified by the diagpath configuration parameter cannot be used.

To avoid a failure scenario where both diagnostic directory paths are affected by a single file system problem, specify primary and alternate diagnostic directory paths that point to different file systems.

The parameter was set successfully, but you can improve logging resiliency further by using different file systems for the diagpath and alt_diagpath configuration parameters.

SQL5191W

The target of the data change operation is a table table-name, which includes a period period-name. The operation caused an adjustment to a recorded time value for the period.

Table table-name is a system-period temporal table. The table includes a period period-name. The requested data change operation was performed and resulted in an adjustment to a recorded time value for the period. This can occur for one of the following reasons:

• Two transactions are accessing the same row. The transaction that started first has a statement that is updating or deleting the row after a statement in the second transaction has already changed that row. This results in the timestamp value in the row begin column being the start time of the second transaction. The first transaction cannot update or delete a row if the row begin time stamp on that row is later than when the first transaction started.
• Data has been loaded into the system-period temporal table with values for the row begin column that override the generated values. The row begin column value that was loaded is in the future relative to the timestamp that the executing transaction would use.

For an update operation, the adjustment can affect both the begin and end columns for the period. For a delete operation, the adjustment only affects the end column for the period.

The statement was processed with an adjustment to the recorded time for the period.

If you did not want the adjustment, issue a rollback and retry the transaction. If data has been loaded into the system-period temporal table with values for the row begin column that override the generated values, clean the data such that the row-begin time values are less than or equal to the value of CURRENT TIMESTAMP. Otherwise, no action is required.

The systime_period_adj configuration parameter can be set to block the adjustment of the affected values.

sqlcode: +5191

sqlstate: 01695

SQL5192W

The ADMIN_SET_INTRA_PARALLEL procedure failed because either shared sort heap memory is not available or the application is assigned to a workload that has a value assigned to MAXIMUM DEGREE. Application name: application-name

There are multiple ways to configure intrapartition parallelism, including by setting the MAXIMUM DEGREE workload attribute or by calling the ADMIN_SET_INTRA_PARALLEL procedure:

• You can enable or disable intrapartition parallelism for a specified workload by setting the MAXIMUM DEGREE workload attribute.
• You can enable or disable intrapartition parallelism for a database application by calling the ADMIN_SET_INTRA_PARALLEL procedure.

The MAXIMUM DEGREE workload attribute overrides any call to the ADMIN_SET_INTRA_PARALLEL procedure.

This message can be returned when the ADMIN_SET_INTRA_PARALLEL procedure is called in either of the following two scenarios:

• The shared sort heap memory is not available
• The application is assigned to a workload for which intrapartition parallelism is already configured with the MAXIMUM DEGREE workload attribute

Control the degree of intrapartition parallelism either at the workload level or from within the application, but not both.

SQL5193N

The current session user does not have usage privilege on any enabled workloads.

The current session user does not have usage privilege on any enabled workloads. All connections to a database must be associated with a workload. In order for a connection to be associated with a workload, the connection attributes must match the attributes for the workload, the workload must be enabled, and the session user must have usage privilege on the workload.

If there are user defined workloads in the database, perform the following steps:

1. Determine which workload the connection should be mapped to by examining the attributes of the connection and comparing them with the attributes of the workload definitions.
2. Verify that the workload the connection should be associated with is enabled, and that the current session user has usage privilege on the workload.

If there are no user defined workloads in the database, perform the following steps:

1. Enable the default user workload, which is named SYSDEFAULTUSERWORKLOAD.
2. Grant usage privilege on this workload to the current session user.

sqlcode: -5193

sqlstate: 42524

SQL5194N

The driver connection failed because the client is unable to obtain a connection to InfoSphere Optim Configuration Manager. Specified httpControllerURL token1. Protocol error code: token2

The driver connection to the data server failed because the client cannot connect to InfoSphere Optim Configuration Manager to obtain initial driver properties.

In the driver db2dsdriver.cfg configuration file, an InfoSphere Optim Configuration Manager controller can be specified with the httpControllerURL keyword of the connectionSupervisorProperties global parameter.

• Ensure that the InfoSphere Optim Configuration Manager controller is running.
• Ensure that the httpControllerURL value is correct.
• Ensure that the controller port is not blocked by a firewall.
• If the driver is not meant to be controlled by InfoSphere Optim Configuration Manager, remove the httpControllerURL keyword from the db2dsdriver.cfg configuration file.

sqlcode: -5194

sqlstate: 08001

SQL5195N

The UPDATE DATABASE CONFIGURATION command failed because the specified value is not supported by the current instance node type. Database configuration parameter: parameter-name. Database configuration parameter value: specified-value. Current instance node type: instance-node-type.

Different database products are associated with different database manager instance node types. The current instance node type is indicated by the runtime token instance-node-type:

1

Database server with local and remote clients

2

Client

3

Database server with local clients

4

Partitioned database Server with local and remote clients

You can configure database functionality by setting database manager configuration parameters. Each instance node type supports only the database manager configuration parameters for the database products that are associated with that instance node type. For some configuration parameters, certain values for those configuration parameters are supported by only a subset of instance node types.

This message is returned when an attempt is made to update a database manager configuration parameter to a value that is not supported by the current instance node type.

Perform one of the following actions:

• Set the database configuration parameter to a valid value that is supported by the current instance node type.
• If the functionality associated with the failed configuration attempt is supported by a different instance node type, update or upgrade the instance node type to a type that supports the functionality and then reissue the UPDATE DATABASE MANAGER CONFIGURATION command.

sqlcode: -5195

sqlstate: 5U001

SQL5196N

The UPDATE DATABASE CONFIGURATION command failed because the specified database configuration parameter is not supported by the instance node type. Database configuration parameter: parameter-name. Current instance node type: instance-node-type.

Different database products are associated with different database manager instance node types. The current instance node type is indicated by the runtime token instance-node-type:

1

Database server with local and remote clients

2

Client

3

Database server with local clients

4

Partitioned database Server with local and remote clients

You can configure database functionality by setting database configuration parameters. Each instance node type supports only the database configuration parameters for the database products that are associated with that instance node type.

This message is returned when an attempt is made to update a database configuration parameter that is not supported by the current instance node type.

1. List the database configuration parameters that are supported by the current instance node type by issuing the GET DATABASE CONFIGURATION command.
2. Perform one of the following actions:
   • Achieve the desired configuration by updating one or more database configuration parameters that are supported with the current instance node type.
   • If the functionality associated with the failed configuration attempt is supported by a different instance node type, update or upgrade the instance node type to a type that supports the functionality and then reissue the UPDATE DATABASE CONFIGURATION command.

sqlcode: -5196

sqlstate: 5U001

SQL5197N

The statement failed because of a communication error with a Db2 Big SQL component. Db2 Big SQL component name: component-name. Reason code: reason-code. Log entry identifier: log-entry-identifier.

The reason code indicates the type of problem:

1

Connection refused.

2

Connection timed out.

3

A row being inserted into or read from an external table exceeds the size of an external table communication buffer. Reduce the amount of data being inserted into or read from the external table.

The log identifier in the token log-entry-identifier is composed of three parts:

1. A three-letter prefix that indicates which log file includes diagnostic details.
2. A three-digit number that indicates on which database partition the log file resides.
3. An identifier that is printed in the log file near the related diagnostic details.

When the log-entry-identifier is 'DB2', you can find the diagnostic details in $BIGSQL_DIST_VAR/diag. Otherwise, you can find them in $BIGSQL_DIST_VAR/logs.

1. Locate the diagnostic details in the appropriate log file by using the information in the log-entry-identifier runtime token.
2. Resolve the cause of the problem.
3. Submit the statement again.

sqlcode: -5197

sqlstate: 57066

Related information:

• LOG_ENTRY table function
• Diagnostic data directory path
• Administration notification log
• DB2 diagnostic (db2diag) log files

SQL5198N

The statement failed because of an authorization error from a Big SQL component. Big SQL component name: component-name. Reason code: reason-code. Log entry identifier: log-entry-identifier.

The reason code indicates more specifically what happened:

2

The user ID of the database manager does not have permission to read, write, or delete files or directories on the Hadoop Distributed File System (HDFS).

3

The user ID of the database manager does not have permission to read or write to the Hive Metastore.

4

A database object has row or column access control rules defined in both Db2 and the service identified by the token component-name. A database object may not have row and column access control defined in Db2 and an external service at the same time.

5

A column mask rule defined in the service identified by the component-name token is incompatible with the column it is defined on.

The log identifier in the token log-entry-identifier is composed of three parts:

1. A three-letter prefix that indicates which log file includes diagnostic details.
2. A three-digit number that indicates on which database partition the log file resides.
3. An identifier that is printed in the log file near the related diagnostic details.

When the log-entry-identifier is 'DB2', you can find the diagnostic details in $BIGSQL_DIST_VAR/diag. Otherwise, you can find them in $BIGSQL_DIST_VAR/logs.

1. Locate the diagnostic details in the appropriate log file by using the information in the log-entry-identifier runtime token.
2. Use the diagnostic details in the log file to perform corrective action corresponding to the reported reason code.

The user response corresponding to the reason code is:

2

Grant the user ID of the Big SQL server database manager authority to read, write, or delete files or directories on the Hadoop Distributed File System (HDFS).

3

Grant the user ID of the Big SQL server database manager authority to perform the operation in the Hive Metastore.

4

Examine the mask and permissions defined on the object in the Db2 catalogs, as well as any row and column access control rules defined in the external service. Modify policies so that row and column access control is only defined in Db2 or in the external service.

5

A column mask definition must have a result data type which is castable to the data type of the column it is defined on. Change the column mask definition to one compatible with the target column.

sqlcode: -5198

sqlstate: 42525

SQL5199N

The statement failed because a connection to a Hadoop/External Table I/O component could not be established or maintained. Hadoop/External Table I/O component name: component-name. Reason code: reason-code. Database partition number: number.

To protect its memory sets and agents, the database manager underlying processing engine uses a fenced-mode process (FMP) to establish and maintain a connection with a Hadoop/External Table I/O component.

This message is returned when the database manager encounters an error with an FMP that is hosting a Hadoop/External Table I/O component. The reason code indicates the source of the problem:

1

The FMP hosting the Hadoop/External Table I/O component is not up and running.

2

The database manager was unable to allocate enough memory from the FMP memory set to communicate with the Hadoop/External Table I/O component.

3

The C++ I/O Engine is not started because it has been deprecated. A user setting attempted to force the statement to execute on the C++ I/O Engine.

4

The database manager detected that there are already the maximum allowed number of Java fenced-mode processes hosting the Hadoop I/O component that are pending termination. Another FMP will not be created.

5

The database manager detected that there is already an embedded Data Virtualization node running in a fenced-mode process. A second FMP will not be created.

Respond according to the reason code:

1

Rerun the statement.

If the error continues, collect the following diagnostic information and troubleshoot the Hadoop/External Table I/O component:

• The value of the INSTANCE_MEMORY database manager configuration parameter
• Related diagnostic information in the db2diag diagnostic log files
• Related diagnostic information collected by First occurrence data capture (FODC)
• Related diagnostic information in the Hadoop/External Table I/O component log files

2

Perform one of the following actions:

• Wait for some statements to finish processing and then rerun the failed statement.
• Increase the amount of memory in the FMP memory set by increasing the INSTANCE_MEMORY database manager configuration parameter.

3

Unset any setting that attempts to force the use of the C++ I/O Engine at a global or table level. See the deprecation statement for the C++ I/O Engine (http://www-01.ibm.com/support/knowledgecenter/SSCRJT_5.0.3/com.ibm.swg.im.bigsql.doc/doc/deprecated.html). For further assistance, contact IBM Support.

4

Rerun the statement. If the error continues, consider cancelling existing long running applications with SYSHADOOP.CANCEL_APPLICATION stored procedure or the FORCE APPLICATION CLP command.

5

Rerun the statement. If the error persists, consider cancelling existing long running applications with SYSHADOOP.CANCEL_APPLICATION stored procedure or the FORCE APPLICATION CLP command.

sqlcode: -5199

sqlstate: 57067

SQL5501N

The format of line line-number in the vendor configuration file file-name is invalid.

The specified line is not in the correct format. Entries must follow the format <evname> = <value>, where <evname> is the name of the environment variable and <value> is the corresponding value.

Ensure the specified line matches the previously described format.