ADM5000-5999

ADM Message ID	Message	Explanation	User Response
ADM5000I	`sevice` interaction was successfully started.	Db2 has successfully begun interaction with the identified service.
ADM5001I	`sevice` processing is now running in diagnostic mode.	Db2 has successfully initiated processing for the identified service in diagnostic mode and will not attempt to send any messages to the identified service.	Modify the appropriate configuration setting to exit diagnostic mode when it is no longer needed.
ADM5002W	Non-fatal error encountered during `phase` processing for `sevice`. Reason code = `reason_code`. Additional details: `token1`, `token2`, `token3`, `token4`, `token5`	A non-fatal error was encountered in Db2 within the `phase` processing for the identified service. The error will be ignored and subsequent Db2 processing for this service will continue. The reason code indicates the specific error encountered. Additional details are provided where appropriate for the error scenario. Possible reason code values are: 1 The directory path, `token4`, provided for the `token3` parameter was not found or is invalid. `token1` indicates which configuration file was being referenced. `token2` indicates the line on which the error was found. If the directory path is too long `token5` indicates the maximum length of the path including file name. 2 A duplicate parameter with the name shown in `token3` was encountered. `token1` indicates which configuration file was being referenced. `token2` indicates the line on which the error was found. 3 A duplicate value, shown in `token4`, was encountered for the parameter name shown in `token3`. `token1` indicates which configuration file was being referenced. `token2` indicates the line on which the error was found. 4 An unrecognized value, shown in `token4`, was encountered for the parameter name shown in `token3`. `token1` indicates which configuration file was being referenced. `token2` indicates the line on which the error was found. 5 The output file to be used for the payload option of the debug parameter is a link. `token1` contains the file name. 6 The Db2 infrastructure needed for processing in the indicated phase encountered a problem. `token1` indicates which part of the infrastructure is affected.	Take the appropriate action indicated for the reason code value given: 1 Create or correct the directory path specified. Possible causes of this are: The directory path is not an absolute path. For Windows an absolute path starts with 'x:\', where 'x' is a non-blank character; for all other platforms, an absolute path starts with '/'. The directory path is too long. Reduce its length to the maximum indicated in `token5` 2 Remove the duplicate parameter. 3 Remove the duplicate value. 4 Remove or correct the unrecognized value. 5 Remove the output file or unlink it. 6 If the affected infrastructure is: "debugpath" - Ensure that the debugpath is properly configured. "payloadfile" - Ensure that Db2 has write permission in the debugpath and the payload file. Also ensure that the drive has sufficient space.
ADM5003N	Fatal error encountered during `phase` processing for `sevice`. Reason code = `reason_code`. Additional details: `token1`, `token2`, `token3`, `token4`	A fatal error was encountered in Db2 within the `phase` processing for the identified service. Interactions with this service will be discontinued. The reason code indicates the specific error encountered. Additional details are provided where appropriate for the error scenario. Possible reason code values are: 1 The Db2 infrastructure needed for processing in the indicated phase encountered a problem. `token1` indicates which part of the infrastructure is affected. 2 An invalid parameter specification was found in the service configuration. `token1` indicates which configuration file was being referenced. `token2` indicates the line on which the error was found. 3 An unknown parameter, shown in `token3`, was specified in the service configuration. `token1` indicates which configuration file was being referenced. `token2` indicates the line on which the error was found. 4 Multiple values were found for a parameter in the service configuration. `token1` indicates which configuration file was being referenced. `token2` indicates the line on which the error was found. `token3` provides the parameter name for which multiple values were provided. `token4` indicates the first extra value encountered. 5 A mandatory parameter was not provided in the service configuration. `token1` indicates which configuration file was being referenced. `token2` indicates the mandatory parameter name that was not found. 6 The value provided for a URL parameter in the service configuration did not start with an expected prefix ("http:" or "https:"). `token1` indicates which configuration file was being referenced. `token2` indicates the name of the URL parameter	Take the appropriate action indicated for the reason code value given: 1 If the affected infrastructure is: "db2acd" - Ensure that the DB2_FMP_COMM_HEAPSZ registry variable is not set to 0. "db2c2c" - Increase the MAXAPPLS database configuration parameter. "memory" - Increase the dbheap database configuration parameter to allow a larger database heap. "cfgfile" - Ensure that Db2 has read permission on the config file. Reduce the length of each line of the config file to the maximum indicated in `token2` "cpi" - Ensure that the provided apikey and apihost values are correct. Additional information about the error can be found in the Db2 diagnostic log. 2 Correct the parameter specification. Possible causes of this error are: The colon separator (":") is missing between the parameter name and the value specified. 3 Remove or correct the unrecognized parameter name. 4 Correct the value specified for the parameter. 5 Provide the mandatory parameter. 6 Correct the value specified for the parameter.
ADM5500W	The database manager is performing lock escalation. The affected application is named `appl_name`, and is associated with the workload name `workload_name` and application ID `appl_id` at member `member_num`. The total number of locks currently held is `locksHeld`, and the target number of locks to hold is `targetNumber`. Reason code: `reason_code`	The reason code indicates why lock escalation is happening: 1 The portion of the lock list that is being held by an application has exceeded the value specified for the maxlocks database configuration parameter. 2 The lock list is full. 3 The global lock list is full.	To reduce the likelihood of lock escalation, take one or more of the following actions: Perform commit operations more frequently. Configure the lock list size to automatically adjust by setting the locklist configuration parameter to AUTOMATIC. Configure the global lock list size to automatically adjust by setting the cf_lock_size configuration parameter to AUTOMATIC. If you are making several updates, consider locking the entire table using the LOCK TABLE statement. Locking the table uses only one lock, as opposed to the several locks that might be required when updating multiple rows. You can also specify that only table locks be used for a table using the LOCKSIZE option of the ALTER TABLE statement. If you use the repeatable read isolation level, the optimizer might elect to acquire a single table-level lock, if it appears that lock escalation is likely. Use the cursor stability isolation level whenever possible to decrease the number of shared locks held. If application integrity requirements are not compromised, use the uncommitted read isolation level instead of cursor stability to further decrease the amount of locking.
ADM5501I	The database manager is performing lock escalation. The affected application is named `appl_name`, and is associated with the workload name `workload_name` and application ID `appl_id` at member `member_num`. The total number of locks currently held is `locksHeld`, and the target number of locks to hold is `targetNumber`. The current statement being executed is `currentStatement`. Reason code: `reason_code`	The possible reason codes that explain why lock escalation is happening are as follows: 1 The portion of lock list held by an application has exceeded the value specified for the maxlocks database configuration parameter. 2 The lock list is full. 3 The global lock list is full.	To reduce the likelihood of lock escalation, you can take one or more of the following actions: Perform commit operations more frequently. Set the locklist configuration parameter to AUTOMATIC to have the lock list size adjusted automatically. Set the cf_lock_sz configuration parameter to AUTOMATIC to have the global lock list size adjusted automatically. If you are making several updates, consider locking the entire table using the LOCK TABLE statement. Locking the table uses only one lock, as opposed to the several locks that might be required when updating multiple rows. You can also specify that only table locks be used for a table using the LOCKSIZE option of the ALTER TABLE statement. If you use the Repeatable Read (RR) isolation level, the optimizer might elect to acquire a single table-level lock, if it appears that lock escalation is likely. Use the Cursor Stability isolation level whenever possible to decrease the number of share locks held. If application integrity requirements are not compromised, use the Uncommitted Read isolation level instead of Cursor Stability to further decrease the amount of locking.
ADM5502W	The escalation of `numLocks` locks on table `tableName` to lock intent `lockIntent` was successful.	The token `numLocks` lists the total number of locks currently held by all applications that are accessing the table.	No user response is required.
ADM5503E	The escalation of `numLocks` locks on table `tableName` to lock intent `lockIntent` has failed. The SQLCODE is `SQLCODE`.
ADM5504W	The escalation of `numLocks` locks on DATAPARTITIONID `datapartitionid` of table `tableName` to lock intent `lockIntent` was successful.
ADM5505E	The escalation of `numLocks` locks on DATAPARTITIONID `datapartitionid` of table `tableName` to lock intent `lockIntent` has failed. The SQLCODE is `SQLCODE`.
ADM5506W	The current unit of work was involved in an unresolved contention for use of an object. The type of the event is: `event-type`. The identifier of the lock on which this event happened is: `lock-ID`. The timestamp of the event is: `timestamp`. The identifier of the member at which the event happened, and the identifier of the event is: `member-ID-event-ID`. The affected application is named `application-name` The application is associated with the workload named `workload-name`. The application identifier is: `application-ID`. The identifier of the member on which the application is running is: `app-member-id`. The role that this application plays with respect to this lock is: `role`.	The current unit of work was involved in an unresolved contention for use of an object. Lock escalation is the process of replacing row locks with table locks, reducing the number of locks in the list.	To investigate this event further, create an event monitor using the CREATE EVENT MONITOR FOR LOCKING statement which should help to narrow down the source of the problem. To help avoid a deadlock or lock timeout, issue frequent COMMIT operations, if possible, for a long-running application, or for an application likely to encounter a deadlock. Deadlocks are often normal or expected while processing certain combinations of SQL statements. It is recommended that you design applications to avoid deadlocks to the extent possible. If a deadlock state was reached because of a queuing threshold such as the CONCURRENTDBCOORDACTIVITIES threshold, increase the value of the queuing threshold. To prevent lock escalations, adjust the locklist and maxlocks configuration parameters.
ADM5507W	The current unit of work was involved in an unresolved contention for use of an object. The type of the event is: `event-type`. The identifier of the lock on which this event happened is: `lock-ID`. The timestamp of the event is: `event-timestamp`. The identifier of the member at which the event happened is: `event-source-member-id`. The identifier of the event is: `event-ID`. The identifier of the member at which the application is holding the lock is: `app-member-id`.	The current unit of work was involved in an unresolved contention for use of an object. Lock escalation is the process of replacing row locks with table locks, reducing the number of locks in the list.	To investigate this event further, create an event monitor using the CREATE EVENT MONITOR FOR LOCKING statement which should help to narrow down the source of the problem. To help avoid a deadlock or lock timeout, issue frequent COMMIT operations, if possible, for a long-running application, or for an application likely to encounter a deadlock. Deadlocks are often normal or expected while processing certain combinations of SQL statements. It is recommended that you design applications to avoid deadlocks to the extent possible. If a deadlock state was reached because of a queuing threshold such as the CONCURRENTDBCOORDACTIVITIES threshold, increase the value of the queuing threshold. To prevent lock escalations, adjust the locklist and maxlocks configuration parameters.
ADM5508I	One or more partitioned indexes on data partition `DATAPARTITIONID` of the table named `tableName` are marked invalid and require rebuilding.	The DB2 data server will automatically rebuild the invalid index partitions on this data partition. A super exclusive Z lock will be held on the data partition from the time that the index rebuild begins until the end of unit of work in which the rebuild occurs.	No response is required.
ADM5509I	Rebuilding `count` index partitions on data partition `DATAPARTITIONID` of the table `tableName`.	The data server is rebuilding index partitions for the table on the specified data partition.	No response is required.
ADM5510E	The table space `tableSpace` (ID `tableSpace`) is full. There is no more room in the internal object table of this table space.
ADM5511E	The object `object` with id `object-id` in tablespace `tbspace-id` for table `tableName` has reached the maximum possible size.
ADM5512N	Rebuild of index partitions on partition `DATAPARTITIONID` of table `tableName` failed with SQLCODE of `SQLCODE`.	The rebuild of the index partitions failed for the specified data partition.	Refer to details of the given SQLCODE.
ADM5513I	Index rebuild on the data partition `DATAPARTITIONID` of table `tableName` completed successfully.	Although the data server successfully rebuilt the index for the data partition, other partitioned indexes on the data partition might still require rebuilding. This index rebuild will occur during the current unit of work.	No response is required.
ADM5514I	Rebuilding index partition with IID `indexIID` in object `indexObjectID` and table space `indexTablespaceID` on data partition `DATAPARTITIONID` of table `tableName`.	The data server is rebuilding the specified index partition.	No response is required.
ADM5515I	Index partitions on data partition `DATAPARTITIONID` of table `tableName` are successfully rebuilt.	The data server has rebuilt the index partitions for the table on the specified data partition.	No response is required.
ADM5520E	This database version is not supported for database upgrade.	The database version that you are trying to upgrade is unsupported in the DB2 copy from which you try to upgrade the database.	Determine what releases are supported for database upgrade in the DB2 copy from which you want to upgrade the database. Upgrade the database to one of those releases. Then re-try upgrading the database to the DB2 copy.
ADM5521C	The table `tableName` is missing or it was truncated and was not migrated. Database migration will continue, but this table will be inaccessible.
ADM5530W	The COMMIT processing of table `tableName` that used NOT LOGGED INITIALLY has been initiated. It is recommended that you take a backup of this table's table space(s).
ADM5540W	Rebuilding `count` indexes on table `tableName`.	The rebuild is either for nonpartitioned indexes on a partitioned table, or for indexes on a nonpartitioned table.	No response is required.
ADM5541W	Rebuilding index with IID `indexIID` in object with ID `indexObjectID` and table space ID `indexTablespaceID` on table `tablename`.	The rebuild is either for nonpartitioned indexes on a partitioned table, or for indexes on a nonpartitioned table.	No response is required.
ADM5542W	Indexes on table `tableName` are successfully rebuilt.	The rebuild was either for nonpartitioned indexes on a partitioned table, or for indexes on a nonpartitioned table.	No response is required.
ADM5543E	Rebuild of indexes on table `tablename` failed with SQLCODE of `SQLCODE`.	The rebuild was either for nonpartitioned indexes on a partitioned table, or for indexes on a nonpartitioned table.	See the referenced SQLCODE for more information.
ADM5550C	The table space `tablespaceName` (ID `tablespaceID`) is being removed from the rollforward set. The SQLCODE is `SQLCODE`.
ADM5560C	The database manager is unable to redo the reorganization of a table unless both the data table space `dataTablespaceName` (ID `dataTablespaceID`) and the long table space `LongTablespaceName` (ID `dataTablespaceID`) are being rolled forward together. Ensure that both of the table spaces are being rolled forward together, or restore a backup image taken after the reorganization to eliminate the need for reorganization to be redone.
ADM5561C	The database manager is unable to redo the reorganization of a table unless both the data table space `dataTablespaceName` (ID `dataTablespaceID`) and the long table space `longTablespaceName` (ID `dataTablespaceID`) are at the same point in time. Ensure that a backup of both table spaces are either from before the table reorganization (so that it can be redone) or from after the table reorganization (so that it does not have to be redone).
ADM5562C	The database manager is unable to undo the in-place reorganization of a table unless both the data table space `dataTablespaceName` (ID `dataTablespaceID`) and the index table space `indexTablespaceName` (ID `dataTablespaceID`) are being rolled forward together. Ensure that both table spaces are being rolled forward together.
ADM5570W	Access was attempted on an unavailable object with id `object-id` in tablespace `tbspace-id` for table `tableName`. If the object is a table it will have to be dropped. If the object is a partition it will have to be detached. If the object is a non-partitioned index the index will have to be dropped.
ADM5571W	The `object` object with ID `object-id` in table space `tbspace-id` for table `tableName` is being marked as unavailable.	The object cannot be accessed.	If the object is a table or a nonpartitioned index, drop it. If the object is a data partition of a partitioned table, detach it.
ADM5572I	One or more indexes on table `tableName` are marked invalid and require rebuilding.	The DB2 data server will automatically rebuild the invalid indexes on this table. The rebuild is either for nonpartitioned indexes on a partitioned table or for indexes on a nonpartitioned table. A super exclusive Z lock will be held on the table for the duration of the index rebuild and the unit of work in which the rebuild occurs.	No response is required.
ADM5580W	The table space with ID `tablespaceID` either does not exist or is not in the set of table spaces being recovered. Recovery will continue, but filtering of this table space or tables/objects in this table space will be ignored.
ADM5581W	The database manager has successfully filtered table space with ID `tablespaceID`, object ID `object-ID`.
ADM5582C	Internal error `error` occurred while attempting to filter table space ID `tablespaceID`, object ID `objectID`.
ADM5583W	The total alloted time of 16.7 hours per Data Links Manager has been exceeded.
ADM5590E	The specified INPLACE table reorganization action on table `tableName` is not allowed on this node because of SQLCODE -2219 reason code `reasonCode`.
ADM5591W	A new compression dictionary could not be built for the object of type `object-type` and object ID `objectID` because insufficient data was found. The object is in the table named `table-name`, which is in the table space: `table-space-id`.	When Automatic Dictionary Creation (ADC) occurs, a compression dictionary is created for a table when the table is enabled for data row compression. A dictionary is created to compress data in the rows of the database table. For a tables with columns of type XML, an additional, separate dictionary is created to compress the data in the XML storage object of the table. A compression dictionary for the table `table-name` was not created. If the `object-type` is DATA, a dictionary could not be created for rows in the table `table-name`. If the `object-type` is XML, a dictionary could not be created for the XML storage object of the table. If a dictionary exists and a new compression dictionary cannot be built, the following occurs: When not using LOAD, the existing dictionary is retained and used. When using LOAD, the existing dictionary is not retained.	No user action required.
ADM5592I	A compression dictionary for the `object-type` object with ID `objectID` in tablespace `table-spaceID` for table `table-name` was built by `dictionary-creator` processing.	When Automatic Dictionary Creation (ADC) occurs, a compression dictionary is created for a table when the table is enabled for data row compression. A dictionary is created to compress data in the rows of the database table. For a tables with columns of type XML, an additional, separate dictionary is created to compress the data in the XML storage object of the table. If the `object-type` is DATA, a compression dictionary was created for the table object for the table `table-name`. If the `object-type` is XML, a compression dictionary was created for the XML storage object of the table.	No user action required.
ADM5593I	Automatic Dictionary Creation (ADC) processing for the `object-type` object with ID `objectID` in tablespace `table-spaceID` for table `table-name` has been temporarily disabled. ADC processing will be enabled again once the instance is restarted.	When Automatic Dictionary Creation (ADC) occurs, a compression dictionary is created for a table when the table is enabled for data row compression. A dictionary is created to compress data in the rows of the database table. For a tables with columns of type XML, an additional, separate dictionary is created to compress the data in the XML storage object of the table. ADC processing has been disabled for the object `objectID`. If the `object-type` is DATA, ADC processing is disabled for the table rows for the table `table-name`. If the `object-type` is XML, ADC processing is disabled for the XML storage object of the table. Even if the table contains sufficient table row data to create a dictionary, a dictionary might not be created if the data is fragmented .	To defragment table row data, use the REORG TABLE command to reorganize the table `table-name`. If `object-type` is XML use the LONGLOBDATA option to reorganize the XML storage object of the table To enable ADC processing, restart the instance.
ADM5594I	Automatic Dictionary Creation (ADC) processing for `object-type` objects has been temporarily disabled for the database.	When Automatic Dictionary Creation (ADC) occurs, a compression dictionary is created for a table when the table is enabled for data row compression. A dictionary is created to compress data in the rows of the database table. For a tables with columns of type XML, an additional, separate dictionary is created to compress the data in the XML storage object of the table. This message is returned when ADC processing is disabled for the database. If the `object-type` is DATA, ADC processing is disabled for the data in tables. If the `object-type` is XML, ADC processing is disabled for data in the XML storage objects of tables.	To enable ADC processing, restart the database.
ADM5595E	An index data inconsistency is detected on table `schema-name`. `table-name`. Please run "INSPECT CHECK TABLE NAME `table-name` SCHEMA `schema-name` INDEXDATA RESULTS KEEP `table-name`_resfile.out" on the node that failed, and then contact DB2 support team to report the problem.
ADM5600I	Scan sharing is temporarily limited due to memory constraints.		No response is required.