ADM0000 - ADM5999

ADM0001C A severe error has occurred. Examine the administration notification log and contact IBM Support if necessary.

ADM0500E The DB2 Service does not have the necessary authority to complete the command. If a user account has been associated with the DB2 Service, ensure that the user account has the correct access rights on the local system and access to the Domain Security Database for user authentication and group enumeration.

ADM0501C A stack overflow exception has occurred. The database manager instance has terminated abnormally. To remedy this problem, you may increase the default stack size for db2syscs.exe using the db2hdr utility as follows: db2hdr \sqllib\bin\db2syscs.exe /s:<stackreserve>[,<stackcommit>] Note that increasing the default stack size will consume virtual memory space and may reduce the maximum number of concurrent connections. Contact IBM Support for further assistance.

ADM0502C The database manager instance has terminated abnormally. To remedy this problem, increase the AGENT_STACK_SZ DBM configuration parameter. Contact IBM Support for further assistance.

ADM0503C An unexpected internal processing error has occurred. All database manager processes associated with this instance have been shutdown. Diagnostic information has been recorded. Contact IBM Support for further assistance.

ADM0504C An unexpected internal processing error has occurred. All database manager processes associated with this instance have been suspended. Diagnostic information has been recorded. Contact IBM Support for further assistance.

ADM0505E The database manager received a SIGDANGER signal from the operating system. This signal indicates that the system is running low on paging space. If the paging space gets too low, the operating system will forcibly terminate user processes. Contact your system administrator to increase your paging space.

ADM0506I The database manager has automatically updated the `parameter` kernel parameter from `originalValue` to the recommended value `recommendedValue`.

ADM0507W The database manager could not automatically update the `parameter` kernel parameter to the recommended value `recommendedValue`. Update this kernel parameter manually.

ADM0508E The database manager was unable to load the Java interpreter library `libraryPath`. This error commonly occurs because of restrictions imposed by the operating system. Consult the IBM documentation for a solution. If this problem persists, contact IBM support.

ADM0509E A non-root database manager instance has been detected. Limited functionality will be available.

ADM0510E AGENTPRI configuration variable or Agent Priority Resource Configuration changes are not possible without root capabilities.

ADM0511E Raw device access using the character device controller has been deprecated by the operating system and might be removed in the future. The database manager processes can access the same device by using the block device interface; however db2relocatedb will need to be run on each individual database to change the name of the affected device in any table space containers and raw log containers.

Explanation

When working with containers to store data, the database manager supports direct disk (raw) access using the block device interface (that is, raw I/O).

User response

Change the name of the affected device in any table space containers and raw log containers by using the db2relocate command.

ADM0512W The database manager instance does not have permission to pin a database memory segment. Contact your system administrator to grant permission for the database manager instance owner to pin memory. The database manager will continue to function with unpinned database memory.

ADM0513W db2start succeeded. However, no I/O completion port (IOCP) is available.

Explanation

This error is returned when there are no I/O completion ports with status "Available" on the computer where DB2 database is installed. An I/O completion port is an operating system channel for I/O requests. Using I/O completion ports can improve the performance of very large databases.

User response

If you want to use I/O completion ports to improve performance, configure I/O completion ports.

ADM0514W The system Network Time Protocol (NTP) process was not detected to be up and running or properly synchronized.

Explanation

To ensure that clock-sensitive operations like error-logging, monitoring and point-in-time recovery run optimally across a distributed environment, it is highly recommended that the Network Time Protocol (NTP) service be running and synchronized to the same system peer across all members.

User response

Ensure that the NTP service is up and running and that all members are synchronized to the same host.

ADM0515W The system clock on this member is out of synchronization by more than the allowed threshold with member `coordinator-member`. The differential is `timestamp-diff` minutes.

Explanation

Timestamps from each member are periodically compared to ensure that the time discrepancy between members is less than the predefined allowable threshold set by the MAX_TIME_DIFF database manager configuration parameter. The differential between the local system clock on this host and that of the indicated remote member has been detected to exceed this limit.

User response

Verify that the differentials between the system clocks on all members are within the limit specified by MAX_TIME_DIFF.

ADM0516W CPU binding information: cluster caching facility (CF) processes are bound to `number` cores.

Explanation

When a cluster caching facility and a DB2 member coexist on a single host, the CF processes will be assigned to a subset of the total cores available. For more specific information on the logical processors, see the db2diag.log file.

User response

No user response is required.

ADM0517W CPU binding information: DB2 member processes are bound to `number` cores.

Explanation

When a DB2 member and a cluster caching facility (CF) coexist on a single host, the member processes will be assigned to a subset of the total cores available. For more specific information on the logical processors, see the db2diag.log file.

User response

No user response is required.

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`.

Explanation

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.

User response

None.

ADM1502C A command has set BACKUP_PENDING state off. Data integrity or the referential integrity of the data is at risk.

Explanation

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.

User response

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.

Explanation

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.

User response

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.

Explanation

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.

User response

No action required.

ADM1505I Crash recovery has completed synchronous processing.

Explanation

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. New connections to the database are allowed while the rolling back of these incomplete transactions executes in the background.

User response

No action required.

ADM1524I Member crash recovery has been initiated.

Explanation

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.

User response

No user action required.

ADM1525I Member crash recovery has completed successfully.

Explanation

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.

User response

No user action required.

ADM1526E Member crash recovery has failed with SQLCODE `SQLCODE`

Explanation

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,

User response

Refer to details of the given SQLCODE.

ADM1527I Group crash recovery has been initiated.

Explanation

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.

User response

No user action required.

ADM1528I Group crash recovery has completed successfully.

Explanation

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.

User response

No user action required.

ADM1529E Group crash recovery has failed with SQLCODE `SQLCODE`

Explanation

Group crash recovery has failed. The database is not available until group crash recovery successfully completes.

User response

Refer to details for the given SQLCODE.

ADM1530I Crash recovery has been initiated.

Explanation

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.

User response

No user action required.

ADM1531I Crash recovery has completed successfully.

Explanation

User response

No user action required.

ADM1532E Crash recovery has failed with SQLCODE `SQLCODE`.

Explanation

Crash recovery has failed. The database is not available until crash recovery successfully completes.

User response

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`.

Explanation

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.

User response

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.

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`.

Explanation

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.

User response

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`.

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.

Explanation

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.

User response

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.

Explanation

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.

User response

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`.

Explanation

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.

User response

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 unable to locate log `logNumber` while attempting to archive it. Your existing recovery strategy may not work if the missing 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.

User response

ADM1842W The database configuration update was successful, but the database could not be made recoverable.

Explanation

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.

User response

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`.

User response

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`.

User response

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.

Explanation

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.

User response

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.

Explanation

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.

User response

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.

ADM2000E The Event Monitor `eventMonitor` was deactivated because it encountered an I/O error.

ADM2001W The Event Monitor `eventMonitor` was deactivated because the MAXFILES and MAXFILESIZE CREATE EVENT MONITOR parameters' limits have been reached.

ADM2002E The Event Monitor `eventMonitor` was deactivated when the process reading from the target pipe had disconnected.

ADM2003W The Event Monitor `eventMonitor` was not activated because the limit on the number of active event monitors has already been reached.

ADM2004E The Event Monitor `eventMonitor` was not activated because there was not enough storage space in the database monitor heap. To remedy this problem, increase the MON_HEAP_SZ DBM configuration parameter.

ADM2005W The database monitor heap is exhausted. Increase the MON_HEAP_SZ DBM configuration parameter.

ADM2006W The database monitor heap is exhausted. Statement elements may be unreliable. Increase the MON_HEAP_SZ DBM configuration parameter.

ADM2007W The event monitor `eventMonitor` was deactivated due to PCTDEACTIVE limit reached. To reactivate the named event monitor, either increase the table space size or increase the PCTDEACTIVE threshold.

ADM2009C The Event Monitor `eventMonitor` detected on table `tableName` (ID `tableID`) that the column name `colName` is invalid.

ADM2010C The Event Monitor `eventMonitor` detected on table `tableName` (ID `tableID`) that the column `colName` is not allowed.

ADM2011C The Event Monitor `eventMonitor` detected on table `tableName` (ID `tableID`) that the column `colName` has an invalid `dataType` data type.

ADM2012C For table `tableName`, (ID `tableID`) the row size is bigger than the page size.

ADM2013C The Event Monitor `eventMonitor` detected on table `tableName` (ID `tableID`) that the column `colName` is incorrect. The first column must be PARTITION_KEY.

ADM2014W The Event Monitor `eventMonitor` detected on table `tableName` (ID `tableID`) that the size of the column `colName` is smaller than the default size of `defaultColumnSize`. Therefore, contents will be truncated to the user specified size.

ADM2015W The SQLCODE received from the remote target node is `SQLCODE`.

ADM2016W The table `tableName` (ID `tableID`) was not found.

ADM2017C The Event Monitor `monitor-name` has reached its file capacity. Delete the files in the target directory `directory` or move them to another directory.

ADM2018W The Event Monitor `monitor-name` has been deactivated. Event monitor data collection cannot be performed.

Explanation

The event monitor deactivated due to some error in processing that is described in probe information found in the administration notification and db2diag log files.

User response

Look in the administration notification or db2diag log file for probe information that indicates why the event monitor deactivated, correct the error, and then reactivate the event monitor by issuing the following statement:

SET EVENT MONITOR monitor-name STATE 1

ADM2500E A serious error has occurred at the database server `DRDAApplicationServer` which has made continued processing impossible. A dump has been generated. If the remote server is DB2 UDB for OS/390,zOS, check the console log for information about this error. If the remote server is DB2 UDB for iSeries, the job log of the server job, and/or a first failure data capture (FFDC) spooled file is usually necessary to determine the cause of the error. If the remote server is DB2 Database for Linux, UNIX, and Windows, check the remote database server's administration log for information regarding this error.

ADM2501C The amount of data received for a data type at the database server did not match the amount which was expected. A dump has been generated. If the remote server is DB2 UDB for OS/390,zOS, check the console log for information about this error. If the remote server is DB2 UDB for iSeries, the job log of the server job, and/or a first failure data capture (FFDC) spooled file is usually necessary to determine the cause of the error. If the remote server is DB2 Database for Linux, UNIX, and Windows, check the remote database server's administration log for information regarding this error.

ADM2502C The remote database server has encountered an error.

Explanation

The client has detected a problem on the remote server.

User response

If the remote server is DB2 UDB for OS/390,zOS, check the console log for information about this error.

If the remote server is DB2 UDB for iSeries, the job log of the server job, and/or a first failure data capture (FFDC) spooled file is usually necessary to determine the cause of the error.

If the remote server is DB2 Database for Linux, UNIX, and Windows, check the remote database server's administration log for information regarding this error.

If the remote server is IBM Informix Dynamic Server, check the online.log or use onstat (-m) for information about this error.

ADM2503C A datastream parsing error has been detected. A dump has been generated.

ADM2504C The LOB data type is not supported on this database server. APAR fixes are required. If this database server is DB2 for OS/390 v6 and v7, apply the fixes for APARs PQ50016 and PQ50017. If the database server is DB2 for iSeries, any release prior to V5.1 is not supported. For DB2 for iSeries v5.1, the PTF for APAR 9A00531 must be applied. If the database server is DB2 for VM and VSE, contact IBM Support.

ADM2505E While the database manager was attempting to utilize sysplex support, a connection could not be established to the database server at SNA address `SNAAddress` due to an unknown cpic symbolic destination name `destName`. Check your SNA configuration and validate it with network support personnel or disable sysplex support at the DB2 Connect Server.

User response

ADM2506W While an application was attempting to issue a deferred SET statement, the server returned a non-zero sqlcode. The sqlcode is `SQLCODE`. Check your application, and validate the deferred SET statement.

ADM2507I Client Reroute failed because of product signature violation. Original product signature: `product signature`. Retry product signature: `product signature`.

ADM2508I Client Reroute successful. Hostname/IP Address: `hostname/IP address` and Service name/Port number: `service name/port number`.

ADM2509I Database connection is successful. Connecting to --> Hostname/IP Address: `hostname/IP address` and Service name/Port number: `service name/port number`.

ADM3000C The network host entry `networkHostEntry` at line `lineNumber` of db2nodes.cfg cannot be resolved.

ADM3001C The database manager cannot create the intermediate socket directory `socketDirectory`. Check the permissions of this path.

ADM3003C The node `node` is no longer present in db2nodes.cfg, even though this node had existed when FCM had started up. This may indicate a communication failure.

ADM3006C The retry limit was reached while attempting to establish a connection to node `node`. The database manager will now initiate node recovery.

ADM3008C The connection with node `node` has been unexpectedly severed. The database manager will now initiate node recovery.

ADM3019C The link between node `node1` and node `node2` is broken. Check your switch and cables.

ADM3020C The number of FCM buffers is too small. This will impact communication between DB2 agents and lead to runtime errors. If this message persists, you should adjust the FCM_NUM_BUFFERS DBM configuration parameter.

ADM3021W VI is enabled on this node.

ADM3500W The group IDs on the database partitions do not match. In a partitioned database, each partition must have the same set of users and groups defined. If the definitions are not the same, a user may be authorized to perform different actions on different partitions. Consistent user and group definitions across all partitions is recommended.

ADM4000W A catalog cache overflow condition has occurred. There is no error but this indicates that the catalog cache has exceeded the configured maximum size. If this condition persists, you may want to adjust the CATALOGCACHE_SZ DB configuration parameter.

ADM4001I A failure has occurred while regenerating the view `viewName`.

ADM4002W The Event Monitor target table `targetTableName` (table schema `tableSchema` ) already exists.

ADM4003E The UPGRADE DATABASE command failed to upgrade the DB2 Text Search catalogs or indexes due to an error in stored procedure `stored-procedure-name`.

Explanation

The database is enabled for DB2 Text Search and has been upgraded successfully. However, an error occurred while upgrading the text search catalogs or indexes.

User response

Call the stored procedures to upgrade the DB2 Text Search catalogs or indexes.

If SYSPROC.SYSTS_UPGRADE_INDEX failed to complete successfully, reissue the stored procedure.
If SYSPROC.SYSTS_UPGRADE_CATALOG failed to complete successfully, then call these upgrade procedures again in this specific order:
1. SYSPROC.SYSTS_UPGRADE_CATALOG
2. SYSPROC.SYSTS_UPGRADE_INDEX

ADM4004W The db2ckupgrade utility found that the database contains the following types of objects, which are not supported by the version to which upgrading is being considered: XML global variables; or compiled SQL functions that use XML parameters or that return XML types.

Explanation

You can verify that a given database can successfully be upgraded to a later version using the db2ckupgrade utility.

This message is returned when the db2ckupgrade utility finds database objects which are not supported in the version to which you are upgrading. Specifically, this message is returned when the following database objects are in a database being checked:

Global variables of type XML
Compiled SQL functions that use parameters of type XML or that return XML types

If you proceed to upgrade the database to the target version, these objects will be invalidated during database upgrade. You will be unable to use these database objects until you upgrade to a version that supports those database objects.

User response

To be able to use the database objects that are invalidated during upgrade, upgrade to a release and fix pack of DB2 database that supports XML global variables and compiled SQL functions that use XML parameters or that return XML types. When you upgrade to a fixpack that supports those database objects, the objects will be automatically revalidated the first time they are referenced after the database has been upgraded.

ADM4005W The upgrade procedure marked the following types of database objects as "invalidated" because those objects are not supported in the upgraded version: XML global variables; and compiled SQL functions that use XML parameters or that return XML types.

Explanation

You can upgrade a database to a later version using the UPGRADE DATABASE command.

This message is returned when a database that contains the following database objects is upgraded to a version that does not support those types of database objects:

Global variables of type XML
Compiled SQL functions that use parameters of type XML or that return XML types

The upgrade operation marked all of these types of database objects as "invalidated". You will be unable to use these database objects until you upgrade to a version that supports those database objects.

User response

To be able to use the database objects that were invalidated during upgrade, upgrade to a release and fix pack of DB2 database that supports XML global variables and compiled SQL functions that use XML parameters or that return XML types. When you upgrade to a fixpack that supports those database objects, the objects will be automatically revalidated the first time they are referenced after the database has been upgraded.

ADM4006E The db2ckupgrade utility detected a configuration problem that will prevent a successful database upgrade: In the DB2_SQLROUTINE_PREPOPTS registry variable, the EXPLAIN value is set to YES or ALL, but there are no explain tables in the database.

Explanation

You can customize precompile and bind options for SQL and XQuery procedures and functions by setting the DB2_SQLROUTINE_PREPOPTS registry variable. For example, you can cause access plan information to be stored in explain tables by specifying "EXPLAIN YES" in DB2_SQLROUTINE_PREPOPTS. (Using the DB2_SQLROUTINE_PREPOPTS registry variable is just one of several ways to configure the behavior of the explain feature.)

This message is returned when the db2ckupgrade utility is used to verify whether a specified database can be upgraded, and the DB2_SQLROUTINE_PREPOPTS registry variable contains either "EXPLAIN YES" or "EXPLAIN ALL", but no explain tables exist in the database.

User response

Resolve this upgrade-blocking problem by taking either one of the following actions:

Set the EXPLAIN value in the DB2_SQLROUTINE_PREPOPTS registry variable to "EXPLAIN NO".
Create explain tables in the database.

After this problem has been resolved, confirm whether there are any other problems that would prevent a successful upgrade operation by issuing the db2ckupgrade command again.

ADM4007W The db2ckupgrade utility detected a configuration problem that might prevent a successful database upgrade: In the DB2_SQLROUTINE_PREPOPTS registry variable, the EXPLAIN value is set to YES or ALL.

Explanation

If you are planning to upgrade a given database, if the DB2_SQLROUTINE_PREPOPTS registry variable contains either "EXPLAIN YES" or "EXPLAIN ALL", and if the database contains no explain tables for your user ID, then if you issue the UPGRADE DATABASE command, the upgrade operation will fail.

When the db2ckupgrade utility detects that the DB2_SQLROUTINE_PREPOPTS registry variable contains either "EXPLAIN YES" or "EXPLAIN ALL", this message is printed to warn you that if there are no explain tables in the database for the ID of the user who issues the UPGRADE DATABASE command, the upgrade operation will fail.

User response

Before upgrading the database, perform one of the following actions:

Set the EXPLAIN value in the DB2_SQLROUTINE_PREPOPTS registry variable to "EXPLAIN NO".
If there are no explain tables in the database for the user who will be performing the database upgrade operation, create explain tables in the database for that user ID.

ADM4014N The ALTER TABLE ATTACH operation failed because either there are no indexes on the source table, or the indexes on the source table `source-table-name` do not match the partitioned index `index-name` on the target table `target-table-name`. Reason: `reason-code`.

Explanation

See the applicable reason code for more information:

1: The indexes on the source table do not match the unique partitioned index on the target table.
2: The indexes on the source table do not match the partitioned XML pattern values index that was created with the REJECT INVALID VALUES on the target table.
3: The indexes on the source table do not match the partitioned indexes on the target table, and the ALTER TABLE ATTACH statement is defined with the REQUIRE MATCHING INDEXES clause.

User response

Respond according to the reason code, and then rerun the ALTER TABLE ATTACH operation.

1: Create a unique index on the source table that matches the unique partitioned index on the target table.
2: Create an XML pattern values index on the source table (using the REJECT INVALID VALUES clause) to match the index on the target table.
3: Either create an index on the source table that matches the partitioned index on the target table, or remove the REQUIRE MATCHING INDEXES clause from the ALTER TABLE ATTACH statement.

ADM4015I No index on the `source-table` source table matches the partitioned index `index-name` on the target table `target-table`. ALTER TABLE ATTACH processing continues.

Explanation

After the ATTACH operation completes successfully, the index partition will be built on the first access to the newly attached table partition. Usually, the first access is from a SET INTEGRITY statement.

To maximize roll-in efficiency, create indexes on the source table that match the partitioned indexes on the target table before attaching the source table to the target table.

User response

No response is required.

ADM4016I The index `indexName` on the source table `source-table` does not match any partitioned indexes on the target table `target-table` . ALTER TABLE ATTACH processing continues.

Explanation

A successful ATTACH operation will drop this index on the source table.

To maximize roll-in efficiency, drop the indexes on the source table that do not match the indexes on the target table before attaching the source table to the target table.

User response

No response is required.

ADM4100W The db2ckupgrade or UPGRADE DATABASE command identified external routines or user-defined wrappers that could have potential incompatibility with the multi-threaded database manager. See the file `generated-file` that contains the list of routines and wrappers identified, or a set of statements to restore the routine or wrapper definitions altered by the UPGRADE DATABASE command.

Explanation

The database manager is multi-threaded, as opposed to multi-processed, on Linux and UNIX operating systems. The execution of NOT FENCED and NOT THREADSAFE external routines or user-defined wrappers, which are NOT FENCED in the multi-threaded database manager, could lead to incorrect results, database corruption, or abnormal termination of the database manager. As a result, all NOT FENCED routines and all NOT FENCED user-defined wrappers must be THREADSAFE.

During database upgrade, all external NOT FENCED routines that have no dependency on the database manager library are altered to FENCED and NOT THREADSAFE. Also, the DB2_FENCED option is set to 'Y' for all user-defined wrappers. The UPGRADE DATABASE command generates a script generated-file that contains the statements to restore the routine or wrapper definitions.

When running db2ckupgrade, external NOT FENCED routines that have no dependency on the database manager library are identified. These routines will be altered to FENCED and NOT THREADSAFE during database upgrade. The file generated-file is generated with a list of all the identified external NOT FENCED routines and user-defined wrappers with the DB2_FENCED option is set to 'N'.

User response

When upgrading the database, verify that all the affected routines and user-defined wrappers can safely be run as NOT FENCED and THREADSAFE. Once verified, they can be altered back to NOT FENCED and THREADSAFE, by running the file generated-file to alter all of the routines and user-defined wrappers to NOT FENCED. Modify this file to contain only the statements that should be executed and run the CLP script after the database has been upgraded.

After running db2ckupgrade and before upgrading your database, alter the identified routines, listed in the generated file generated-file, to FENCED and NOT THREADSAFE and set the DB2_FENCED option to 'Y' for user-defined wrappers.

ADM4101W The UPGRADE DATABASE command failed to automatically collect statistics on the `table-name` system catalog table. The following RUNSTATS command returned SQLCODE `sqlcode` with tokens `tokens` : `command`.

Explanation

After successfully completing the database upgrade, the UPGRADE DATABASE command was unable to collect the statistics on the table-name system catalog table. The RUNSTATS command returned SQLCODE sqlcode with tokens tokens.

User response

Determine the appropriate user response based on the SQLCODE sqlcode returned.
Correct the problem and re-issue the RUNSTATS command on the table-name system catalog table to collect statistics.

ADM4102W The database contains one or more identifiers called NULL. To avoid conflict with the NULL keyword, you should qualify or delimit with double quotes any identifiers called NULL in SQL statements.

Explanation

An untyped NULL specification can occur anywhere in an expression. If an identifier called NULL is used in an SQL statement without being fully qualified or delimited, the identifier specification might resolve to the NULL keyword instead of the identifier reference. This would result in a change in behavior from previous releases.

User response

Determine if you have identifiers called NULL in the database by issuing the following statements:

SELECT TABSCHEMA, TABNAME, COLNAME FROM SYSCAT.COLUMNS WHERE COLNAME = 'NULL';
SELECT ROUTINESCHEMA, ROUTINENAME, PARMNAME FROM SYSCAT.ROUTINEPARMS WHERE PARMNAME = 'NULL';
For Version 9.5 databases or later, SELECT VARSCHEMA, VARNAME FROM SYSCAT.VARIABLES WHERE VARNAME = 'NULL'.

To avoid conflict with the NULL keyword, qualify or delimit with double quotes the identifiers called NULL in SQL statements.

ADM4103W The connection attribute `attributename` contains asterisks () in the workload `workloadname`. A single asterisk () will be replaced with two asterisks (**) during database upgrade. Reason code = `reason-code`.

Explanation

Starting with DB2 Version 9.7, you can use a single asterisk (*) as a wildcard character and two asterisks (**) to represent one literal asterisk (*) in some workload attributes.

The db2ckupgrade command identifies asterisks (*) in the connection attribute and the UPGRADE DATABASE command replaces the single asterisk (*) with two asterisks (**) if the type of connection attribute is one of the following values: 1 ( APPLNAME ) 6 ( CURRENT CLIENT_USERID ) 7 ( CURRENT CLIENT_APPLNAME ) 8 ( CURRENT CLIENT_WRKSTNNAME ) 9 ( CURRENT CLIENT_ACCTNG )

Reason codes are as follows:

1: The connection attribute was truncated because it reached the maximum length when a single asterisk (*) is replaced with two asterisks (**) during database upgrade.
2: The connection attribute was not truncated when a single asterisk (*) is replaced with two asterisks (**) during database upgrade.

User response

Replace asterisks (*) in the connection attribute with another character if possible.

ADM4104E One or more databases are enabled for XML Extender. You must remove the XML Extender functionality from the instance and databases before upgrading.

Explanation

Starting with DB2 Version 9.7, XML Extender is discontinued. Possible reasons for this error are:

The instance that you specified for upgrade has XML Extender functionality enabled, and the implicit call to db2ckupgrade fails because one or more databases are enabled for XML Extender.
The database that you are checking for upgrade is enabled for XML Extender.

User response

Remove the XML Extender functionality from the instance and disable databases for XML Extender. Then re-issue the db2iupgrade or db2ckupgrade command.

ADM4105W The Database is enabled for DB2 WebSphere MQ functions. The set of functions defined for XML Extender will be dropped during database upgrade.

Explanation

Starting with DB2 Version 9.7, XML Extender is discontinued. The set of DB2 WebSphere MQ functions that are defined for XML Extender will be dropped during database upgrade. These functions declare parameters using XML Extender user-defined data types.

User response

After the database upgrade, if you want to use DB2 WebSphere MQ functions with xml data type parameters, run the enable_MQFunctions command with the -force and -xml parameters to create new MQ functions for XML data type and re-create the existing MQ functions.

ADM4106W The upgraded database was enabled for XML Extender. XML Extender functionality was not disabled during database upgrade. However, this functionality will fail to run.

Explanation

Starting with DB2 Version 9.7, XML Extender has been discontinued. The database that you restored from a backup image created in a previous release is enabled for XML Extender.

The database was upgraded successfully. However, the XML Extender functionality such as routines will fail to run.

User response

Restore the database to a DB2 copy running a database product version that supports XML Extender, then upgrade from XML Extender.

ADM4200N The data type of the column could not be changed because of the data in the row with row identifier `rowid`.

Explanation

You can change the data type of a table column by using the ALTER TABLE statement with the ALTER COLUMN clause and the SET DATA TYPE clause.

This message is returned when an attempt to change the data type of a column fails because of an incompatibility between data in one of the rows of the table and the data type to which the column is being changed.

User response

Review the db2diag logs for more detailed information about why the data in the named row prevented the data type of the column from being changed.
Resolve the incompatibility by doing one of the following:
- Modify the data in the row so that the data type of the column can be changed.
- Change the data type of the column to one that is compatible with the existing data.

ADM4201N The data type of the column could not be changed because of the default values for the column named `column-name` in the table named `table-name`.

Explanation

You can change the data type of a table column by using the ALTER TABLE statement with the ALTER COLUMN clause and the SET DATA TYPE clause.

This message is returned when an attempt to change the data type of a column fails because of an incompatibility with the default values for the column being altered.

User response

Review the db2diag logs for more detailed information about why the default values for the column prevented the data type of the column from being changed.
Resolve the incompatibility by doing one of the following:
- Modify or drop the default values for the column so that the data type of the column can be changed.
- Change the data type of the column to one that is compatible with the existing data.

ADM4500W A package cache overflow condition has occurred. There is no error but this indicates that the package cache has exceeded the configured maximum size. If this condition persists, you should perform additional monitoring to determine if you need to change the PCKCACHESZ DB configuration parameter. You could also set it to AUTOMATIC.

ADM5000I `sevice` interaction was successfully started.

Explanation

Db2 has successfully begun interaction with the identified service.

ADM5001I `sevice` processing is now running in diagnostic mode.

Explanation

Db2 has successfully initiated processing for the identified service in diagnostic mode and will not attempt to send any messages to the identified service.

User response

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`

Explanation

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.

User response

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`

Explanation

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

User response

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`

Explanation

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.

User response

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`

Explanation

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.

User response

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.

Explanation

The token numLocks lists the total number of locks currently held by all applications that are accessing the table.

User response

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`.

Explanation

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.

User response

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`.

Explanation

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.

User response

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.

Explanation

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.

User response

No response is required.

ADM5509I Rebuilding `count` index partitions on data partition `DATAPARTITIONID` of the table `tableName`.

Explanation

The data server is rebuilding index partitions for the table on the specified data partition.

User response

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`.

Explanation

The rebuild of the index partitions failed for the specified data partition.

User response

Refer to details of the given SQLCODE.

ADM5513I Index rebuild on the data partition `DATAPARTITIONID` of table `tableName` completed successfully.

Explanation

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.

User response

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`.

Explanation

The data server is rebuilding the specified index partition.

User response

No response is required.

ADM5515I Index partitions on data partition `DATAPARTITIONID` of table `tableName` are successfully rebuilt.

Explanation

The data server has rebuilt the index partitions for the table on the specified data partition.

User response

No response is required.

ADM5520E This database version is not supported for database upgrade.

Explanation

The database version that you are trying to upgrade is unsupported in the DB2 copy from which you try to upgrade the database.

User response

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`.

Explanation

The rebuild is either for nonpartitioned indexes on a partitioned table, or for indexes on a nonpartitioned table.

User response

No response is required.

ADM5541W Rebuilding index with IID `indexIID` in object with ID `indexObjectID` and table space ID `indexTablespaceID` on table `tablename`.

Explanation

The rebuild is either for nonpartitioned indexes on a partitioned table, or for indexes on a nonpartitioned table.

User response

No response is required.

ADM5542W Indexes on table `tableName` are successfully rebuilt.

Explanation

The rebuild was either for nonpartitioned indexes on a partitioned table, or for indexes on a nonpartitioned table.

User response

No response is required.

ADM5543E Rebuild of indexes on table `tablename` failed with SQLCODE of `SQLCODE`.

Explanation

The rebuild was either for nonpartitioned indexes on a partitioned table, or for indexes on a nonpartitioned table.

User response

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.

Explanation

The object cannot be accessed.

User response

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.

Explanation

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.

User response

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`.

Explanation

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.

User response

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.

Explanation

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.

User response

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.

Explanation

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 .

User response

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.

Explanation

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.

User response

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.

User response

No response is required.

ADM0000 - ADM5999

ADM0001C A severe error has occurred. Examine the administration notification log and contact IBM Support if necessary.

ADM0502C The database manager instance has terminated abnormally. To remedy this problem, increase the AGENT_STACK_SZ DBM configuration parameter. Contact IBM Support for further assistance.

ADM0503C An unexpected internal processing error has occurred. All database manager processes associated with this instance have been shutdown. Diagnostic information has been recorded. Contact IBM Support for further assistance.

ADM0504C An unexpected internal processing error has occurred. All database manager processes associated with this instance have been suspended. Diagnostic information has been recorded. Contact IBM Support for further assistance.

ADM0506I The database manager has automatically updated the parameter kernel parameter from originalValue to the recommended value recommendedValue.

ADM0507W The database manager could not automatically update the parameter kernel parameter to the recommended value recommendedValue. Update this kernel parameter manually.

ADM0508E The database manager was unable to load the Java interpreter library libraryPath. This error commonly occurs because of restrictions imposed by the operating system. Consult the IBM documentation for a solution. If this problem persists, contact IBM support.

ADM0509E A non-root database manager instance has been detected. Limited functionality will be available.

ADM0510E AGENTPRI configuration variable or Agent Priority Resource Configuration changes are not possible without root capabilities.

Explanation

User response

ADM0512W The database manager instance does not have permission to pin a database memory segment. Contact your system administrator to grant permission for the database manager instance owner to pin memory. The database manager will continue to function with unpinned database memory.

ADM0513W db2start succeeded. However, no I/O completion port (IOCP) is available.

Explanation

User response

ADM0514W The system Network Time Protocol (NTP) process was not detected to be up and running or properly synchronized.

Explanation

User response

ADM0515W The system clock on this member is out of synchronization by more than the allowed threshold with member coordinator-member. The differential is timestamp-diff minutes.

Explanation

User response

ADM0516W CPU binding information: cluster caching facility (CF) processes are bound to number cores.

Explanation

User response

ADM0517W CPU binding information: DB2 member processes are bound to number cores.

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.

Explanation

User response

ADM1502C A command has set BACKUP_PENDING state off. Data integrity or the referential integrity of the data is at risk.

Explanation

User response

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.

Explanation

User response

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.

Explanation

User response

ADM1505I Crash recovery has completed synchronous processing.

Explanation

User response

ADM1524I Member crash recovery has been initiated.

Explanation

User response

ADM1525I Member crash recovery has completed successfully.

Explanation

User response

ADM1526E Member crash recovery has failed with SQLCODE SQLCODE

Explanation

User response

ADM1527I Group crash recovery has been initiated.

Explanation

User response

ADM1528I Group crash recovery has completed successfully.

Explanation

User response

ADM1529E Group crash recovery has failed with SQLCODE SQLCODE

Explanation

User response

ADM1530I Crash recovery has been initiated.

Explanation

User response

ADM1531I Crash recovery has completed successfully.

Explanation

User response

ADM1532E Crash recovery has failed with SQLCODE SQLCODE.

Explanation

User response

ADM1533W Database has recovered. However, one or more table spaces are offline.

ADM0506I The database manager has automatically updated the `parameter` kernel parameter from `originalValue` to the recommended value `recommendedValue`.

ADM0507W The database manager could not automatically update the `parameter` kernel parameter to the recommended value `recommendedValue`. Update this kernel parameter manually.

ADM0508E The database manager was unable to load the Java interpreter library `libraryPath`. This error commonly occurs because of restrictions imposed by the operating system. Consult the IBM documentation for a solution. If this problem persists, contact IBM support.

ADM0515W The system clock on this member is out of synchronization by more than the allowed threshold with member `coordinator-member`. The differential is `timestamp-diff` minutes.

ADM0516W CPU binding information: cluster caching facility (CF) processes are bound to `number` cores.

ADM0517W CPU binding information: DB2 member processes are bound to `number` cores.

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`.

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.

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.

ADM1526E Member crash recovery has failed with SQLCODE `SQLCODE`

ADM1529E Group crash recovery has failed with SQLCODE `SQLCODE`

ADM1532E Crash recovery has failed with SQLCODE `SQLCODE`.

ADM1534W Table space `tablespaceName` could not be reduced in size because there are used pages at the end of the table space.

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`.

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`.

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.

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.

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`.

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.

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.

ADM1806E Unable to use the NEWLOGPATH DB configuration parameter `newLogPath` so the database manager will continue to use the current log path.

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.

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.