ADM1000-1999

ADM Message ID	Message	Explanation	User Response
ADM1010I	Reconcile started on table `tableName`.
ADM1011I	Reconcile has completed successfully on table `tableName`.
ADM1012W	Reconcile has failed on table `tableName`. The table will now be placed into DATALINK Reconcile Not Possible (DRNP) state.
ADM1013W	Reconcile for table `tableName` is successful on Data Links Managers (DLMs) that were up and is pending on DLMs that were down. The table will now be placed in DATALINK Reconcile Pending (DRP) state.
ADM1014E	Reconcile has failed on table `tableName`.
ADM1022W	The metadata information for the DATALINK column(s) is missing on DB2 Data Links Manager `serverName`.
ADM1023W	Reconcile processing is PENDING on Data Links Manager `serverName`.
ADM1024W	Reconcile processing is COMPLETE on Data Links Manager `serverName`.
ADM1500W	The database manager is unable to locate log file `filename`.
ADM1501W	Log file compression failed on log file `log-file` during archiving for `log-archive-method` for database `database` on member `member-number`.	A log file could not be compressed before it was archived. The warning message is logged in the db2diag.log file. The log file is still archived without being compressed. Should the archive of the log file fail, an ADM1848W message is also logged in the db2diag.log file.	None.
ADM1502C	A command has set BACKUP_PENDING state off. Data integrity or the referential integrity of the data is at risk.	There are multiple events that can turn on BACKUP_PENDING state for a database. In general, when a database is in BACKUP_PENDING state, you should perform a backup operation to turn the BACKUP_PENDING state off. You can manually change the BACKUP_PENDING database state to OFF by using the db2dart tool. Using the db2dart tool to change the database state should be done only in rare circumstances, because changing the database state in this way puts data integrity at risk. This message is returned when the BACKUP_PENDING state has been manually turned off and as a result data integrity or the referential integrity of the data cannot be guaranteed if a full, offline database backup is not taken.	To ensure data integrity or the referential integrity of the data, perform a full offline database backup.
ADM1503W	Application `appl-name` with application handle `appl-handle` and application id `appl-id` running under authentication ID `auth_id` has been forced off of the database because caching facility (CF) has run out of memory used for locking. The unit of work will be rolled back.	The CF memory used for locking for this particular database has been exhausted. This application has been forced off the database in order to make CF memory available for locking purposes. The unit of work will be rolled back. This condition indicates that the LOCKLIST database configuration parameter is too large relative to the CF_LOCK_SZ database configuration parameter. Reducing the LOCKLIST database configuration parameter or increasing the CF_LOCK_SZ parameter can help avoid this condition.	Take the following action: Decrease the LOCKLIST database configuration parameter Increase the CF_LOCK_SZ database configuration parameter.
ADM1504W	The caching facility (CF) memory used for locking has run out of memory. The amount of CF memory used for locking will be increased and the amount of CF memory used for group buffer pool usage will be decreased. The performance of database `db-name` may be impacted.	The caching facility (CF) has run out of memory used for locking. To make more CF memory available for locking purpose, the amount of the CF memory used for group buffer pool purpose will be reduced. This condition indicates that the LOCKLIST database configuration parameter is too large relative to the CF_LOCK_SZ database configuration parameter. If this condition persists, reduce the LOCKLIST database configuration parameter or increase the CF_LOCK_SZ parameter.	No action required.
ADM1505I	Crash recovery has completed synchronous processing.	The database has been returned to a usable state. Some incomplete transactions that were in memory when the crash occurred will be rolled back asynchronously. ew connections to the database will be allowed while the rolling back of these incomplete transactions executes in the background.	None.
ADM1524I	Member crash recovery has been initiated.	The database modified by a DB2 member is being returned to a consistent and usable state. Any incomplete transactions that were in memory when the DB2 member crashed will be rolled back, and any committed transactions that were in memory when the DB2 member crashed will be completed. The database is not available on this DB2 member until member crash recovery successfully completes; however, other DB2 members can continue to access the database while the recovery is in progress.	No user action required.
ADM1525I	Member crash recovery has completed successfully.	The database modified by this DB2 member has been returned to a consistent state. Any incomplete transactions that were in memory when the crash occurred were rolled back and any committed transactions were completed.	No user action required.
ADM1526E	Member crash recovery has failed with SQLCODE `SQLCODE`	Member crash recovery has failed. The database is not available on the failed DB2 member until member crash recovery successfully completes. Transactions on other DB2 members may be affected if there were any retained locks held on the member at the time of the DB2 member's abnormal termination,	Refer to details of the given SQLCODE.
ADM1527I	Group crash recovery has been initiated.	The database is being returned to a consistent and usable state. Any incomplete transactions that were in memory when the crash occurred will be rolled back and any committed transactions will be completed. The database is not available until group crash recovery successfully completes.	No user action required.
ADM1528I	Group crash recovery has completed successfully.	The database has been returned to a consistent and usable state. Any incomplete transactions that were in memory when the crash occurred were rolled back and any committed transactions were completed.	No user action required.
ADM1529E	Group crash recovery has failed with SQLCODE `SQLCODE`	Group crash recovery has failed. The database is not available until group crash recovery successfully completes.	Refer to details for the given SQLCODE.
ADM1530I	Crash recovery has been initiated.	The database is being returned to a consistent and usable state. Any incomplete transactions that were in memory when the crash occurred will be rolled back, and any committed transactions that were in memory when the crash occurred will be completed. The database is not available until crash recovery successfully completes.	No user action required.
ADM1531I	Crash recovery has completed successfully.	The database has been returned to a consistent and usable state. Any incomplete transactions that were in memory when the crash occurred were rolled back and any committed transactions were completed.	No user action required.
ADM1532E	Crash recovery has failed with SQLCODE `SQLCODE`.	Crash recovery has failed. The database is not available until crash recovery successfully completes.	Refer to the details of the given SQLCODE.
ADM1533W	Database has recovered. However, one or more table spaces are offline.
ADM1534W	Table space `tablespaceName` could not be reduced in size because there are used pages at the end of the table space.
ADM1540W	Application `appl_name` with application handle `appl_handle` and application id `appl_id` executing under authentication id `auth_id` has used more log space then allowed by database configuration parameter MAX_LOG (current value `MAX_LOG_value`). Terminate this application by COMMIT, ROLLBACK or FORCE APPLICATION.
ADM1541W	Application `appl_name` with application handle `appl_handle` and application id `appl_id` executing under authentication id `auth_id` has been forced off of the database for violating database configuration parameter NUM_LOG_SPAN (current value `NUM_LOG_SPAN_value`). The unit of work will be rolled back.
ADM1542W	Application `appl_name` with application handle `appl_handle` and application id `appl_id` executing under authentication id `auth_id` will be forced off of the database for violating database configuration parameter MAX_LOG (current value `MAX_LOG_value`). The unit of work will be rolled back.
ADM1550W	The active log space exceeds the LOGPRIMARY DB configuration parameter. ROLLBACK may be slow if log files have to be retrieved from archive.
ADM1551W	The database manager is retrieving the active log file `fileName` from archive. This may result in a delay.
ADM1552E	The database manager is unable to open active log file `filename`. This could be caused by problem in retrieving the log file from archive. The database manager will try again every 5 minutes.
ADM1553W	Member crash recovery is waiting for lock `lockName` held by member `holdingMemberId`.	It is uncommon to see member crash recovery (MCR) being blocked by lock held by another member. If this condition continues, it could be an indication that the holding member is not healthy.	Examine the health of the member holding lock needed by member crash recovery. Contact IBM support to determine why the lock is not being released.
ADM1560W	Unable to read from extraction log file `log-file-name`.	Not able to read transaction log data from this file, either because the file is missing, or its content is not correct. This may result in retrieving of active log file(s) from archive.	Investigate the cause of the failure by reviewing the Db2 diagnostic (db2diag) log files.
ADM1600W	There was not enough memory to enable parallel recovery; however, recovery is proceeding. Increase either the DBHEAP or UTIL_HEAP_SZ configuration parameters by `blockSize` for any future recoveries.
ADM1601E	A recovery or rollforward operation on database `database-name` cannot continue because of a missing log file `log-file-name` on database partition `dbpartitionnum` and log stream `log-stream-ID`.	The recovery or rollforward operation cannot find the specified log file in the archive, database log directory, or overflow log directory for the given log stream. If the operation was a crash recovery, the database is left in an inconsistent state. If the operation was a rollforward operation, the operation has stopped and the database is left in rollforward pending state.	Recover the missing log file by taking one of the following actions: Move the specified log file into the database log directory and restart the operation. If an overflow log path can be specified, restart the operation with the overflow log path, specifying the path that contains the log file. If the missing log file cannot be found, determine whether one of the following special cases applies: If the operation is a ROLLFORWARD DATABASE command to maintain a standby system through log shipping, this error might be normal, because some files that are available on the primary site might not yet be available on the standby system. To ensure that your standby system is up-to-date, issue a ROLLFORWARD DATABASE command with the QUERY STATUS option after each rollforward operation to verify that the log replay is progressing properly. If you find that a rollforward operation on the standby system is not making progress over an extended period of time, determine why the log file that is reported as missing is not available on the standby system, and correct the problem. Note that the ARCHIVE LOG command can be used to truncate currently active log files on the primary system, making them eligible for archiving and subsequent replay on the standby system. If a ROLLFORWARD DATABASE command with the TO END OF LOGS option was issued following a restore operation from an online backup image in which the only available logs are those that were included in the backup image, there are two possible scenarios to consider: Scenario 1: All of the log files contained in the backup image are found by the rollforward operation. However, the rollforward operation still looks for log files that were updated following the original backup operation. Bring the database to a consistent state by issuing the ROLLFORWARD DATABASE command with the STOP option (without the TO END OF LOGS option). To avoid this scenario in the future, use the END OF BACKUP option instead of the END OF LOGS option, because the rollforward operation will not look for log files that were updated after the backup was taken. Scenario 2: One or more log files that were contained in the backup image were not found by the rollforward operation. These log files are required to bring the database to a consistent state. Attempting to bring the database to a consistent state by issuing the ROLLFORWARD DATABASE command with the STOP option (without the TO END OF LOGS option) will fail with SQL1273N; recover the missing log file, as described earlier in this section. If the missing log file cannot be recovered: If the operation is a ROLLFORWARD DATABASE command, you can issue the ROLLFORWARD DATABASE command again with the STOP option (without the END OF LOGS option or the END OF BACKUP option) to bring the database to a consistent state. If this consistency point (immediately prior to the missing log file) is not acceptable, you can restore the database and roll forward to any point in time that is prior to the missing log file by providing an earlier time stamp to the ROLLFORWARD DATABASE command. If the operation is a ROLLFORWARD DATABASE command with the STOP or COMPLETE option (without the END OF LOGS option or the END OF BACKUP option), the missing log file is needed to bring the database to a consistent state. Because you cannot recover the missing log file, you must restore and roll forward to an earlier point in time (as long as that point in time is not prior to the minimum recovery time).
ADM1602W	Rollforward recovery has been initiated.
ADM1603I	The database manager is invoking the forward phase of the database rollforward recovery.
ADM1604I	The database manager is invoking the forward phase of the table space rollforward recovery.
ADM1605I	The database manager is invoking the backward phase of database rollforward recovery.
ADM1606I	The database manager is invoking the backward phase of table space rollforward recovery.
ADM1607I	The database manager is invoking the completion phase of the database rollforward recovery.
ADM1608I	The database manager is invoking the completion phase of the table space rollforward recovery.
ADM1609W	The database manager is canceling the database rollforward recovery.
ADM1610W	The database manager is canceling the table space rollforward recovery.
ADM1611W	The rollforward recovery phase has been completed.
ADM1612W	Online table space rollforward recovery could not complete due to the high volume of database activity. Either reduce the database activity, increase the MAXAPPLS configuration parameter, or perform an offline table space rollforward.
ADM1613W	The table space `tablespaceName` (ID `tablespaceID`) was previously rolled forward to `timestampPIT` at `timestampRFWD`.
ADM1614W	The table space `tablespaceName` (ID `tablespaceID`) has been placed into restore pending state. The rest of the table spaces have been rolled forward to the end of logs.
ADM1615W	The database manager cannot roll forward table space `tablespaceName` (ID `tablespaceID`) because it is still used by an active transaction. The application handle is `appHandle`. Terminate this application by COMMIT, ROLLBACK, or FORCE APPLICATION.
ADM1616E	The database manager could not find the dropped table log record that matches the given dropped table with ID `droppedTableID` during recovery.
ADM1617W	The table space `tablespaceName` (ID `tablespaceID`) that was included in the last rollforward has not yet completed. It has not been included in the table space list provided for this rollforward. It has been placed into restore pending state.
ADM1618W	The database manager cannot recover table space `tablespaceName` (ID `tablespaceID`) during database rollforward. The table space has been placed in rollforward pending state. To recover, perform a table space rollforward after the database rollforward is complete.
ADM1620W	Table partition with objectID `objectID` in tablespace `tablespaceID` was skipped during drop table recovery. To recover the data from this partition include the tablespace in the rollforward list.
ADM1700W	The database manager is unable to use the log path specified by the backup image; Switching to the default log path.
ADM1710C	The database is not accessible because the database manager cannot write to the log control file `file-name` on database partition `database-partition-num`. Possible reasons for this include: the file does not exist; the file is not accessible to the database manager because of network, file system, or OS problems; or incorrect file permissions are preventing the database manager from writing to the file. Ensure that the file is accessible to the database manager and that the file system is functioning properly, and restart or reconnect to the database.
ADM1711W	The log control file `log-control-file-name` on database partition `database-partition-num` was missing or corrupt. This might be a result of the database previously being stopped abnormally. The database manager recreated this file.
ADM1712C	The log control file `file-name` on database partition `database-partition-num` was missing or corrupt. The database manager attempted to recreate it, but was not successful. Possible reasons for this include: the file is not accessible to the database manager because of network, file system, or OS problems; or incorrect file permissions are preventing the database manager from reading from or writing to the file. Ensure that the file is accessible to the database manager and that the file system is functioning properly.
ADM1713C	The database manager cannot start the database on database partition `database-partition-num` because the database manager can open neither the primary log control file `primary-log-file` nor the secondary log control file `secondary-log-file`.
ADM1714W	The recovery control file `recovery-control-file-name` on database partition `database-partition-num` was corrupt. This might be a result of the database previously being stopped abnormally. The database manager recreated this file.
ADM1715C	The recovery control file `recovery-control-file-name` on database partition `database-partition-num` was corrupt. The database manager attempted to recreate it, but was not successful. Possible reasons for this include: the file is not accessible to the database manager because of network, file system, or OS problems; or incorrect file permissions are preventing the database manager from reading from or writing to the file. Ensure that the file is accessible to the database manager and that the file system is functioning properly.
ADM1716C	The database manager cannot start the database on database partition `database-partition-num` because the database manager cannot open the recovery control file `recovery-control-file-name`.
ADM1800E	The database manager was unable to confirm log `logNumber` was archived on the old log path. Take a database backup to ensure that the database may be recovered.
ADM1801W	The database manager could not access more than 2GB of file storage on the raw device. Therefore, only 2GB of file storage will be used for logging.
ADM1802W	Database was put into offline backup pending state because the LOGFILSIZ DB configuration parameter has changed while using raw device for logging.
ADM1803W	There is not enough space left on raw device `path` for log files. The actual device size is `actualDevice` 4K pages. The minimum required device size is `minimumDevice` 4K pages.
ADM1804W	The raw device is too small to support active log space. `actualDeviceSize` 4K pages are available, however, `minimumDeviceSize` 4K pages are required. Use a larger device or reduce the LOGPRIMARY and/or the LOGFILSIZ DB configuration parameters.
ADM1805E	The database manager is unable to use the NEWLOGPATH DB configuration parameter because the raw device is already being used as a log or table space container elsewhere.
ADM1806E	Unable to use the NEWLOGPATH DB configuration parameter `newLogPath` so the database manager will continue to use the current log path.
ADM1807E	The new DB configuration parameter values for NEWLOGPATH and MIRRORLOGPATH are identical, this is not allowed. Ensure that the values are different for the two parameters.
ADM1810E	The new value of the MIRRORLOGPATH DB configuration parameter is invalid or cannot be used. The database manager will ignore the new value. Confirm the new path value and ensure that it is valid.
ADM1811E	The database manager will now switch to the default log path `logpath`.
ADM1812E	The new value of the MIRRORPATH DB configuration parameter `newMirrorPath` is not usable. The database manager will continue to use the existing mirror path `defaultMirrorPath`.
ADM1813E	The current mirror path `currentMirrorPath` is invalid.
ADM1814E	The current log path `currentLogPath` is invalid.
ADM1815E	An error occurred while the database manager was trying to remove log files from `logFilePath`.
ADM1817E	The database manager was unable to execute the user exit program when archiving log file `logFilename` from `dirPath` for database `DBName`. The error code was `returnCode`. Verify user exit program by manually running it.
ADM1818E	An error was received from the user exit program. The database manager will not call the user exit program for this database for 5 minutes.
ADM1819C	The database manager was unable to switch to the new log file size because an error occurred while archiving an old log on the raw device. As a result, the database cannot be accessed.
ADM1821E	The log path has been reset to the default value.
ADM1822W	The active transaction log is being held by dirty pages. Database performance may be impacted.	The rate at which the database work load is generating dirty pages has exceeded the rate at which the page-cleaner agents are writing dirty pages to disk. Dirty pages that have not yet been written to disk are holding the transaction log.	Reduce the database work load, if possible. If this problem persists, take the following action: Decrease the value of the PAGE_AGE_TRGT_MCR and PAGE_AGE_TRGT_GCR database configuration parameters Increase the value of the NUM_IOCLEANERS database configuration parameter
ADM1823E	The active log is full and is held by application handle `handle`. Terminate this application by COMMIT, ROLLBACK or FORCE APPLICATION.
ADM1824W	The database manager cannot delete the log file `filename`. User must manually delete the log file.
ADM1825W	The database manager cannot create the next log file because of a user exit problem.
ADM1826E	The database manager cannot continue because the disk used for logging is full.
ADM1827E	There is no space left on raw device used for logging. User must make an offline backup of the database.
ADM1828C	The database manager will attempt to create the log file again in 5 minutes.
ADM1829E	The active log is full and is held by an indoubt transaction.	This message is returned when the database manager must release the current active log file and use a different log file, but cannot release the current active log file because an indoubt transaction has a lock on the current active log file.	Resolve the indoubt transaction using the LIST INDOUBT TRANSACTIONS WITH PROMPTING command.
ADM1830E	The active log path is set to the default value.
ADM1831E	The database manager was unable to execute user exit program when retrieving log file `logFilename` to `dirPath` for database `DBName`. The error code was `returnCode`. Verify the user exit program by manually running it.
ADM1832E	The database manager was unable to find the user exit program when archiving log file `logFilename` from `dirPath` for database `DBName`. The error code was `returnCode`.
ADM1833E	The user exit program returned an error when archiving log file `logFilename` from `dirPath` for database `DBName`. The error code was `returnCode`.
ADM1834E	The database manager was unable to find the user exit program when retrieving log file `logFilename` to `dirPath` for database `DBName`. The error code was `returnCode`.
ADM1835E	The user exit program returned an error when retrieving log file `logFilename` to `dirPath` for database `DBName`. The error code that was returned by the user exit program to the database manager was: `returnCode`.	You can automate log file archiving and retrieval by creating a user exit program that the database manager calls to carry out the archiving or retrieval operation. When the database manager invokes your user exit program, the following happens: The database manager passes control to the user exit program The database manager passes parameters to the user exit program On completion, the use exit program passes a return code back to the database manager The database manager can only handle specific error codes. However, a user exit program might encounter many different kinds of error conditions, such as operating system errors. A user exit program must map the error conditions it encounters to error codes that the database manager can handle. This message is returned when a user exit program fails and returns the specified return code to the database manager.	Refer to the documented list of standard user exit error codes. Refer to any error handling information for your user exit program.
ADM1836W	The table `tableID` (ID `tableID`) on `tablespaceName` (ID `tablespaceName`) is in DATALINK Reconcile Pending (DRP) state.
ADM1837W	The table `tableName` (ID `tableID`) on `tablespaceName` (ID `tablespaceID`) is in DATALINK Reconcile Not Possible (DRNP) state.
ADM1838W	An application is waiting for a lock held by an indoubt transaction. This will cause the application to wait indefinitely. Use the LIST INDOUBT TRANSACTIONS command to investigate and resolve the indoubt transactions.
ADM1839W	An error occurred while the database manager was writing log data to log file `logFile` on path `logPath1`. The log file is still available on log path `logPath2`. The database manager will attempt to use both paths for subsequent log files. In the meantime, check that the specified log path in which the error occurred exists and is accessible. Also check that there is space available in the file system.
ADM1840W	The error on log path `logPath` has been resolved. The database manager will now write log files to this path.
ADM1841W	The database manager was either unable to locate log `logFile` or found a validation issue with the log while attempting to archive it. Your existing recovery strategy may not work if this log file is required during recovery. A database backup is required to ensure the recoverability of the database. However, the backup should be taken after the First Active Log file (LOGHEAD) DB configuration parameter is beyond the specified log. You might want to consider deactivating the database now to have the First Active Log file (LOGHEAD) move up, and then take a backup.
ADM1842W	The database configuration update was successful, but the database could not be made recoverable.	Although the update was successful, the database is not recoverable. Possible reasons for this are: At least one table space is in a table space state other than "Normal" Member crash recovery is pending on at least one member in this DB2 pureScale instance. The database will continue to use circular logging until all of the table spaces are in a "Normal" state. In environments using DB2 pureScale, all members are consistent.	If this error is being returned because one or more table spaces are not in "Normal" state, respond to this error by performing the following steps: Determine which table spaces are not in the "Normal" state using the MON_GET_TABLESPACE table function. For each table spaces that is not in "Normal" state, resolve the issue that corresponds to the state that it is in. If this error is being caused by a pending member crash recovery, perform member crash recovery on each member that is inconsistent. In most cases, this requires no user response because member crash recovery is initiated automatically. If member crash recovery is not initiated automatically, issue a RESTART DATABASE command. The database will be recoverable when it is next started or activated. A full database backup will be required at that time.
ADM1843I	Started retrieve for log file `logFilename`.
ADM1844I	Started archive for log file `logFilename`
ADM1845I	Completed retrieve for log file `logFilename` on chain `chain-number` from `destPath` to `dirPath`.
ADM1846I	Completed archive for log file `logFilename` to `destPath` from `dirPath`.
ADM1847W	Failed to retrieve log file `logFilename` on chain `chain-number` from `destPath` to `dirPath`.
ADM1848W	Failed to archive log file `logFilename` to `destPath` from `dirPath`.
ADM1849C	The database has reached `current-LSN/LSO/LFS-value` for log record identifier type `LSN/LSO/LFS-type`, which is approaching its maximum value. After that maximum value is reached, you will no longer be able to use the database.	The database manager identifies database log records using various non-decreasing identifiers: LSN, LFS, and LSO. Your database has used nearly all of the possible values for at least one of these identifiers.	Before your database runs out of unique LSN/LSO/LFS values, perform the following steps: Unload all of the data from the database. Drop and recreate the database. Reload the data. The LSN/LSO/LFS values will restart at 0 after these steps have been completed. For additional assistance in responding to this error, contact IBM software support.
ADM1850C	The database has run out of log record identifiers. Log record identifier type `LSN/LSO/LFS-type` has reached `current-LSN/LSO/LFS-value`. The database cannot process any transactions that require additional log records to be written.	The database manager identifies database log records using various non-decreasing identifiers: LSN, LFS, and LSO. Your database has used nearly all of the possible values for the `LSN/LSO/LFS-type` identifier. No more log records can be written.	Perform the following steps: Unload all of the data from the database. Drop and recreate the database. Reload the data. The LSN/LSO/LFS values will restart at 0 after these steps have been completed. For additional assistance in responding to this error, contact IBM software support.