Explanation

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

The requested change is not made.

Explanation

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.

Explanation

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.

Explanation

The statement cannot be processed.

Explanation

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

The requested change is not made.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

The command cannot be processed.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

There is not enough memory available to execute this function.

The function cannot be completed.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

The command cannot be processed.

Explanation

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.

Explanation

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

The command cannot be processed.

Explanation

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.

Explanation

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.

Explanation

The parameter specified is not supported by this server release.

Explanation

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.

Explanation

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

The requested change is not made.

Explanation

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

The requested change is not made.

Explanation

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.

Explanation

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

The requested change is not made.

Explanation

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

Explanation

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, or LOGARCHMETH2.

9

The path cannot be accessed.

10

The path string is longer than 206 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 or VENDOR, a 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, 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.

The requested change is not made.

Explanation

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.

Explanation

This edition of DB2 does not offer the WLM utility.

Explanation

  bufferpool_size > 
    (number of active_processes * 2)

The requested change is not made.

Explanation

A Hadoop table is one that references a Hadoop Distributed File System (HDFS). You can create an empty Hadoop table by issuing the CREATE HADOOP TABLE statement. You can create and populate a Hadoop table using a query by issuing the CREATE HADOOP TABLE ... AS statement.

When a query is issued against an empty Hadoop table, the data in HDFS is mapped to the table definition in the CREATE HADOOP TABLE statement that was used to create the Hadoop table. This message is returned when the data in HDFS cannot be mapped to the table definition.

The token column-index specifies the ordinal position in the table definition of the column for which there is a data type mismatch.

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.

Explanation

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.

Explanation

A Hadoop table is one that references a Hadoop Distributed File System (HDFS). You can create an empty Hadoop table by issuing the CREATE HADOOP TABLE statement. You can create and populate a Hadoop table using a query by issuing the CREATE HADOOP TABLE ... AS statement.

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

This message is returned when there are changes to either the Hive metastore or the Big SQL catalogs which causes them to become unsynchronized.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

The user request is denied.

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.

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

The requested change was not made.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

The configuration parameter is not set or too long.

Explanation

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.

Explanation

Explanation

maxappls * maxlocks >= 100

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

Explanation

Explanation

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.

Explanation

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.

Explanation

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

The requested change is not made.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

The requested change is not made.

Explanation

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.

Explanation

The requested change is not made.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

This message is returned when an attempt is made to configure the DB2 environment by setting a DB2 environment variable, DB2 registry variable, database manager configuration parameter, or DB2 database configuration parameter that has been discontinued.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

The reason code indicates the type of problem:

1

Connection refused.

2

Connection timed out.

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.

Explanation

This message is returned when the user ID of the database manager underlying the Big SQL server does not have authority or permission to perform an operation. This error might happen in different scenarios, such as if the user ID of the database manager does not have permission to modify the Hive metastore.

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

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.

Explanation

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

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

1

The FMP hosting the Hadoop 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 I/O component.

Explanation

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.