SQL1509N The statement cannot be processed because all available transports are in use, and no more transports can be created. Reason code: reason-code.

Explanation

A transport is a physical connection to a database.

The reason that no more transports can be created is indicated by the given reason code:

1

No memory is available for additional transports.

2

The value set for the configuration parameter maxTransports has been reached.

User response

Respond to this error according to the reason code:

1

Resolve the memory shortage:

  1. Make more memory available to the application. For example, terminate any unused connections.
  2. Rerun the statement.
2

Change the database configuration to allow more transports:

  1. Set the maxTransports configuration parameter to a higher value in the db2dsdriver.cfg configuration file.
  2. Restart the application.

sqlcode: -1509

sqlstate: 57060

SQL1510N The result set element list in a WITH RETURN TO CLIENT clause of a CREATE PROCEDURE statement is invalid. The following reason code indicates why the result set element list is invalid: reason-code

Explanation

You can return multiple, interleaved result sets from stored procedures by using the WITH RETURN TO CLIENT clause in the CREATE PROCEDURE statement.

The given reason code indicates what is invalid about the specified result set elements:

1

The list of result set elements contained a value that is not a positive integer. Result set elements specified with WITH RETURN TO CLIENT must be positive integers. For example, the following are not valid result set elements: -2, 0, 2.3

2

The list of result set elements contained duplicate entries. You cannot include a result set element multiple times in the list. For example, the following list is not valid: (1, 2, 2).

3

The result set elements were not specified in ascending order. For example, the following list is valid: (1, 3). The following list is not valid: (3, 1).

4

An element in the result set list was greater than 32767. The largest valid result set list element is 32767.

The stored procedure was not created.

User response

Call the CREATE PROCEDURE statement again specifying valid result set elements.

SQL1511N The specified clause, clause, is not supported for service subclasses.

Explanation

The clause, clause, that is specified is valid for a service superclass but is not valid for a service subclass.

User response

Remove the unsupported clause, or specify a service superclass.

sqlcode: -1511

sqlstate: 5U044

SQL1512N ddcstrc could not write to the specified file.

Explanation

ddcstrc was not able to write the trace information to the filename that it has been instructed to write to.

User response

Ensure that the filename specified is valid for your file system. If a filename is not specified, ensure that you have the necessary permission to write to the default file ddcstrc.tmp.

SQL1513W ddcstrc has not been turned off.

Explanation

Because of an error condition ddcstrc has not been turned off. This was done to ensure that the trace information will not be lost before being safely placed in a file.

User response

Correct the ddcstrc error condition reported prior to this error and attempt to turn off the trace again.

SQL1514N DB2START with the ADMIN MODE option cannot proceed because the specified member is part of a DB2 pureScale environment.

Explanation

The db2start command is not compatible with the ADMIN MODE option in a DB2 pureScale environment.

User response

If you need to restrict access to a certain member, use the QUIESCE option of the db2stop or STOP DATABASE MANAGER commands.

SQL1515N The user mapping cannot be created for server server-name because of a conflict with an existing user mapping or federated server option. Reason code reason-code.

Explanation

A user mapping defined for PUBLIC cannot coexist on a server with user mappings defined for individual users or on a server defined with the federated server option FED_PROXY_USER. The attempt to create the user mapping failed.

User response

The reason code reason-code indicates the particular situation. The following actions can resolve the situation.

1

A user mapping for an individual user is being defined but server server-name already has a user mapping defined for PUBLIC. Drop the user mapping defined for PUBLIC from the server and create the user mapping again.

2

A user mapping for PUBLIC is being defined but server server-name already has a user mapping defined for an individual user. Drop all user mappings defined for individual users from the server and create the user mapping for PUBLIC again.

3

A user mapping for PUBLIC is being defined but server server-name is already defined with federated server option FED_PROXY_USER. Alter the server to remove the FED_PROXY_USER option and create the user mapping for PUBLIC again.

sqlcode: -1515

sqlstate: 428HE

SQL1516N The ALTER SERVER statement cannot add the FED_PROXY_USER federated server option to server server-name because of a conflict with an existing user mapping.

Explanation

The FED_PROXY_USER federated server option cannot be added to server server-name because it has an existing user mapping defined for PUBLIC. The ALTER SERVER statement failed.

User response

Drop the user mapping defined for PUBLIC from the server and issue the ALTER SERVER statement again.

sqlcode: -1516

sqlstate: 428HE

SQL1517N db2start failed because the cluster manager resource states are inconsistent.

Explanation

The db2start command has failed to start the processes because there are inconsistencies between the cluster manager resource model and the db2nodes.cfg file. These inconsistencies occur when there is a modification (intentional or unintentional) to db2nodes.cfg that is not synchronized with the cluster manager.

A DB2 pureScale instance or new resources cannot be started until the inconsistencies have been resolved. DB2 resources that are already started are not affected by this error.

User response

Restore the db2nodes.cfg file to an earlier configuration (one that was synchronized with the cluster manager). If this cannot be done, repair the cluster resource model. To do this, issue a global db2stop to stop the instance, and run the db2cluster tool with the -repair option.

SQL1520N Buffersize must be a numeric value greater than or equal to 65536.

Explanation

The user specified an invalid buffersize for the ddcstrc command.

User response

Ensure that the buffersize used is numeric and greater than or equal to 65536 (64K). Note that the memory to be used will be a multiple of 64K. ddcstrc rounds down the buffersize specified to the nearest multiple of 64K.

SQL1522N The deactivate command failed at one or more members where indoubt transactions were detected for the given database.

Explanation

This message is returned when an attempt is made to explicitly deactivate a database using the DEACTIVATE DATABASE command or the sqle_deactivate_db API but the database could not be deactivated because indoubt transactions were detected for the given database at one or more members.

The database has been deactivated at members where no indoubt transactions were detected. At members where indoubts were detected, the database will be left activated or in the same state it was in, prior to the deactivate command being issued.

User response

Respond to this error in one of the following ways:

  • Wait for the transaction manager to resolve the indoubt transactions:
    1. Identify the indoubt transaction that involve the database using the LIST INDOUBT TRANSACTIONS command.
    2. Monitor the indoubt transactions until the transaction manager automatically resolve the indoubt transactions.
    3. Resubmit the DEACTIVATE DATABASE command or call the sqle_deactivate_db API again.
  • Resolve the transactions manually:
    1. Identify the indoubt transaction that involve the database using the LIST INDOUBT TRANSACTIONS command.
    2. Manually resolve the indoubt transactions. Resubmit the DEACTIVATE DATABASE command or call the sqle_deactivate_db API again.
  • Force the database deactivation by calling the DEACTIVATE DATABASE command with the FORCE option:
    1. Determine on which members the deactivation operation failed by reviewing the db2diag log files.
    2. On each member on which the deactivation operation failed, call the DEACTIVATE DATABASE command with the FORCE option.

      Any indoubt transactions will be left unresolved.

SQL1523N An extent movement operation attempted to access the table space named tablespace-name while another process was already accessing that table space. Reason code = reason-code.

Explanation

An extent movement operation attempted to reclaim unused storage to lower the high water mark but a utility or process is already accessing the table space. The extent movement operation resulted from an ALTER TABLESPACE statement specifying a REDUCE or LOWER HIGH WATER MARK clause.

The utility or process that is affecting the table space is indicated by one of the following reason codes:

1

The table space is in a backup pending state.

2

The table space is in a restore in progress state.

3

The table space is in a restore pending or a recovery pending state.

4

The table space is in a rebalance in progress state.

5

The table space is in a rollforward in progress state.

6

The table space is in a rollforward pending state.

7

The table space is in a redistribute in progress state.

8

The table space is in a quiesce shared state.

9

The table space is in a quiesce update state.

10

The table space is in a quiesce exclusive state.

11

The table space is in a pstat_deletion state.

12

The table space is in a pstat_creation state.

13

The table space is in a stordef pending state.

14

The table space is in a disable pending state.

15

The table space is in a move in progress state.

User response

Refer to the documentation on the different states that a table space can be in. The documentation also tells you how to change the state to one that will allow the desired extent movement operation, or you can wait until the operation in process completes. For example, you can back up the table space to change the state from backup pending. Reissue the statement.

sqlcode: -1523

sqlstate: 55039

SQL1524N The request cannot occur until all applications in the instance are aware of the new database partition server.

Explanation

A new database partition server has been added online to the instance. When this event occurs, an existing application becomes aware of the new database partition server at its next transaction boundary (the exception occurs if the application has an open WITH HOLD cursor). A new database application becomes aware of the new database partition server at its first request. Until all applications in the instance are aware of the new database partition server, CREATE DATABASE PARTITION GROUP, ALTER DATABASE PARTITION GROUP, DROP DATABASE PARTITION GROUP, REDISTRIBUTE DATABASE PARTITION GROUP, and DROP DATABASE requests are not allowed.

User response

One of the following, then try the request again.

  • Wait until all applications are aware of the new database partition server.
  • If waiting is not an option, terminate the application that is causing the request to fail. You can identify this application by using the db2pd -addnode oldviewapps command or the db2pd -addnode oldviewapps detail command.
  • If multiple database applications are preventing the request, you can force all the applications or quiesce the instance.

sqlcode: -1524

sqlstate: 55077

SQL1525N An error occurred when starting the DB2 security daemon.

Explanation

An unexpected error occurred when starting the DB2 security daemon.

User response

Retry the DB2START command. If the problem persists, contact IBM Service.

SQL1526N db2start failed because DB2VIA support was not started. Reason code reason-code.

Explanation

DB2VIA support was not started successfully at db2start time. The reason code indicates the error:
  1. The VIPL library specified in DB2_VI_VIPL registry variable could not be loaded.
  2. The Device name specified in DB2_VI_DEVICE registry variable could not be opened.
  3. DB2 does not support the VIA implementation installed.

User response

  1. Make sure the DB2 registry DB2_VI_VIPL is properly set and the name specified in DB2_VI_VIPL is in the %PATH% environment variable.
  2. Make sure the DB2 registry DB2_VI_DEVICE is properly set.
  3. DB2 only supports a VIA implementation that supports at least Reliable Delivery reliability level. It is also required that the VIA implementation complies with Intel Virtual Interface Architecture Implementation Guide and passes the conformance Suite. Make sure the VIA implementation you chose satisfies these requirements.

SQL1528W An enabled workload is associated with a disabled service class.

Explanation

Incoming connections will be assigned to the enabled workload workload-name, but the workload cannot map any new requests to the service class service-class-name, because the service class is disabled. Any new request mapped or remapped to the disabled service class will receive an SQL4714N error message.

User response

If necessary, correct the issue by disabling the workload or by enabling the service class. Otherwise, no action is required.

sqlcode: +1528

sqlstate: 01HN0

SQL1529N The last remaining CF cannot be dropped.

Explanation

In a DB2 pureScale environment at least one cluster caching facility (CF) must exist. The last one cannot be dropped.

User response

Add a new CF and activate the changes before dropping this one.

SQL1530W The specified degree of parallelism will be ignored because the system is not enabled for intra-partition parallelism.

Explanation

Either the DEGREE bind option was specified with a value greater than 1 or the SET CURRENT DEGREE statement was executed with a value greater than 1, but the database manager was not enabled for intra-partition parallelism.

The database manager must be started with the intra_parallel configuration parameter set to ON in order for the instance to be enabled for intra-partition parallelism.

The statement or command completed successfully, but the degree specification was ignored.

User response

If you want to use intra-partition parallelism restart the database manager with the intra_parallel configuration parameter set to ON.

Otherwise use a value of 1 or ANY for the degree specification.

sqlcode: +1530

sqlstate: 01623

SQL1531N The connection failed because the name specified with the DSN connection string keyword could not be found in either the db2dsdriver.cfg configuration file or the db2cli.ini configuration file. Data source name specified in the connection string: DSN.

Explanation

The db2dsdriver.cfg configuration file contains database directory information and client configuration parameters for use by some IBM data server clients and drivers.

The CLI/ODBC initialization file (db2cli.ini) contains various keywords and values that can be used to configure the behavior of CLI and the applications using CLI.

This message is returned when a data source name is specified in a connection string with the "DSN" connection keyword but the specified data source name cannot be found in either of the following locations:

  • Specified with the "dsn alias" configuration keyword in the db2dsdriver.cfg configuration file
  • Specified as a section header in the db2cli.ini configuration file

User response

  1. Add the specified data source name to the db2dsdriver.cfg configuration file or the db2cli.ini configuration file.
  2. Stop and restart the application process for the new configuration settings to take effect.
  3. Resubmit the connection request to the specified data source name.

SQL1532N The db2dsdriver.cfg configuration file contains multiple entries for the database alias database-alias.

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 multiple identical database alias entries or multiple identical database entries.

User response

  1. Remove duplicate entries from the db2dsdriver.cfg configuration file.
  2. Stop the application process and start it again for the new db2dsdriver.cfg file settings to take effect.

SQL1533N The db2dsdriver.cfg configuration file contains multiple entries for a database with the following properties: database name database-name; server name server-name; and port number port-number.

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 multiple identical database alias entries or multiple identical database entries.

User response

  1. Remove duplicate entries from the db2dsdriver.cfg configuration file.
  2. Stop the application process and start it again for the new db2dsdriver.cfg file settings to take effect.

SQL1534N The call to db2dsdcfgfill failed because invalid command options were specified.

Explanation

You can use the db2dsdcfgfill command to create and populate a db2dsdriver.cfg configuration file based on the contents of the local database directory, node directory, and DCS directory.

This message is returned when an invalid parameter or parameter value is specified with the db2dsdcfgfill command.

User response

Run db2dsdcfgfill again, specifying valid command options.

SQL1535I The db2dsdcfgfill utility successfully created the db2dsdriver.cfg configuration file.

Explanation

The configuration file db2dsdriver.cfg contains database directory information and client configuration parameters in a human-readable format. You can create and populate the configuration file db2dsdriver.cfg using the db2dsdcfgfill utility.

User response

You do not need to respond to this message.

SQL1536N The db2dsdcfgfill utility failed to create the db2dsdriver.cfg configuration file. Reason code: reason-code.

Explanation

You can use the db2dsdcfgfill utility to create and populate a db2dsdriver.cfg configuration file based on the contents of the local database directory, node directory, and DCS directory.

The reason codes are as follows:

1

The db2dsdcfgfill utility could not create the db2dsdriver.cfg configuration file because there were insufficient system resources. For example, this error can happen if there is not enough room in the output directory to create the new file.

2

A non-severe, internal or system error occurred.

User response

Run the db2dsdcfgfill utility again.

If the problem persists, respond to this error according to the given reason code:

1

Resolve the system resources problem:

  1. Use operating system diagnostics tools to examine system resource data. For example, verify that there is enough space to create the new file.
  2. Make more system resources available. For example, free disk space.
  3. Run the db2dsdcfgfill utility again.
2

Work with IBM support to resolve the internal or system error:

  1. Collect diagnostic information using db2trace while running the db2dsdcfgfill utility.
  2. Contact IBM Support to investigate the collected db2trace diagnostic information.

SQL1537N The db2dsdcfgfill utility failed because an invalid value was passed to the command. Reason-code: reason-code.

Explanation

You can use the db2dsdcfgfill utility to create and populate a db2dsdriver.cfg configuration file based on the contents of the local database directory, node directory, and DCS directory.

The reason this message was returned is indicated by the given reason code:

1

The specified database manager instance does not exist on this client.

2

The specified database manager instance path is not valid. For example, the path might not exist, or the db2dsdcfgfill utilty might not have permission to access that directory.

3

The specified output directory is invalid. For example, the directory might not exist, or the db2dsdcfgfill utility does not have permission to create a file in that directory.

4

The specified db2cli.ini file path is invalid. For example, the directory might not exist, or the db2dsdcfgfill utility does not have permission to access that file or directory.

User response

Respond to this message according to the given reason code:

1

Run db2dsdcfgfill again, specifying a valid database manager instance.

2

Resolve the problem with the database manager instance directory:

  1. Determine why db2dsdcfgfill could not access the specified database manager instance directory. For example, determine if the permission settings of the directory prevent db2dsdcfgfill from accessing the directory.
  2. Address the reason db2dsdcfgfill could not access the specified database manager instance directory. For example, change the permission settings of the directory to allow db2dsdcfgfill to access the directory.
  3. Run db2dsdcfgfill again.
3

Resolve the problem with the output directory:

  1. Determine why db2dsdcfgfill could not access the specified output directory. For example, determine if the permission settings of the directory prevent db2dsdcfgfill from creating a file in the directory.
  2. Address the reason db2dsdcfgfill could not create the db2dsdriver.cfg configuration file in the specified directory. For example, change the permission settings of the directory to allow db2dsdcfgfill to create a file in the directory.
  3. Run db2dsdcfgfill again.
4

Resolve the problem with the db2cli.ini file path:

  1. Determine why db2dsdcfgfill could not access the specified file. For example, determine if the permission settings of the directory prevent db2dsdcfgfill from accessing a file in the directory.
  2. Address the reason db2dsdcfgfill could not access the db2cli.ini file in the specified directory. For example, change the permission settings of the directory to allow db2dsdcfgfill to read a file in the directory.
  3. Run db2dsdcfgfill again.

SQL1538N The following keyword is not supported in the current environment: keyword.

Explanation

The keyword you specified is not supported in a DB2 pureScale environment.

User response

Rerun the command or execute the SQL statement again specifying only supported keywords.

sqlcode: -1538

sqlstate: 56038

SQL1539N The load operation failed because the load target table is incompatible with exception tables in general or with the specific exception table in particular. Reason code: reason-code.

Explanation

You can efficiently move large quantities of data into newly created tables, or into tables that already contain data using the load utility.

You can create a consolidated report of all of the rows that violated unique index rules, range constraints, and security policies during a load operation using a load exception table. You specify a load exception table by using the FOR EXCEPTION clause of the LOAD command.

The reason code indicates the specific reason this error was returned:

1

The load target table uses LBAC security and has at least one XML column.

2

The load target table is partitioned and has at least one XML column.

3

The partition map for the load target table is not the same as the partition map for the specified load exception table.

A partition map determines the distribution of the rows of a table among database partitions. The distribution of the rows of the load target table must be the same as the distribution of the rows of the load exception table.

4

The exception table is column organized. Column-organized tables are not supported as exception tables.

User response

Re-issue the LOAD command without the FOR EXCEPTION option.

sqlcode: -1539

sqlstate: 5U049

SQL1540N An SQL statement or a DB2 utility encountered an error because a storage group or table space object is not accessible on a member. Object identifier: object-id. Member: member-id. Object type keyword: object-type-keyword.

Explanation

An SQL statement or a DB2 utility encountered an error because the storage group or table space where a database object resides is not accessible on this member. The SYSCAT.TABLESPACES catalog view can be used to identify the table space name given a table space identifier. The SYSCAT.STOGROUPS catalog view can be used to identify the storage group name given a storage group identifier. If the object identifier token value is "*N", a storage group file header is not accessible on this member.

User response

Verify that all database storage paths are accessible on this member and reissue the SQL statement, or issue the SQL statement on a different member.

sqlcode: -1540

sqlstate: 57048

SQL1541N Dropping the member failed because the specified member is the only member in this DB2 pureScale instance. The last member cannot be dropped.

Explanation

In a DB2 pureScale environment at least one member must exist. The last one cannot be dropped.

User response

  1. Add a new member using the db2iupdt command with the -add option.
  2. Drop the original member using the db2iupdt command with the -drop option.

SQL1542N Adding the CF failed because the maximum number of CFs in the database manager instance has been reached.

Explanation

A DB2 pureScale environment supports a maximum of 2 cluster caching facilities (CFs) for each database manager instance. This message is returned when an attempt is made to add more CFs than the maximum.

User response

  1. Drop one of the existing CFs using the db2iupdt command with the -drop option
  2. Add the new CF using the db2iupdt command with the -add option

SQL1543N The host specified for the CF is a duplicate.

Explanation

In a DB2 pureScale environment only one cluster caching facility (CF) can exist on a given host.

User response

Specify a different host that does not already have a CF.

SQL1544N Backup of a database following a topology change in a DB2 pureScale environment cannot be performed from a newly added member.

Explanation

Following a topology change in a DB2 pureScale environment, a backup of the database is required. This must be performed from one of the preexisting instance members.

User response

Perform the backup from one of the preexisting members.

SQL1545N Restore of a database image from a previous topology is not supported.

Explanation

In a DB2 pureScale environment, restore of an image with a topology different than the current database topology (different setup or number of members) is not permitted.

User response

Restore the image taken following the most recent topology change and proceed from there.

SQL1546N The rollforward operation failed because the rollforward utility encountered an event in the database logs through which rolling forward cannot continue. Reason code: reason-code.

Explanation

The reason code indicates what type of event was encountered in the logs:

1

A topology change that made transaction logs and table space backups that were created before the topology change incompatible with the database after the topology change:

  • A drop member operation
  • A restore of a pureScale database to a pureScale instance where the source member topology includes members that are not included in the target member topology
  • A restore of a Enterprise Server Edition database to a pureScale instance
  • A restore of a pureScale database to a Enterprise Server Edition instance

The rollforward utility cannot roll forward through these types of topology change. This message is returned when an attempt is made to roll forward through one of these types of topology change.

2

A non-recoverable upgrade operation. The rollforward utility cannot rollforward through this event.

3

A DB2 version change that made the transaction logs incompatible in the current DB2 version. The rollforward utility has stopped.

4

A DB2 version change that made a log record incompatible in the current DB2 version was encountered. The rollforward utility has stopped.

5

An invalid log record was encountered. The rollforward utility has stopped.

User response

If the reason code refers to an invalid log record, see the db2diag.log and attempt to correct the problem before proceeding.

If the reason code and your recovery scenario refers to one of the following conditions:

  • a topology change event
  • a non-recoverable upgrade operation
  • a DB2 version change event and you wish to stay in the current DB2 version
  • an invalid log record

then run the ROLLFORWARD DATABASE command with the STOP option to accomplish the following outcomes:

  • Stop the rolling forward of log records and complete the rollforward recovery process. All committed transactions have been restored up to the event that has stopped the rollforward operation.
  • Roll back any incomplete transactions.
  • Turn off the rollforward pending state of the database.
  • Provide access to the database or table spaces that are being rolled forward.

If the reason code refers to a version change event and you would like to proceed with the roll forward, then issue the ROLLFORWARD DATABASE command from the later version of the product to complete the operation.

SQL1547N The start or stop command failed because there was a previous incomplete add or drop operations.

Explanation

An attempt to add or drop a DB2 member or cluster caching facility (CF) failed. As a result, the start or stop command cannot be processed until the incomplete add or drop operation is corrected.

Use response

  1. Manually correct the failed add or drop operation using the db2iupdt command with the fixtopology parameter.

    Note that using the db2iupdt command with the fixtopology parameter always performs a drop operation to complete an incomplete add or drop operation.

  2. Resubmit the start or stop command.

User response

SQL1548N The REORG command failed because the ALLOW WRITE ACCESS and ALLOW READ ACCESS modes are not valid for a partitioned table.

Explanation

You can reorganize indexes or tables by using the REORG command. You can control what access users have to the affected index or table by using the following clauses:

  • ALLOW NO ACCESS
  • ALLOW READ ACCESS
  • ALLOW WRITE ACCESS

There are restrictions and requirements for how these ALLOW clauses can be used. For example, when the REORG INDEXES ALL command is run on a data partitioned table, the ALLOW WRITE ACCESS clause is supported only when one or more of the following clauses is also specified: ON DATA PARTITION, CLEANUP, and RECLAIM EXTENTS.

This message is returned when a data partitioned table is being reorganized and one of the ALLOW clauses is specified in a way that is not supported.

User response

Reissue the REORG command with the appropriate access mode for a partitioned table.

sqlcode: -1548

sqlstate: 5U047

SQL1549N The ON DATA PARTITION clause is not allowed with the command.

Explanation

A REORG TABLE command with the ON DATA PARTITION clause is not allowed on a table that meets both conditions:

  • It is in the reorg pending state.
  • One or more nonpartitioned indexes are defined on the table. A nonpartitioned index can be a user-defined index or a system-created index such as an XML PATH index that is created when the table contains an XML column.

User response

Issue the REORG TABLE command without the ON DATA PARTITION clause.

sqlcode: -1549

sqlstate: 5U047

SQL1550N The SET WRITE SUSPEND command failed because of the condition that is indicated by the reason code. Reason code = reason-code.

Explanation

You cannot issue the SET WRITE SUSPEND command until the condition indicated by reason-code is resolved:

1

The database is not activated.

2

A backup database operation is currently in progress for the target database.

3

A restore database operation is currently in progress for the target database.

4

Write operations have already been suspended for the database.

5

One of the following conditions exists:

  • The current state of one or more table spaces does not permit the suspension of write operations.
  • Changes to the buffer pools that are associated with the table spaces are still pending and do not permit the suspension of write operations.
6

An error occurred during an attempt to suspend write operations for the database.

In a DB2 pureScale environment, SQL1550N can be returned with reason code 6 if the SET WRITE command failed on one or more members in the DB2 cluster.

7

The database is quiesced or in a temporary state that does not permit the suspension of write operations. This can be caused, for example, by a quiesced database or instance, or by a database deactivation in progress.

8

Set write suspend is not supported on an HADR standby.

User response

Respond to this message according to the reason code:

1

Activate the database by issuing the ACTIVATE DATABASE command, and then reissue the SET WRITE SUSPEND command.

2

After the BACKUP procedure finishes, reissue the SET WRITE SUSPEND command.

3

After the RESTORE procedure finishes, reissue the SET WRITE SUSPEND command.

4

If you want to resume write operations for the database, issue the SET WRITE RESUME command.

5
  • View the table space states by using the MON_GET_TABLESPACE table function. If there are table spaces that are in a pending state, issue the appropriate command to bring them out of the pending state before reissuing the SET WRITE SUSPEND command.
  • If an operation is in progress for one or more table spaces, wait until the operation is complete before reissuing the SET WRITE SUSPEND command. For example, if the self-tuning memory manager is enabled, buffer pool changes might be in progress. When the changes are complete, the write suspend operations will be allowed.
6

Respond to reason code 6 by performing the following steps:

  1. Investigate the cause of the failure by reviewing the administration notification log.

    In a DB2 pureScale environment, review the administration notification log on each member in the DB2 cluster.

  2. Correct the problem that is preventing the SET WRITE command from succeeding.

    In a DB2 pureScale environment, if different members in the DB2 cluster are reporting different root causes for this problem, correct all of the causes reported by the members.

  3. Reissue the SET WRITE SUSPEND command.
7

Unquiesce the database if quiesced, or wait a short period of time and reissue the SET WRITE command with the SUSPEND option.

8

Issue the SET WRITE command on the HADR primary.

SQL1551N The SET WRITE RESUME command or the RESTART DATABASE command with the WRITE RESUME parameter failed because of the condition that is indicated by the reason code. Reason code = reason-code.

Explanation

You cannot issue the SET WRITE RESUME command or the RESTART DATABASE command with the WRITE RESUME parameter until the condition indicated by reason-code is resolved:

1

A snapshot backup is in progress for the target database.

2

The database is not currently in the WRITE SUSPEND state.

3

An error occurred during an attempt to resume the write operations for the database.

User response

Respond to this message according to the reason code:

1
  1. Wait until the snapshot backup is complete.
  2. Reissue the SET WRITE RESUME command.
2

If the command that failed is the SET WRITE RESUME command, no action is required because write operations are already enabled for this database. To suspend write operations for the database, issue the SET WRITE SUSPEND command.

If the command that failed is the RESTART DATABASE command with the WRITE RESUME parameter, issue the RESTART DATABASE command without the WRITE RESUME parameter. If this fails and the database is not in the WRITE SUSPEND state:

  1. Wait until all SET WRITE SUSPEND operations are completed.
  2. Reissue the RESTART DATABASE command with the WRITE RESUME parameter.
3
  1. Investigate the cause of the failure by reviewing the diagnostic (db2diag) log files.
  2. Correct the problem.
  3. Reissue the SET WRITE RESUME command.

SQL1552N The command failed because write operations for the database are suspended or are being suspended.

Explanation

You can suspend write operations for a database using the db2SetWriteForDB API or the SET WRITE command with the SUSPEND clause. There are some operations that cannot be performed on a database when write operations for that database have been suspended, or while the database manager is in the process of suspending write operations for that database:

  • Backing up the database
  • Restoring the database
  • Restarting the database
  • Connecting to or activating the database
  • Updating or resetting database configuration files

This message is returned when an attempt is made to perform these kinds of operations against a database that is in WRITE SUSPEND state, or that is in the process of having write operations suspended.

User response

First, if write operations for the database are in the process of being suspended, monitor the state of the database using the suspend_io configuration parameter, and wait until the SET WRITE SUSPEND operation completes before you continue.

Second, respond to this error according to the scenario in which the message was returned:

Backing up or restoring the database:
  1. Resume write operations for the database by issuing the SET WRITE RESUME FOR DATABASE command.
  2. Perform the backup or restore operation again.
Restarting the database without the WRITE RESUME clause:

Perform the restart again by performing one of the following actions:

  • Issue the RESTART DATABASE command with the WRITE RESUME clause.
  • Call the db2DatabaseRestart API specifying the DB2_RESUME_WRITE option

In a multiple database partition environment, reissue the restart command or API call on each database partition.

Restarting the database with the WRITE RESUME clause in DB2 pureScale environments:
  • If automatic restart is enabled, with the autorestart database configuration parameter set to ON, wait for several seconds and submit the restart again, specifying the WRITE RESUME clause or the DB2_RESUME_WRITE option.
  • If automatic restart is disabled, with the autorestart database configuration parameter set to OFF, perform the following two steps:
    1. Restart the database without specifying the WRITE RESUME clause or the DB2_RESUME_WRITE option.
    2. Restart the database again, specifying the WRITE RESUME clause or the DB2_RESUME_WRITE option.
Other scenarios (including connecting to the database, activating the database, or updating database configuration files):

Restart the database by performing one of the following actions:

  • Issue the RESTART command with the WRITE RESUME clause.
  • Call the db2DatabaseRestart API specifying the DB2_RESUME_WRITE option.

In DB2 pureScale environments, issuing the command or API on any one member will cause write operations to resume on all suspended members.

SQL1553N The database manager cannot be stopped because one or more databases are in WRITE SUSPEND state.

Explanation

You cannot shut down a database for which write operations are suspended. The database is in WRITE SUSPEND state.

User response

Issue the SET WRITE RESUME command to resume write operations for the database, then re-issue the db2stop command.

sqlcode: -1553

SQL1554N The command failed because LIST TABLESPACES and LIST TABLESPACE CONTAINERS commands have been deprecated and are not supported in a DB2 pureScale environment.

Explanation

The commands and APIs that show information about table spaces and table space containers have been deprecated, are not supported in a DB2 pureScale environment, and might be removed in a future release. The LIST TABLESPACES and LIST TABLESPACE CONTAINERS commands are no longer being updated with new features.

User response

Modify any of your existing scripts using the deprecated commands or APIs to call the MON_GET_TABLESPACE or the MON_GET_CONTAINER table functions instead. These table functions return more information than was provided by the deprecated commands and APIs.

sqlcode: -1554

sqlstate: 5U001

SQL1560N Statistics profile does not exist for table table-name.

Explanation

A statistics profile needs to be defined before use.

User response

Register a statistics profile for the table using the SET PROFILE option of the RUNSTATS command and then reissue the operation.

SQL1561N Statistics option not compatible with the database server level.

Explanation

One or more of the options specified are not compatible with the database server level. This database server version does not support all of the statistics options available using the db2runstats API.

User response

Use the sqlustat API to collect the statistics or use the db2runstats API and specify only those options that are available using the sqlustat API.

SQL1562N Statistics node option is not compatible with the existed statistics for table table-name.

Explanation

The statistics node option is different from the existing table and/or index statistics of the table.

User response

Use consistent node option to collect the statistics for a table.

SQL1563N The SYSINSTALLOBJECTS procedure failed to migrate the explain tables.

Explanation

You can migrate explain tables using the SYSINSTALLOBJECTS procedure only if the explain tables were created in DB2 Version 9.5 or higher.

User response

Migrate the explain tables using the db2exmig command.

sqlcode: -1563

sqlstate: 5U048

SQL1564N The restore or rollforward operation did not complete successfully because the specified operation is not supported. Reason code reason-code.

Explanation

1

Restoring a database backup image when the image topology is a superset of the target member topology without specifying the WITHOUT ROLLING FORWARD clause.

2

An attempt was made to restore a table space from a backup image that was taken before one of the following events:

  • A DB2 member was dropped from a DB2 pureScale instance
  • A backup image from a DB2 Enterprise Server Edition (ESE) instance was restored to a DB2 pureScale instance
3

Restoring any backup image (database or tablespace) where the current member driving the restore does not exist in the backup image topology.

5

Restoring a backup image of an inconsistent database when the image topology is not a superset of the target member topology.

6

When restoring a backup image between a DB2 pureScale instance and a DB2 Enterprise Server Edition instance, either this is not a database restore or the backup image is not an offline database backup image.

7

Restoring a backup image of an inconsistent database between a DB2 Enterprise Server Edition instance and a DB2 pureScale Feature instance.

8

A down-level image can be restored only when both of the following conditions are satisfied:

  • The source topology matches the target topology.
  • The source instance type matches the target instance type.
9

Restoring a backup image between a DB2 pureScale instance and a DB2 Enterprise Server Edition instance without specifying the WITHOUT ROLLING FORWARD clause.

User response

The action corresponding to the reason code:

1

Rerun the RESTORE command with WITHOUT ROLLING FORWARD clause.

2

Restore the closest full database backup taken before the tablespace backup, then rerun the RESTORE command.

3

Run the RESTORE command from a common member between the backup image topology and the current member topology.

5

Either perform an offline backup on the source instance or update the target instance to include at least all members in the source instance, then rerun the RESTORE command.

6

You must perform a full offline database backup on the source instance, then restore the full database backup by running the DATABASE RESTORE command with the WITHOUT ROLLING FORWARD clause.

7

Either perform an offline backup on the source instance or update the target instance to include the member identifier in the source instance, then rerun the RESTORE command.

8

To restore a down-level image, do one or both of the following:

  • Modify the target instance topology to add or drop members, or switch to another instance that matches the topology.
  • Run the RESTORE command on the same type of instance as the type of instance on which the BACKUP command was run. For example, if the BACKUP command was run on a DB2 pureScale instance, run the RESTORE command on a DB2 pureScale instance.
9

Rerun the RESTORE command with the WITHOUT ROLLING FORWARD clause.

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

Explanation

The entry in the database manager configuration file for the diagnostic directory path of the cluster caching facility (CF) is cf_diagpath.

This message is returned when you try to update the dbm config parameter cf_diagpath with specification of an invalid path. An invalid value for cf_diagpath is specified in the UPDATE DATABASE MANAGER CONFIGURATION command. For example, this message can be returned if a path is specified that does not exist, or if a path is specified for which the database manager does not have write access.

User response

Run the command again, specifying a valid value for the cf_diagpath. Ensure that this is a valid and fully qualifed path.

sqlcode: -1565

sqlstate: 5U054

SQL1566N The UPDATE DATABASE MANAGER CONFIGURATION command failed because the specified value for the cf_diaglevel configuration parameter is invalid.

Explanation

You can specify the level of diagnostic errors that are recorded in the cfdiag.log file using the database manager configuration parameter cf_diaglevel.

This message is returned when an invalid value for cf_diaglevel is specified in the UPDATE DATABASE MANAGER CONFIGURATION command.

User response

Run the command again, specifying a valid value for the cf_diaglevel.

sqlcode: -1566

sqlstate: 5U054

SQL1567N An exclusive connection to a single database partition cannot be made in this environment

Explanation

In a DB2 pureScale environment, connecting to a single database partition in exclusive mode is not supported.

User response

Do not specify the ON SINGLE DBPARTITIONNUM clause on the CONNECT statement.

SQL1568N The database manager configuration file is not accessible.

Explanation

An error occurred while attempting to access the database manager configuration file. This file is created during instance creation and is critical for all database manager processing. An inaccessible database manager configuration file can be an indication of an incomplete instance setup or a damaged instance.

This message can also be returned when the file system on which the database manager configuration file resides is unavailable. For example, if the shared file system is IBM General Parallel File System (GPFS), this message can be returned if the GPFS cluster is offline.

The command cannot be processed.

User response

Respond to this message be performing the following troubleshooting steps:

  • Confirm that the shared file system where the database manager configuration file is located is mounted.
  • If the shared file system is of type GPFS, confirm that the file system cluster is not stopped by performing the following steps:
    1. Verify the status of the shared file system cluster using the following command:
      db2cluster -cfs -list -host -state
    2. If the shared file system cluster is stopped, restart the cluster using the following command:
      db2cluster -cfs -start -host <hostname>
  • If the database manager instance was recently created, recreate the instance using db2icrt command.

SQL1569N The operation failed because the command or API specified invalid database partitions.

Explanation

If this message is being returned as a result of a backup operation, the specified database partitions are not currently defined in the database. If this message is being returned as a result of a rollforward or recover operation, either the ON DBPARTITIONNUMS or the ON DBPARTITIONNUM clause were specified and an invalid database partition number was specified. In non-DPF environments, only the current database partition can be specified.

User response

For backup operations, reissue the command or API, specifying existing database partitions. For rollforward and recover operations, reissue the command or API without specifying ON DBPARTITIONNUMS or only specify the current database partition

sqlcode: -1569

sqlstate: 428A9

SQL1572N The database rollforward or group crash recovery has failed because of a disk full situation.

Explanation

If a log full situation occurs during a database rollforward or group crash recovery, more log files are automatically allocated as needed. However, in this case, new log files could not be allocated due to insufficient disk space. The recovery or rollforward operation has failed.

User response

Make more disk space available to the group crash recovery or the database rollforward, and reissue the command.

Alternatively, the operation may succeed if reissued on a different member as follows:

  • If the operation that failed was a group crash recovery, DB2 cluster services will automatically reissue the group crash recovery on a different member. If the DB2 pureScale instance does not have automatic crash recovery enabled, the group crash recovery operation needs to be reissued manually on a different member.
  • If the operation that failed was a database rollforward, the rollforward operation needs to be restarted manually on another member.

SQL1573N The database cannot be activated or connected to in the current instance environment.

Explanation

This message is returned if

  • You are trying to activate or connect to a database that has not been verified for a DB2 pureScale environment, but are using a DB2 pureScale environment.
  • You are trying to activate or connect to a database that has been verified for a DB2 pureScale environment, but are not using a DB2 pureScale environment.

These two actions are not supported.

User response

If you are using a DB2 pureScale environment you can use the db2checkSD utility to determine if the database can be used in that environment. If the db2checkSD utility does not report any errors, activate or connect to the database again.

sqlcode: -1573

sqlstate: 55001

SQL1575N The most recent attempt to add or drop a DB2 member for database dbname in this DB2 pureScale environment failed.

Explanation

Adding or dropping a DB2 member (a topology change) in this DB2 pureScale environment would leave database dbname in an unrecoverable state.

User response

Backup or drop the database dbname then repeat the add or drop DB2 member operation.

SQL1576N The database removal failed because of a cluster manager error.

Explanation

A cluster manager error occurred that prevented successful processing of the drop command.

All data files associated with the database has been removed. However, the database location information might not have been removed.

User response

Clean up the database resources that the cluster manager failed to remove by performing the following steps:

  1. Collect as much of the following diagnostic information as possible:
    • Error information from the SQLCA
    • Related errors in the db2diag log files
  2. Make the necessary corrective actions based on the cluster manager return code in the db2diag log files.
  3. Manually remove or delete the related mount resources.
  4. Remove the database location information from the system database directory using the UNCATALOG DATABASE command.

If you are unable to successfully remove the database resources using this procedure, contact IBM support with the following information:

  • Problem description
  • SQLCODE
  • SQLCA contents, if possible
  • Environment data on the client and server collected using the db2support command

sqlcode: -1576

sqlstate: 5U056

SQL1577N The START command failed because the STANDALONE parameter was specified, and the current environment is a DB2 pureScale environment.

Explanation

The STANDALONE parameter is not supported with the START command in a DB2 pureScale environment.

User response

Call the command again without specifying the STANDALONE parameter.

SQL1578N The START command failed because the RESTART parameter was specified, and the current environment is a DB2 pureScale environment.

Explanation

The RESTART parameter is not supported with the START command in a DB2 pureScale environment.

User response

Call the command again without specifying the RESTART parameter.

SQL1579N Two or more log streams for database dbname on database partition dbpartitionnum are following different log chains. Log file file1 on log stream stream1 follows log chain chain1 and log file file2 on log stream stream2 follows log chain chain2.

Explanation

When a database rollforward to a point-in-time operation completes, or a database restore operation without rolling forward is done, a new history of the database, called a log chain, is created. The database manager assigns log chain numbers to log extents and other database objects so that it can verify that the set of objects belongs to the same database history. The database manager has detected that two or more log streams are following different log chains, and has halted the current operation.

User response

Check the log streams that are identified in this message and determine which log stream is following the correct log chain. Retrieve the required log files from the invalid log stream into an overflow log path, and attempt the operation again.

SQL1580W Trailing blanks were truncated while performing conversion from codepage source-code-page to codepage target-code-page. The maximum size of the target area was max-len. The source string length was source-len and its hexadecimal representation was string.

Explanation

During the execution of the SQL statement, a code page conversion operation has resulted in a string that is longer than the maximum size of the target object. Processing continued because only blank characters were truncated.

User response

Ensure that the output is as expected and that the truncation has not caused any unexpected consequences.

sqlcode: +1580

sqlstate: 01004

SQL1581N The table table-name cannot be in append mode and have a clustering index.

Explanation

There are two situations where this error is issued.
  • A clustered index exists for a table and ALTER TABLE is used to attempt to place the table in append mode.
  • A table is in append mode and CREATE INDEX is used to attempt to create a clustering index.

User response

If a clustering index is necessary then alter the table to set append mode off. If append mode is desired, drop the existing clustering index on the table.

sqlcode: -1581

sqlstate: 428CA

SQL1582N The PAGESIZE of the table space tbspace-name does not match the PAGESIZE of the bufferpool bufferpool-name associated with the table space.

Explanation

The PAGESIZE value specified in the CREATE TABLESPACE statement does not match the page size of the bufferpool specified for use with the table space. These values must match.

The statement cannot be processed.

User response

Change the value specified for PAGESIZE to match the page size of the bufferpool or change the bufferpool to one that has a page size that matches.

sqlcode: -1582

sqlstate: 428CB

SQL1583N PAGESIZE value pagesize is not supported.

Explanation

The PAGESIZE that is specified is not a supported page size. The supported page sizes are 4096, 8192, 16384, and 32768, while a value of 4 K, 8 K, 16 K, or 32 K can also be specified.

The statement cannot be processed.

User response

Specify one of the supported page sizes.

sqlcode: -1583

sqlstate: 428DE

SQL1584N System temporary tablespace with page size of at least pagesize could not be found.

Explanation

A system temporary table space was required to process the statement. There was no system temporary table space available that had a page size of pagesize or larger.

The statement cannot be processed.

User response

Create a system temporary table space with a page size of at least pagesize.

sqlcode: -1584

sqlstate: 57055

SQL1585N A temporary table could not be created because there is no available system temporary table space that has a compatible page size.

Explanation

Temporary table spaces hold temporary data required by the database manager when performing operations such as sorts or joins, since these activities require extra space to process the results set. This message is returned when the database manager fails to create a temporary table because the database manager cannot find a table space with a compatible page size that is in a "normal" state.

This message can be returned when one of the following conditions occurs:

  • The row length of the system temporary table being generated is larger than can be accommodated by the system temporary table space with the largest page size that is currently in "normal" state.
  • The number of columns required in a system temporary table exceeded the limit that can be accommodated in the largest system temporary table space in the database.
  • A tablespace might be offline.

User response

Perform the following troubleshooting steps:

  1. Calculate what size of temporary table space is required.
  2. Determine whether a temporary table space exists that has the required page size and is in "normal" state by using the MON_GET_TABLESPACE table function.
  • If a table space with the required page size does not exist, create a system temporary table space with the required page size.
  • If a table space with the required page size exists:
    • If the table space is not in "normal" state, move the table space to a "normal" state. For example, drop and recreate the table space.
    • If the table space is in "normal" state, perform one of the following steps:
      • Eliminate one or more columns from the system temporary table.
      • Create separate tables or views, as required, to hold additional information beyond the limit.

sqlcode: -1585

sqlstate: 54048

SQL1586N The statement was not executed because the query compiler was unable to successfully resolve the text search function in the statement.

Explanation

There are some rare situations in which text search functions cannot successfully be resolved by the query compiler. One example of such a situation is the application of a text search function to a column from the null-producer of an OUTER JOIN.

This message is returned when the query compiler is unable to successfully resolve text search functions.

The statement was not executed.

User response

No user response is required. The specified statement cannot be executed.

SQL1587N The command or statement failed because there is currently a CF on the host on which the command was run or the statement executed. Command or statement type: command-statement-code. Host name: host.

Explanation

There are some DB2 commands, such as "ATTACH", and SQL statements, such as "CONNECT", that cannot be performed on a host where a DB2 cluster caching facility (CF) is located. This message can be returned when these commands or statements have been issued explicitly or implicitly.

The token command-statement-code indicates which type of command or SQL statement was attempted:

1

Explicit or implicit CONNECT TO <database-alias>

2

Explicit or implicit ATTACH TO <instance-alias>

User response

Respond to this message in one of the following ways:

  • Run the command or execute the statement again on a host that does not have a CF on it by performing the following steps:
    1. Find a host that does not currently have a CF on it using the following command:
      db2instance -list
    2. Log in to a host that does not currently have a CF on it.
    3. Run the DB2 command or execute the SQL statement again.
  • Specify a host that does not currently have a CF on it by using one of the following methods:
    • Use the environment variable DB2NODE to specify the member and run the DB2 command or execute the SQL statement again.
    • Use the Set Client command's CONNECT_MEMBER or ATTACH_MEMBER option with the DB2 command or SQL statement.

sqlcode: -1587

sqlstate: 560CW

SQL1588N Error sqlcode on member member-ID prevents processing of the current statement.

Explanation

The current member cannot process data change statements until the condition causing error sqlcode on member member-ID is corrected. The statement cannot be processed.

The runtime token, sqlcode, indicates the underlying sqlcode that was returned.

User response

Retry the operation. If the error persists, correct the problem and try again.

sqlcode: -1588

sqlstate: 57063

SQL1589N The database connection failed because an operating system resource limit was reached.

Explanation

This message can be returned when there are more than 1024 simultaneous local database connections, and as a result, an operating system limit is reached. On AIX operating systems, no more than 1024 local database connections established by a single process or application can exist simultaneously.

This message can also be returned when the database manager encounters an internal error while making operating system calls.

User response

Terminate any unneeded local database connections.

If terminating local database connections resolves the problem, prevent reoccurrences of this error by modifying your applications to use fewer simultaneous local connections. If your applications require many database connections, use remote connections (or loopback connections when the database server and client are on the same host machine) using TCP/IP instead of local connections.

If reducing the number of local connections does not resolve this problem, contact IBM software support for help with investigating the cause of the problem.

sqlcode: -1589

sqlstate: 54067

SQL1590N LONG VARCHAR and LONG VARGRAPHIC fields are not permitted in TABLESPACEs which are built on DEVICEs.

Explanation

Devices (raw i/o) on HP require i/o to be aligned on 1024 byte boundaries. LONG VARCHAR and LONG VARGRAPHIC fields are handled in 512 byte pieces, and thus can only be used in SYSTEM MANAGED TABLESPACEs or in DATABASE MANAGED TABLESPACEs with only FILE containers.

User response

Alternatives:
  • Choose one of the LOB columns types (BLOB,CLOB,DBCLOB) instead of LONG.
  • Use a table space with the correct attributes.

sqlcode: -1590

sqlstate: 56097

SQL1592N The INCREMENTAL option is not valid with reason code reason-code since the table table-name cannot be incrementally processed.

Explanation

The cause is based on the reason code reason-code:

32

The table is not a REFRESH IMMEDIATE materialized query table, nor a REFRESH DEFERRED materialized query table with a supporting staging table, nor a PROPAGATE IMMEDIATE staging table.

33

A LOAD REPLACE or LOAD INSERT has occurred to the table if it is a materialized query table or staging table.

34

A LOAD REPLACE has occurred to the table after the last integrity check.

35

One of the following:

  • The materialized query or staging table was newly created. Full processing is required for the first time the table is checked for integrity after it has been created.
  • New constraint has been added to the table itself or its parents (or its underlying table if it is a materialized query table or staging table) while in the Set Integrity Pending state.
  • If it is a materialized query table or staging table, a LOAD REPLACE has occurred to any underlying table of the table after the last refresh.
  • If it is a materialized query table, at least one underlying table was forced to full access (using the FULL ACCESS option) before the materialized query table was refreshed.
  • If it is a staging table, at least one underlying table was forced to full access (USING the FULL ACCESS option) before the staging table was propagated.
  • If it is a deferred materialized query table and its corresponding staging table is in incomplete state.
  • Some of its parents (or underlying tables for materialized query tables or staging tables) have been non-incrementally checked for integrity.
  • The table was in the Set Integrity Pending state before database upgrade. Full processing is required for the first time the table is checked for integrity after database upgrade.
  • The table was placed in the Set Integrity Pending state during a point in time roll-forward operation.

User response

Do not specify the INCREMENTAL option. The system will check the entire table for constraint violations (or if it is a materialized query table, recompute the materialized query table definition query).

sqlcode: -1592

sqlstate: 55019

SQL1594W Integrity of non-incremental data remains unverified by the database manager.

Explanation

The table was previously unchecked. When the option NOT INCREMENTAL is not specified, incremental processing of the table is done. The previously unchecked portion of the table remains unchecked and the corresponding values in the CONST_CHECKED column remains marked as 'U'.

User response

No action is required. To verify the integrity of previously unchecked data and have the system maintain the integrity of the data in the table, issue the SET INTEGRITY statement with the OFF option to place the table in the Set Integrity Pending state and then re-execute the SET INTEGRITY statement with the IMMEDIATE CHECKED and NOT INCREMENTAL options.

sqlcode: +1594

sqlstate: 01636

SQL1596N WITH EMPTY TABLE cannot be specified for table-name.

Explanation

The WITH EMPTY TABLE clause cannot be specified for table table-name because the table meets one of the following conditions:

  • It is a materialized query table or is a staging table.
  • It has a dependent refresh immediate materialized query table or has a dependent propagate immediate staging table.
  • It is the parent in a referential constraint.
  • It has attached data partitions that have not been checked for constraint violations.
  • The ALTER TABLE statement was previously executed against this table, specifying the DETACH PARTITION clause, and that asynchronous detach operation is not complete. There are data partitions in this table that are still in the logically detached state (SYSCAT.DATAPARTITIONS.STATUS = 'L').

The WITH EMPTY TABLE clause cannot be specified when altering such a table to ACTIVATE NOT LOGGED INITIALLY.

The statement cannot be processed.

User response

If the table does not have a logically detached partition, issue the ALTER TABLE statement without the WITH EMPTY TABLE clause.

If the table does have a logically detached partition, perform the following steps:

  1. Wait for the asynchronous partition detach task to complete.

    You can monitor the progress of the detach task in the following ways:

    • Monitor the progress of the detach task by using the LIST UTILITIES command and look for the description containing source table table-name.
    • Confirm that there are no data partitions in the logically detached state by using the SYSCAT.DATAPARTITIONS catalog view. Any data partitions that are still logically detached will have an 'L' in the column named STATUS.
  2. Execute the ALTER TABLE statement again.

sqlcode: -1596

sqlstate: 42928

SQL1597N Configuring the DB2 environment failed because the specified DB2 configuration parameter is discontinued.

Explanation

The LOGRETAIN and USEREXIT database configuration parameters have been discontinued.

Log retention and the use of user exit programs to archive and retrieve the files are still supported. To configure a database to use log retention and user exit programs, you should use the LOGARCHMETH1 database configuration parameter.

User response

To enable log retention, set the LOGARCHMETH1 database configuration parameter to LOGRETAIN.

To enable log retention and identify that a user exit program should be used to archive and retrieve the log files, set the LOGARCHMETH1 database configuration parameter to USEREXIT.

SQL1598N An attempt to connect to the database server failed because of a licensing problem.

Explanation

This message can be returned in the following situations:

Connecting directly to the database server using IBM DB2 Connect Unlimited Edition for System z

If you use IBM DB2 Connect Unlimited Edition for System z to connect directly to the database server, this message is returned when a valid license has not been activated on the DB2 for z/OS subsystem.

Connecting directly to the database server using an edition of IBM DB2 Connect other than IBM DB2 Connect Unlimited Edition for System z

If you use an edition other than IBM DB2 Connect Unlimited Edition for System z to connect directly to a database server, this message is returned when a valid license is not present on the client computer.

Connecting to a database server through a DB2 Connect gateway server

If you connect to a database server through a DB2 Connect gateway server, this message is returned when a valid license is not present on the DB2 Connect gateway server.

User response

Respond to this message according to which scenario applies to your situation:

Connecting directly to the database server using IBM DB2 Connect Unlimited Edition for System z

If you use IBM DB2 Connect Unlimited Edition for System z to connect directly to the database server, activate the license by running the activation program in the activation kit.

Connecting directly to the database server using an edition of IBM DB2 Connect other than IBM DB2 Connect Unlimited Edition for System z

If you use an edition other than IBM DB2 Connect Unlimited Edition for System z to connect directly to a database server, ensure that a DB2 Connect product and valid license key are installed on your client computer.

Connecting to a database server through a DB2 Connect gateway server

If you connect to a database server through a DB2 Connect gateway server, ensure that a valid license key is installed on the gateway server.

sqlcode: -1598

sqlstate: 42968

SQL1599N Creating the public alias failed because the environment is configured for SAP.

Explanation

You can configure the DB2 environment for SAP by setting the system environment variable named DB2_WORKLOAD to the value SAP.

You can reference objects outside the local schema using public aliases, also known as public synonyms. You can create public aliases using the CREATE PUBLIC ALIAS statement.

Public aliases are not supported in a DB2 environment that is configured for SAP. This message is returned when an attempt is made to create a public alias when the system environment variable named DB2_WORKLOAD is set to the value SAP.

There are several ways to refer to objects outside of the local schema without creating public aliases, including: using full-qualified names, or creating local aliases. In the following examples, the local schema is called "schemaA" and there is a table called "tableX" in a different schema, called "schemaB".

Example 1: Using fully-qualified names

You could refer to tableX using a fully-qualified name:

select * from schemaB.tableX
Example 2: Creating a local alias

You could refer to tableX by first creating a local alias:

create alias AX for table schemaB.tableX
select * from AX

User response

Instead of creating public aliases, refer to database objects outside of the local schema by using fully-qualified names, or by creating local aliases.

sqlcode: -1599

sqlstate: 42612

SQL1600N The storage group storage-group cannot be dropped because it is the default storage group.

Explanation

DROP STOGROUP cannot be processed because storage-group-name is the current default storage group.

The statement cannot be processed.

User response

Before dropping the current default storage group, designate a new default storage group by using the ALTER STOGROUP statement.

sqlcode: -1600

sqlstate: 42893

SQL1601N The Database System Monitor input parameter parameter is a null pointer.

Explanation

The user called one of the Database System Monitor APIs and provided a null pointer instead of a required parameter.

The command can not be processed.

User response

The user should reissue the command with a valid parameter value.

SQL1602N An object type supplied in the input data structure (sqlma) is not supported.

Explanation

An object type specified in the variable data area of the input data structure (sqlma) for Database System Monitor Snapshot API is not supported.

The command can not be processed.

User response

Reissue the command using a valid object type.

SQL1603N The parameter parameter is not specified in the input data structure (sqlma).

Explanation

A required parameter is not specified in the input data structure (sqlma) of the Database System Monitor Snapshot or Estimate Buffer Size API.

The command cannot be processed.

User response

The user should reissue the command specifying a valid parameter value.

SQL1604N The parameter parameter is not null terminated.

Explanation

A null character is expected at the end of the character string parameter.

The command can not be processed.

User response

Add a null character at the end of the character string parameter and reissue the command.

SQL1605W The database db-alias is not active.

Explanation

The Database System Monitor Reset API was called for a specific database, but the database was not active.

The command completed successfully but no action was taken.

User response

Verify that the database alias is correct and the database has been started.

SQL1606W The Database System Monitor output buffer is full.

Explanation

The Database System Monitor output buffer area is not large enough to accommodate the returned data. Likely causes are intense system activity when the call was made, or in the case of a Database Monitor API call within a user application, the user allocated a buffer too small to contain the returned data.

The command completed successfully and data collected prior to the buffer overflow is returned in the user's buffer.

User response

The user should reissue the command, or in the case of a Database Monitor API call within a user application, allocate a larger buffer or reduce the amount of information requested.

SQL1607N There is not enough working memory to execute the requested Database Monitor function.

Explanation

The database manager is out of working memory to process the Database System Monitor command.

The command can not be processed.

User response

Reduce the buffer size in the input parameter and reissue the command.

SQL1608W Two or more database aliases specified as input refer to the same database.

Explanation

A Database System Monitor Snapshot or Estimate Buffer Size API call was issued specifying the same request for two or more database aliases in the sqlma input data structure, and they point to the same database.

Database System Monitor executes successfully, but returns only one copy of the information in the output buffer.

User response

No action is required. However, the user should verify that the database aliases specified on input are correct if information on different databases was expected.

SQL1609N The database alias db-alias is a remote database and cannot be monitored.

Explanation

A Database System Monitor API call was issued specifying the database alias of a remote database. Database System Monitor does not support monitoring of remote databases.

The command cannot be processed.

User response

The user should verify that the database alias specified on input is correct, and reissue the command with the correct database alias.

SQL1610N The Database System Monitor input parameter parameter is invalid.

Explanation

The user called one of the Database System Monitor APIs and specified an invalid value for the specified parameter.

The command can not be processed.

User response

The user should reissue the command with a valid parameter value.

SQL1611W No data was returned by Database System Monitor.

Explanation

None of the monitoring information requested by the users was available at the time the Database System Monitor API call was issued. This can occur when a requested database or application is inactive, or when a monitoring group such as the Table group is turned OFF, and Table information is requested.

User response

The command completed successfully, but no data is returned to the user.

The user should make sure that the databases or applications for which monitoring is desired are active at the time the Database System Monitor API is called, or that the desired monitoring groups are active.

SQL1612N The specified event monitor target path is invalid.

Explanation

The target path specified in the CREATE EVENT MONITOR statement is not a valid path name. The command could not be processed.

User response

Resubmit the statement with the correct event monitor target path.

sqlcode: -1612

sqlstate: 428A3

SQL1613N The specified event monitor option is invalid.

Explanation

The option specified in the CREATE EVENT MONITOR statement is not valid. Possible causes include:
  • The specified MAXFILES, MAXFILESIZE, or BUFFERSIZE is too low.
  • MAXFILESIZE is smaller than BUFFERSIZE.
  • MAXFILESIZE NONE was specified with MAXFILES not equal to 1.

The command could not be processed.

User response

Resubmit the statement with the corrected event monitor options.

sqlcode: -1613

sqlstate: 428A4

SQL1614N An I/O error occurred when activating an event monitor. Reason code = reason-code.

Explanation

An I/O error was detected when an event monitor was activated. <reason-code> is one of the following:
1
Encountered an unknown event monitor target type.
2
The Event monitor target path was not found.
3
Access to event monitor target path was denied.
4
Event monitor target path is not the name of a pipe.
5
No process has opened the event monitor target pipe for reading.
6
Encountered an unexpected I/O error.

User response

Where possible, fix the problem described by the reason code, and resubmit the SET EVENT MONITOR statement.

sqlcode: -1614

sqlstate: 58030

SQL1615W The specified event monitor or usage list is already in the requested state.

Explanation

An attempt was made to either activate an already active event monitor or usage list, or to deactivate an already inactive event monitor or usage list. The SET EVENT MONITOR or SET USAGE LIST statement was ignored.

In a partitioned database environment or a DB2 pureScale environment, the usage list on one or more members was already in the requested state. Any usage lists that were not in the requested state when the statement was issued were changed to the requested state.

If the statement was issued for a usage list for a partitioned table or index, the usage list for one or more data partitions was already in the requested state. Any usage lists that were not in the requested state when the statement was issued were changed to the requested state.

User response

No user response is required.

sqlcode: +1615

sqlstate: 01598

SQL1616N The limit on the maximum number of active event monitors has already been reached.

Explanation

A maximum of 128 event monitors can be active simultaneously on each database partition.

In a multiple partition database environment, a maximum of 32 GLOBAL event monitors can be active simultaneously on each database.

One of these limits has already been reached. The specified event monitor cannot be activated.

User response

If possible, deactivate one of the active event monitors and resubmit the SET EVENT MONITOR statement. Use the following query to determine all the active event monitors and whether or not they are global:

SELECT EVMONNAME, MONSCOPE FROM SYSCAT.EVENTMONITORS WHERE EVENT_MON_STATE(EVMONNAME) = 1

sqlcode: -1616

sqlstate: 54030

SQL1617N The specified event monitor has already reached its MAXFILES and MAXFILESIZE limit.

Explanation

The specified event monitor was created with a limit on the amount of data that would be allowed in the event monitor target directory. This limit has already been reached. The specified event monitor cannot be activated.

User response

If possible, delete some of the event monitor data files from the target directory, and resubmit the SET EVENT MONITOR statement.

sqlcode: -1617

sqlstate: 54031

SQL1618N The target path of the specified event monitor is in use by another event monitor.

Explanation

The specified event monitor was created with the same target path as another event monitor. This other event monitor was activated at least once, and has left .evt and/or .ctl files in the target path. These files may be in use by application(s) that are reading the event information they contain.

User response

If the other event monitor is currently active, deactivate it. After ensuring no application(s) are using the files it created in the target path, remove the files. Then resubmit the SET EVENT MONITOR statement.

Alternatively, recreate the required event monitor, specifying a different target path, and resubmit the SET EVENT MONITOR statement.

sqlcode: -1618

sqlstate: 51026

SQL1619N Cannot DROP an active event monitor.

Explanation

The specified event monitor is currently active, and therefore cannot be dropped.

User response

Deactivate the event monitor and resubmit the DROP EVENT MONITOR statement.

sqlcode: -1619

sqlstate: 55034

SQL1620N Unable to flush event monitor. Reason code rc.

Explanation

The event monitor could not be flushed. Possible reasons are indicated by the following reason codes:

1

The event monitor is not active.

2

The event monitor is running at a pre-version 6 level of output, for which flush is not available.

3

The flush succeeded on some database partitions, but failed on at least one database partition.

4

The database partition is in write-suspended state.

User response

Actions, according to reason code, are provided as follows:

1

Ensure that the event monitor is active and, if necessary, issue a SET EVENT MONITOR evmonname STATE 1 statement to activate the event monitor.

2

If the event monitor is running at a pre-version 6 level of output, do not attempt to flush it.

3

If the flush failed on at least one database partition, check the db2diag log file for any probes from routines sqlm_bds_flush_monitor or sqlm_bds_flush_monitor_hdl which would indicate the partition experiencing the issue with the event monitor being flushed, take any required corrective actions (for example, make sure there is enough monitor heap on that partition, and for a write-to-table event monitor, ensure the table space has enough space on that partition), and then deactivate and reactivate the event monitor by issuing the following statements:

SET EVENT MONITOR evmonname STATE 0
SET EVENT MONITOR evmonname STATE 1
4

Enable the resumption of write operations on the database partition by issuing the SET WRITE command with the RESUME parameter.

sqlcode: -1620

sqlstate: 55034

SQL1621N The transaction in which the specified event monitor or usage list was created has not yet been committed. The event monitor or usage list cannot be activated.

Explanation

An event monitor or usage list cannot be activated until the transaction in which it was created has been committed.

User response

Commit the transaction in which the event monitor or usage list was created and then reissue the SET EVENT MONITOR or SET USAGE LIST statement.

sqlcode: -1621

sqlstate: 55033

SQL1622N The STATE value specified in the SET EVENT MONITOR STATE or the SET USAGE LIST STATE statement is not valid.

Explanation

The STATE value specified in the SET EVENT MONITOR STATE or the SET USAGE LIST STATE statement is not within the range of valid values, or the value is NULL as a result of an indicator variable.

Valid values for the event monitor state are:

0

to deactivate the event monitor

1

to activate the event monitor

Valid values for the usage list state are:

ACTIVE

to activate the usage list

INACTIVE

to deactivate the usage list

RELEASED

to release the memory associated with the usage list

The statement cannot be executed.

User response

Correct the event monitor or usage list state value and/or any indicator variable and reissue the statement.

sqlcode: -1622

sqlstate: 42815

SQL1623N The sqlmonsz or sqlmonss API was called with too many objects specified in the sqlma input structure.

Explanation

The limit imposed on the number of objects that are permitted in the sqlma input structure has been exceeded.

User response

Reduce the number of objects in the sqlma parameter and try the call again.

SQL1624N All databases referenced by the sqlmonsz or sqlmonss API must be located at the same node.

Explanation

The sqlma parameter contained references to databases that reside on different nodes.

User response

Modify the sqlma parameter so that all database objects reference the same node and then try the call again.

SQL1625W The monitor is not able to convert from the code page source to the code page target. This conversion was attempted for data pertaining to type type.

Explanation

Possible types are as follows:
  1. statement text
  2. dcs application
  3. application
  4. table
  5. locks
  6. table space
Conversion of data from the source code page to the target code page is not supported. This condition can occur under the following conditions:
  1. source and target code page combination is not supported by the database manager.
  2. source and target code page combination is not supported by the operating system character conversion utility on the server node.

This situation can occur when the monitor tries to convert data pertaining to a database whose code page is incompatible to that of the monitor application.

User response

Check your operating system documentation for a list of supported conversions and ensure that the appropriate ones are installed and accessible to the database manager.

If possible ensure that the database being monitored and the monitoring application are in the same codepage.

SQL1626W Overflow occurred while performing conversion from codepage source to codepage target. The size of the target area was max-len, the data pertained to type type, and the first eight characters are data.

Explanation

Possible types are as follows:
  1. statement text
  2. dcs application
  3. application
  4. table
  5. locks
  6. table space

The monitor is unable to convert the data due to space constraints. The data is retained in its original form.

User response

If possible ensure that the database being monitored and the monitoring application are in the same codepage.

SQL1627W A snapshot api request was made at the self-describing datastream level, but the server was only able to return a snapshot of the fixed size structure format.

Explanation

Although the application issuing the snapshot request made it at the SQLM_DBMON_VERSION6 or later level, the server returning the snapshot returned a downlevel view of the data.

User response

In the self describing data format for snapshot (DB2 version 6 and later), collected information, including the server level, is returned as part of the snapshot datastream. In the pre-version 6 levels of DB2, the snapshot collected information is returned in an sqlm_collected structure. You must use the sqlm_collected structure, and the old data stream processing method to parse this snapshot datastream.

SQL1628W A remote get switches operation returned partial results because the output buffer is full. To retrieve the full results, use a minimum buffer size of size bytes.

Explanation

The output buffer provided was not large enough to return all the switch data available. The monitor returned as much data as possible using the given output buffer.

User response

Allocate a larger data buffer and re-issue the switch request.

SQL1629W A remote snapshot operation failed on node or nodes node-list, with reason code or codes reason-list.

Explanation

Some type of failure occurred during an operation on a remote node for reason <reason-code>, which is one of the following:
1
FCM was unable to communicate with the target node, due to a node failure or communications error.
2
The snapshot operation failed to complete on the target node. Please see the administration notification log for the specific sqlca.

User response

If the cause of the error was a node failure, or communication error, you will need to resolve the communication error, or restart the node that failed to correct the error.

If the error was due to a snapshot operation failure on a remote node, see the administration notification log for the sqlca from the failed operation, and refer to the instructions for that code to correct the problem.

SQL1630N The specified event monitor has already reached its PCTDEACTIVATE limit.

Explanation

The specified Write to Table event monitor was created with a PCTDEACTIVATE limit, specifying how full a DMS table space must be before the event monitor automatically deactivates, and this limit has already been reached. The specified event monitor cannot be activated.

User response

Reduce the space used in the table space, and resubmit the SET EVENT MONITOR statement. Alternatively, drop the event monitor and recreate it with a higher PCTDEACTIVATE limit value.

sqlcode: -1630

sqlstate: 54063

SQL1631N Event monitor event-monitor-name of type event-monitor-type is already active. Event monitor was not activated.

Explanation

Only one event monitor of type ACTIVITIES, STATISTICS or THRESHOLD VIOLATIONS may be active at any one time. Event monitor activation failed because an event monitor of the same type is already active.

User response

Deactivate event monitor event-monitor-name before attempting to activate this event monitor.

sqlcode: -1631

sqlstate: 5U024

SQL1632W The collect and reset statistics request was ignored because another collect and reset statistics request is already in progress.

Explanation

The collect and reset statistics request was ignored because a previous collect and reset statistics request is already in progress. Only one collect and reset statistics request may be processed at one time on this database.

User response

No action required.

sqlcode: +1632

sqlstate: 01H53

SQL1633W The activity identified by application handle application-handle, unit of work ID unit-of-work-id, and activity ID activity-id could not be captured because there is no active activity event monitor.

Explanation

An attempt was made to capture an activity identified by an application handle, a unit of work identifier, and an activity identifier. This requires that an activity event monitor be created and its state set to active. There currently is no activity event monitor in the active state.

User response

If there already is an activity event monitor but it is not in active state, set its state to active. If there are no activity event monitors in this database, create one, set its state to active. Reinvoke this procedure.

sqlcode: +1633

sqlstate: 01H53

SQL1634N Statistics could not be collected because there is no active statistics event monitor.

Explanation

An attempt was made to collect workload management statistics. This requires that a statistics event monitor be created and its state set to active. There currently is no statistics event monitor in the active state.

User response

If there already is a statistics event monitor but it is not in active state, set its state to active. If there are no statistics event monitors in this database, create one, set its state to active. Reinvoke this procedure.

sqlcode: -1634

sqlstate: 51042

SQL1635N The snapshot operation failed because the size of the snapshot is snapshot-size bytes, which exceeds the maximum allowable size of max-size bytes.

Explanation

You can collect DB2 database and related operating system information by using the snapshot monitor. In multiple database partition environments, you can take a snapshot of the current database partition, a specified database partition, or all database partitions. Taking a snapshot of all database partitions at once is referred to as a taking global snapshot.

In general, the size of the data buffer that the snapshot operation allocates is restricted by system resource constraints. For global snapshots, you can optionally specify the maximum allowed size of the data buffer by setting the DB2_MAX_GLOBAL_SNAPSHOT_SIZE registry variable.

This message can be returned in two types of scenarios:

  • In general, this message is returned when the requested snapshot size exceeds the maximum possible snapshot size.
  • For global snapshot operations, this message can also be returned when the requested snapshot size exceeds the value that is set in the DB2_MAX_GLOBAL_SNAPSHOT_SIZE registry variable.

User response

Respond to this message by performing one or more of the following actions.

General:
  • Create a smaller snapshot by reducing the amount of information that is collected.

    Two examples of ways to collect smaller snapshots by changing the parameters that are specified with the GET SNAPSHOT command:

    • Collect information for only one database by using the DATABASE parameter instead of using the ALL DATABASES parameter.
    • Collect information for only the applications that are connected to a particular database by using the APPLICATIONS ON parameter instead of using the ALL APPLICATIONS parameter.
Global snapshots only:
  • Collect multiple, smaller snapshots by running the GET SNAPSHOT command separately on each database partition instead of creating a global snapshot.
  • If the DB2_MAX_GLOBAL_SNAPSHOT_SIZE registry variable is set, increase DB2_MAX_GLOBAL_SNAPSHOT_SIZE to a value that is at least as large as the actual size given in this message in the snapshot-size runtime variable, and then run the GET SNAPSHOT command again.

SQL1636N The event monitor encountered errors during activation. Reason code reason-code.

Explanation

During the activation of the event monitor, errors were encountered as indicated by the following reason code:

1

The event monitor was successfully activated. However this is a DB2 pureScale environment and an error has occurred leading to limited or no restart capability for this global or write-to-table event monitor. If the monitoring member is no longer able to run the event monitor, the system may not be able to restart it on another member.

2

The event monitor failed to activate on the current member. However this is a DB2 pureScale environment and this global or write-to-table event monitor may have been successfully activated on another member.

User response

The action corresponding to the reason code is:

1

Examine the administration notification log and the db2diag.log for details. Correct the problem affecting the member and deactivate and reactivate the event monitor to ensure full restart capability is enabled.

2

Examine the administration notification log and the db2diag.log for details. Correct the problem affecting the member. Check to see if the event monitor is active, deactivate the event monitor if required and reactivate the event monitor to ensure full restart capability is enabled.

sqlcode: -1636

sqlstate: 560CS

SQL1637N The statement failed because a clause was specified that is not supported with transparent DDL. Specified clause: clause.

Explanation

You can create, alter, and drop remote tables in a federated environment using familiar SQL statements such as CREATE TABLE, ALTER TABLE, and DROP TABLE by using transparent DDL. The ability to work with both local and remote tables using the same, familiar SQL statements simplifies the administration of federated database environments. You can enable using transparent DDL with a remote table by creating the table using the CREATE TABLE statement with the OPTIONS clause.

This message is returned when the CREATE TABLE statement or the ALTER TABLE statement is called, specifying a clause that is not supported with transparent DDL.

User response

Execute the statement again, without specifying the unsupported clause.

sqlcode: -1637

sqlstate: 428I2

SQL1638N Redirecting storage group paths is not possible.

Explanation

A process attempted to modify storage group paths using the SET STOGROUP PATHS command or the db2SetStogroupPaths API at a time when this is not possible. For example, this message can be returned when an attempt is made to redirect a storage group path during a table space restore. Storage group paths can only be redirected during a redirected database restore.

User response

Possible actions include: To modify storage group paths of an active database, use the ALTER STOGROUP statement. To perform a redirected restore, issue a RESTORE DATABASE command using the REDIRECT option. During the redirected restore it is possible to use the SET STOGROUP PATHS command or the db2SetStogroupPaths API to redirect storage group paths.

sqlcode: -1638

sqlstate: 5U057

SQL1639N The database server was unable to perform authentication because security-related database manager files on the server do not have the required operating system permissions.

Explanation

The DB2 database system requires that your instance and database directories, and the files in those directories, have a minimum level of operating system permissions. When the instance and database directories are created by the database manager the permissions are accurate, and changing those permissions could cause database manager functions to fail. The complexity of DB2 file permissions is increased in the case of non-root installed instances and operating system-based authentication.

This message is returned when security-related database manager executable files do not have necessary permissions for the database manager to perform remote connection authentication-related tasks.

There are several reasons why these security-related files might not have the necessary permissions, including the following reasons:

  • The database manager instance is a non-root installed instance and operating system-based authentication has not been enabled using the db2rfe command
  • Operating system permissions of database manager files were accidentally changed

User response

Respond to this message in one of the following ways:

  • If the instance is a non-root installed instance, enable operating system-based authentication using the db2rfe command.
  • Reset all of the operating system permissions for the database manager binary files for this instance by running the following command as a superuser:
    db2iupdt -k <instance-name>

    where <instance-name> is the name of the affected instance.

Note that both the db2rfe command and the db2iupdt command require that the database manager instance be stopped and restarted.

sqlcode: -1639

sqlstate: 08001

SQL1640N A usage list cannot be created for the object object-name.

Explanation

Usage lists can be created only for regular tables and indexes. For more information about the types of objects for which usage lists can be created, refer to the Related topics section.

User response

Use the name of a valid table or index object.

sqlcode: -1640

sqlstate: 42809

SQL1641N The db2start command failed because one or more database manager program files was prevented from executing with root privileges by file system mount settings.

Explanation

With a root-installed instance in UNIX and Linux environments, several database manager executable programs are what is known as "set user ID upon execution" (setuid) programs. A setuid program executes with the privileges of the owner of the program, instead of the privileges of the user than ran the program. For example, database manager programs such as the db2start program are owned by root, and therefore executes with root privileges regardless of what the privileges are of the user who runs the db2start command.

The ability of programs to run with setuid privileges on a mounted file system is configured using the nosuid option when the file system is mounted. Mounting a file system with the nosuid option prevents programs from running with setuid privileges.

This message is returned in UNIX and Linux environments when database manager programs that are needed to start a database instance were not able to execute as root because the file system on which the the database manager programs are located was mounted with the nosuid option.

User response

  1. Remount the file system on which the database product files, including the sqllib directory and the db2start program, are located without the nosuid option.
  2. Re-run the db2start command.

SQL1642N The database manager failed to connect to an internet socket on a remote computer because the connection request was refused by the remote computer.

Explanation

To interact with a remote database across a network, the database manager must use a communication protocol, such as TCP/IP, and use operating system interfaces, such as an internet socket, to connect to database-related operating system services on the computer on which the remote database is located.

This message is returned when the database manager attempts to connect to a remote computer using the TCP/IP communication protocol and receives the error code ECONNREFUSED or WSAECONNREFUSED from the TCP/IP function called CONNECT. Usually, the connection is refused because the database-related operating system service to which the database manager is attempting to connect on the remote computer is inactive.

There are multiple scenarios that can lead to this error being returned, including the following scenarios:

  • The database manager on the remote computer is stopped
  • There is a problem with the way the remote database is cataloged
  • There is a problem with the way the remote database server is configured
  • The DB2COMM registry variable at the remote database server is not set to the communication protocol that is being used by the client
  • Firewall software on the remote computer is blocking the database manager connection attempt
  • There are more TCP/IP connection requests than the remote computer can handle

User response

Respond to this error by systematically eliminating the possible causes:

  1. Ensure that the database manager on the remote computer has been started successfully.
  2. Ensure that the database is cataloged correctly.
  3. Ensure that the entries in the database manager configuration file for the remote database are valid and consistent.
  4. Ensure that the DB2COMM environment variable at the remote database server is set to the communication protocol that is being used by the client.
  5. Ensure that firewall software is not blocking the TCP/IP connection to the remote computer.
  6. Ensure the number of connection requests being sent to the remote computer by all applications is less than the number of request that can be handled by the computer.

If you have eliminated the possible causes listed here, collect diagnostic information using the db2support command and then contact IBM software support.

SQL1643C The database manager failed to allocate shared memory because the database manager instance memory limit has been reached.

Explanation

The maximum amount of memory that can be allocated for each database partition is controlled by the instance_memory database manager parameter. DB2 memory consumption varies depending on workload and configuration. In addition to this, self-tuning of database_memory becomes a factor if it is enabled. There are many factors that contribute to the calculation of instance_memory and the affect that parameter has on the instance memory limit, including the following factors:

  • You can specify the maximum amount of memory that can be allocated for a database partition using the instance_memory database manager parameter.
  • Setting the instance_memory database manager parameter to AUTOMATIC allows the database manager instance memory to grow as needed, up to a limit calculated based on physical RAM on the computer and on the maximum allowed by the database product license.

This message is returned when the database manager is unable to allocate shared memory during activities such as activating a database or rolling a database forward, because the instance memory limit has been reached.

User response

  1. Determine the total instance memory consumption by a database manager instance for a specific database partition, or for all database partitions using the ADMIN_GET_DBP_MEM_USAGE table function or the db2pd command with the -dbptnmem parameter.
  2. Increase the value to which the instance_memory database manager parameter is set or set instance_memory to AUTOMATIC.
  3. If this error continues to happen after you have set instance_memory as large as possible, or have set instance_memory to AUTOMATIC, collect diagnostic information using the db2support utility and contact IBM software support.

sqlcode: -1643

sqlstate: 57019

SQL1644N The database manager failed to send data to an internet socket on a remote computer because the connection request was reset by the remote computer.

Explanation

To interact with a remote database across a network, the database manager must use a communication protocol, such as TCP/IP, and use operating system interfaces, such as an internet socket, to connect to database-related operating system services on the computer on which the remote database is located.

This message is returned when the database manager attempts to send data to a remote computer using the TCP/IP communication protocol and receives the error code ECONNRESET or WSAECONNRESET from the TCP/IP function called RECV.

There are multiple scenarios that can lead to this error being returned, including the following scenarios:

  • Client-side connection pooling is enabled and a database application has not been retrying after database connection failures.
  • A database agent was forced off of the remote computer.
  • A database agent on the remote computer was terminated.
  • A database-related operating system thread on the remote computer has timed out.
  • The connection was closed by the remote gateway or server at the TCP/IP level.

User response

Systematically investigate and resolve the possible causes:

Client-side connection pool problems

If client-side connection pooling is enabled, ensure that the database application retries database connections after receiving database connection failures.

Database agent forced off
  1. Investigate whether any events might have forced a database agent off of the remote computer, such as an administrator forcing all users and agents off the remote computer to perform maintenance.
  2. If database agents have been forced off the remote computer, work with a database or system administrator to bring the database server back online and ready to process requests, and then retry the unit of work.
Database agent terminated
  1. Investigate whether any failures on the remote computer might have terminated a database agent. For example, the termination of a key database manager process might cause the termination of a database agent.
  2. If failures on the remote computer have terminated a key database manager process, work with a database or system administrator to bring the database server back online and ready to process requests, and then retry the unit of work.
Thread timed out
  1. Review diagnostic logs on the remote computer for error messages that indicate an operating system thread timed out.
  2. If database-related operating system threads ran longer than the idle thread timeout (IDTHTOIN) operating system parameter, take one or more of the following corrective actions:
    • Increase the value of the IDTHTOIN parameter.
    • If connection pooling is enabled at the gateway, disable that connection pooling.
    • Ensure that the database application is not holding resources open longer than necessary. For example, ensure the database application closes with-hold cursors after the cursors are no longer needed.
Connection closed by the remote gateway or server

Resolve any problems external to the database product that might have caused a TCP/IP connection to be closed on the remote gateway or server. Some examples of problems that could cause the connection to be closed include the following problems:

  • Firewall software errors or failure
  • Power failure
  • Network failure

If you have eliminated the possible causes listed here, collect diagnostic information using the db2support command and then contact IBM software support.

sqlcode: -1644

sqlstate: 08001

SQL1645N The database manager failed to connect to or send data to an internet socket on a remote computer because the connection was terminated by the remote computer.

Explanation

To interact with a remote database across a network, the database manager must use a communication protocol, such as TCP/IP, and use operating system interfaces, such as an internet socket, to connect to database-related operating system services on the computer on which the remote database is located.

There are multiple scenarios that can lead to this error being returned, including the following scenarios:

  • A database agent could not be started at the remote computer because of a memory allocation failure.
  • A database agent was forced off of the remote computer.
  • A database agent on the remote computer was terminated.
  • The connection was closed by the remote gateway or server at the TCP/IP level.

User response

Systematically investigate and resolve the possible causes:

Failure to start a new database agent
  1. Investigate diagnostic logs at the remote computer to determine whether any memory limits have been exceeded and memory allocation failures happened as a result.
  2. If any memory limits have been reached at the remote computer, or if there were memory allocation failures at the remote computer, work with a database or system administrator to resolve the cause of the memory allocation problems, and then retry the unit of work.
Database agent forced off
  1. Investigate whether any events might have forced a database agent off of the remote computer, such as an administrator forcing all users and agents off the remote computer to perform maintenance.
  2. If database agents have been forced off the remote computer, work with you database or system administrator to bring the database server back online and ready to process requests, and then retry the unit of work.
Database agent terminated
  1. Investigate whether any failures on the remote computer might have terminated a database agent. For example, the termination of a key database manager process might cause the termination of a database agent.
  2. If failures on the remote computer have terminated a key database manager process, work with you database or system administrator to bring the database server back online and ready to process requests, and then retry the unit of work.
Connection closed by the remote gateway or server

Resolve any problems external to the database product that might have caused a TCP/IP connection to be closed on the remote gateway or server. Some examples of problems that could cause the connection to be closed include the following problems:

  • Firewall software errors or failure
  • Power failure
  • Network failure

If you have eliminated the possible causes listed here, collect diagnostic information using the db2support command and then contact IBM software support.

sqlcode: -1645

sqlstate: 08001

SQL1646N A routine failed because the fenced user ID cannot access required files in the sqllib directory or other instance or database directories.

Explanation

The database manager runs user defined functions and stored procedures outside of the DB2 database address space by running those routines as the DB2 fenced user. The default fenced user ID is "db2fenc1" and the default group is "db2fadm1".

The fenced user ID needs to be able to access DB2 database-related files, such as executable and library files, in the sqllib directory and other instance and database directories. When the instance and database directories are created by the database manager, the file and directory operating system permissions are set correctly and should not be changed.

This message can be returned when you are working with fenced stored procedures or routines directly, or when a DB2 utility, such as the health monitor, runs as a fenced mode process.

The most common cause of this error is that the operating system file permissions for DB2 database-related files or directories were accidentally changed after the database manager created the instance and database directories.

User response

Respond to this error by performing the following troubleshooting steps:

  • If possible, determine which file or directory the database manager or the db2fmp process itself was unable to access by reviewing available database diagnostic information (such as the db2diag log files) or operating system diagnostic information.
  • Compare the operating system permissions on DB2 database-related files and directories, including the sqllib directory and the db2fmp executable itself, with the documented default permissions that the database manager would have set when the instance and database directories were initially created.

sqlcode: -1646

sqlstate: 58004

SQL1648N The SQL statement or command cannot be processed because of the state of a DB2 member or CF in a DB2 pureScale environment. Member = member-id. Reason code = reason-code.

Explanation

The state of a DB2 member or CF prevents the SQL statement or command from being processed. This could be a result of one of the following reasons:

1

The database manager is being stopped or started on a member.

2

Member crash recovery is being performed for a failed member.

3

The statement or command cannot be issued from a DB2 member that has a code level higher than the current effective code level (CECL). When there is a fix pack update in progress on a DB2 pureScale instance, you can have DB2 members with a higher code level than the CECL. Some statements and commands can only be issued from DB2 member that have the same code level as the CECL.

4

The statement or command is not supported because there is a fix pack update in progress and at least one DB2 member or cluster caching facility (CF) have a different code level than the CECL. Some statements and commands are only supported when all DB2 members and CFs have the same code level as the CECL. The value of "*N" as the member-id indicates that the condition is not specific to a particular member or CF.

5

A connection to or activation of the database cannot be made because one or more commands, statements, or operations that are not compatible is in progress.

6

After an add member operation, the first use of the database failed because no members have been started.

7

After an add member operation, the first use of the database failed because the database is not active on any previously existing member (a member that was in the database manager instance the last time the database was usable, before the new member was added.) The use of the database was blocked because some actions of the add member operation have not yet completed.

8

A connection to the database for the first time after the member was added failed because of an error while processing it on another member.

9

The operation cannot be initiated from a member that was not on the source member topology.

10

An add member operation was attempted from a different code level than the CECL, or an add member operation was attempted while the database manager instance is in a heterogeneous state.

11

The command failed because after a drop member operation, an explicit connection to the database must be made.

User response

Respond this message by performing the corresponding action for each reason code:

1

Wait until the DB2 member is available. Then re-issue the statement or command.

2

Wait until crash recovery is completed and the DB2 member is available. Then re-issue the statement or command.

3

Perform one of the following actions:

  • Re-issue the statement from a member that has a code level equal to the CECL.
  • Complete the fix pack update so that all members are at the same code level as the CECL, then re-issue the statement from any DB2 member.
4

Complete and commit the fix pack update operation. After all the DB2 members and CFs are at the same code level, retry the operation.

5

Wait until the restricted operation is completed, then rerun the command.

6

Respond to reason code 6 by performing the following actions:

  1. Start a previously existing member (a member that was in the database manager instance the last time the database was usable.)
  2. Connect to or activate the database on that previously existing member.
  3. Re-attempt to connect to the database on the newly added member.
7

Respond to reason code 7 by performing the following actions:

  1. Cause any uncompleted actions of the add member operation to finish by connecting to or activating the database on a previously existing member (a member that was in the database manager instance the last time the database was usable.)
  2. Perform the failed operation again.
8

Make necessary configuration changes to avoid exceeding database or operating system limits and re-issue the command.

9

Connect to the database from a member that was in the source member topology.

10

To add a member, move the database manager instance to a homogeneous state (in other words, bring all DB2 members and CFs to the same code level) and then issue the add member request from a member that is part of the instance.

11

Connect to the database from an existing member, then rerun the command.

sqlcode: -1648

sqlstate: 57061

SQL1649W Deactivate database is successful, however, the database remains available in suspended I/O write operations mode.

Explanation

The database cannot be shutdown while it is in suspended I/O write operations mode. The database will be shut down when I/O write operations are resumed.

User response

No action required. Issue a 'SET WRITE RESUME' command to resume I/O write operations and deactivate the database completely.

SQL1650N The function invoked is no longer supported.

Explanation

The user has attempted to call an API that is no longer supported in this version of the database manager.

User response

The function required may be supported by a different API call.

If your Windows application calls the sqledgne API or the db2DbDirGetNextEntry API with a pre-V9 version number, it must be updated to call the db2DbDirGetNextEntry API with the current version number.

SQL1651N The request cannot be executed because the database server version does not support this functionality.

Explanation

Some new functionality is not supported against older database server versions. Another possible cause of this error could be the request referenced objects with qualifiers of length that exceeds the support of the server version.

User response

Execute the request against a database server where the latest database server version has been installed, or upgrade the server to the latest database server version.

SQL1652N File I/O error occurred.

Explanation

Error occurred either opening, reading, writing, or closing a file.

User response

Check the db2diag log file for details. Also, check for disk full conditions, file permissions, and operating system errors.

SQL1653N An invalid profile path was specified.

Explanation

A full path to a file where server information should be generated must be specified.

User response

Ensure that the profile path specified is correct and not null.

SQL1654N An instance path error was encountered.

Explanation

The instance path could not be returned.

User response

Check that the DB2INSTANCE path was specified correctly. Check that the complete path length specified is not approaching the maximum supported by the operating system.

SQL1655C The operation could not be completed due to an error accessing data on disk.

Explanation

The failure to complete the operation is due to a problem in accessing data on a disk. The SQL statement has been rolled back or the operation has been aborted. The database remains accessible.

User response

The application can retry the operation, although it may continue to fail. If the operation continues to fail, it may be necessary to contact the DB2 system administrator to investigate further.

Check the administration notification log for details that may help to diagnose the problem. Investigate the errors and determine the cause, possibly involving IBM Software Support.

If DB2 data is determined to be in error, then restore and rollforward the table space or database.

If hardware or other software is determined to be the cause, repair the systems involved (possibly requiring a DB2 outage).

sqlcode: -1655

sqlstate: 58030

SQL1656C An error occurred while processing data. The operation could not be completed, but the database remains accessible. Contact IBM Software Support.

Explanation

The failure to complete the operation is due to a detected DB2 page inconsistency. The SQL statement has failed or the operation has been aborted. The database remains accessible.

User response

Contact IBM Software Support for instructions on what diagnostic data to collect to assist in resolving this issue. The application can retry the operation, although it may continue to fail.

sqlcode: -1656

sqlstate: 58004

SQL1657W The database was successfully deactivated. Because the database is an HADR primary database and because the database was in disconnected peer state when it was deactivated, crash recovery will automatically be performed on the database when it is restarted.

Explanation

In general, you can deactivate an HADR primary database using one of the following methods:

  • DEACTIVATE DATABASE command or the sqle_deactivate API
  • db2stop command with the FORCE option

If an HADR primary database is deactivated while it is in disconnected peer state, the database will be deactivated in an inconsistent state, and crash recovery will automatically be performed when the database is restarted.

Attempts to perform offline backup operations on this database will fail until the database is successfully restarted.

User response

No response is required.

When the database is restarted, the database manager will automatically perform crash recovery for this database.

SQL1658N The quiesce operation failed for the object named name. Reason code: reason-code.

Explanation

Before performing maintenance activities, you can force users off of a database manager instance or database by quiescing the object.

The specific reason this message was returned is indicated by the reason-code:

1

An attempt was made to quiesce a database that is in WRITE SUSPEND state.

2

An attempt was made to quiesce a database manager instance in which at least one databases is in WRITE SUSPEND state.

User response

Respond to this error according to the reason code:

Reason code 1

To quiesce a database that is in WRITE SUSPEND state perform the following steps:

  1. Resume writes on the database using the SET WRITE command with the RESUME option or using the db2SetWriteForDB API with the DB2_RESUME_WRITE option.
  2. Re-issue the quiesce operation.
Reason code 2

To quiesce an instance in which there are one or more databases in WRITE SUSPEND state perform the following steps:

  1. Determine which databases are in WRITE SUSPEND state by reefrring to the suspend_io configuration parameter for each database in the instance.
  2. For each database that is in WRITE SUSPEND state, resume writes on the database using the SET WRITE command with the RESUME option or using the db2SetWriteForDB API with the DB2_RESUME_WRITE option.
  3. Re-issue the quiesce operation.

SQL1659N The database manager started with fewer Host Channel Adapters (HCAs) than configured for the cluster caching facilities (CFs) or members.

Explanation

The database manager encountered a non-critical error when starting. Communication could not be established with one or more HCAs on a cluster caching facility (CF) or member, however each CF or member is connected by at least one HCA. With fewer HCAs the CF or member has less throughput capacity. There is also a greater risk of downtime due to the reduced redundancy.

User response

Review cluster alerts by running 'db2cluster -cm -list -alert' to see which HCAs are not responding. Follow the corrective actions given by the alerts to rectify any reported problem.

SQL1660N The Generator at the server, which is used by Discovery to gather server information, has failed.

Explanation

A server system failure has occurred.

User response

Report the failure to your database server administrator. More details of the failure can be found in the server's db2diag log file.

SQL1661N The query failed because the information you are trying to retrieve could not be found on the HADR standby database.

Explanation

The statement or command is trying to retrieve an XML value that is not available on the HADR standby database. This might be because that value has not yet been replayed on the standby.

User response

Retry your query on the read-enabled HADR standby later, or submit the query against the HADR primary database.

sqlcode: -1661

sqlstate: 58004

SQL1662N Log archive compression failed while archiving or retrieving log file log-file for log-archive-method for database database on member member-number. Reason code: reason-code.

Explanation

While archive log file compression is enabled, an error occurred when archiving or retrieving an archived log file.

User response

Check the db2diag.log file for more details.

Contact IBM Support.

SQL1663W Log archive compression is not fully enabled for log-archive-method.

Explanation

Log archive compression is not fully enabled for log-archive-method until log-archive-method is set to DISK, TSM, or VENDOR.

User response

You can change log-archive-method to DISK, TSM, or VENDOR with the UPDATE DATABASE CONFIGURATION command.

SQL1664W A warning code was received from an in-database analytics provider. Warning code: warning-code. Provider name: provider-name. Associated text and tokens: tokens.

Explanation

You can perform in-database analytics using an embedded analytics provider.

While referencing an in-database analytics provider, an unexpected warning code was received from the specified provider.

User response

Respond to this error by performing the following troubleshooting steps:

  • Identify and correct the root cause of the warning by locating the appropriate message text and corrective action for the specified error at the provider.
  • Check any appropriate diagnostic logs that are generated by the provider.

sqlcode: +1664

sqlstate: 01699

SQL1665N The command failed because log archive compression is not supported when raw devices are used for database logging.

Explanation

Log archive compression is not supported when log files, yet to be archived, are on raw devices. You receive this error when:

  • A command to enable log archive compression was issued and the LOGPATH or NEWLOGPATH database configuration parameters already point to raw devices.
  • A command to set the NEWLOGPATH database configuration parameter to a raw device was issued and log archive compression is already active.
  • A command to enable log archive compression and set the NEWLOGPATH database configuration parameter to a raw device was issued.

User response

If you want to use log archive compression, ensure that both LOGPATH and NEWLOGPATH do not point to raw devices.

If you must set NEWLOGPATH to point to a raw device, first disable log archive compression, then retry setting the NEWLOGPATH configuration parameter.

SQL1666N The table definition statement failed because some functionality was specified in the table definition that is not supported with the table type. Unsupported functionality: functionality-keyword.

Explanation

This message is returned when an attempt is made to create or alter a table with functionality that is not supported with that type of table.

The functionality-keyword runtime token lists the clause or keyword that indicates the unsupported functionality.

User response

Review the supported functionality and restrictions of the type of table. Then submit the statement again, specifying only functionality that is supported with the table type.

sqlcode: -1666

sqlstate: 42613

SQL1667N The operation failed because the operation is not supported with the type of the specified table. Specified table: table-name. Table type: table-type. Operation: operation-keyword.

Explanation

This message is returned when an attempt is made to perform an operation against a table that is not supported with that type of table.

User response

Review the supported functionality and restrictions of the type of table. Then submit the statement again, specifying only functionality that is supported with the table type.

sqlcode: -1667

sqlstate: 42858

SQL1668N The operation failed because the operation is not supported with this environment. Reason code: reason-code.

Explanation

This message is returned when an attempt is made to perform an operation that is not supported in a specific environment. The reason code indicates why the operation failed:

1

The database includes one or more column-organized tables and the operation tried to enable or use functionality that is not supported with column-organized tables.

4

An attempt was made to create a column-organized table in an operating system environment that is not supported with column-organized tables.

5

An attempt was made to use column-organized tables in an environment in which intrapartition parallelism is disabled.

6

An attempt was made to use column-organized tables in a partitioned database environment.

7

An attempt was made to use column-organized tables in a DB2 pureScale environment.

8

An attempt was made to create or access a column-organized table in an XA transaction.

9

This message is returned with reason code 9 when an attempt is made to use self-tuning for sort memory with column-organized table functionality:

  • An attempt is made to set one or both of the following configuration parameters to "AUTOMATIC" when there are one or more column-organized tables in the database: SORTHEAP, SHEAPTHRES_SHR.
  • An attempt is made to create a column-organized table while one or both of the following configuration parameters was set to "AUTOMATIC": SORTHEAP, SHEAPTHRES_SHR.
10

An attempt was made to create a shadow table by specifying the MAINTAINED BY REPLICATION clause in a partitioned database environment or in a DB2 pureScale environment.

11

An attempt was made to perform an external table operation in DB2 environment on windows operating system.

User response

Respond to this error according to the reason code:

1

To enable functionality that is not supported with column-organized tables, drop and recreate existing column-organized tables as row-organized tables.

5

Enable intrapartition parallelism and then execute the operation again. Ensure that enough shared sort heap is available by setting the DB2_WORKLOAD registry variable to ANALYTICS or setting the sheapthres database manager configuration parameter to 0.

4, 6, and 7

Create the table as a row-organized table.

8

Respond to reason code 8 in the following ways:

  • Create or access column-organized tables in only non-XA transactions.
  • In XA transactions, create or access only row-organized tables.
9

Respond to reason code 9 in the following ways:

  • To use column-organized tables, or to create a column-organized table), disable self-tuning for sort memory by setting the SORTHEAP and SHEAPTHRES_SHR configuration parameters to appropriate, numerical values instead of "AUTOMATIC".
  • To use self-tuning for sort memory, use row-organized tables instead of column-organized tables.
10

Shadow tables cannot be created in a partitioned database environment or in a DB2 pureScale environment. However, to create a materialized query table that is not a shadow table, create the table without specifying the MAINTAINED BY REPLICATION clause.

11

External table operation cannot be performed in DB2 environment on windows operating system.

sqlcode: -1668

sqlstate: 56038

SQL1669W The operation operation-keyword succeeded. However the following option was ignored: SQL-keyword.

Explanation

This message is returned when an attempt is made to perform an operation that is neither supported with column-oriented tables nor blocked with column-oriented tables.

For example, this message can be returned when an attempt is made to use the ALTER TABLE statement to turn off append mode for a column-organized table. Column-organized tables are always in append mode, so turning append mode off is not supported and attempts to turn append mode off are ignored.

User response

No response is required.

SQL1670N The discover type specified in the DISCOVER database manager configuration parameter indicates discovery is disabled.

Explanation

DISCOVER = DISABLE is configured in the database manager configuration file.

User response

If DISCOVER functionality is required, change the discover type to KNOWN or SEARCH.

SQL1671N The search discovery request failed. Check the administration notification log for further details.

Explanation

The search discovery request failed for one of the following reasons:

  1. Initialization failed (sqleCommonInitializationForAPIs)
  2. Failed to retrieve the client instance path (sqloinstancepath)
  3. Failed to open the output file (sqlofopn)
  4. Failed to write to output file (sqlofprt)
  5. Failed to get memory (sqlogmblk)
  6. Failed to retrieve database manager configuration (sqlfcsys)
  7. DB2 internal system function failed (sqlogpid, sqlogmt)

Check the db2diag log file for details.

User response

  1. If initialization fails, try re-booting the machine or re-installing the product.
  2. If there was an instance path failure, check the DB2INSTANCE value to ensure it is correctly set.
  3. If the open or write to file failed, check that you have access to open and write a file to the <sqllib path>\<instance>\tmp directory on Intel machines, or the <instance path>/sqllib/tmp directory on UNIX machines.
  4. If get memory failed, check the available memory on your machine.
  5. If retrieving the DBM configuration failed, try re-booting the machine or re-installing the product.
  6. If a DB2 internal system function failed, check that the operating system functions on your machine are functioning correctly.

DB2 Service can provide details about the error codes returned by these functions and written to the db2diag log file.

SQL1673N The address list specified as input to the discover interface is invalid.

Explanation

The application program used an invalid input address list pointer. The address list points to nothing.

User response

Ensure that a valid input address list pointer is specified in the application program, and that it is not null.

SQL1674N The server address specified as input to the discover interface is invalid.

Explanation

The application program used an invalid input server address pointer. The server address points to nothing.

User response

Ensure that a valid input server address is specified in the application program, and that it is not null.

SQL1675N Discovery is only allowed against DB2 administration servers. The communications information provided does not access an administration server.

Explanation

A KNOWN discovery request was issued against a database server that is not a DB2 administration server. The communications information specified is not correct.

User response

Verify that DB2ADMINSERVER is set on the database server instance you are accessing. This indicates that the server instance is a DB2 administration server. Retry the KNOWN discovery request with the correct communications information.

SQL1676N The CREATE TABLE STATEMENT failed because functionality that is not compatible with the specified type of table is currently enabled for the database. Incompatible functionality keyword: functionality-keyword.

Explanation

You can create column-organized tables by using one of two different methods:

  • Specifying the ORGANIZE BY COLUMN clause with the CREATE TABLE statement
  • Setting the DFT_TABLE_ORG database configuration parameter to COLUMN and then calling the CREATE TABLE statement without the ORGANIZE BY ROW clause

This message is returned when an attempt is made to create a column-organized table while functionality that is not supported with column-organized tables is enabled in the database. The run-time token functionality-keyword indicates the nature of the functionality that is incompatible.

User response

Respond to this message in one of the following ways:

  • To be able to create a column-organized table, disable the functionality identified in the run-time token functionality-keyword.
  • To create a table with the functionality identified in the run-time token functionality-keyword still enabled, create a row-organized table instead of a column-organized table.

SQL1677N DB2START or DB2STOP processing failed due to a DB2 cluster services error.

Explanation

DB2 cluster services failed to perform the required operation.

User response

Troubleshoot the DB2 cluster services status using the db2cluster command and the db2instance command.

In an environment with multiple members and cluster caching facilities (CFs), collect diagnostic details from the host machine where the members and CFs reside.

SQL1678W DB2START of CF with identifier identifier was not possible on host host-name because the instance was previously stopped using the "db2stop INSTANCE ON" command. CF duplexing is not available on this instance.

Explanation

While multiple cluster caching facilities (CFs) are configured in this database manager instance, the CF has been temporarily disabled by the user from participation in the instance through the use of "db2stop INSTANCE ON" command.

Typical reasons for this are to allow for rolling upgrades of the CF or, to allow the instance to start without CF duplexing. If the CF server failed to start with an error this allows the instance to be started up while the source of the error is resolved by the user.

User response

Once the CF becomes available, issue a "db2start INSTANCE ON" command followed by "db2start CF" command to start the CF and to make it available for the instance. CF duplexing will automatically be re-established by the database manager once the CF is started.

SQL1679N DB2START was unable to start a CF with identifier identifier on host host-name. Reason code reason-code.

Explanation

The reason code indicates why this error was returned:

1

This message can be returned with reason code 1 for multiple reasons, including the following reasons:

  • The host on which the cluster caching facility (CF) is located is unavailable.
  • A TCP/IP communication error occurred while trying to establish a connection with the host on which the CF is located.
  • DB2 cluster services was unable to allocate memory for the CF because the CF memory database manager configuration parameter CF_MEM_SZ is set to a value that is larger than the amount of memory that is available.

User response

Respond to this message according to the reason code:

1
  1. Perform the following troubleshooting activities:
    • Ensure that the host has the proper authorization defined in the .rhosts or the host.equiv files to execute remote commands.
    • Ensure that the application is not using more than the maximum allowed file descriptors at the same time: 500 + (1995 - 2* total_number_of_nodes)
    • Ensure all the Enterprise Server Edition environment variables are defined in the profile file.
    • Ensure the profile file is written in valid Korn Shell script format.
    • Ensure that all the host names defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
    • Ensure that the DB2FCMCOMM registry variable specifies the correct IP format to use (TCPIP4 or TCPIP6).
    • Ensure that the CF_MEM_SZ database manager configuration parameter is set to a valid value.
  2. Then, rerun the DB2START command.

SQL1680W An error occurred during DB2START processing of DB2 member with identifier identifier on host host-name. Reason code reason-code. The database manager will asynchronously attempt to start the member in recovery mode on another available host.

Explanation

An error was encountered while attempting to start the member on the host. The DB2START command has failed as a result of this error.

The reason code indicates why this error was returned:

1

Host is not reachable because the host is unavailable or a TCP/IP communication error occurred while trying to establish a connection with the host.

User response

Respond to this message according to the reason code:

1

For reason code 1, perform the following troubleshooting activities:

  1. Ensure that the host has the proper authorization defined in the .rhosts or the host.equiv files
  2. Ensure that the application is not using more than (500 + (1995 - 2* total_number_of_nodes)) file descriptors at the same time.
  3. Ensure all the Enterprise Server Edition environment variables are defined in the profile file.
  4. Ensure the profile file is written in the Korn Shell script format.
  5. Ensure that all the host name defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
  6. Ensure that the DB2FCMCOMM registry variable is set correctly.
  7. Rerun the DB2START command.

SQL1681W DB2START of DB2 member with identifier identifier was not possible on host host-name as the instance was previously stopped using the "db2stop INSTANCE ON" command. The database manager will asynchronously attempt to start the DB2 member in light mode on another available host. While in recovery mode, the DB2 member will not accept any client connections.

Explanation

The instance on the host was previously stopped by "db2stop INSTANCE ON" command. One of the reasons for doing so is to bring down the host for maintenance or software rolling upgrade. The member could not be started on this host. However, the database manager will attempt to start it in light mode on another available host.

User response

The user can issue DB2 LIST command to find out if and on which host the member has been started. Once the software upgrade or maintenance work has been completed on the host, the user should issue "db2start INSTANCE ON" command to start up the instance on the host and then reissue "db2start MEMBER" command to relocate the member to this host.

SQL1682W DB2START processing was successful on host host-name. Due to a previous DB2START failure of a DB2 member or host failure, the DB2 member has been relocated by the database manager to this host.

Explanation

When the member was previously stopped, it was running in restart light mode. It will continue to run in restart light mode until its home host becomes active and database manager relocates it to its home host.

User response

No user response is required.

SQL1683N An error was encountered during DB2START processing. The database manager failed to restart the DB2 member with identifier identifier as a light member on host host-name.

Explanation

The member failed to start as a light member on the host either because there was no DB2 idle processes running on the host or the animation of one of the DB2 idle processes failed.

User response

Investigate the problems on the host.

SQL1684N An error was encountered during DB2START processing. The database manager failed to start a component of the DB2 pureScale environment.

Explanation

A component of the DB2 pureScale environment failed to start due to insufficient memory, CPU resources, or a problem with the DB2 cluster file system.

User response

Run the db2cluster command to check the health of the DB2 cluster file system. Also ensure that the hosts in the DB2 pureScale instance have sufficient memory and CPU resources.

SQL1685N An error was encountered during DB2START processing of DB2 member with identifier identifier because the database manager failed to start one or more CFs.

Explanation

The database manager failed to start the cluster caching facilities (CFs), therefore the DB2 member could not be started.

There are multiple reasons for which this message can be returned. For example, this message can be returned because the CF_MEM_SZ memory configuration parameter was set to a value that is larger than the physical memory limit of the system. When this message is returned because CF_MEM_SZ is set too large, there will be messages in the db2diag log files indicating that there are not enough system resources to process requests.

User response

  • Ensure that the instance is configured with functioning CFs by performing the following steps:
    1. Identify problems with any CFs using the following db2cluster command:
      db2cluster -cm -list -alert
    2. Resolve the identified problems using the db2cluster command with the -clear parameter:
      db2cluster -cm -clear -alert
  • If the CF is under maintenance, run the "db2start INSTANCE ON" command after the maintenance has completed.
  • To force the database manager instance to start without a redundant CF, manually start one CF by issuing the command "db2start 129", then start the instance by issuing the db2start command again.

SQL1686N An error was encountered during DB2START processing on host host-name as the database manager failed to activate the host.

Explanation

The database manager tried to start up the instance on the host while the DB2 cluster services failed to make the host active and rejoin the DB2 pureScale cluster.

User response

Determine why the DB2 cluster services failed to make the host active and rejoin the DB2 cluster.

SQL1687N An error was encountered during DB2STOP processing. The DB2 member with identifier identifier is performing restart recovery, or has unresolved indoubt transactions.

Explanation

The member cannot be stopped when it is still performing restart recovery or has unresolved indoubt transactions.

User response

  1. Determine the status of this member using the db2instance command with the -list parameter. You can also use the DB2_MEMBER administrative view or the DB2_GET_INSTANCE_INFO table function.
  2. Resolve the indoubt transactions, if they exist.

SQL1688N DB2STOP failed to stop the CF with identifier identifier. Reason code reason.

Explanation

The reason code indicates why this error was returned:

1

The cluster caching facility (CF) still contains dirty pages or holds locks.

2

The named CF is the only running CF in the instance.

3

The primary CF cannot be stopped until the secondary CF is in PEER state and ready to take over. The secondary CF has not yet completed the transition from the initial CATCHUP state to a PEER state.

4

The instance is in the process of failing over the CF primary role, no CF can be stopped.

User response

Respond to this message according to the reason code:

1

Ensure that no active member is running. The user should also wait for the CF to flush out dirty pages before issuing the "db2stop CF" command again.

2

Perform the following steps:

  1. If there are active members, stop each of the members using the "db2stop MEMBER" command.
  2. After the members have been stopped, stop the CF with a global call to db2stop.
3

Wait for the secondary CF to transition to a PEER state before re-running this command. Refer to the STATE column in the DB2_CF administrative view for this information.

4

Stop the instance by running a global "db2stop FORCE" command.

SQL1689W DB2STOP processing was successful. However, the DB2 member with identifier identifier was running in recovery mode on a host other than its home host host-name.

Explanation

The member was successfully stopped, however the host it was running on was not its home host. It was running in light mode on another DB2 member's host. Typically it is not advisable to stop DB2 members that are running in light mode.

User response

No user response is required.

It is recommended that if the member is running in light mode on a host other than its home host, the user performs the necessary actions so that the member is to be relocated by the database manager to its home host before stopping it.

SQL1690N An error occurred during DB2STOP processing of a DB2 member or CF with identifier identifier on host host-name. Reason code reason-code.

Explanation

The reason code indicates why this error was returned:

1

The host is not reachable because the host is unavailable or a TCP/IP communication error occurred while trying to establish a connection with the host.

2

The cluster manager successfully stopped the DB2 member or cluster caching facility (CF) even though there was a communication error.

This message can also be returned when a password has expired.

User response

Respond to this message according to the reason code:

1

Perform the following troubleshooting activities for reason code 1:

  • Ensure that the host has the proper authorization defined in the .rhosts or the host.equiv files
  • Ensure that the application is not using more than (500 + (1995 - 2* total_number_of_nodes)) file descriptors at the same time.
  • Ensure all the Enterprise Server Edition environment variables are defined in the profile file.
  • Ensure the profile file is written in the Korn Shell script format.
  • Ensure that all the host name defined in the db2nodes.cfg file in the sqllib directory are defined on the network and are running.
  • Ensure that the DB2FCMCOMM registry variable is set correctly.
  • Verify whether the member or CF has been stopped by running the command "db2instance -list".

Then, rerun the DB2STOP command.

2

Verify whether the member or CF has been stopped by running the command "db2instance -list".

Review the db2diag log files for more information.

SQL1691N An error was encountered during DB2STOP processing on host host-name. Reason code reason-code. The database manager failed to bring down the host for maintenance.

Explanation

The reason code indicates why this error was returned:

1

One or more DB2 members or cluster caching facilities (CFs) were still active on the host and could not be stopped.

2

The instance was still active and the CF running on this host is not stoppable.

The instance on the host could not be stopped due to active DB2 members or CFs were running.

User response

Respond to this message according to the reason code:

1

Run "db2stop MEMBER" or "db2stop CF" command to stop the member or CF prior to stop the instance on the host. To force the instance on the host to shut down, run "db2stop INSTANCE ON" command with FORCE option.

2

Ensure all members are stopped and retry "db2stop INSTANCE ON" command

SQL1692N An error was encountered during DB2STOP processing. The database manager failed to stop a component of the DB2 pureScale environment.

Explanation

A component of the DB2 pureScale environment failed to respond to the DB2 cluster services and did not shut down.

User response

  1. Determine which components of the database manager instance failed to stop using the following command:
    db2instance -list
  2. Stop the components that failed to stop by performing the following steps:
    1. Collect more information about the reasons why these components failed to stop from the diagnostic information collected in the db2diag log files.
    2. Resolve the problems that caused the components to fail to stop.
    3. Stop the components manually.
  3. [Optional] Clean up interprocess communications for the instance by running the following command as the instance owner at each physical partition:
    $HOME/sqllib/bin/ipclean

SQL1693N An error was encountered during DB2STOP processing on host host-name as the database manager failed to deactivate the host. The database manager failed to bring down the host for maintenance.

Explanation

The database manager tried to stop the instance on the host while the DB2 cluster services failed to temporarily take the host out of the DB2 pureScale cluster.

User response

Determine why the DB2 cluster services failed to temporarily take the host out of the DB2 pureScale cluster

SQL1694N The command option option is not valid for a DB2 pureScale instance.

Explanation

Some options are only supported on certain instance types. The option that was specified is not available with a DB2 pureScale instance.

User response

Use the supported command options for DB2 pureScale instance.

sqlcode: -1694

sqlstate: 56038

SQL1695N The command option option is not valid for an instance that is not a DB2 pureScale instance.

Explanation

Some options are only supported on certain instance types. The option that was specified is not available with an instance that is not a DB2 pureScale instance.

User response

Use the supported command options for instances that are not DB2 pureScale instances.

sqlcode: -1695

sqlstate: 56038

SQL1696N Statement precompilation failed because the option COMPATIBILITY_MODE ORA was not specified. Reason Code: reason-code.

Explanation

You can process an application program source file containing embedded SQL statements to produce a modified source file that contains host language calls for the SQL statements and to produce a package in the database by using the PRECOMPILE command or the PREP command.

You can configure the way the application source file is compiled by specifying precompile options with the PRECOMPILE command. For example, you can enable features that facilitate the migration of embedded SQL C applications from other database systems by specifying the precompiler option COMPATIBILITY_MODE ORA with the PRECOMPILE command.

This message is returned when an attempt is made to use a feature that requires the precompiler option COMPATIBILITY_MODE to be set to ORA, but the COMPATIBILITY_MODE ORA option was not specified.

The reason code, reason-code, indicates the reasons for the precompilation failure:

1

The UNSAFENULL precompile option was specified without the required COMPATIBILITY_MODE ORA option.

2

The "EXEC SQL COMMIT WORK RELEASE" or "EXEC SQL ROLLBACK WORK RELEASE", "EXEC SQL COMMIT RELEASE", or "EXEC SQL ROLLBACK RELEASE" statement was found in the embedded SQL code and PRECOMPILE command was issued without the required COMPATIBILITY_MODE ORA option.

User response

Call the PRECOMPILE command again, specifying the required COMPATIBILITY_MODE ORA option.

SQL1697N The statement cannot be precompiled because an indicator variable structure was specified that contains fewer members than the corresponding host variable structure. Indicator variable structure name: variable-name. Number of members in the host variable structure: number-of-members.

Explanation

In embedded SQL applications, information about the contents of host variable structures can be stored in corresponding indicator variable structures. When an indicator variable structure is specified, the number of members in the indicator variable structure must be equal to the corresponding host variable structure.

This message is returned when the number of members in an indicator variable structure does not equal the number of members in the corresponding host variable structure.

User response

  1. Modify the embedded SQL application to declare equal number of members in the indicator variable structure as that of the host variable structure.
  2. Recompile and rerun the embedded SQL application.

SQL1698N The START DATABASE MANAGER command failed on a DB2 pureScale instance where fix pack updates are being applied or have been applied. Reason code: reason-code.

Explanation

The reason code indicates why the START DATABASE MANAGER command failed:

1

The fix pack update installation on the member or cluster caching facility (CF) is corrupted.

2

During an online fix pack update, an attempt was made to start a member or CF with a code level lower than the current effective code level (CECL). To start a member or CF, their code level must be equal or higher to the CECL.

3

During an offline fix pack update, an attempt was made to start a member or CF with a code level that is not equal to the CECL. To start a member or CF, their code level must be equal to the CECL.

4

The fix pack update installation on a member or CF is incomplete.

5

The information about the CEAL and CECL is corrupted.

6

The CEAL or CECL database manager configuration parameter has an invalid value.

7

The instance information is missing from the configuration file for fix pack updates.

User response

Respond this message by performing the corresponding action to the reason code:

1

Retry the fix pack update operation.

2

Update the member or CF to a code level equal or higher than the CECL. Then restart the member or CF.

3

Ensure that all members and CFs are at a code level equal to CECL. Then restart the member or CF.

4

Retry the fix pack update operation.

6

Recreate the instance.

7

Contact IBM support to assist you in the repair of the configuration file.

SQL1699N The specified member subset attribute is not valid. Reason code = reason-code Attribute name: attribute-name Value: value

Explanation

The statement cannot be processed because of the following reason code:

1

The specified value is only valid in a data sharing environment.

2

You cannot change a member subsets catalogDatabaseAlias attribute without also changing the databaseAlias attribute.

3

The database name cannot be used for the database alias attribute in a member subset.

User response

The action corresponding to the reason code is as follows:

1

Reissue the member subset management routine with a different attribute value.

2

Specify a new databaseAlias attribute value or do not change the catalogDatabaseAlias attribute value.

3

Specify another name for the databaseAlias attribute value.

sqlcode: -1699

sqlstate: 530AA

SQL1700N The reserved schema name name was found in the database during database upgrade.

Explanation

The database contains one or more database objects using the schema name name which is a reserved schema name in the DB2 copy version to which you want to upgrade the database.

The command cannot be processed.

User response

Ensure that all the database objects that use the reserved schema name are dropped and recreate the objects using a different schema name.

Reverse the database upgrade and make the corrections using the DB2 copy version where the database resided prior to the database upgrade.

Ensure that no reserved schema names are in use before attempting the database upgrade again.

Then, re-issue the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade the database.

SQL1701N The database cannot be upgraded because the database terminated abnormally.

Explanation

The database terminated abnormally (for example, due to a power failure) before attempting to upgrade the database. You must restart the database before you can upgrade the database successfully.

The command cannot be processed.

User response

You must issue the RESTART DATABASE command using the DB2 copy where the database resided prior to attempting to upgrade the database. Then, re-issue the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade.

SQL1702W The protocol connection managers have started successfully.

User response

No action required.

SQL1703W The db2event directory could not be created during database upgrade.

Explanation

The database was upgraded successfully but the db2event directory could not be created.

This is a warning only.

User response

The db2event directory must be created to use the event monitor. The db2event directory must be created in the database directory where the upgraded database resides. The database directory of the upgraded database can be determined by issuing the LIST DATABASE DIRECTORY command.

SQL1704N Database upgrade failed. Reason code reason-code.

Explanation

Database upgrade failed. The reason codes are as follows:

2

database cannot be upgraded because it could be in one of the following states:

  • backup pending state
  • restore pending state
  • roll-forward pending state
  • transaction inconsistent state
  • HADR has marked the database inconsistent
3

database logs are full.

4

insufficient disk space.

5

cannot update database configuration file.

7

failed to access the database subdirectory or one of the database files.

8

failed to update database container tag.

9

table space access is not allowed.

17

Failure to allocate new page from the system catalog table space.

21

Database upgrade is complete on the catalog partition but not on all the other database partitions. There are database partitions that cannot be upgraded due to system errors, such as node failure or connection failure.

22

Database upgrade failed because the catalog partition cannot be upgraded due to system errors, such as database partition failure or connection failure.

24

Error creating the dbpath/db2event/db2detaildeadlock event monitor directory where dbpath is the file path used to create the database.

25

Database upgrade failed because the HADR primary's log shipping position does not match the HADR standby's log replay position.

User response

Possible solutions based on the reason code are:

2

Reverse the database upgrade and correct the database state by performing any necessary corrective action in the DB2 copy version where the database resided prior to the upgrade. For HADR systems, stop HADR should be issued prior to attempting to upgrade the HADR primary database. Resubmit the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade the database.

3

Increase the database configuration parameters logfilsiz or logprimary to a larger value. Resubmit the UPGRADE DATABASE command.

4

Ensure that there is sufficient disk space and resubmit the UPGRADE DATABASE command.

5

There was a problem in updating the database configuration file. Ensure that the database configuration file is not being held exclusively by any users and is updatable. Resubmit the UPGRADE DATABASE command. If the problem persists, inform your IBM service representatives.

7

Restore the database from the database backup.

8

Resubmit the UPGRADE DATABASE command. If the problem persists, contact your IBM service representative.

9

Reverse the database upgrade and correct the table space access. Resubmit the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade the database. Refer to message SQL0290N for the suggested actions to take to correct the table space.

17

If the system catalog table space is an Automatic Storage DMS table space or SMS table space, ensure that there is at least 50% free disk space available for the system catalog table space, then upgrade the database. If the system catalog table space is a DMS table space. Reverse the database upgrade and add more containers to the system catalog table space from the DB2 copy version where the database resided prior to upgrade. You should allocate 50% free space for database upgrade. Resubmit the UPGRADE DATABASE command from the DB2 copy version to which you want to upgrade the database.

21

Check the administration notification log to determine the database partitions that cannot be upgraded. Correct the situation and resubmit the UPGRADE DATABASE command. As database upgrade only takes place on database partitions that require upgrade, you can submit the UPGRADE DATABASE command from any database partition.

22

Correct the database partition failure situation on the catalog partition. Resubmit the UPGRADE DATABASE command.

24

Remove the dbpath/db2event/db2detaildeadlock event monitor directory where dbpath is the file path used to create the database. Resubmit the UPGRADE DATABASE command.

25

Issue the STOP HADR command on the primary database followed by reissuing the UPGRADE DATABASE command. The standby database will have to be re-initialized.

SQL1705W Unable to update a database directory entry to the current release level.

Explanation

One or more database aliases could not be updated in the database directory for a database which has just been upgraded from a previous release.

User response

Uncatalog database aliases for the upgraded database and re-catalog them using the same information.

SQL1706W At least one non local database was detected in the node directory for this instance during word size instance update.

Explanation

While performing word size instance update, at least one database not created under this instance was encountered. Such databases must have the same word size as this instance for instance update to complete successfully.

User response

Ensure that all databases cataloged at the instance have the same word size.

SQL1707N Unable to update the instance word size.

Explanation

There was an error while attempting to update the word size of the instance. Please contact your IBM service representative.

User response

Contact your IBM service representative.

SQL1708W Database upgrade is completed with the warning-code warning code.

Explanation

Database upgrade is completed with a warning. The warning codes are as follows:

1

One or more database partitions were not upgraded.

User response

Possible solution based on the warning codes:

1

Re-issue the UPGRADE DATABASE command.

SQL1709N The CREATE INDEX statement failed because the RANDOM keyword was specified and functionality that is not supported with the RANDOM keyword was included in the index definition. Reason code: reason-code.

Explanation

You can reduce some types of index page contention in DB2 pureScale environments by randomizing the keys of indexes. Specifying the RANDOM keyword for a column will cause the index keys for that column to be randomized.

There are some restrictions on functionality that is supported with the RANDOM keyword. This message is returned when a CREATE INDEX statement includes the RANDOM keyword, but some other functionality that is included in the index definition is not supported with the RANDOM keyword.

The reason code indicates more specifically why this message was returned:

1

The RANDOM keyword was specified for a column that is a of type CHAR or VARCHAR, the database was using UCA collation and the column was not defined as FOR BIT DATA.

2

The RANDOM keyword was specified for a column that is a of type GRAPHIC or VARGRAPHIC and the database was using UCA collation.

3

The index definition included one or more expression-based keys.

User response

Respond to this error according to the reason code:

1

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

  • Resubmit the CREATE INDEX statement, specifying the RANDOM keyword with a column that is a data type that is supported with the RANDOM keyword.
  • Alter the column so that the column is identified as FOR BIT DATA by issuing the ALTER TABLE statement, reorganize the table, and then resubmit the CREATE INDEX statement.
2

Resubmit the CREATE INDEX statement, specifying the RANDOM keyword with a column that is a data type that is supported with the RANDOM keyword.

3

Resubmit the CREATE INDEX statement using either the RANDOM keyword or an expression-based key but not both.

sqlcode: -1709

sqlstate: 42997

SQL1710N The operation cannot be performed because the source member topology and the target member topology have no common member.

Explanation

The target member topology does not contain a common member with the source member topology. The source and target members must have at least one common member.

User response

Rerun the command against an instance with at least one common member with those in the source member topology.

SQL1712N The command failed. The source and target member topologies are different, and the source and target instances are not at the same database product level. Command: command-token

Explanation

The specified command failed because both conditions are true:

  • The source and target member topologies are different, and
  • The source and target instances are not at the same database product level.

For the specified command to run successfully, you must fix one of these conditions.

User response

You can either:

  • Upgrade the down-level source database to the higher level, then rerun the command, or
  • Match the topologies by either adding or dropping a member to the source member topology or the target member topology.

SQL1713N CATALOG DATABASE command failed. One or more files in the member database directories do not belong to the same database.

Explanation

The command failed because an inconsistency was found in at least one of the files.

User response

Cleanup the member database directories for the members that do not belong to this database, and rerun the command.

SQL1714N The ROLLFORWARD command failed because it was run on a member that did not exist in the source member topology.

Explanation

Following a backup and restore, if the target member topology contains all the member identifiers contained in the source member topology, you can roll forward through one or more add member events in the transaction logs. However, the ROLLFORWARD command must be run from a member that existed in the source member topology at the time of the backup operation.

User response

Rerun the ROLLFORWARD command from a member that existed in the original source member topology.

SQL1715N The rollforward operation encountered an add member event for a member that does not exist in the current member topology.

Explanation

During a roll forward operation, if the ROLLFORWARD command encounters an add member log record for a member, that member must exist in the member topology.

User response

Add the member that was on the source member topology and is not in the current member topology. Rerun the ROLLFORWARD command.

SQL1716N Alter or drop the member failed because the resulting subset does not have a primary member.

Explanation

A member subset must contain at least one primary member.

User response

Before dropping or altering the specified member, add another primary member to the subset. To add another member to the subset, run the SYSPROC.WLM_ALTER_MEMBER_SUBSET routine. If you no longer need the member subset, drop the member subset by running WLM_DROP_MEMBER_SUBSET statement.

sqlcode: -1716

sqlstate: 530AB

SQL1717N Connection to the database alias rejected because the application was assigned to a member subset that is disabled. Database alias: database-alias-token Member subset: member-subset-token

Explanation

The connection request was rejected because the application was assigned to a disabled member subset.

User response

You can either connect to a different database alias or enable the member subset. To enable the subset, use the alter member subset management routine WLM_ALTER_MEMBER_SUBSET.

sqlcode: -1717

sqlstate: 08001

SQL1718N The database alias database_alias cannot be uncatalogued.

Explanation

If a database alias was cataloged using member subset routine WLM_CREATE_MEMBER_SUBSET, the database alias must be uncataloged using a member subset routine. Neither the UNCATALOG DB command nor the sqleuncd() API can be used to uncatalog this database alias.

User response

Uncatalog the database alias using member subset routine WLM_DROP_MEMBER_SUBSET.

SQL1719N The SQL statement failed because column-organized tables are not supported. Reason code: reason-code

Explanation

Column-organized tables are not supported when certain conditions are true. The conditions are indicated by the following reason codes:

1

Intra-partition parallelism is disabled.

2

Database partitioning feature is enabled.

3

DB2 pureScale feature is enabled.

User response

Perform the action corresponding to the reason code to enable support of column-organized tables:

1

Enable Intra-partition parallelism and re-issue the SQL statement.

2

Re-create the table as row-organized table and re-issue the SQL statement.

3

Re-create the table as row-organized table and re-issue the SQL statement.

sqlcode: -1719

sqlstate: 56038

SQL1720N Could not drop the only member.

Explanation

You cannot drop the only member that the database could be connected to because dropping the member, results in dropping the database. The database must be dropped first.

User response

First drop the database, then drop the member.

SQL1721N Starting the database manager failed because of a problem with a configuration file that is needed by RDMA.

Explanation

In DB2 pureScale environments, you can specify that communication between the cluster caching facility (CF) and DB2 members uses Remote Direct Memory Access (RDMA) by setting the database manager configuration parameter CF_TRANSPORT_METHOD to "RDMA".

This message is returned when the CF_TRANSPORT_METHOD configuration parameter is set to "RDMA" and there is a problem with configuration files related to RDMA functionality.

Examples of problems that could cause this message to be returned:

  • The direct access transport (DAT) configuration file, dat.conf, is missing or contains invalid entries
  • Files are missing from the OpenFabrics Enterprise Distribution (OFED) package

User response

Respond to this error in one of the following ways:

  • If using RDMA is not needed, unset the CF_TRANSPORT_METHOD database manager configuration parameter.
  • To use RDMA, verify files associated with DAT configuration, such as the dat.conf file, and file associated with the OFED software.

SQL1722N The configuration parameter was not updated because the keyword MEMBER was used and the configuration parameter cannot be set to the specified value on a per-member basis. Configuration parameter: configuration-parameter. Specified value: specified-value.

Explanation

You can configure aspects of your database manager instance by calling the UPDATE DATABASE MANAGER CONFIGURATION command to set database manager configuration parameters. You can configure aspects of individual databases by calling the UPDATE DATABASE CONFIGURATION command to set database configuration parameters.

In a DB2 pureScale environment, some configuration parameters can be set on a local, per-member basis. When you set a local value for a specific DB2 member the local value overrides the global (instance-wide or database-wide) value. To set a configuration parameter locally to a particular member, you would specify the MEMBER keyword with the UPDATE DATABASE MANAGER CONFIGURATION command or the UPDATE DATABASE CONFIGURATION command.

Some configuration settings are valid as global settings, but are not supported as per-member settings. This message is returned when an attempt is made to set a configuration parameter locally for a DB2 member to a value that is not supported as a per-member setting.

User response

Respond to this message in one of the following ways:

  • To set the configuration parameter to the specified value globally, call the command again without the MEMBER keyword.
  • To set the configuration parameter on a per-member basis, review the supported values for the configuration parameter and then call the command again specifying only supported values.

SQL1723N The CREATE TABLESPACE statement or ALTER TABLESPACE statement failed because a file system caching option was specified that is not supported in the current environment.

Explanation

File caching allows you to save recently used data on the disk for quick access in subsequent calls to the same data. Enabling file system caching can improve your database performance if you often use the same set of data.

There are restrictions on and requirements for using file caching. There are also restrictions on and requirements for bypassing file caching in some environments. This message is returned when an attempt is made to use file system caching or bypass file system caching in an unsupported environment, such as a disk sector size that is not supported.

User response

  1. Review supported file system caching configurations.
  2. Make changes to resolve the restriction that was encountered or satisfy the requirement that was missed by performing one or more of the following kinds of troubleshooting actions:
    • Change the environment: format the target disk to have the required sector size.
    • Change the statement: enable file system caching using the FILE SYSTEM CACHING option.
  3. Reissue the statement.

SQL1724W The table table-name was successfully created as a column-organized table. However, one or both of the SORTHEAP and SHEAPTHRES_SHR configuration parameters is currently set to a value that cannot be used with column-organized tables.

Explanation

You can enable self-tuning for sort memory by setting the database configuration parameters SORTHEAP and SHEAPTHRES_SHR to "AUTOMATIC".

Self-tuning for sort memory is not supported with column-organized tables.

This message is returned when a column-organized table is created while either of the following configuration parameters is set to "AUTOMATIC": SORTHEAP and SHEAPTHRES_SHR.

User response

To use column-organized tables, set both of the configuration parameters SORTHEAP and SHEAPTHRES_SHR to a fixed value.

SQL1725N Could not perform the specified action because the status of the indoubt transaction changed after you issued the LIST INDOUBT TRANSACTIONS command.

Explanation

When you run the LIST INDOUBT TRANSACTIONS command on the client, it returns the current state of the indoubt transactions. However, the output is not refreshed on the client if the status changes on the server. If the status of an indoubt transaction is not synchronized between the server and the client, you might not be able to perform all of the actions that are listed as valid options in the LIST INDOUBT TRANSACTIONS command output.

User response

Quit the interactive window and reissue the LIST INDOUBT TRANSACTIONS command to obtain the most recent status of the indoubt transactions from the server.

SQL1726N The database manager was not started because the CF_TRANSPORT_METHOD database manager configuration parameter is set to "TCP" but the Ethernet card is not at least 10GE.

Explanation

In DB2 pureScale environments, you can specify that communication between the cluster caching facility (CF) and DB2 members be done using sockets by setting the database manager configuration parameter CF_TRANSPORT_METHOD to "TCP". To use the sockets communication method, you must be using at least a 10GE Ethernet card.

This message is returned when the CF_TRANSPORT_METHOD configuration parameter is set to "TCP" but an Ethernet card of at least 10GE has not been configured.

User response

Respond to this message in one of the following ways:

  • To use the sockets communication method, perform one of the following tasks:
    • Configure a 10GE network.
    • To use a Ethernet that is not at least 10GE, set the DB2_SD_ALLOW_SLOW_NETWORK registry variable to ON.
  • To use a different communication method set the CF_TRANSPORT_METHOD configuration parameter to a different value, such as "RDMA".

SQL1727N The statement was not precompiled because the following host variable array or structure array contains an unsupported data type: variable_name

Explanation

The COMPATIBILITY_MODE ORA precompile option allows the use of host variable arrays, structure arrays, and indicator arrays in an embedded SQL statement. A host variable array or structure array declared for an INSERT, UPDATE, or DELETE statement must contain supported data types.

User response

  1. Remove the unsupported data types in the declared host variable arrays, or structure arrays.
  2. Precompile the modified embedded SQL application.

SQL1728N The command or operation failed because the keystore could not be accessed. Reason code reason-code.

Explanation

DB2 native encryption stores encryption keys in a keystore file. To use this functionality, you must perform the following set-up and configuration tasks:

  • Create a keystore file (also known as a key database) for storing encryption objects, such as private keys.
  • Configure the database manager to use the keystore file by setting encryption configuration parameters, such as KEYSTORE_TYPE and KEYSTORE_LOCATION.
  • Manage passwords for accessing the keystore file (save the password in a stash file, for example.)

This message is returned when the database manager fails to retrieve or update information in the keystore file while performing one of several different types of operations:

  • Creating an encrypted database
  • Creating an encrypted backup image of a database
  • Restoring an encrypted backup image
  • Issuing a DB2 command, such as db2cklog, against an encrypted database

The reason code indicates more specifically the reason for the failure:

1

The following database manager configuration parameters are not set to valid and compatible values: KEYSTORE_LOCATION, KEYSTORE_TYPE.

2

The keystore file specified in the KEYSTORE_LOCATION database manager configuration parameter does not exist.

3

No password was given (the password required to open the keystore is not stashed and no password was provided with the command.)

4

The given password (the password that is stashed or that was provided with the command) is not valid to access the keystore file.

5

Reason code 5 can be returned for three general reasons:

  • The database manager process ran as the instance owner ID, and the instance owner ID does not have read permission and write permission for the keystore file.
  • A DB2 utility was invoked by a user other than the instance owner.
  • The disk containing the keystore file is out of space.
6

The database manager failed to process the contents of the keystore file.

Example: If the database manager is configured to use a keystore file that is compliant with the PKCS#12 standard, but the format of the keystore file is not compliant with the PKCS#12 standard, then the database manager will be unable to use the keystore file.

7

An error was returned from an IBM Global Security Kit (GSKit) command. The GSKit error details were printed in the db2diag diagnostic log file.

User response

Resolve the problem according to the reason code, and then retry reissue the command:

1

Set both of the database manager configuration parameters KEYSTORE_LOCATION and KEYSTORE_TYPE to valid and compatible values.

2

Set the KEYSTORE_LOCATION database manager configuration parameter to a valid file name.

3, 4

Provide the database server with a valid password for accessing the keystore file in one of the following ways:

  • Recreate the stash file
  • Provide the keystore password as an argument to the command
5

Respond to reason code 5 in the following ways:

  • Set the keystore file permissions so that the file can be read and written to by only the instance owner ID.
  • Invoke encryption-related DB2 utilities, such as dbckbkup, as the instance owner.
  • If this message is returned because the disk containing the keystore file is out of space, increase the amount of space that is available on that disk.
6

Recover the current keystore file from a backup copy.

7

Review the GSKit error that is printed in the db2diag diagnostic log file, correct the problem that is causing the GSKit error, and then reissue the command. If the GSKit errors continue, contact IBM Software Support for assistance.

SQL1729N The command failed because the label label does not exist in the keystore.

Explanation

DB2 native encryption stores encryption keys in a keystore. Keys are accessed by a master key label, which is also stored in the keystore. When you issue DB2 commands against databases that are configured to use this functionality, the database manager must look up the appropriate key using a label:

  • You can specify the label as a parameter to the command.
  • If you do not specify a label, the database manager will use the label that is configured for the database.

This error is returned when a label is specified with a command parameter but the specified label could not be found in the keystore.

User response

Respond to this error in one of the following ways:

  • Reissue the command, specifying a label that exists in the keystore.
  • Reissue the command without specifying a label to cause the label that is configured for the database to be used automatically.

SQL1730N The command or operation failed because the master key label does not exist in the keystore. Label being used: label. File type number: file-type-number. File name: file-name.

Explanation

DB2 native encryption stores encryption keys in a keystore. When you issue DB2 commands against databases that are configured to use this functionality, the database manager must look up the appropriate key using a label:

  • You can specify the label as a parameter to the command.
  • If you do not specify a label, the database manager will use the label that is configured for the database. Sometimes the database manager will save a label in a log file, a configuration file, or a backup image and then retrieve that saved label as appropriate.

This message is returned when the database manager retrieves a label that was successfully used in past operations (saved in a log file, for example) but the label cannot be found in the current keystore. This error scenario can arise in multiple ways, including the following examples:

  • A label was deleted from the keystore.
  • An older copy of the keystore was restored and the restored copy does not contain the label.
  • A label that was available in a previously used keystore was not migrated to the currently configured keystore.
  • An attempt is made to restore a backup image which references a label, but that label is not in the keystore configured on the host machine where the restore operation is happening.
  • An attempt is made to roll forward through transactions in archived log files that reference a label, but that label is not in the keystore configured on the host machine where the transactions are being replayed.
  • The contents of the keystore where a high availability disaster recovery (HADR) primary database resides do not match the keystore contents where the corresponding standby database resides.

The runtime token file-name indicates the name of the file in which the reused label appeared. The file-type-number runtime token indicates the type of file in which the reused label appeared:

1

Database log file

2

Configuration file

3

Backup image

User response

Respond to this error in one of the following ways:

  • If the keystore has become out of date (because a label has been deleted, for example) restore the label from a backed-up version of the keystore.
  • If the keystore is not synchronized on two host machines involved in an operation (such as an HADR primary-standby pair, or when a backup image taken on one host machine is restored to a different host machine) synchronize the two keystores and then reissue the command.

SQL1731C An encryption operation failed. Database name: database-name. Log file name: log-file-name. Database partition number: db-partition-number. Log stream ID: log-stream-ID.

Explanation

You can encrypt data in databases using the IBM DB2 Encryption Offering.

This message is returned when an encryption-related operation fails because of a critical, internal error.

User response

Collect diagnostic information, including the log file given in the runtime token log-file-name and db2diag diagnostic log files, and then contact IBM Software Support for assistance.

SQL1732N The command failed because the specified encryption options are not supported together or not supported in this environment.

Explanation

To use DB2 native encryption, encryption options must be specified in the ENCROPTS database configuration parameter or with the ENCROPTS command parameter.

The value of the ENCROPTS database configuration parameter and the ENCROPTS command parameter must be a string, in a specific format, indicating a combination of encryption-related configuration details.

This message is returned when an incompatible or unsupported combination of configuration details is specified.

User response

Correct the configuration details specified in the ENCROPTS configuration parameter or the ENCROPTS command parameter and then reissue the command.

SQL1733N The command was not executed because the specified label is too long.

Explanation

DB2 native encryption stores encryption keys in a keystore. Keys are accessed by a master key label, which is also stored in the keystore. The label is created in one of two ways:

  • You create the label when you create a key manually.
  • The database manager generates a label when creating a key.

This message is returned when a manually created label is specified with a command, and the label is longer than the supported label size.

User response

Reissue the command, specifying a label that is a supported length.

SQL1734N The command or operation failed because the master key does not match a supported key length.

Explanation

DB2 native encryption uses a master key to manage encryption for data in databases. The master key for a given database can be created in two ways:

  • You can create a master key manually, and specify the label for that key (with the CREATE DATABASE statement, for example.)
  • You can allow the database manager to generate a master key for a database.

This message is returned when the label of a manually created master key is specified with a command or statement, but the length of the manually created key is not supported with DB2 native encryption.

User response

Reissue the command, specifying the label of a master key that is a supported length.

SQL1735N The RESTORE command failed because the encryption key label specified in the command does not match the label used to encrypt the backup image.

Explanation

DB2 native encryption stores encryption keys in a keystore. Keys are accessed by a master key label, which is also stored in the keystore. When you issue DB2 commands against databases that are configured to use this functionality, the database manager must look up the appropriate key using a label:

  • You can specify the label as a parameter to the command.
  • If you do not specify a label, the database manager will use the label that is configured for the database.

When you create an encrypted backup image, you can specify multiple master key labels. When you restore an encrypted backup image, you must specify one of the master key labels that were used when the backup image was created.

This message is returned when an attempt is made to restore a backup image, specifying a master key label that was not used to create the backup image.

User response

Respond to this error in one of the following ways:

  • Allow the restore utility to look up the correct master key label by issuing the RESTORE command without specifying any label.
  • Manually determine what master key labels were used to create the backup image by issuing the RESTORE command specifying "show master key details" with the ENCROPTS parameter, and then perform the restore operation specifying one of the labels that were used to create the backup image.

SQL1736N The command failed to retrieve the keystore password. Reason code reason-code.

Explanation

DB2 native encryption stores encryption keys in a keystore. When you issue DB2 commands (the START DATABASE MANAGER command, for example) in an environment configured to use this functionality, the database manager looks up keys in the keystore.

The keystore is protected with a password. In order for the database manager to look up an encryption key, the keystore password must be provided to the database manager in one of two ways:

  • The password can be stored in a stash file.
  • The password can be specified with a parameter to DB2 commands.

This message is returned when keystore password information is specified with a parameter to a DB2 command, but the database manager is unable to use the password information that was specified with the parameter.

The reason code indicates more specifically what error the database manager encountered while processing the specified password information:

1

The password information could not be processed because the format of the argument was not recognized.

2

The argument was processed by the command, but the specified password information could not be used successfully (the file name specified does not exist, for example.)

User response

Reissue the command, with a password argument corrected according to the reason code:

1

Specify the password information using a valid string format.

2

Specify the correct password, an open, readable file handle, or the name of an existing file.

SQL1737N The command or operation failed because the database is not encrypted.

Explanation

You can encrypt data in databases using DB2 native encryption. You can perform encryption operations on encrypted databases by specifying encryption-related parameters with commands or by using the ADMIN_ROTATE_MASTER_KEY built-in stored procedure.

This message is returned when an attempt is made to perform DB2 native encryption operations with a database that is not encrypted.

User response

Respond to this error in one of the following ways:

  • Reissue the command without specifying parameters that are specific to DB2 native encryption.
  • Reissue the command against a database that is encrypted.

SQL1738N The command was not executed because a label was not provided.

Explanation

DB2 native encryption stores encryption keys in a keystore. Keys are accessed by a master key label, which is also stored in the keystore. In general, the label is provided in one of two ways:

  • You can specify a label with a command parameter.
  • You can allow the database manager to generate a new label or use the existing label configured for the database.

There are some cases where a master key label must always be specified. This message is returned when a label must be specified, but no label is specified:

  • The ADMIN_ROTATE_MASTER_KEY stored procedure is issued in an HADR environment.
  • The BACKUP command is issued with the ENCRYPT clause to create an encrypted backup image of a database that is not encrypted.

User response

Reissue the command, specifying a master key label.

SQL1739N The command or operation failed because the value specified with the ENCROPTS parameter is invalid.

Explanation

To use DB2 native encryption, encryption options must be specified in the ENCROPTS database configuration parameter or with the ENCROPTS command parameter.

The value of the ENCROPTS database configuration parameter and the ENCROPTS command parameter must be a string, in a specific format, listing a combination of encryption-related configuration details.

This message is returned when the database manager is unable to parse the configuration information specified in the ENCROPTS configuration parameter or the ENCROPTS command parameter because the format of the specified string is unexpected.

User response

Correct the configuration details specified in the ENCROPTS configuration parameter or the ENCROPTS command parameter and then reissue the command.

SQL1740N The key rotation operation failed. Reason code: reason-code.

Explanation

DB2 native encryption uses a master key to manage encryption for data in databases. You can rotate the master key for a database by using the ADMIN_ROTATE_MASTER_KEY built-in stored procedure.

This message is returned when rotating the master key fails because of an internal error. The reason code, which is useful for IBM support personnel only, indicates more specifically the nature of the underlying problem:

1

Memory management errors, other than out-of-memory conditions, were encountered.

2

Internal latch errors were encountered.

3

Key rotation was attempted on a partitioned system where not all database partitions are active.

User response

For reason codes 1 and 2, perform the operation again.

For reason code 3, wait until all database partitions are active and then reissue the command.

If this error continues, collect diagnostic information, including the db2diag diagnostic log files, and then contact IBM Software Support for further assistance.

SQL1741N The command or operation failed because the master key for master key label label has changed.

Explanation

DB2 native encryption stores encryption keys in a keystore. Keys are accessed by a master key label, which is also stored in the keystore. The label is created in one of two ways:

  • You create the label when you create a key manually.
  • The database manager generates a label when creating a key.

Once a key is created with a given label, the key for that label cannot change. This message is returned when the key has changed for a given master key label.

The key for a master key label can appear to have changed for different reasons, including the following examples:

  • The same label is used for different keys in different keystores.
  • The key was accidentally changed manually.

User response

Perform the following troubleshooting steps:

  • Verify that the keystore contains the correct master key and master key label.
  • If required, restore the label from the most recent backup image of the keystore and retry the command or operation.

SQL1742N Creating the primary key failed because the columns of the primary key definition do not correspond to the columns of a unique constraint or primary key constraint on the base table.

Explanation

You can create a primary key on a shadow table. However there are some requirements and restrictions related to creating a primary key on shadow tables. This message is returned when an attempt is made to create a primary key on a shadow table, but there is no corresponding primary key or unique constraint for the base table of the shadow table.

User response

To create a primary key on a shadow table, include a set of columns in the definition of the new primary key that corresponds to the set of columns from a primary key or a unique constraint of the base table.

sqlcode: -1742

sqlstate: 428I7

SQL1743N The RESTORE command failed because the backup image is of an encrypted database but the target database is not encrypted.

Explanation

You can encrypt data in databases by using DB2 native encryption. For example, you can create an encrypted database by specifying encryption parameters with the CREATE DATABASE command.

When an encrypted database is backed up, that backup image cannot be restored into an existing, target database that is not encrypted, unless the NO ENCRYPT parameter is specified with the RESTORE command.

This message is returned when an attempt is made to restore the image of an encrypted database to a target database that is not encrypted and the NO ENCRYPT parameter is not specified with the RESTORE command.

User response

To restore the backup image into a non-encrypted target database, issue the RESTORE command with the NO ENCRYPT parameter.

SQL1744N The RESTORE command failed because the target database already exists and encryption options were specified.

Explanation

You can encrypt data in databases by using DB2 native encryption. For example, you can create an encrypted database in two ways:

  • Specifying encryption-related parameters with the CREATE DATABASE command
  • Restoring from a backup image into a new, encrypted database by specifying encryption-related parameters with the RESTORE command

What is not supported, however, is specifying encryption-related parameters with the RESTORE command when restoring into an existing database that is not encrypted.

User response

To restore into an existing database that is not encrypted, perform one of the following actions:

  • To restore a backup image of an encrypted database into an existing database that is not encrypted, issue the RESTORE command without specifying any encryption-related parameters other than the NO ENCRYPT parameter.
  • To restore a backup image of a non-encrypted database into an existing database that is not encrypted, issue the RESTORE command without specifying any encryption-related parameters.

SQL1745N The API_name API failed because the API attempted to read encrypted logs.

Explanation

You can encrypt data in databases by using DB2 native encryption. With databases that are configured to use this functionality, database log files are also encrypted. You can work with encrypted log files by using the db2ReadLogNoConn API.

This message is returned when an attempt is made to work with encrypted database log files using a utility that is not supported with encrypted log files.

User response

To work with log files that have been encrypted by DB2 native encryption functionality, use only utilities that are supported with encrypted log files.

SQL1746W The database, database-name, was successfully created. However, database configuration was not automatically tuned for your system resources.

Explanation

When the sqlecrea API is invoked or the CREATE DATABASE command is issued, by default the Configuration Advisor tunes the database configuration according to your system resources. (You can disable the Configuration Advisor from running at database creation by using the DB2_ENABLE_AUTOCONFIG_DEFAULT registry variable.)

This message is returned when the Configuration Advisor is enabled to run at database creation time, but the Configuration Advisor encounters an error and is unable to optimize the database configuration for your system resources.

User response

To tune the database configuration, manually run the AUTOCONFIGURE command.

sqlcode: +1746

sqlstate: 5U061

SQL1747N The statement was not processed because of an error specifying the ENVIRONMENT clause. Reason code: reason-code. Substring: substring.

Explanation

You can specify multiple named routine environment variables with associated values in the ENVIRONMENT clause of the CREATE FUNCTION statement. The ENVIRONMENT clause is specified as a comma-separated list of name-value pairs.

This message is returned when there is a problem with one or more of the names or values specified with the ENVIRONMENT clause.

The reason code identifies the problem more specifically:

1

More routine environment variables were specified than the maximum supported number of routine environment variables.

2

A value string that is longer than the maximum supported length was specified with a routine environment variable.

3

A routine environment variable name was specified that is longer than the maximum supported length for a name.

4

A routine environment variable name was specified more than once.

Depending on the nature of the problem, the token substring might be empty, or might contain a substring showing where the problem occurs in the ENVIRONMENT clause.

User response

Reissue the SQL statement, specifying a valid ENVIRONMENT clause.

sqlcode: -1747

sqlstate: 428I8

SQL1748N A user-defined function has encountered a deadlock with a CPad. Function name: function-name. Specific name: specific-name.

Explanation

A deadlock is created when two applications both lock data that is needed by the other, such that neither application can continue executing.

You can use a CPad to allocate a named, unique area of memory as a temporary storage area and work pad for user-defined functions.

This message is returned when two user-defined functions encounter a deadlock scenario accessing the same CPad.

User response

Rewrite the user-defined function to avoid deadlock scenarios.

sqlcode: -1748

sqlstate: 57068

SQL1749N The statement failed because it references a type type-name which was generated for an array or row column definition.

Explanation

The use of a ROW type or ARRAY type as the data type for columns in a CREATE HADOOP TABLE statement generates a user-defined data type using a system-generated name.

The data types that are generated for this purpose cannot be referenced in other statements or expressions, with the exception of the COMMENT statement.

User response

Replace or remove the reference to the generated data type and resubmit the statement.

sqlcode: -1749

sqlstate: 429CC