User response

Check the syntax of the size expression.

SQL4010N Illegal nesting of Compound SQL statements.

Explanation

This error is returned when a BEGIN COMPOUND clause is detected as a sub-statement of a Compound SQL statement.

User response

Resubmit the precompilation without the nested BEGIN COMPOUND.

SQL4011N Invalid SQL sub-statement in a Compound SQL statement.

Explanation

This error is returned when an invalid sub-statement is detected in a Compound SQL statement. Valid statements are:

ALTER TABLE
COMMENT ON
CREATE INDEX
CREATE TABLE
CREATE VIEW
Positioned DELETE
Searched DELETE
DROP
GRANT
INSERT
LOCK TABLE
REVOKE
SELECT INTO
Positioned UPDATE
Searched UPDATE

Explanation

This error is returned when a Compound SQL statement contains a syntax error. Possible causes include:

END COMPOUND is missing
one of the substatements is empty (zero length or blank).

User response

Fix the syntax error and re-precompile.

SQL4015N An error has occurred during preprocessing.

Explanation

The external preprocessor has terminated with one or more errors.

The command cannot be processed.

User response

Please refer to the ".err" file for the corresponding source file for more details.

SQL4016N The preprocessor specified cannot be found.

Explanation

One of the following conditions has not been met:

Length value should be greater than zero.
Precision value should be greater than zero.
Scale value should not be greater than precision.

Processing continues.

User response

Correct the SQL statement.

SQL4108W An indicator variable has data type other than exact numeric, or has a non-zero scale.

Explanation

Data type of an indicator variable should be exact numeric with a scale of zero.

Processing continues.

User response

Correct the SQL statement.

SQL4109W The SET FUNCTION SPECIFICATION references column `column`.

Explanation

One of the following conditions has not been met:

The COLUMN REFERENCE of a DISTINCT SET FUNCTION cannot reference a column derived from a SET FUNCTION SPECIFICATION.
COLUMN REFERENCEs in the VALUE EXPRESSION of an ALL SET FUNCTION cannot reference a column derived from a SET FUNCTION SPECIFICATION.

The table or correlation name used as a qualifier does not exist.
The column name does not exist within the current scope or the scope of the qualifier.

A VALUE EXPRESSION containing a DISTINCT SET FUNCTION cannot include dyadic operators.
First character following a monadic operator cannot be a plus or minus sign.
VALUE EXPRESSION should not contain operators if PRIMARY is of type character string.

Processing continues.

User response

Correct the SQL statement.

SQL4118W The `exptype` EXPRESSION is comparing incompatible data types.

Explanation

The data types of one of the following (identified by exptype) do not match:

exptype = COMPARISON - Comparison operators must match
exptype = BETWEEN - The three VALUE EXPRESSIONs must match
exptype = IN - VALUE EXPRESSION, subquery and all VALUE SPECIFICATIONs must match
exptype = QUANTIFIED - VALUE EXPRESSION and subquery must match

Processing continues.

User response

Correct the SQL statement.

SQL4119W The operand in the LIKE predicate is not a character string.

Explanation

One of the following conditions has not been met:

Data type of the column in a LIKE predicate is not a character string.
Data type of the pattern in a LIKE predicate is not a character string.

Table name occurs more than once in a FROM clause.
Correlation name is identical to a table name or to another correlation name in a FROM clause.

If the TABLE EXPRESSION is a grouped view, the SELECT LIST of a subquery cannot contain a SET FUNCTION SPECIFICATION.
If the TABLE EXPRESSION is a grouped view, the SELECT LIST of a QUERY SPECIFICATION cannot contain a column function.

Processing continues.

User response

Correct the SQL statement.

SQL4131W The COLUMN REFERENCE for `column` is invalid.

Explanation

One of the following conditions has not been met:

For a GROUPed table, the COLUMN REFERENCE must reference a GROUPing column or be specified within a SET FUNCTION SPECIFICATION.
If not a GROUPed table and VALUE EXPRESSION includes a SET FUNCTION SPECIFICATION, then each COLUMN REFERENCE must be specified within a SET FUNCTION SPECIFICATION.

Processing continues.

User response

Correct the SQL statement.

SQL4132W DISTINCT is specified more than once.

Explanation

One of the following conditions has not been met:

DISTINCT must not be specified more than once in a QUERY SPECIFICATION, excluding any subquery of that QUERY SPECIFICATION.
DISTINCT must not be specified more than once in a subquery, excluding any subquery contained in that subquery.

In a FETCH statement, between source and target.
In a SELECT statement, between source and target.

Processing continues.

User response

Correct the SQL statement.

SQL4139W You must specify a VIEW COLUMN LIST for `schema-name`.`table`.

Explanation

If any two columns in the table specified by the QUERY SPECIFICATION have the same column name, or if any column of that table is an unnamed column, then a VIEW COLUMN LIST must be specified.

Processing continues.

User response

Correct the SQL statement.

SQL4140W An error has occurred causing the flagger to stop. Module name = `module-name`. Internal error code = `error-code`.

Explanation

The flagger has encountered an internal error. If the syntax, bindfile or package option is also specified, processing continues but flagger operation is discontinued. Otherwise, processing is terminated.

User response

Record this message number (SQLCODE), module name and error code in the message. Contact your technical service representative with the information.

SQL4141W An error has occurred when attempting to produce message `message-number` in module `module-name`.

Explanation

One of the following conditions has not been met:

If the data type of the column name is character string, then the corresponding item in the INSERT or UPDATE statement should be character string of length equal to or less than the length of the column name.
If the data type of the column name is exact numeric, then the corresponding item in the INSERT or UPDATE statement should be exact numeric.
If the data type of the column name is approximate numeric, then the corresponding item in the INSERT or UPDATE statement should be approximate numeric or exact numeric.

SQL4300N Java support is not installed or properly configured on this platform.

Explanation

Support for Java stored procedures and user-defined functions is not installed and configured on this server.

User response

Ensure that a compatible Java Runtime Environment or Java Development Kit for the server is installed. Ensure that the "JDK_PATH" configuration parameter is correctly set.

sqlcode: -4300

sqlstate: 42724

SQL4301N Java or .NET interpreter startup or communication failed, reason code `reason-code`.

Explanation

An error occurred while attempting to start or communicate with a Java interpreter. The reason codes are:

1: Java environment variables or Java database configuration parameters are invalid.
2: A Java Native Interface call to the Java interpreter failed.
3: The "db2java.zip" file may be corrupt or missing.
4: The Java interpreter has terminated itself and cannot be restarted.
5: Unable to load a dependent .NET library.
6: A call to the .NET interpreter failed.

User response

1: The class was not found on the CLASSPATH.
2: The class did not implement the required interface ("COM.ibm.db2.app.StoredProc" or "COM.ibm.db2.app.UDF") or lacked the Java "public" access flag.
3: The default constructor failed or was unavailable.
4: Could not load driver for "jdbc:default:connection".
5: Could not establish default context.

User response

Ensure that the compiled ".class" file is installed in the CLASSPATH, for example under "sqllib/function". Ensure it implements the required Java interfaces and is "public".

sqlcode: -4304

sqlstate: 42724

SQL4306N Java stored procedure or user-defined function `name`, specific name `spec-name` could not call Java method `method`, signature `string`.

Explanation

The Java method given by the EXTERNAL NAME clause of a CREATE PROCEDURE or CREATE FUNCTION statement could not be found. Its declared argument list may not match what the database expects, or it may not be a "public" instance method.

User response

Ensure that a Java instance method exists with the "public" flag and the expected argument list for this call.

sqlcode: -4306

sqlstate: 42724

SQL4400N `authorization-ID` does not have the authority to perform the administration task at the DB2 Administration Server.

Explanation

The user does not have the necessary authority at the DB2 Administration Server to perform the attempted administrative action.

User response

Submit the request to the DB2 Administration Server using a user ID with DASADM authority. DASADM authority is required to perform any administrative actions against the DB2 Administration Server. The DASADM group is a DB2 Administration Server configuration parameter. Verify the current setting of the DASADM group by viewing the DB2 Administration Server configuration parameters using the GET ADMIN CONFIGURATION command. To modify the value of any configuration parameter, use the UPDATE ADMIN CONFIGURATION command.

SQL4401C The DB2 Administration Server encountered an error during startup.

Explanation

An error was encountered during startup of the DB2 Administration Server.

User response

User response

Create the DB2 Administration Server on the machine.

On Windows operating systems, issue the following command:
```
db2admin create
```
On UNIX platforms, ensure that you have root authority, and issue the following command from the DB2DIR/instance directory, where DB2DIR is the installation path of DB2. <ASName> represents the name of the Administration Server:
```
dascrt <ASName>
```

    DB2ADMIN STOP

You can set up the logon user account for the DB2 Administration Server by using the following command:

    DB2ADMIN SETID <userid>
                   <password>

SQL4413W Usage: DB2ADMIN creates, drops, starts, or stops the DB2 Administration Server.

Explanation

The DB2ADMIN command syntax is:

DB2ADMIN CREATE [
             /USER:<username>
             /PASSWORD:<password>
             ]
         DROP
         START
         STOP [/FORCE]
         SETID <username>
               <password>
         SETSCHEDID <username> <password>
         /h

The command options are:

CREATE: create the DB2 Administration Server
DROP: delete the DB2 Administration Server
START: start the DB2 Administration Server
STOP: stop the DB2 Administration Server
SETID: set the logon account for the DB2 Administration Server
SETSCHEDID: set the logon account used by the scheduler to connect to the tools catalog database. Only required if the scheduler is enabled and the tools catalog database is remote to the DB2 Administration Server.
/USER: specify the logon account name during DB2ADMIN CREATE
/PASSWORD: specify the logon account password during DB2ADMIN CREATE
/FORCE: stop the DB2 Administration Server during DB2ADMIN STOP regardless of whether or not it is in the process of servicing any requests
/h: display the usage information

User response

Issue the DB2ADMIN command with one of the valid command options.

SQL4414N The DB2 Administration Server is not active.

Explanation

The request cannot be processed unless the DB2 Administration Server is active.

User response

Start the DB2 Administration Server by issuing the command DB2ADMIN START, and reissue the request.

SQL4701N Maximal number of data partitions (`max-number`) exceeded.

Explanation

An attempt was made to exceed the maximum number of data partitions.

User response

If the error occurred on a CREATE TABLE statement with an EVERY clause, the interval was not large enough. Specify a larger interval to reduce the number of data partitions required.

If the error occurred on a CREATE TABLE statement without an EVERY clause, too many data partitions were listed. Reduce the number of data partitions specified.

If the error occurred on an ALTER TABLE ... ATTACH PARTITION or an ALTER TABLE ... ADD PARTITION statement, the table already has the maximum number of data partitions allowed. Data partitions must be detached before additional data partitions can be added or attached.

sqlcode: -4701

sqlstate: 54054

SQL4702N The activity identified by application handle `application-handle`, unit of work ID `unit-of-work-id`, and activity ID `activity-id` does not exist.

Explanation

An attempt was made to perform an operation on an activity identified by an application handle, a unit of work identifier, and an activity identifier. Such an activity does not currently exist within this database.

User response

Verify that the arguments that were specified for application handle, unit of work identifier, and activity identifier match those of the activity that was intended. Note that it is possible that an activity could leave the system before an operation can be performed on it.

sqlcode: -4702

sqlstate: 5U035

SQL4703N The activity identified by application handle `application-handle`, unit of work ID `unit-of-work-id`, and activity ID `activity-id` cannot be cancelled. Reason code = `reason-code`.

Explanation

The identified activity cannot be cancelled at this time because of its state or the type of activity it is.

User response

The reason code indicates the situation and particular action to take.

1: The activity is in the initialization state. The activity can be cancelled after the initialization has completed.
2: The activity cannot be cancelled because its type is not a supported activity type. If you wish to stop this activity from continuing to execute or queue in this system, you may force the application that issued this activity to stop by using the FORCE APPLICATION command.

The workload attributes for the intended workload match the connection attributes.
The intended workload is enabled.
The evaluation order for the intended workload is earlier than the evaluation order for the named workload.

If connections associated with the named workload should be allowed to access this database, alter the named workload using the ALTER WORKLOAD statement with the ALLOW DB ACCESS option.

sqlcode: -4707

sqlstate: 5U020

SQL4708N Only a COMMIT or ROLLBACK statement is allowed at this time for this unit of work.

Explanation

One of the following statements has been issued and it must be committed or rolled back before any other SQL statement can be issued:

CREATE SERVICE CLASS, ALTER SERVICE CLASS, or DROP (of a SERVICE CLASS)
CREATE THRESHOLD, ALTER THRESHOLD, or DROP (of a THRESHOLD)
CREATE TRUSTED CONTEXT, ALTER TRUSTED CONTEXT, or DROP (of a TRUSTED CONTEXT)
CREATE WORK ACTION SET, ALTER WORK ACTION SET, or DROP (of a WORK ACTION SET)
CREATE WORK CLASS SET, ALTER WORK CLASS SET, or DROP (of a WORK CLASS SET)
CREATE WORKLOAD, ALTER WORKLOAD, or DROP (of a WORKLOAD)
GRANT (Workload privileges) or REVOKE (Workload privileges)
CREATE AUDIT POLICY, ALTER AUDIT POLICY, or DROP (of an AUDIT POLICY)

The workload assignment that was performed at the beginning of the unit of work failed. Subsequent requests cannot be processed until the current unit of work is ended.

User response

COMMIT or ROLLBACK before issuing another statement.

sqlcode: -4708

sqlstate: 5U021

SQL4709N The last connection attribute cannot be dropped from the definition of workload `workload-name`.

Explanation

The ALTER WORKLOAD statement would have resulted in the last connection attribute being dropped from the workload workload-name, This operation is not allowed. There must be at least one connection attribute specified in the definition of the workload.

User response

Ensure that the ALTER WORKLOAD statement leaves at least one connection attribute in the definition of the workload.

sqlcode: -4709

sqlstate: 5U022

SQL4710N The workload `workload-name` cannot be dropped because it is not disabled, it has active workload occurrences, or it has a threshold or a work action set associated with it.

Explanation

An attempt to drop workload workload-name has failed for one of the following reasons.

The workload has not been disabled.
The workload has active workload occurrences.
A threshold is associated with the workload.
A work action set is associated with the workload

User response

Do one of the following:

If the workload is not yet disabled, issue the ALTER WORKLOAD statement to disable the workload and keep new workload occurrences from becoming active.
Wait until there are no more active workload occurrences running on the system and then issue the DROP statement to drop the workload.
If a threshold is associated with the workload, issue the DROP THRESHOLD statement to drop the associated threshold.
If a work action set is associated with the workload, issue the DROP WORK ACTION SET statement to drop the associated work action set.

sqlcode: -4710

sqlstate: 5U023

SQL4711N The threshold `threshold-name` cannot be dropped. The threshold is not disabled, the threshold queue is not empty, or an activity is running under the control of the threshold.

Explanation

An attempt to drop threshold threshold-name failed. The threshold is not disabled, the threshold queue is not empty, or an activity is running under the control of the threshold.

User response

If the threshold is not yet disabled, disable it. If the threshold is part of a work action set, you must use the ALTER WORK ACTION SET statement to disable it. If the threshold is not part of a work action set, use the ALTER THRESHOLD statement to disable it. Disabling the threshold prevents new requests from running under the control of the threshold. If the concurrency limit for a queueing threshold has been reached, the DISABLE action prevents new requests from joining the queue. Wait until the currently executing request completes or no more requests are in the queue, then issue the DROP THRESHOLD statement again.

sqlcode: -4711

sqlstate: 5U025

SQL4712N The activity or request was stopped because the threshold `threshold-name` has been exceeded. Reason code: `reason-code`.

Explanation

You can help maintain stability in your system by creating thresholds to identify and react to work that behaves abnormally. For example, you can limit how long a unit of work executes, by using the UOWTOTALTIME unit of work threshold. Or you can limit the amount of system temporary table space a given activity can consume on a member by using the SQLTEMPSPACE activity threshold.

This message is returned when the a threshold has been exceeded and as a result the associated activity or request was stopped.

The reason code indicates the reason that the threshold was exceeded:

1: An overflow agent cannot be queued. The activity is using an overflow agent and either the number of coordinator connections is exceeded or the number of database coordinator activities is exceeded.
2: The maximum number of connections per database partition has been reached (TOTALMEMBERCONNECTIONS condition).
3: The maximum number of connections and queued connections per database partition in a specific service superclass has been reached (QUEUEDCONNECTIONS or TOTALSCMEMBERCONNECTIONS condition).
4: The maximum number of workload occurrences per database partition has been reached (CONCURRENTWORKLOADOCCURRENCES condition).
5: The maximum number of workload activities per database partition has been reached (CONCURRENTWORKLOADACTIVITIES condition).
6: The maximum number of database coordinator activities and queued database coordinator activities at the specified enforcement scope in the domain has been reached (CONCURRENTDBCOORDACTIVITIES or QUEUEDACTIVITIES condition). In a DB2 pureScale environment, the enforcement scope is at the member level (MEMBER enforcement scope). In environments other than DB2 pureScale environments, the enforcement scope is at the database level (DATABASE enforcement scope).
7: The estimated cost for the activity exceeds that allowed by the threshold (ESTIMATEDSQLCOST condition).
8: The number of rows returned for the activity would exceed that allowed by the threshold (SQLROWSRETURNED condition).
9: The maximum total time for the activity has exceeded that allowed by the threshold (ACTIVITYTOTALTIME condition).
10: The amount of temporary system space requested for the activity exceeds that allowed by the threshold (SQLTEMPSPACE condition).
11: The number of rows read by the activity during its lifetime has exceeded that allowed by the threshold (SQLROWSREAD condition).
12: The number of rows read by the activity while executing in the current service subclass has exceeded that allowed by the threshold (SQLROWSREADINSC condition).
13: The amount of CPU time used by the activity during its lifetime has exceeded that allowed by the threshold (CPUTIME condition).
14: The amount of CPU time used by the activity while executing in the current service subclass has exceeded that allowed by the threshold (CPUTIMEINSC condition).
15: The total amount of temporary system space requested for the service subclass exceeds that allowed by the threshold (AGGSQLTEMPSPACE condition).
16: The amount of time used by the unit of work has exceeded that allowed by the threshold (UOWTOTALTIME condition).
17: The data tag of a table referenced by the activity is in the list of data tags specified in the threshold (DATATAGINSC IN condition).
18: The data tag of a table referenced by the activity is in the list of data tags specified in the threshold (DATATAGINSC NOT IN condition).
19: The maximum total runtime for the activity has exceeded that allowed by the threshold (ACTIVITYTOTALRUNTIME condition).
20: The maximum total runtime for the activity has exceeded that allowed by the threshold (ACTIVITYTOTALRUNTIMEINALLSC condition).

User response

Perform one or more of the following actions:

Review details of the threshold that was exceeded by looking up the given threshold in the SYSCAT.THRESHOLDS catalog view.
Increase the threshold limit.
Modify the activity or request so that it uses less of the resource that is being monitored by the threshold.
If the activity violated a concurrency threshold, execute the activity at another time when there are fewer activities executing on the system.

sqlcode: -4715

sqlstate: 5U029

SQL4716N An error occurred while communicating with the external workload manager.

Explanation

The database manager failed to communicate with the external workload manager. The following could have caused the error:

The external workload manager is not installed
The external workload manager is installed but is not active

User response

If the instance is running on AIX, ensure AIX WLM is installed and active. If the instance is running on Linux, ensure Linux WLM is installed and active.

sqlcode: -4716

sqlstate: 5U030

SQL4717N The service class `service-class-name` was not dropped. Reason code: `reason-code`.

Explanation

There are several conditions under which a service class may not be dropped, such as if the service class is still enabled or the service class is still referenced by another workload manager object. This message is returned when a service class is prevented from being dropped because of one of these conditions.

The token reason-code indicates what condition is preventing the service class from being dropped:

1: The service superclass has user-defined service subclasses.
2: The service class has a workload association.
3: The service class has a work action set association.
4: The service class has a work action association.
5: The service class has connections, workload occurrences, activities or resources governed by workload manager admission control associated with it on one or more partitions.
6: The service class has a threshold associated with it.
7: The service class is not disabled.
8: The service class is a default service class.
9: The service class is the target of a threshold REMAP ACTIVITY action.

User response

To drop the service class, first resolve the condition that is preventing the service class from being dropped, according to the reason code:

1

Drop all user-defined service subclasses under the service superclass.

2

Determine which workloads are associated with the service class by referring to the SYSCAT.WORKLOADS catalog view, and then remove the associated workloads.

3

Determine which work action sets are associated with the service class by referring to the SYSCAT.WORKACTIONSETS catalog view, and then remove the associated work action sets.

4

Determine which work actions are associated with the service class by referring to the SYSCAT.WORKACTIONS catalog view, and then remove the associated work actions.

5

Respond to reason code 5 in one of the following ways:

Wait until all connections, workload occurrences, and activities currently using the service class have completed and until all resources governed by workload manager admission control have been released.
Force connections associated with the service class to disconnect from the service class by issuing the FORCE APPLICATION command.
Cancel all the activities currently executing in the service class.

6

Determine which thresholds are associated with the service class by referring to the SYSCAT.THRESHOLDS catalog view, and then remove the associated thresholds.

7

Disable the service class by issuing the ALTER SERVICE CLASS statement.

8

Specify a user-defined service class.

9

Determine which thresholds specify a REMAP ACTIVITY action that targets the service class by referring to the SYSCAT.THRESHOLDS catalog view. Then, for each associated threshold, drop the threshold or alter the threshold REMAP ACTIVITY action to target another service subclass under the same service superclass.

sqlcode: -4717

sqlstate: 5U031

SQL4718N Default workload management object `wlm-object-name` was not altered, associated, or configured as specified. Reason code: `reason-code`.

Explanation

There are default workload management objects (such as the default user workload and the default administration workload), that are defined by the system rather than the user. Some actions that you may perform on user-defined workload management objects are not supported on default workload management objects.

This message is returned when an attempt is made to perform an unsupported action on a default workload management object.

The reason code indicates why the action was not performed:

1: An attempt was made to disable the default system service class, the default maintenance service class, or the default user service class.
2: An attempt was made to associate the default system service class or the default maintenance service class with a workload, work action set, or threshold. Or an attempt was made to associate the default user service class with a work action set.
3: An attempt was made to alter an attribute that may not be altered for a default service subclass.
4: An attempt was made to associate the default service subclass with a workload.
5: An attempt was made to configure a CPU share or a CPU limit on the SYSDEFAULTSYSTEMCLASS service class or its subclass.
6: An attempt was made to add or drop a work class in the SYSDEFAULTUSERWCS work class set.
7: An attempt was made to add or drop a work action in the SYSDEFAULTUSERWAS work action set.
8: An attempt was made to associate the default user work class set with a user-defined work action set.
9: An attempt was made to alter an attribute that may not be altered for a work class in the SYSDEFAULTUSERWCS work class set.
10: An attempt was made to alter an attribute that may not be altered for a work action in the SYSDEFAULTUSERWAS work action set.
11: An attempt was made to configure resource shares, minimum resource share percent or admission queue order on the SYSDEFAULTSYSTEMCLASS or SYSDEFAULTMAINTENANCE service classes or their subclasses.

User response

Based on the reason code, perform one of the following actions:

1, 2, 4: Specify a user-defined service class.
3: Alter the attribute for the parent superclass instead.
5: Configure a CPU share, a CPU limit, or both on a user or maintenance service class.
6, 8: Specify a user-defined work class set.
7: Specify a user-defined work action set.
9: Specify a user-defined work class in a user-defined work class set.
10: Specify a user-defined work action in a user-defined work action set.
11: Specify a user-defined service class.

sqlcode: -4718

sqlstate: 5U032

SQL4719N The PREVENT EXECUTION work action `work-action_name` is applied to this activity, and so the activity was not run.

Explanation

A PREVENT EXECUTION work action is preventing the activity from running.

User response

Either remove or disable the PREVENT EXECUTION work action.

sqlcode: -4719

sqlstate: 5U033

SQL4720N The work action type specified is not valid for work action `work-action-name`. Reason code `reason-code`.

Explanation

The type of work action specified is not valid for one of the following reasons:

1: Duplicate work action type specified for the work class of the same work action set.
2: The work action type is MAP ACTIVITY, but the work action set is associated with a database or a workload. Mapping work actions are only valid for work action sets applied to service classes.
3: The work action type is a threshold, but the work action set is associated with a service class. Threshold work actions are only valid for work action sets applied to a database or a workload.
4: The work action type is COLLECT AGGREGATE ACTIVITY DATA, but the work action set is associated with a database. COLLECT AGGREGATE ACTIVITY DATA work actions are only valid for work action sets applied to service classes or workloads.

User response

Specify a different type of work action.

sqlcode: -4720

sqlstate: 5U034

SQL4721N The threshold `threshold-name` cannot be created or altered (reason code = `reason-code`).

Explanation

The threshold cannot be created or altered because it violates a restriction as indicated by the following reason code:

1: The service superclass does not exist.
2: The service subclass does not exist.
3: The workload definition does not exist.
4: This type of threshold is not supported with the specified definition domain and enforcement scope.
5: The value specified for the condition of the threshold is out of range.
6: When maxValue is set to 0 for a queuing threshold, the queueSize must also be 0 and the action must be STOP EXECUTION.
7: The threshold predicate cannot be changed by an ALTER THRESHOLD statement.
8: The service class specified in a REMAP ACTIVITY action does not exist under the service superclass of the threshold.
9: The service subclass specified in a REMAP ACTIVITY action cannot be the same as the service subclass of the threshold.
10: The REMAP ACTIVITY action is not supported for the specified threshold.
11: The threshold specified is not supported for a default service class under a default service superclass.
12: The REMAP ACTIVITY action is not supported for work action thresholds.
13: The FORCE APPLICATION action is not supported for the specified threshold.
14: A section with the specified executable ID was not found in the package cache or catalog.

User response

The action corresponding to the reason code is:

1: Create the service superclass then issue the CREATE THRESHOLD or ALTER THRESHOLD statement again.
2: Create the service subclass then issue the CREATE THRESHOLD or ALTER THRESHOLD statement again.
3: Create the workload then issue the CREATE THRESHOLD or ALTER THRESHOLD statement again.
4: Issue the CREATE THRESHOLD or ALTER THRESHOLD statement with a valid definition domain and enforcement scope.
5: Issue the CREATE THRESHOLD or ALTER THRESHOLD statement with a maximum value in the valid range.
6: Issue the CREATE THRESHOLD or ALTER THRESHOLD statement with a queueSize of 0 and the action STOP EXECUTION.
7: Drop the threshold and create a new threshold with the predicate you want. Alternatively, you can keep the existing threshold and create a new threshold with the predicate that you want.
8: Create the service subclass under the service superclass of the threshold, then issue the CREATE THRESHOLD or ALTER THRESHOLD statement again.
9: Issue the CREATE THRESHOLD or ALTER THRESHOLD statement with a REMAP ACTIVITY action that specifies a different service subclass under the service superclass of the threshold.
10: Issue the CREATE THRESHOLD or ALTER THRESHOLD statement with a different threshold exceeded action.
11: Issue the CREATE THRESHOLD or ALTER THRESHOLD statement with a user defined service subclass specified for the threshold domain.
12: Issue the CREATE WORK ACTION SET or ALTER WORK ACTION SET statement with a different threshold exceeded action for the threshold work action.
13: When you issue the CREATE THRESHOLD or ALTER THRESHOLD statement, specify a different action to be taken if the maximum value for the threshold is exceeded.
14: If you are using static SQL, ensure that you have specified the correct executable ID. For dynamic SQL, use a PREPARE statement to add a prepared or executable version of the statement to the package cache.

sqlcode: -4721

sqlstate: 5U037

SQL4722N The threshold was not created because a threshold `object-name` with a matching definition already exists.

SQL4727N The activity cannot be mapped to the service subclass you specified because at least one of the input parameters to the routine WLM_REMAP_ACTIVITY is not valid. Reason code = `reason-code`.

Explanation

The routine WLM_REMAP_ACTIVITY failed because one or more of the input parameters is not valid. The reason codes are as follows:

1: The activity can be remapped only to a service subclass under the service superclass of the activity. Specify the service superclass name of the activity in the service_superclass_name parameter or set it to null. Setting the service_superclass_name parameter to null defaults the input parameter to the current service superclass name of the activity.
2: A valid service subclass under the service superclass of the activity must be specified in the service_subclass_name parameter.
3: Specify Y in the log_evmon_record parameter to log an event monitor record to the THRESHOLD VIOLATIONS event monitor when the activity is remapped on a partition. Specify N in the log_evmon_record parameter to prevent logging an event monitor record to the THRESHOLD VIOLATION event monitor when the activity is remapped on a partition.

User response

Ensure that the condition in the reason code is satisfied and reinvoke the WLM_REMAP_ACTIVITY routine.

sqlcode: -4727

sqlstate: 5U046

SQL4728W A priority setting was assigned to a service class that is higher than the priority setting of the default system service class SYSDEFAULTSYSTEMCLASS and this might negatively impact performance.

Explanation

To ensure that system work can take precedence over user work, the priority settings of the default system service class SYSDEFAULTSYSTEMCLASS should always be higher than the priorities that were set for all other service classes. Failure to assign higher priority settings to the default system service class can result in a negative impact on performance because system-type activities run in the default system service class.

User response

The function cannot be completed.

User response

For point-in-time table space recovery, a table space list must be specified.
For point-in-time table space recovery, a self-contained list of table space names must be specified. The table spaces in the list must contain all objects of every table included in the table spaces.
Point-in-time table space recovery is not allowed for the system catalogs.
End-of-logs table space recovery is allowed for the system catalogs but it can be the only table space name in the list.
The CANCEL option for rollforward must have a table space list if there are no table spaces in "rollforward-in-progress" state.

User response

Check the table space list and resubmit the rollforward command with the complete table space list.

SQL4907W Database `name` is recovered but one or more of the tables in the table space list included for the rollforward operation are placed in the Set Integrity Pending state.

Explanation

One or more of the tables involved in the point-in-time tablespace recovery have referential constraints with tables outside of the table space list used for recovery, or have dependent materialized query tables or dependent staging tables outside of the table space list used for recovery. All these tables are placed in the Set Integrity Pending state. Rollforward operation has otherwise completed successfully.

User response

Check the state for the tables in the table spaces and take appropriate actions if necessary.

SQL4908N The table space list specified for roll-forward recovery on database `name` is invalid on members or nodes `node-list`.

Explanation

Check for one or more of the following conditions:

The tablespace list contains duplicate names.
If starting a new table space rollforward, one or more of the table spaces specified in the list to be rolled forward is not in rollforward pending state on the specified members or nodes.
If continuing a table space rollforward that is already in progress, one or more of the table spaces specified in the list to be rolled forward is not in rollforward in progress state or is offline on the specified members or nodes.

User response

Ensure that there are no duplicate table space names in the list.

Use the MON_GET_TABLESPACE table function on the members or nodes specified to find out which table spaces are not ready to be rolled forward. Use the QUERY STATUS option of the rollforward command to determine the status of the table space rollforward. If the rollforward status is "TBS pending", a new table space rollforward can be started. If the rollforward status is "TBS working", a table space rollforward is already in progress.

If starting a new table space rollforward, put the tablespaces into rollforward pending state by restoring them.

If continuing a table space rollforward and one or more of the table spaces involved have been restored and put into rollforward pending state, the table space rollforward in progress must be canceled. Submit the rollforward command again with the CANCEL option and the same table space list. When the rollforward in progress is canceled, the table spaces will have been put into restore pending state. Restore the table spaces and submit the original rollforward command again.

If continuing a table space rollforward and one or more of the table spaces involved is offline, there are three options:

Bring the tablespace back online and submit the original rollforward command again.
Re-submit the rollforward command but remove the offline tablespaces from the tablespace list. These tablespaces will be put into restore pending state.
Submit the rollforward command again with the CANCEL option and the same table space list. When the rollforward in progress is canceled, the table spaces will have been put into restore pending state.

sqlcode: -4930

sqlstate: 56095

SQL4940N The `clause` clause is not permitted or is required.

Explanation

The indicated clause is either not allowed in the context where it appears in the SQL statement or it is required in the statement.

Explanation

One of the following occurred:

The update or insert value was NULL but the object column is declared as NOT NULL in the table definition. Therefore, null values cannot be inserted into that column, and values in that column cannot be set to NULL by an update.
The column name list for the INSERT statement omits a column that was declared as NOT NULL in the table definition.
The view for the INSERT statement omits a column that was declared as NOT NULL in the base table definition.

The function cannot be completed.

User response

Correct the section_number parameter in the application program.

SQL4970N Rollforward recovery stopped on the database named `database-name` because the rollforward utility cannot reach the specified stop point (end-of-log or point-in-time) on the following database partitions: `database-partition-list`.

Explanation

This message is returned in the following situations:

The rollforward utility cannot access one or more files because the files are missing or the files have data integrity problems. Here are some examples:
- A request was made to bring the specified database out of rollforward pending state. However, the rollforward utility cannot find the necessary archive log files in the database log directory or the overflow log directory on the specified database partitions to reach the stopping point from the previous rollforward operation.
- In a multi-partitioned database environment that is not a DB2 pureScale environment: the rollforward utility cannot find the necessary archive log files to bring a database partition into synchronization with the catalog partition.
This was a point-in-time rollforward in which the specified point-in-time timestamp was not reachable in the log files. This might indicate there are missing log files, or that the point in time was after the end of logs and make the database available. In a partitioned database environment, use the ROLLFORWARD DATABASE command with the QUERY STATUS option to ensure that the roll-forward is in a normal state.
This was a DB2 pureScale database rollforward that replayed a log file that was partially shipped from an HADR primary database to an HADR standby database.
This could happen, for example, if the HADR standby was in remote catchup, then a STOP HADR, or database restore command was run followed by this database rollforward.

The log file exists but is incomplete and is missing log records. Other log streams may have dependencies on these missing log records.

If ",..." is displayed at the end of the database partition list, see the administration notification log for the complete list of database partitions.

Rollforward recovery has stopped. The database is left in rollforward pending state.

User response

Determine the last log file processed by the rollforward by issuing a rollforward command with the QUERY STATUS option. Then ensure that any necessary files, following the last log file processed, are made available by moving them to the appropriate location:
- Check in the database log directory or the overflow log path (if specified).
- If log archiving is enabled ensure that the necessary files exist in the archive location. Ensure also that the log archiving retrieval method is working: check the administration notification log for the presence of message ADM0083I and make corrections to the retrieval method if necessary.
After verifying these two things, re-issue the ROLLFORWARD DATABASE command.

If the log files are present and re-issuing ROLLFORWARD DATABASE fails (potential data integrity issues with the log files), or the log files cannot be found, restore and rollforward the database to an earlier point in time referenced in one of the processed log files (use a timestamp that is earlier than that of the earliest missing file).
If the point-in-time timestamp was correct, and there are no missing log files, then the point-in-time specified may actually be beyond any work performed against the database. In this case, issue the ROLLFORWARD DATABASE command with the STOP option which will complete the rollforward recovery at the current position in the log files.
If a complete copy of the log file is available on the HADR primary database or some other source such as an archive, copy it to this database's log path (and save any file to be overwritten by making a copy or renaming).
If no complete copy of the log file is available, then issue the ROLLFORWARD DATABASE command with the STOP option which will complete the rollforward recovery at the current position in the log files.

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

SQL4974W The ROLLFORWARD DATABASE QUERY STATUS command encountered sqlcode `sqlcode`.

Explanation

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

User response

Look up the sqlcode sqlcode in the Message Reference, or online to determine the problems on the failed nodes. Take the required corrective actions, then continue the forward recovery on these nodes.

SQL4975W Roll-forward operation was canceled successfully. The database or selected table spaces have to be restored on members or nodes `node-list`.

Explanation

A roll-forward operation was canceled before it successfully completed, and the database or selected table spaces are left in in an inconsistent state. The database or selected table spaces are in restore pending state on the listed members or nodes.

If ",..." is displayed at the end of the member or node list, see the administration notification log for the complete list of members or nodes.

Note: The member or node numbers provide useful information only in DB2 pureScale environments and partitioned database environments. Otherwise, the information should be ignored.

User response

Restore the database or selected table spaces on the listed members or nodes. The table spaces that are in restore pending state can be identified on the specified members or nodes by the MON_GET_TABLESPACE table function. In environments other than DB2 pureScale environments, you can also use the db2dart utility.

SQL4976N This command cannot be submitted on a non-catalog node.

SQL4980N Recovery on database `name` has encountered a corrupt log file `log-file` on database partition `dbpart-num` and log stream `log-stream-ID`.

Explanation

A corrupt log file has been encountered during recovery of the database.

It is possible that a checksum error occurred on a log page. A checksum error indicates that the information in a log page on disk does not match the information that is expected by DB2. The content of this log page cannot be trusted.

User response

Possible actions include:

Run hardware diagnostics to check if the system is experiencing any hardware problems.
If there is another copy of this log file available, put the file in the database log directory or the overflow log path and reissue the command.
For a database rollforward operation in a non-partitioned database environment where a copy of the log file is unavailable, issue a rollforward stop command. This will bring the database to a point before the corrupted log file was encountered. It is important to note that log data beyond this point will not be available.
For a database rollforward operation in a partitioned database environment where a copy of the log file is unavailable, restore each database partition and issue a point in time rollforward to a stop time before the corrupt log file is encountered. It is important to note that log database beyond this point will not be available.
If the problem persists, save a copy of this corrupted file for analysis by IBM Support. IBM support will be able to determine which page is corrupted.

If trace was active, invoke the Independent Trace Facility at the operating system command prompt.

Environment: Outer Precompiler Using Precompiler Services API
Required information:
- Problem description
- SQLCODE
- SQLCA contents if possible
- Trace file if possible.

SQL4000 - SQL4999

SQL4001N The character character in column column on line line is not valid.

Explanation

User response

SQL4002N token-1 and token-2 are undeclared host variables that cannot both be used as descriptor names in a single SQL statement.

Explanation

User response

SQL4003N The SQL statement on line line is not supported by this version of the precompiler.

Explanation

User response

SQL4004N The package name is not valid.

Explanation

User response

SQL4005N An invalid token token was found starting in position position on line line.

Explanation

User response

SQL4006N The structures are nested too deeply.

Explanation

User response

SQL4007N The host structure host-structure has no fields.

Explanation

User response

SQL4008N The host variable name cannot be uniquely referenced even with full qualification.

Explanation

User response

SQL4009N The expression for data length is invalid.

Explanation

User response

SQL4010N Illegal nesting of Compound SQL statements.

Explanation

User response

SQL4011N Invalid SQL sub-statement in a Compound SQL statement.

Explanation

User response

SQL4012N Invalid use of COMMIT in a Compound SQL statement.

Explanation

User response

SQL4013N An END COMPOUND statement was found without a previous BEGIN COMPOUND statement.

Explanation

User response

SQL4014N Invalid Compound SQL syntax.

Explanation

User response

SQL4015N An error has occurred during preprocessing.

Explanation

User response

SQL4016N The preprocessor specified cannot be found.

Explanation

User response

SQL4017W Preprocessing has completed successfully.

Explanation

User response

SQL4018W Starting to process the preprocessed file preprocessed-file.

Explanation

User response

SQL4019W Completed processing the preprocessed file preprocessed-file.

Explanation

User response

SQL4020N The 'long' host variable token-1 is not valid. Use 'sqlint32' instead.

Explanation

User response

SQL4100I The sqlflag-type SQL language syntax is used for syntax checking by the flagger.

Explanation

User response

SQL4102W An SQL syntax deviation has occurred at the token starting with the text text.

Explanation

User response

SQL4103W A data definition statement is not within a CREATE SCHEMA statement.

Explanation

User response

SQL4104W There is a non-standard embedded comment.

Explanation

User response

SQL4105W An SQL syntax deviation has occurred. The statement is not complete.

Explanation

User response

SQL4106W The identifier identifier is more than 18 characters.

Explanation

User response

SQL4107W Column column has an invalid length, precision, or scale attribute.

SQL4001N The character `character` in column `column` on line `line` is not valid.

SQL4002N `token-1` and `token-2` are undeclared host variables that cannot both be used as descriptor names in a single SQL statement.

SQL4003N The SQL statement on line `line` is not supported by this version of the precompiler.

SQL4005N An invalid token `token` was found starting in position `position` on line `line`.

SQL4007N The host structure `host-structure` has no fields.

SQL4008N The host variable `name` cannot be uniquely referenced even with full qualification.

SQL4018W Starting to process the preprocessed file `preprocessed-file`.

SQL4019W Completed processing the preprocessed file `preprocessed-file`.

SQL4020N The 'long' host variable `token-1` is not valid. Use 'sqlint32' instead.

SQL4100I The `sqlflag-type` SQL language syntax is used for syntax checking by the flagger.

SQL4102W An SQL syntax deviation has occurred at the token starting with the text `text`.

SQL4106W The identifier `identifier` is more than 18 characters.

SQL4107W Column `column` has an invalid length, precision, or scale attribute.

SQL4109W The SET FUNCTION SPECIFICATION references column `column`.

SQL4110W A VALUE EXPRESSION containing `column` cannot include operators.

SQL4111W The COLUMN REFERENCE is missing or is invalid for the ALL column function `function`.

SQL4112W Column `column` is not unique and requires qualification.

SQL4114W Column `column` does not identify a column of a table within the current scope.

SQL4115W A column function that contains the OUTER REFERENCE column `column` is not in the subquery of a HAVING clause.

SQL4117W Operator `operator` is invalid in this context.

SQL4118W The `exptype` EXPRESSION is comparing incompatible data types.

SQL4121W The WHERE clause, GROUP BY clause or HAVING clause is invalid for the grouped view `schema-name`.`view`.

SQL4122W `schema-name`.`name` occurs more than once in a FROM clause.

SQL4124W A reference to column `column` derived from a column function is invalid in a WHERE clause.

SQL4126W The COLUMN REFERENCE for `column` must be an OUTER REFERENCE.

SQL4127W Column `column` is duplicated within the current scope.

SQL4128W The COLUMN REFERENCE for `column-name` should be a grouping column or should be specified within a column function.

SQL4129W DEGREE of table `schema-name`.`table` should be 1 when using a SELECT LIST of *.

SQL4130W The column function is not valid for the TABLE EXPRESSION beginning with table `schema-name`.`table`.