SQL7001N Unknown command command was requested.

Explanation

The command submitted to REXX could not be recognized.

The command cannot be processed.

User response

Verify that the command is a valid SQL statement and rerun the procedure. Note that all commands must be in uppercase.

SQL7002N The cursor name is invalid.

Explanation

The user specified an incorrect cursor name.

The command cannot be processed.

User response

Verify that the cursor name is one of the form “c1” through “c100”.

SQL7003N The statement name is invalid.

Explanation

The user has specified an incorrect statement name.

The command cannot be processed.

User response

Verify that the statement name is of the form “s1” through “s100”.

SQL7004N The syntax of the request is invalid.

Explanation

REXX was unable to parse the command string submitted.

The command cannot be processed.

User response

Use proper command syntax.

SQL7005W The cursor used by this OPEN statement has not been declared.

Explanation

An OPEN statement was attempted without a declaring a cursor.

The command cannot be processed.

User response

Insert a DECLARE statement before the OPEN statement and rerun the procedure.

SQL7006N Invalid keyword keyword given on request.

Explanation

The statement contains a not valid keyword keyword.

The command cannot be processed.

User response

Specify the correct keyword format.

SQL7007N REXX variable variable does not exist.

Explanation

A REXX variable that did not exist in the REXX variable pool was passed.

The command cannot be processed.

User response

Verify that all variable names in the host-variable list are assigned before the command that failed. Then run the procedure again.

SQL7008N REXX variable variable contains inconsistent data.

Explanation

A variable that contained inconsistent data was passed to REXX.

The command cannot be processed.

User response

If the variable is an SQLDA, verify that the data and length fields have been assigned correctly. If it is a REXX variable, verify that the type of data is appropriate to the command where it is being used.

SQL7009N Truncated REXX variable variable.

Explanation

The variable variable passed to REXX contained inconsistent data. The data string from variable was truncated.

The command cannot be processed.

User response

Verify that the data length is consistent with the length given in the input SQLDA, and run the procedure again.

SQL7010N Invalid scan ID ID.

Explanation

The scan ID variable passed to REXX did not exist or contained inconsistent or missing data.

The command cannot be processed.

User response

Verify that the data contained in the scan ID has been assigned correctly, and run the procedure again.

SQL7011N Required parameter parameter not given.

Explanation

The parameter parameter is required by REXX command syntax but was not specified.

The command cannot be processed.

User response

Specify the required parameter value, and run the procedure again.

SQL7012N Attempted ISL change while connected to a database.

Explanation

Isolation level (ISL) may not be changed while connected to a database.

The command is ignored.

User response

If a change in isolation level is necessary, disconnect from the current database, then set the isolation level and connect to the database.

SQL7013N Mismatched cursor and statement name or hold attribute.

Explanation

In REXX, the cursor and statement name form must be 'cnn' and 'snn,' where 'nn' is a number from 1 to 100. The numbers must be the same for a cursor and statement pair. Also, c1 through c50 are declared without hold and c51 through c100 with hold.

The command is ignored.

User response

Verify that the cursor and statement numbers match and rerun the procedure.

SQL7014N Incorrect number of host variable components.

Explanation

In REXX, the first component of a compound host variable lists a number which is not equal to the actual number of components defined.

The command is ignored.

User response

Verify that the number in the first component matches the number of components actually defined and rerun the procedure.

SQL7015N The variable name variable is not valid in REXX.

Explanation

The variable name specified is not valid in REXX. The name must conform to the language requirements.

The command cannot be processed.

User response

Change the name to one that conforms to the REXX requirements and resubmit the command.

SQL7016N Invalid syntax provided to the SQLDB2 interface. Related Error: db2-error.

Explanation

Invalid syntax was provided to the SQLDB2 interface, e.g. both an input file and a command were specified.

User response

Look up the related error code for more information.

SQL7032N SQL procedure procedure-name not created. Diagnostic file is file-name.

Explanation

SQL Procedure procedure-name was not created. One of the following has occurred:
  • Support for SQL stored procedures is not installed and configured on this server. You need to have the IBM Data Server Client and a C compiler installed on the server to create SQL procedures. You may need to set the DB2 registry variable DB2_SQLROUTINE_COMPILER_PATH to point to a script or batch file that contains environment settings for the C compiler on your platform.
  • DB2 failed to precompile or compile the SQL stored procedure. DB2 creates an SQL procedure as a C program that contains embedded SQL. Errors not found during the initial parsing of the CREATE PROCEDURE statement can be found during the precompile or compile stage.

For UNIX platforms, the full path of the file that contains diagnostic information is:

$DB2PATH/function/routine/sqlproc/ \
$DATABASE/$SCHEMA/tmp/file-name

where $DATABASE represents the name of the database, and $SCHEMA represents the schema name of the SQL procedure.

For Windows operating systems, the full path of the file that contains diagnostic information is:

%DB2PATH%\function\routine\sqlproc\ \
%DATABASE%\%SCHEMA%\tmp\file-name

where %DATABASE% represents the name of the database, and %SCHEMA% represents the schema name of the SQL procedure.

User response

Ensure that both a compatible C compiler and a DB2 Application Development Client are installed on the server. If a precompile or compile error occurred, refer to the messages from the precompiler or compiler in the diagnostic file file-name.

Ensure that the DB2 registry variable DB2_SQLROUTINE_COMPILER_PATH is set to point to a script or batch file that sets up the C compiler environment. On a UNIX operating system, for example, you may create a script called “sr_cpath” in the /home/DB2INSTANCE/sqllib/function/routine directory. To set the DB2 registry variable DB2_SQL_ROUTINE_COMPILER_PATH accordingly, issue the following command: 
db2set DB2_SQLROUTINE_COMPILER_PATH =
/home/DB2INSTANCE/sqllib/function/routine/sr_cpath

sqlcode: -7032

sqlstate: 42904

SQL7035W The executable of the SQL procedure procedure-name is not saved in the database catalog.

Explanation

The executable of the SQL procedure exceeds the limit of 2 megabytes and therefore cannot be stored in the database catalog. It will not be recovered automatically at database restore time or on ROLLBACK of a DROP PROCEDURE statement.

User response

If the warning resulted from a CREATE PROCEDURE statement, ensure that you keep a backup of the executable associated with SQL procedure procedure-name. If the warning was issued during a restore operation or a ROLLBACK of a DROP PROCEDURE statement, then the executable associated with procedure-name must be manually synchronized with the SQL procedure that is defined in the catalog.

sqlcode: +7035

sqlstate: 01645

SQL7099N Invalid error error has occurred.

Explanation

A REXX internal error has occurred.

The command cannot be processed.

User response

Verify that REXX is installed properly and rerun the procedure. If the error continues, note the error number and call the dealer.

SQL8000N DB2START processing failed; a valid product license was not found. If you have licensed this product, ensure the license key is properly registered. You can register the license using the db2licm command. The license key can be obtained from your licensed product CD.

Explanation

A valid license key could not be found and the evaluation period has expired.

User response

Install a license key for the fully entitled version of the product. You can obtain a license key for the product by contacting your IBM representative or authorized dealer.

SQL8001N An attempt to connect to the database failed due to a product license problem.

Explanation

The connection attempt failed due to one of the following licensing issues:

  • A license key is not present.
  • A license key has not been correctly installed.
  • A license key has expired.
  • This product edition does not support a license key.

User response

Instruct your database administrator to verify that a valid license key for the database product is installed correctly, and has not expired.

  • Use the db2licm -l command to view licenses.
  • Use the db2licm -a command to register a license.
  • You can obtain a license key for the product by contacting your IBM representative or authorized dealer.

sqlcode: -8001

sqlstate: 42968

SQL8002N An attempt to connect to a host failed due to a missing DB2 Connect product or invalid license.

Explanation

If connecting directly to a host server, a DB2 Connect product with a valid license may not be present on your machine.

If connecting to a host server through a DB2 Connect gateway, a valid license may not be present on the DB2 Connect gateway.

User response

Instruct your database administrator to check the following:

If connecting directly to the host, first ensure that a DB2 Connect product is present and that the appropriate license key is installed on your machine and is unexpired.

If connecting through a DB2 Connect gateway, ensure that the appropriate license key is installed on the gateway and is unexpired.

  • To view licenses, use the db2licm -l command.
  • To register a license, use the db2licm -a command.
  • You can obtain a license key for the product by contacting your IBM representative or authorized dealer.

Note: Some database product editions may not support connections to a host server.

sqlcode: -8002

sqlstate: 42968

SQL8003N A valid license key was not found for the requested function.

Explanation

The current license key(s) do not allow the requested functionality.

User response

Purchase the license key for this function from your IBM representative or authorized dealer and update your license using the db2licm command.

SQL8004N A valid license key was not found for the requested function.

Explanation

The current license key(s) do not allow the requested functionality.

User response

Examine the administration notification log for more information.

SQL8005N The license certificate license-certificate-file-name was not applied because a conflicting license certificate is already registered on the system. Conflicting license certificate: conflicting-license-certificate-name.

Explanation

To license your product, you must register the appropriate license key with your database product. There are some restrictions on the supported combinations of licenses. This message is returned when an attempt is made to apply an unsupported combination of licenses:

  • An attempt was made to apply the DB2 pureScale feature license on a system on which either the DB2 Advanced Workgroup Server Edition terabyte license or the DB2 Advanced Enterprise Server Edition terabyte license is already registered.
  • An attempt was made to apply the DB2 Advanced Workgroup Server Edition terabyte license or the DB2 Advanced Enterprise Server Edition terabyte license on a system on which the DB2 pureScale feature license is already registered.

User response

Remove the conflicting license by issuing the db2licm -r command, and then apply the new license again.

SQL8006W The product product-name does not have a valid license key registered. If you have licensed this product, ensure the license key is properly registered. You can register the license by using the db2licm command. The license key can be obtained from your licensed product CD. If a license key is not registered, this product will be enabled for a number day evaluation period. USE OF THE PRODUCT FOR THE EVALUATION PERIOD CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE AGREEMENT located in the installation path of this product in the license directory.

Explanation

A valid license key has not been installed for this product. The product will be enabled to operate for a limited period of time for evaluation purposes. THE EVALUATION PERIOD IS CONTROLLED BY A TIME DISABLING DEVICE.

User response

If you have purchased a fully entitled version of this product, install your license key as described in the product installation documentation. If you have already installed the license key, verify your license file for accuracy.

USE OF THE PRODUCT FOR THE EVALUATION PERIOD IS SUBJECT TO THE TERMS OF THE IBM LICENSE AGREEMENT AND LICENSE INFORMATION DOCUMENT FOR THIS PRODUCT. YOUR USE OF THE PRODUCT DURING THE EVALUATION PERIOD CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS.

If you do not accept the terms, you are not authorized to use the product and you must de-install it. You can obtain a license key for the fully authorized program with the product by contacting your IBM representative or authorized dealer.

SQL8007W There are number day(s) left in the evaluation period for the product product-name. For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license by using the db2licm command line utility. The license key can be obtained from your licensed product CD.

Explanation

A valid license key has not been installed for this product. The evaluation period will expire after the specified number of days.

User response

The product is operating in evaluation mode, and is enabled for a limited period of time. When the evaluation period has expired it will not execute until a license key for the fully entitled version of the product is installed.

You can obtain a license key for the product by contacting your IBM representative or authorized dealer.

sqlcode: +8007

sqlstate: 0168H

SQL8008N The product text does not have a valid license key installed and the evaluation period has expired. Functions specific to this product are not enabled.

Explanation

A valid license key could not be found and the evaluation period has expired.

User response

Install a license key for the fully entitled version of the product. You can obtain a license key for the product by contacting your IBM representative or authorized dealer.

SQL8009W The number of concurrent users of the DB2 Workgroup product has exceeded the defined entitlement of number. Concurrent user count is number.

Explanation

The number of concurrent users has exceeded the number of defined DB2 concurrent user entitlements.

User response

Contact your IBM representative or authorized dealer to obtain additional DB2 user entitlements and update the DB2 license information using the db2licm command.

sqlcode: +8009

sqlstate: 01632

SQL8010W The number of concurrent users of the DB2 Connect product has exceeded the defined entitlement of number. Concurrent user count is number.

Explanation

The number of concurrent users has exceeded the number of defined DB2 concurrent user entitlements.

User response

Contact your IBM representative or authorized dealer to obtain additional DB2 user entitlements and update the DB2 license information using the db2licm command.

sqlcode: +8010

sqlstate: 01632

SQL8011W One or more database partitions does not have a valid DB2 license key installed for the product-name product.

Explanation

A valid license key has not been installed for this product on all database partitions. The product will be enabled to operate for a limited period of time for evaluation purposes. THE EVALUATION PERIOD IS CONTROLLED BY A TIME DISABLING DEVICE.

User response

If you have purchased a fully entitled version of this product, please install your license key as described in the product installation documentation. If you have already installed the license key, please verify your license file for accuracy.

USE OF THE PRODUCT FOR THE EVALUATION PERIOD IS SUBJECT TO THE TERMS OF THE IBM EVALUATION AGREEMENT IN THE EVALUATE.ARG FILE. YOUR USE OF THE PRODUCT DURING THE EVALUATION PERIOD CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS.

If you do not accept the terms, you are not authorized to use the product and you must de-install it. You can obtain a license key for the fully authorized program with the product by contacting your IBM representative or authorized dealer.

SQL8012W The number of concurrent users of the DB2 Enterprise product has exceeded the defined entitlement of number. Concurrent user count is number.

Explanation

The number of concurrent users has exceeded the number of defined DB2 concurrent user entitlements.

User response

Contact your IBM representative or authorized dealer to obtain additional DB2 user entitlements and update the DB2 license information using the db2licm command.

sqlcode: +8012

sqlstate: 01632

SQL8013W The number of concurrent database connections to the DB2 Connect product has exceeded the defined entitlement of number. Database connection count is number.

Explanation

The license for the DB2 Connect product you are using supports a limited number of concurrent database connections. You have requested a number of connections that exceeds this limit.

User response

Upgrade to a version of the DB2 Connect product with a higher limit of concurrent database connections.

DB2 Connect Enterprise Edition users: obtain licenses for additional users by purchasing Additional User Packs.

sqlcode: +8013

sqlstate: 01632

SQL8014N The version of the DB2 Connect product you are using is not licensed for use with TCP/IP protocol. Upgrade to a full function DB2 Connect product to use TCP/IP.

Explanation

This version of DB2 Connect is limited to SNA connectivity. TCP/IP connections are not supported.

User response

Upgrade to a full function DB2 Connect product.

sqlcode: -8014

sqlstate: 42968

SQL8015N The version of the DB2 Connect product you are using is not licensed for updating multiple databases in the same transaction.

Explanation

This version of DB2 Connect is limited to working with a single database in a transaction. It does not support 2-phase commit protocol.

User response

Upgrade to a full function DB2 Connect product to be able to update multiple databases in a single transaction.

sqlcode: -8015

sqlstate: 42968

SQL8017W The number of processors on this machine exceeds the defined entitlement of licensed-quantity for the product product-name. The number of processors on this machine is processor-quantity. You should purchase additional processor based entitlements from your IBM representative or authorized dealer and update your license using the db2licm command.

User response

SQL8018W The number of concurrent users for this product has exceeded the defined entitlement of number. Concurrent user count is number.

Explanation

The number of concurrent users has exceeded the number of defined concurrent user entitlements.

User response

Contact your IBM representative or authorized dealer to obtain additional user entitlements and update the DB2 license information using the db2licm command.

sqlcode: +8018

sqlstate: 01632

SQL8019N There was an error updating the license for the OLAP Starter Kit. RC = reason-code.

Explanation

The license utility could not update the OLAP Starter Kit license because of an unknown error.

User response

Try the command again. If the problem persists, please contact an IBM service representative.

sqlcode: -8019

SQL8020W The number of concurrent connectors for one server has exceeded the defined entitlement of number-sources. Current number of connectors is number-entitled.

Explanation

The number of concurrent connectors has exceeded the number of defined entitlements.

User response

Contact your IBM representative or authorized dealer to obtain additional entitlements and then update the DB2 license information using the db2licm command.

SQL8022N Database partitioning feature is being used without database partitioning license. The database manager has detected that the database partitioning feature is being used but the database partitioning feature license has not been installed. Ensure that you have purchased database partitioning feature entitlements from your IBM representative or authorized dealer and have updated your license using the db2licm command.

User response

SQL8023N The number of concurrent users for product-name product has exceeded the defined entitlement of entitlement. Concurrent user count is count. You should purchase additional user based entitlements from your IBM representative or authorized dealer and update your license using the the db2licm command.

User response

SQL8024N A valid license key was not found for the requested function. The current license key for product-name product does not allow the requested functionality. Purchase the license key for this function from your IBM representative or authorized dealer and update your license using the db2licm command.

User response

SQL8025W The connection to the server server-name is not allowed. A valid WebSphere Federated Server license could not be found.

Explanation

Your current WebSphere Federated Server license does not allow connection to the specified data source.

User response

Refer to the Administration Notification log for possible causes of this error. If this problem persist, contact IBM Support.

SQL8026W DB2 server has detected that a valid license for this product has not been registered.

Explanation

Registration of a valid license key is required in order to comply with the terms and conditions of your License Agreement. The license keys for this product are located on this product's media in the 'license' directory.

User response

Use the db2licm command to register the appropriate licenses that you have purchased. The License Agreement text is located in the 'license' directory in the installation directory of this product.

SQL8027N The table partitioning feature is being used without a DB2 Enterprise Server Edition license. The database manager has detected that the table partitioning feature is being used without a DB2 Enterprise Server Edition license. Ensure that you have purchased a valid DB2 Enterprise Server Edition entitlement from your IBM representative or authorized dealer and have updated your license using the db2licm command.

User response

SQL8028N The feature feature is being used without a license license. The database manager has detected that this feature is being used without the appropriate entitlements. Ensure that you have purchased appropriate entitlements from your IBM representative or authorized dealer and have updated your license using the db2licm command.

User response

SQL8029N A valid license key was not found for the requested functionality. Reference numbers: list-of-numbers.

Explanation

License keys are required for all database products. To use the database product features or to be in compliance with your current product entitlement, you must apply the licenses manually after installation.

This message is returned when the database manager detects that a feature or functionality is being used for which no valid license key is registered.

The list of function numbers in list-of-numbers identifies one or more features or functionality that is missing a valid license key:

1

Column-organized tables

2

DB2 pureScale Feature

3

Table partitioning

4

Database partitioning

5

Row compression

6

Index compression

7

Workload management

8

DB2 native encryption

User response

Purchase the license key from your IBM representative or authorized dealer, and then update your license using the db2licm command.

sqlcode: -8029

sqlstate: 560D8

SQL8030W The license for the product product will expire in number day(s). You can register and update your license using the db2licm command. The license key can be obtained from your licensed product CD.

User response

SQL8100N The table is full.

Explanation

When creating a database the following parameters may be specified:

  • maximum number of pages per segment per file
  • number of segments

Each table part may now have multiple files within the database segments. The file can grow until it reaches its maximum size in a segment (maximum number of pages per segment) and then it moves to the next segment to add more data. This occurs until it has used the maximum number of pages per segment in all configured segments, and the table becomes full.

Therefore, the total amount of space per database part is the product of the maximum number of pages and the number of segments. The table will be full if any of the table parts use all of their configured space.

Federated system users: this situation can also be detected by the data source.

User response

  • Delete rows from the table
  • Reorganize the table to make more space
  • Create a new database with larger values for maximum pages per segment and number of segments, back up the original database and restore to the new database.

Federated system users: isolate the problem to the data source failing the request and:

  • Take the necessary steps to increase the space in the table at the data source.
  • If the table is on the federated server, create a new database with larger values for maximum pages per segment and number of segments. Back up the original database and restore to the new database.

SQL8101N A Database segment may be incorrect.

Explanation

This error could occur in two ways:
  1. Every database segment has an identifier file. The file may be missing or the contents of the file may be incorrect.
  2. One, or more, previously allocated database segments are missing.

User response

  • Check to ensure that the file systems are mounted correctly
  • Restore the database from a backup
  • Call your IBM service representative

SQL9301N An invalid option is specified or an option parameter is missing.

Explanation

Either the option specified is invalid or an option parameter is not specified.

The command cannot be processed.

User response

Correct the option and resubmit the command.

SQL9302N Invalid option parameter: option-parameter.

Explanation

The option parameter specified is invalid.

The command cannot be processed.

User response

Correct the option parameter and resubmit the command.

SQL9303N No option is specified.

Explanation

The required option option is not specified.

The command cannot be processed.

User response

Resubmit the command with the required option.

SQL9304N Unable to open file filename for writing.

Explanation

The command cannot be processed.

User response

Ensure that the system can access the file.

SQL9305N The name is too long. The maximum length is max-length.

Explanation

The <name> is longer than the maximum length of <max-length>.

The command cannot be processed.

User response

Ensure that the <name> does not exceed the maximum length.

SQL9306N One or more of the field names are too long. The maximum length is max-length.

Explanation

The total length of a field name includes the specified prefix and/or a column suffix, which can either be its name or its number. This total length must not exceed the maximum length.

The command cannot be processed.

User response

Ensure that all the field names do not exceed the maximum length.

SQL9307N Remarks cannot be retrieved from the database. Error code = sqlcode.

Explanation

An error has occurred when attempting to retrieve the remarks of a column from the database.

The command cannot be processed.

User response

Check the error code for more information.

SQL9308W SQL data type sqltype of the column colname is not supported.

Explanation

The SQL data type sqltype is not supported in the specified host language.

No declaration is generated for this column.

User response

Ensure that this is the desired table.