ADM8000-9999

ADM Message ID Message Explanation User Response

ADM8000C

 Backup has been terminated. The SQLCODE returned is SQLCODE.

ADM8001W

 Incremental backup was not enabled for this database because the TRACKMOD DB configuration parameter was not enabled.

ADM8002W

 This backup image cannot be used for ROLLFORWARD because the logs associated with this backup has been overwritten on the raw device. Use a more recent backup image.

ADM8003C

 Restore has been terminated. The SQLCODE returned is SQLCODE.

ADM8004W

 Incremental backup was not enabled for table space tablespaceName (ID tablespaceID) because the TRACKMOD configuration parameter was not enabled.

ADM8005W

 Incremental backup was not enabled for table space tablespaceName (ID tablespaceID). A non-incremental backup of this table space is required.

ADM8006W

 The database manager cannot use the specified restore buffer size of restoreBufferSize 4K pages. A restore buffer size must be multiple of backup buffer size of backupBufferSize 4K pages. The restore operation will continue with the default buffer size.

ADM8007W

 The database manager cannot perform multiple concurrent incremental restores.

ADM8008W

 The database manager could not find and/or delete the online reorganization state files for all table spaces during restore. Manual intervention may be needed to remove the file(s).

ADM8009W

 Could not find and/or delete the online reorganization state files for table space tablespaceName (ID tablespaceID ) during restore. Manual intervention may be needed to remove the file(s).

ADM8010E

 Backup was unable to copy requested log file logfileName for inclusion in the backup image. The backup has been aborted.

ADM8011W

 The database backup succeeded. However, the database server was unable to create part of the incremental chain of images during the backup, and will be unable to use the affected images during restore. Specifically, you will not be able to use the backup image with timestamp timestamp for incremental restores involving table space table-space-name.

ADM8012W

 The database backup succeeded. However, the entry in the recovery history file corresponding to the backup image with timestamp timestamp will not be well-formed, because a write error occurred while updating the recovery history file itself. See the db2diag log file for more information.

ADM8013E

 The command or operation failed due to an error in the encryption or compression library.

Initialization of the encryption or compression library failed causing the command or operation to fail.

Check the admin log and check the associated SQLCA structure. The SQLCA structure contains an associated SQLCODE which provides further explanation on the error and applicable user responses.

ADM8014W

 The keystore file has changed.

DB2 native encryption uses a master key to manage encryption for data in databases. The database manager creates new master keys in two scenarios:

  • A new, encrypted database is created without a manually created master key being specified, so the database manager creates a master key for the new database.
  • The ADMIN_ROTATE_MASTER_KEY built-in stored procedure is invoked to rotate the master key for a database without a manually created master key being specified, so the database manager creates a new master key for the database.

The master keys and corresponding labels are stored in a keystore file. This message is printed to inform you that the database manager has inserted a new master key and master key label into the keystore file.

To maintain data integrity, back up the keystore file.

ADM8500W

 The database manager has failed to read from the history file because of a possible data corruption. Ensure that the file exists and is intact.

ADM8501W

 The database manager has failed to write to the history file because the disk is full.

ADM8502W

 The history file is corrupt. An unrecoverable error has been detected with the file. The existing file has been deleted and a backup has been made. If you would like to determine the root cause of the problem, contact IBM Support. Otherwise, no further action is needed.

ADM8503W

 The database manager was unable to record a history entry for operation operation.

ADM8504I

 Successfully deleted the backup image with timestamp timestamp.

ADM8505I

 Successfully deleted the load copy image with timestamp timestamp.

ADM8506I

 Successfully deleted the following database logs log-list in log chain log-chain.

ADM8507N

 Unable to delete the backup image with timestamp timestamp.

The database manager attempted to delete the given backup image, but was unsuccessful.

Verify that the database manager has access to the storage manager or directory where the backup images are stored. See the db2diag log file for more information.

ADM8508N

 Unable to delete the load copy image with timestamp timestamp.

The database manager attempted to delete the given load copy image, but was unsuccessful.

Verify that the database manager has access to the storage manager or directory where the load copy images are stored. See the db2diag log file for more information.

ADM8509N

 Unable to delete the database logs log-list in log chain log-chain.

The database manager attempted to delete the given database logs, but was unsuccessful.

Verify that the database manager has access to the storage manager or directory where the log files are stored. See the db2diag log file for more information.

ADM9000W

 Prefetching was disabled during sort merge; performance may be suboptimal. If this message persists, consider increasing the buffer pool size for temporary table space tablespaceName (ID tablespaceID) or increase the value of the SORTHEAP DB configuration parameter to reduce the extent of sort spilling.

ADM9500W

 Too many concurrent updates had occurred on table tableName (ID tableID) and table space tablespaceName (ID tablespaceID) during online index create/reorganization. Thus, it will take a longer time to finish online index create/reorganization. You may want to increase your UTIL_HEAP_SZ DB configuration parameter.

ADM9501W

 Index reorganization has started for table tableName (ID tableID) and table space tablespaceName (ID tablespaceID).

The data server is reorganizing the indexes for the specified table. The re-organization is either for nonpartitioned indexes on a partitioned table or for indexes on a nonpartitioned table.

No response is required.

ADM9502W

 Index reorganization is complete for table tableName (ID tableID) and table space tablespaceName (ID tablespaceID).

The data server reorganized the indexes for the specified table. The index reorganization was either for nonpartitioned indexes on a partitioned table or for indexes on a nonpartitioned table.

No response is required.

ADM9503W

 Reorganizing index IID indexIID (OBJECTID indexObjectID) in table space indexTablespaceName (ID indexTablespaceID) for table tableName (ID tableID) in table space tablespaceName (ID tablespaceID).

The data server is reorganizing the specified index. The reorganization is either for nonpartitioned indexes on a partitioned table or for indexes on a nonpartitioned table.

No response is required.

ADM9504W

 Index reorganization on table tableName (ID tableID) and table space tablespaceName (ID tablespaceID) failed on this database partition with SQLCODE SQLCODE reason code reasonCode.

Index reorganization failed on this database partition for the reason described by the SQLCODE. The indexes referred to in this context are either nonpartitioned indexes on a partitioned table or indexes on a nonpartitioned table

Correct the problem that is described by the SQLCODE, and then retry the REORG INDEXES command on the database partition.

ADM9505W

 Online index reorganization on table tableName (ID tableID) and table space tablespaceName (ID tablespaceID) has been switched to offline mode because the indexes are marked for rebuild. These indexes may have been marked for rebuild during a roll forward through an index creation and/or recreation. If this is the case, consider setting the INDEXREC database manager configuration parameter to RESTART. This will cause indexes that are marked for rebuild during roll forward to be rebuilt during RESTART DATABASE processing.

ADM9506W

 HADR is enabled, but full logging is disabled for any index creation, recreation, or reorganization on table table-name (table object id: object-id) in tablespace tablespace-name (tablespace id: tablespace-id), since you have explicitly requested to disable it. As a result, any index build operations on this table will not be recovered immediately on the secondary database server using HADR. Indexes on the secondary database server will be recreated implicitly at the end of the HADR takeover process or after the HADR takeover process when the underlying tables are to be accessed. If this is not the desired behavior, enable the full logging on the table before any create, recreate, or reorg index is performed.

ADM9507W

 When HADR is enabled, it is recommended that the database configuration parameter LOGINDEXBUILD is set to ON, on both the HADR primary database server and the HADR secondary database server. Otherwise, you may not log your index creation, recreation, or reorganization on current or future HADR primary database server. Any non-fully logged index creation, recreation, or reorganization on the primary database server will not be recovered on the secondary database server using HADR. Those indexes which cannot be recovered will be marked as invalid, and will be rebuilt implicitly at the end of the HADR takeover process or after the HADR takeover process when the underlying tables are accessed. If this is not the desired behavior, enable the full logging or use the default setting for this configuration parameter before any index build operations take place.

ADM9508W

 When HADR is enabled, it is recommended that the database or database manager configuration parameter INDEXREC is set to either RESTART or ACCESS in order to enable redo of any index creation, recreation or reorganization. Otherwise, any fully logged index creation, recreation, or reorganization on the primary database server will not be recovered on the secondary database server using HADR. Those indexes which cannot be recovered will be marked as invalid and will be rebuilt implicitly at the end of the HADR takeover process or after the HADR takeover process when the underlying tables are accessed. If this is not the desired behavior, update INDEXREC or use the default setting for this configuration parameter before any index build operations take place.

ADM9509W

 It is recommended that the database configuration parameter LOGINDEXBUILD is set to ON before HADR is started. Otherwise, any index creation, recreate, or reorganization on the current or future primary database server may not be recovered on the current or future secondary database server using HADR. Those indexes which cannot be recovered will be marked as invalid and will be rebuilt implicitly either at the end of the HADR takeover process or after the HADR takeover process when the underlying tables are to be accessed. If this is not the desired behavior, update the database configuration parameter LOGINDEXBUILD to ON.

ADM9510W

 An error (sqlcode sqlcode) occurred which prevented the completion of the index rebuild process. Any invalid indexes that have not been rebuilt when the process terminated will be recreated on the first table access. The index rebuild process was invoked either during an explicit or implicit restarting of the database, or at the end of the HADR takeover.

ADM9511W

 Index reorganization proceeds on index indexname (IID indexIID, OBJECTID indexObjectID) in table space indexTablespaceName (ID indexTablespaceID) for table tableName (ID tableID) in table space ID tablespaceID.

ADM9512W

 Index reorganization for index indexname (IID indexIID, OBJECTID indexObjectID) in table space indexTablespaceName (ID indexTablespaceID) for table tableName (ID tableID) in table space ID tablespaceID failed on this node with SQLCODE SQLCODE reason code reasonCode. To resolve this problem, re-submit the REORG INDEX command on the failing node(s).

ADM9513W

 Online index reorganization on table tableName (ID tableID) in table space tablespaceName (ID tablespaceID) found one or more indexes that are marked invalid and cannot proceed until they are rebuilt.

The data server will automatically rebuild the indexes on this table. If any nonpartitioned indexes are being rebuilt, the data server will obtain a super exclusive Z table lock for the duration of the rebuild. If only partitioned indexes are being rebuilt, the data server will obtain a super exclusive Z partition lock on each data partition that has invalid indexes for the duration of the rebuild. After the rebuild is complete, the online index reorganization will proceed (using the original lock modes) for any indexes that were specified for reorganization by the current command and have not yet been rebuilt.

No response is required.

ADM9514I

 BEGIN async index cleanup on table tableName (ID tableID) and table space tablespaceName (ID tablespaceID).

ADM9515I

 END async index cleanup on table tableName (ID tableID) and table space tablespaceName (ID tablespaceID).

ADM9516W

 Indexes on the table table_identifier were marked to be rebuilt while upgrading the database.

The table_identifier is shown in one of the following forms:

  • TBSPACEID=table_space_id.TABLEID=table_id
  • schema_name.table_name

The indexes on the identified table must be rebuilt because one of the following situations was encountered during a database upgrade:

  • A root page has insufficient space
  • A type-1 index was detected
  • One or more non-severe errors occurred converting the index page.

Indexes will be rebuilt automatically after upgrading the database in one of the following ways:

  • If the indexrec database configuration parameter is set to RESTART or RESTART_NO_REDO, then issuing the RESTART DATABASE command will trigger the rebuild of the indexes.
  • If the indexrec database configuration parameter is set to ACCESS or ACCESS_NO_REDO, then the indexes will be rebuilt on first access to the table on which the indexes are defined. The ADMIN_GET_TAB_INFO function can be used to identify which tables have indexes that require rebuilding.

There will be a one-time performance impact while the indexes are rebuilt.

ADM9517W

 The index object with ID object-ID in table space table-space-ID for table table-name has been marked invalid during log replay on an HADR standby database. The index will be rebuilt automatically upon subsequent query to this table, if there is a fail over to make this database the HADR primary.

The index object can no longer be maintained due to the invalid state. Subsequent log records on this index objects are ignored by database recovery. If no action is taken, in the event of HADR fail over that makes this database the HADR primary, the index will be rebuilt automatically upon subsequent query to this table.

Reinitialize the HADR standby via a new backup of the primary database, to avoid the need of index rebuild in the event of HADR fail over.

ADM9518I

 Index reorganization has started for the partitioned indexes on data partition dataPartitionID of table tableName (ID tableID) and table space tablespace-Name (ID tablespaceID).

The data server is reorganizing the partitioned indexes for the specified data partition.

No response is required.

ADM9519I

 Index reorganization is complete for partitioned indexes on data partition dataPartitionID of table tableName (ID tableID) and table space tablespaceName (ID tablespaceID).

The data server has reorganized the partitioned indexes for the specified data partition.

No response is required.

ADM9520I

 Reorganizing partitioned index IID indexIID (OBJECTID indexObjectID) in table space indexTablespaceName (ID indexTablespaceID) for data partition dataPartitionID of table tableName (ID tableID) in table space tablespaceName (ID tablespaceID).

The data server is reorganizing the index partition on the specified data partition for the specified partitioned index.

No response is required.

ADM9521W

 Index reorganization for partitioned indexes on data partition dataPartitionID of table tableName (ID tableID) and table space tablespaceName (ID tablespaceID) failed on this database partition with SQLCODE SQLCODE reason code reasonCode.

Index reorganization of the partitioned indexes failed on this database partition for the reason described by the SQLCODE.

Correct the problem that is described by the SQLCODE, and then retry the REORG INDEXES command on the database partition.

ADM9522I

 Index reorganization is complete for partitioned indexes on data partition datapartitionID of table tableName (ID tableID) and table space tablespaceName (ID tablespaceID).

The data server has reorganized the partitioned indexes for the specified data partition. Some partitioned indexes on the data partition might still need to be reorganized. This index reorganization will occur later during the reorganization.

No response is required.

ADM9523W

 An error was encountered on index object with ID object-ID in table space table-space-ID for table table-name during log replay on an HADR standby database. The index object has been marked invalid. The index will be rebuilt automatically upon subsequent query to this table, if there is a fail over to make this database the HADR primary.

The index object can no longer be maintained due to the unexpected error. Subsequent log records on this index objects are ignored by database recovery. If no action is taken, in the event of HADR fail over that makes this database the HADR primary, the index will be rebuilt automatically upon subsequent query to this table.

Contact IBM Support to investigate the root cause of the index error. Reinitialize the HADR standby via a new backup of the primary database, to avoid the need of index rebuild in the event of HADR fail over.

ADM9524W

 An error was encountered on index object with ID object-ID in table space table-space-ID for table table-name during database recovery. The index object has been marked invalid. The index will be rebuilt automatically after the completion of database recovery.

The index object can no longer be maintained due to the unexpected error. Subsequent log records on this index objects are ignored by database recovery. The index will be rebuilt automatically, either immediately upon completion of database recovery, or upon subsequent query to this table, depending on the value of indexrec database configuration parameter.

Contact IBM Support to investigate the root cause of the index error.

ADM9525W

 The index object with ID object-ID in table space table-space-ID for table table-name has been marked invalid. The index will be rebuilt automatically after the completion of database recovery.

The index object can no longer be maintained due to the invalid state. Subsequent log records on this index objects are ignored by database recovery. The index will be rebuilt automatically, either immediately upon completion of database recovery, or upon subsequent query to this table, depending on the value of indexrec database configuration parameter.

No response is required.