ADM6000-7999

ADM Message ID	Message	Explanation	User Response
ADM6000E	The database manager encountered a read error while reading page `page-number` from tablespace `tbspace-id` for object `object-id` (located at offset `offset` of container `container-path`). The database manager was able to bypass the error by re-reading the page, but this may indicate the presence of a serious problem that could result in a future outage. You may wish to begin an investigation of the hardware (such as disk, controllers, network) and/or the filesystem involved in accessing the container.
ADM6001I	A container was renamed based on the rules defined in the path rename configuration file `configFile`. The container `oldName` has been renamed to `newName`.
ADM6002E	A container path of an invalid length was specified. The path specified was `containerName`. Refer to the documentation for SQLCODE -297.
ADM6003I	A container was not renamed because it was not affected by the rules defined in the path rename configuration file `configFile`. Its name remains as `contname`.
ADM6004N	The SET WRITE SUSPEND command failed for the database. Database name: `database-name`.	An error occurred during an attempt to suspend the write operations for the database.	Investigate the cause of the failure by reviewing the diagnostic (db2diag) log files. Correct the problem. Reissue the SET WRITE SUSPEND command again.
ADM6005N	The SET WRITE RESUME command failed for the database. Database name: `database-name`.	An error occurred during an attempt to resume the write operations for the database.	Investigate the cause of the failure by reviewing the diagnostic (db2diag) log files. Correct the problem. Reissue the SET WRITE RESUME command again.
ADM6006E	The database manager encountered an error while reading page `page-number` from table space `tbspace-id` for object `object-id` (located at offset `offset` of container `container-path`).	The database manager was not able to complete the operation, but the database remains accessible. This may indicate the presence of a serious problem that could result in a future outage.	You can begin an investigation of the hardware (such as disk, controllers, network) and/or the file system involved in accessing the container. If it is suspected that the DB2 data itself is in error, contact IBM Software Support and they will guide you through the proper corrective actions.
ADM6007C	DB2 detected an error while processing page `page-number` from table space `tbspace-id` for object `object-id` of object type `object-type`.	The database manager was not able to complete the operation, but the database remains accessible. This may indicate the presence of a serious problem that could result in a future outage.	Contact IBM Software Support and they will guide you through the proper corrective actions.
ADM6008I	Extents within the following table space have been updated: `table-space-name`. Table space ID: `table-space-id`.	You can reclaim unused extents in a given table space by issuing the ALTER TABLESPACE statement with the REDUCE clause. The ALTER TABLESPACE statement starts an asynchronous extent movement operation and then the statement immediately returns successfully. The outcome of the asynchronous extent movement operation will be logged in messages, such as this message, in the administration notification log. This message is returned when an asynchronous extent movement operation has completed successfully and the unused extents have been moved.	No response is required.
ADM6009W	The database manager detected that the amount of restart light memory (rstrt_light_mem) is too small for optimal recovery performance.	The database manager automatically reserves some memory on each member host to be used for restart light operation. This reserved memory is used to accommodate failed members that need to be restarted in restart light mode, on a host other than their home host. The rstrt_light_mem database manager configuration parameter specifies the maximum amount of memory that is allocated and reserved on a host for restart light recovery purposes. This message is returned when the amount of memory reserved for restart light purposes on a host is not large enough for optimal recovery performance.	Optional: To improve recovery performance, increase the value of the following database manager configuration parameters: RSTRT_LIGHT_MEM INSTANCE_MEMORY
ADM6010I	Rebalance for table space `tsname` (ID `tsid`) has been suspended.	The rebalance operation for the table space has been manually suspended using the ALTER TABLESPACE REBALANCE SUSPEND statement.	Manually resume the table space rebalance operation by running the following statement: ALTER TABLESPACE tablespace-name REBALANCE RESUME
ADM6011E	Write operations could not be suspended or resumed on this DB2 member because the database is in the process of shutting down or stopping, or the database is quiesced.	You can suspend and resume write operations for a database using the SET WRITE command or the db2SetWriteForDB API. In a DB2 pureScale environment, when you execute the SET WRITE command or call the db2SetWriteForDB API on any member, write operations are suspended or resumed on all members in the DB2 cluster. Write operations can be successfully suspend or resumed only when the database is either active or stopped. This message is returned when an attempt is made to suspend or resume write operations for a database that is neither active nor stopped. For example, this message can be returned when the SET WRITE command is executed in the following kinds of scenarios: The STOP DATABASE command has been executed for the database but the database has not completely stopped. The QUIESCE DATABASE command has been executed. The database encountered an error and is entering crash recovery. This message is returned in DB2 pureScale environments only. Specifically, this message is printed to the administration notification log for the member that detected the problem with the status of the database.	To resolve the problem that is preventing the SET WRITE command from succeeding on the member that is reporting this error, wait until the database makes the transition into being either active or stopped. After resolving the problem on this member, review the administration notification log on other members in the DB2 cluster.
ADM6012W	The total combined maximum number of authorization IDs that can be specified in both of the DB2_HI_PRI_PREFETCH_AUTHID and DB2_LO_PRI_PREFETCH_AUTHID registry variables `maxAuthIds` has been surpassed. Ensure that no more than this specified number of authorization IDs is specified by removing authorization IDs from one or both of the registry variables. The changes made will not take effect until the instance is restarted.
ADM6013W	Authorization ID `authId` was specified multiple times in either one or both of the DB2_HI_PRI_PREFETCH_AUTHID and DB2_LO_PR_PREFETCH_AUTHID registry variables. As a result, the highest priority was chosen for this authorization ID. If this behaviour is undesirable, it is necessary to set the registry variables accordingly ensuring that there are no duplicate authorization IDs among them. The changes made will not take effect until the instance is restarted.
ADM6014E	Write operations could not be suspended or resumed on this DB2 member because one or more table spaces are not in NORMAL state.	You can suspend and resume write operations for a database using the SET WRITE command or the db2SetWriteForDB API. In a DB2 pureScale environment, when you execute the SET WRITE command or call the db2SetWriteForDB API on any member, write operations are suspended or resumed on all members in the DB2 cluster. Write operations can be successfully suspend or resumed only when all table spaces in the database are in the NORMAL state. This message is returned in DB2 pureScale environments only. Specifically, this message is printed to the administration notification log for the member that detected the problem with the state of the table spaces.	To resolve the problem that is preventing the SET WRITE command from succeeding on the DB2 member that is reporting this error, perform the following steps: Identify which table spaces are not in NORMAL state using the MON_GET_TABLESPACE table function. The TBSP_STATE column lists the table space state. Change any table spaces in the database that are not in a NORMAL state into a NORMAL state by performing the required troubleshooting steps. After resolving the problem on this member, review the administration notification log on other members in the DB2 cluster.
ADM6015E	Write operations could not be suspended on this DB2 member because an internal error was encountered while database logging was being suspended.	You can suspend and resume write operations for a database using the SET WRITE command or the db2SetWriteForDB API. In a DB2 pureScale environment, when you execute the SET WRITE command or call the db2SetWriteForDB API on any member, write operations are suspended or resumed on all members in the DB2 cluster. This message is returned in DB2 pureScale environments only. Specifically, this message is printed to the administration notification log for the member that detected the internal problem processing the suspend operation.	To resolve the problem that is preventing the SET WRITE command from succeeding on the DB2 member that is reporting this error, perform the following troubleshooting steps: Collect additional diagnostic information from the diagnostic (db2diag) log files on this member. Identify and resolve the root cause of the failure of the suspend operation using the additional diagnostic information from the db2diag log files. After resolving the problem on this member, review the administration notification log on other members in the DB2 cluster.
ADM6016E	Write operations could not be resumed on this DB2 member because an internal error was encountered while database logging was being resumed.	You can suspend and resume write operations for a database using the SET WRITE command or the db2SetWriteForDB API. In a DB2 pureScale environment, when you execute the SET WRITE command or call the db2SetWriteForDB API on any member, write operations are suspended or resumed on all members in the DB2 cluster. This message is returned in DB2 pureScale environments only. Specifically, this message is printed to the administration notification log for the member that detected the internal problem processing the resume operation.	To resolve the problem that is preventing the SET WRITE command from succeeding on the DB2 member that is reporting this error, perform the following troubleshooting steps: Collect additional diagnostic information from the diagnostic (db2diag) log files on this member. Identify and resolve the root cause of the failure of the resume operation using the additional diagnostic information from the db2diag log files. After resolving the problem on this member, review the administration notification log on other members in the DB2 cluster.
ADM6017E	The following table space is full. Table space name: `table-space-name`. Table space identifier: `table-space-ID`. Container path: `container-path`. Container identifier: `container-ID`.	This message can be returned for many different reasons, including the following reasons: The underlying file system is full. The maximum allowed space usage for the file system has been reached. User limits on maximum file size have been reached. User limits on maximum number of open files have been reached.	Review information in diagnostic logs to determine which limits have been reached. Depending on the limits that were reached, free the necessary resources. For example, free memory, allocate more memory, or close open files.
ADM6018I	Unmounting filesystem at `directory-path`.
ADM6019E	All pages in buffer pool `bpname` (ID `bpid`) are in use. Refer to the documentation for SQLCODE -1218.
ADM6020I	Leaving mounted filesystem used for `contPath`.
ADM6021I	Multi-page file allocation is not currently enabled. Disabling it has no effect.
ADM6022W	Asynchronous drop of a temporary table failed. The resources associated with this table will not be freed until next database startup. You are advised to restart the database for this reason. You are also advised to contact IBM support to determine the reason for the failure.
ADM6023I	The table space `tablespaceName` (ID `tablespaceID`) is in state `tablespaceState`. The table space cannot be accessed. Refer to the documentation for SQLCODE -290.
ADM6024C	The database cannot be restarted. Database name: `database-name`.	The database cannot be restarted because write operations for the database are suspended or are being suspended.	To restart the database if the database write operations are suspended, specify the RESTART DATABASE command with the WRITE RESUME parameter. To restart the database if the database write operations are being suspended, wait until the SET WRITE SUSPEND operation that is being processed completes, then reissue the RESTART DATABASE command with the WRITE RESUME parameter.
ADM6025I	The table space `tsname` (ID `tsid`) is in state `state`. `operation` is not possible. Refer to the documentation for SQLCODE -290.
ADM6026E	Write operations could not be suspended or resumed on this DB2 member because an internal error occurred during the suspend or resume process.	You can suspend and resume write operations for a database using the SET WRITE command or the db2SetWriteForDB API. In a DB2 pureScale environment, when you execute the SET WRITE command or call the db2SetWriteForDB API on any member, write operations are suspended or resumed on all members in the DB2 cluster. This message is returned in DB2 pureScale environments only. Specifically, this message is printed to the administration notification log for the member that detected the internal problem processing the suspend or resume operation.	To resolve the problem that is preventing the SET WRITE command from succeeding on the DB2 member that is reporting this error, perform the following troubleshooting steps: Collect additional diagnostic information from the diagnostic (db2diag) log files on this member. Identify and resolve the root cause of the failure of the suspend or resume operation using the additional diagnostic information from the db2diag log files. After resolving the problem on this member, review the administration notification log on other members in the DB2 cluster.
ADM6027E	Error writing page `page-number` from table space `tbspace-id` for object `object-id` (writing to offset `offset` of container `container-path`). The operation did not complete.	The database manager was not able to complete the operation, but the database remains accessible. This might indicate a serious problem that could result in a future outage.	Investigate the hardware such as disk, controllers, and network, and the file system involved in accessing the container. If the problem is being caused by errors in the DB2 data, contact DB2 Support for guidance through the proper corrective actions.
ADM6028W	The registry variable setting `regvarstr` was ignored because of an out of memory condition that did not permit the processing of the registry variable setting.
ADM6029W	The registry variable setting (`regvarstr`) was ignored because the specified setting is invalid.
ADM6030E	Extents in the following table space have not been completely moved: `table-space-name`. Table space ID: `table-space-id`. Reason code: `reason-code`.	You can reclaim unused extents in a given table space by issuing the ALTER TABLESPACE statement with the REDUCE clause. The ALTER TABLESPACE statement starts an asynchronous extent movement operation and then the statement immediately returns successfully. The outcome of the asynchronous extent movement operation will be logged in messages, such as this message, in the administration notification log. This message is returned when an asynchronous extent movement operation failed. The reason code indicates the reason for the failure: 1 Another utility attempted to work with the table space and interrupted the extent movement. 2 Some extents are in "pending delete" state, which is preventing the movement of the high water mark. 3 Some extents were moved, but there is not enough free space in the table space to move the remaining extents. 4 The table space is in an incompatible state.	Respond to this message according to the reason code: 1 Monitor the state of the table space by using the MON_GET_TABLESPACE table function, and then perform the extent movement when another utility cannot interrupt the move operation. 2 Monitor the extents that are in pending delete state by using the MON_GET_TABLESPACE table function or by using the db2pd utility with the -tablespace parameter. Wait for the extents that are in pending delete state to be deleted, and then perform the extent movement operation. 3 No action is required. 4 Monitor the state of the table space by using the MON_GET_TABLESPACE table function, and then perform the extent movement when the table space is in a state that allows extent movement operations.
ADM6031W	EXTENDED STORAGE was configured for use with buffer pool `bpname` (ID `bpid`) but this configuration will be ignored because AWE is enabled for the database. EXTENDED STORAGE should be disabled and buffer pools should be configured not to use it.
ADM6034W	EXTENDED STORAGE was configured for use with buffer pool `bpname` (ID `bpid`) but this configuration will be ignored because the DB2_OVERRIDE_BPF registry variable is set. This registry variable is only meant to be used under the direction of IBM support.
ADM6035W	Scattered read could not be used because the registry variable DB2NTNOCACHE was not set. Set the DB2NTNOCACHE registry variable to enable scattered read.
ADM6036W	EXTENDED STORAGE is being used for multiple page sizes. Performance may not be optimal. Refer to the documentation for more information regarding the use of EXTENDED STORAGE.
ADM6037W	Container `path` was created to be `userBytes` KB in size on a device that is `userBytes` KB in size. Extra storage will be wasted. The container can be extended to use the wasted space by using ALTER TABLESPACE.
ADM6038E	Unable to perform an operation on container `path` because it does not exist in table space `tsname` (ID `tsid`). Refer to the documentation for SQLCODE -298.
ADM6039E	Invalid stripe set `sset` specified in ALTER TABLESPACE for table space `tsname` (ID `tsid`). Maximum stripe set in table space is `maxsset`.
ADM6040E	Invalid container size specified for container `contpath`. The number of pages specified for use is too large. Refer to the documentation for SQLCODE -1422.
ADM6041E	A table space operation failed because the resulting size of the table space would have exceeded the defined maximum size for the table space. Table space name: `table-space-name`. Table space identifier: `table-space-id`. Defined maximum size: `max-size`.	Rows of table data are organized into blocks called pages. For database-managed spaces (DMS), temporary DMS and nontemporary automatic storage table spaces, the page size you choose for your database using the PAGESIZE database configuration parameter determines the upper limit for the table space size. This message is returned when a table space operation on a REGULAR or USER TEMPORARY DMS table space causes the size of the table space to increase beyond the defined maximum allowed size, as determined by the PAGESIZE database configuration parameter.	Respond to this error in one of the following ways: Increase the maximum allowable size of the table space using the ALTER TABLESPACE statement with the MAXSIZE clause or the EXTEND clause, and then execute the table space operation again. Modify the table space operation so that it does not increase the size of the table space beyond the maximum allowed size, as determined by the PAGESIZE database configuration parameter, and then execute the table space operation again.
ADM6042E	An operation for table space `tsname` (ID `tsid`) was not successful because the size of the current table space is too big. The size of a REGULAR table space is limited to 0x0100 0000 (16777216) pages while the size of LARGE and TEMPORARY table spaces are limited to 0x7FFF FEFF (2147483391) pages. Refer to the documentation for SQLCODE -1139.
ADM6043W	The registry variable DB2_NO_MPFA_FOR_NEW_DB is set to an invalid value (`regVarVal`). As a result, the newly created database will have multi-page file allocation enabled. If this is not the desired result, set the DB2_NO_MPFA_FOR_NEW_DB registry variable to YES and recreate the database. To disable multi-page file allocation for all newly created databases, set the DB2_NO_MPFA_FOR_NEW_DB registry variable to YES.
ADM6044E	The DMS table space `tsname` (ID `tsid`) is full. If this is an autoresize or automatic storage DMS tablespace, the maximum table space size may have been reached or the existing containers or storage paths cannot grow any more. Additional space can be added to the table space by either adding new containers or extending existing ones using the ALTER TABLESPACE SQL statement. If this is an autoresize or automatic storage DMS table space, additional space can be added by adding containers to an autoresize table space or by adding new storage paths to the storage group it is using.
ADM6045I	The database is no longer in the WRITE SUSPEND state. Database name: `database-name`.	The WRITE SUSPEND state has been removed because write operations were resumed for the database by either the db2DatabaseRestart API or the RESTART DATABASE command with the WRITE RESUME parameter.	No user action is required.
ADM6046I	Multi-page file allocation already enabled. Enabling it again has no effect.
ADM6047W	The table space `tsname` ( ID `tsid`) is in the DROP_PENDING state. The table space will be kept OFFLINE. The table space state is `state`. This table space is unusable and should be dropped.
ADM6048I	The table space `tsname` (ID `tsid`), which was previously OFFLINE has been brought back ONLINE. The table space state is `state`.
ADM6049E	The database cannot be restarted because one or more table spaces cannot be brought online. To restart the database specify the "DROP PENDING TABLESPACES" option on the RESTART DATABASE command. Putting a table space into the drop pending state means that no further access to the table space will be allowed. The contents of the table space will be inaccessible throughout the remainder of the life of the table space; and the only operation that will be allowed on that table space is "DROP TABLE SPACE". There is no way in which it can be brought back. It is important that you consider the consequences of this action as data can be lost as a result. Before proceeding consult the documentation and contact IBM support if necessary. The table spaces to specify in the DROP PENDING TABLESPACES list are: `tsnames`.
ADM6050W	The ALTER BUFFERPOOL statement for buffer pool `bpname` (ID `bpid`) was successful but could not be performed immediately because of insufficient memory. The change will take effect on the next database startup. Refer to the documentation for SQLCODE 20189.
ADM6051E	The REORG command failed during RESTART DATABASE (crash recovery).	An index or index partition cannot be recreated because the associated table or data partition is in a table space that is in the DROP_PENDING state.	Set the INDEXREC database configuration parameter to "ACCESS" to delay index recreation until RESTART DATABASE completes.
ADM6052E	Invalid container size specified for container `contpath` in the CREATE TABLESPACE or ALTER TABLESPACE statement. The number of pages specified for use is too small.	You can specify the size of database managed space (DMS) table space containers when you create the table space using the CREATE TABLESPACE command. You can also change the size of DMS table space containers using the ALTER TABLESPACE command. This message is returned when the specified number of pages is too small, when compared to the value of EXTENTSIZE that was specified when the table space was created.	If you are executing the CREATE TABLESPACE statement, execute the statement again, specifying a value for the container size that is at least twice as large as the value specified for EXTENTSIZE. If you are executing the ALTER TABLESPACE statement, execute the statement again, specifying a value for the container size that is at least twice as large as the value for EXTENTSIZE that was specified when the table was created.
ADM6053W	The CREATE BUFFERPOOL statement for buffer pool `bpname` (ID `bpid`) could not be performed immediately because not enough free memory existed in the database shared memory. The bufferpool will be created on the next database restart. Refer to the documentation for SQLCODE 20189.
ADM6054I	DB2DART encountered table space `tsname` (ID `tsid`) which is currently not accessible. Since DB2DART is a diagnostic utility it will continue working on this table space.
ADM6055I	Page `pagenum` was requested from table space `tsname` (ID `tsid`) but is not yet available because a rebalance which is in progress on this table space has not yet made that space useable. The requestor will wait for the page to become available.
ADM6056I	Prefetch queue full has been encountered. A prefetch request has not been queued as a result and performance will not be optimal. Reconsider the prefetcher configuration (NUM_IOSERVERS, PREFETCHSIZE) and number of containers in each table space.
ADM6057I	Prefetch queue full has been encountered. Agent will wait for space to free up on the queue and thus performance will not be optimal. Reconsider the prefetcher configuration (NUM_IOSERVERS, PREFETCHSIZE) and number of containers in each table space.
ADM6058I	Rebalancer for table space `tsname` (ID `tsid`) was started.
ADM6059I	Rebalancer for table space `tsname` (ID `tsid`) was restarted.
ADM6060I	The rebalancer utility started successfully for table space `tsname` (ID `tsid`) but due to an out of memory condition the ability to throttle the execution of this utility has been disabled. Restarting the instance may resolve the memory issue and will allow throttling to be enabled.
ADM6061I	Rebalance for table space `tsname` (ID `tsid`) stopping. The last extent moved by the rebalance was `lastext`.
ADM6062I	Rebalance for table space `tsname` (ID `tsid`) has been completed.
ADM6063I	Rebalance for table space `tsname` (ID `tsid`) has been paused.
ADM6064I	Rollforward is waiting on rebalance of table space `tsname` (ID `tsid`) to complete.
ADM6065I	An attempt was made to remove the OFFLINE state from table space `tsname` (ID `tsid`) but it was not offline. This command will be ignored. The table space state is `tsstate`.
ADM6066I	An attempt was made to remove the OFFLINE state from table space `tsname` (ID `tsid`) but the action was not successful and so the table space will remain in this state. The table space state is `tsstate`. Refer to the documentation for SQLCODE -293.
ADM6069W	Buffer pool `bpname` (ID `bpid`) has a NUMBLOCKPAGES value of `oldNumBlockPages` which exceeds the maximum supported value for a buffer pool of this size. The NUMBLOCKPAGES value for this buffer pool has been reduced to `newNumBlockPages` for its current activation. The value of NUMBLOCKPAGES can be permanently changed by using the ALTER BUFFERPOOL SQL statement.
ADM6070W	Buffer pool `bpname` (ID `bpid`) has a NUMBLOCKPAGES value of `numBlockPages`. This value is smaller than the smallest allowable value for NUMBLOCKPAGES which is the BLOCKSIZE of `blockSize`. As a result the buffer pool will not be made block based for its current activation. The value for NUMBLOCKPAGES can be permanently changed by using ALTER BUFFERPOOL SQL statement.
ADM6071I	The maximum number of pinned pages allowed concurrently was reached in buffer pool `bpname` (ID `bpid`). As a result performance may not be optimal. Increasing the SORTHEAP database configuration parameter may reduce the chances of this condition occurring in the future.
ADM6072W	Disk full was encountered when writing out a temporary page from buffer pool `bpname` (ID `bpid`). The buffer pool cannot be decreased in size until all necessary pages have been written to disk. Refer to previous messages in the administration notification log for details regarding the disk full condition. The database manager will continue to retry writing this page to disk until the disk full condition is resolved.
ADM6073W	The table space `tsname` (ID `tsid`) is configured to use buffer pool ID `ondiskBP`, but this buffer pool is not active at this time. In the interim the table space will use buffer pool ID `RTBP`. The inactive buffer pool should become available at next database startup provided that the required memory is available.
ADM6074I	The SET WRITE SUSPEND command had no effect because the specified database is already in the WRITE SUSPENDED state. Database name: `database-name`.	An attempt was made to suspend write operations on the specified database, but this database is already in the WRITE SUSPENDED state.	No user action is required.
ADM6075W	The database has been placed in the WRITE SUSPENDED state. Database name: `database-name`.	You can suspend I/O write operations for a database by calling the SET WRITE SUSPEND command or by using the db2SetWriteForDB API. This message is returned when a database has been placed in WRITE SUSPENDED state.	No user action is required. Optional: To move the database out of WRITE SUSPENDED state, issue a SET WRITE RESUME command or a RESTART DATABASE command with the WRITE RESUME parameter.
ADM6076W	The database is no longer in the WRITE SUSPEND state. Database name: `database-name`.	The database, which was previously in the WRITE SUSPEND state, is no longer in that state. Write operations have resumed for the database.	No user action is required.
ADM6077I	The database is not in the WRITE SUSPEND state. Database name: `database-name`.	An attempt was made to remove the database from the WRITE SUSPEND state, but the database is not in the WRITE SUSPEND state. Specifying WRITE RESUME has no effect.	If the command that failed is the SET WRITE RESUME command, no user action is required. If the command that failed is the RESTART DATABASE command with the WRITE RESUME parameter, issue the RESTART DATABASE command without the WRITE RESUME parameter. If this fails and the database is not in the WRITE SUSPEND state: Wait until all SET WRITE SUSPEND operations are completed. Reissue the RESTART DATABASE command with the WRITE RESUME parameter.
ADM6078W	The following table spaces were specified on the RESTART DATABASE command to be placed in the DROP_PENDING state: `tsnames`.
ADM6079E	The table space `tsname` (ID `tsid`), was in the ROLLFORWARD_IN_PROGRESS state but can no longer be accessed. The table space has been taken offline and put into the RESTORE_PENDING state.
ADM6080E	The table space `tsname` (ID `tsid`), was put OFFLINE and in ROLLFORWARD_PENDING. Tablespace state is `tsstate`.
ADM6081W	The table space `tsname` (ID `tsid`) is in the OFFLINE state and is not accessible. The table space state is `tsstate`. Refer to the documentation for SQLCODE -293.
ADM6082W	The current transaction is attempting to do work that is not allowed to fail. However, this work could not be completed as there are no free pages available in the buffer pool. Further attempts will be made to find free pages but in the future this situation can be avoided by increasing the size of buffer pool `bpname` (ID `bpid`).
ADM6083E	An error occurred while redoing an alter tablespace operation against table space `tsname` (ID `tsid`) This error will be temporarily ignored while the remainder of the transaction is replayed. If the alter operation is eventually rolled back then the error will be discarded. However, if the operation is committed then this error will be returned, stopping recovery against the table space.
ADM6084E	An attempt is being made to commit an alter operation against table space `tsname` (ID `tsid`) but a previous error is preventing this from being done. Resolve the original error before attempting the recovery again.
ADM6085I	An out of memory condition was encountered while resizing buffer pool hash buckets. As a result of this condition, performance may not be optimal. It is recommended that database be shut down and started again so that the buffer pool can start up with an optimally sized hash table.
ADM6086W	The attempt to acquire and reset the phantom quiesce state for table space `tsname` (ID `tsid`) did not change the state even though the command returned successfully. The authorization ID of the current user does not match the quiescer authorization ID and these must be the same to successfully acquire and reset a phantom quiesce. Determine the correct quiescer authorization ID by taking a table space snapshot and retry the quiesce reset command using that ID.
ADM6087I	An attempt has been made to reset the quiesce state of table space `tsname` (ID `tsid`) but the table space is not currently in the quiesce state.
ADM6088W	Due to an out of memory condition, the current agent is unable to monitor table space `tsname` (ID `tsid`). As a result, monitor output may be unreliable. Increase the DBHEAP configuration parameter to avoid this problem in the future.
ADM6089I	The rebalancer utility started successfully for table space `tsname` (ID `tsid`), but due to an out of memory condition the progress monitor service is disabled. Restarting the instance may resolve the memory issue and will enable the progress monitor service again.
ADM6090W	A file handle limit, system wide or process/thread specific, was reached by a page cleaner. The page cleaner will respond by closing all file handles opened by the cleaner that received the error condition. This error will only be logged once per page cleaner that receives this error. Recommended actions are: check operating system file handle limits, then reduce the value of the maxfilop configuration parameter. You must restart the database (database deactivation or last connection termination), for any changes to these parameters to take effect.
ADM6091W	An attempt was made to automatically increase the size of auto-resize table space `tsname` (ID `tsid`) but the table space's maximum size (`maxsize` bytes) has been reached. Note that this value may be lower than expected due to uncommitted ALTER TABLESPACE statements. Also, because the database manager attempts to extend containers at the same rate and extending must occur in a multiple of extents, it may not actually be possible to reach the maximum size exactly. In this case, the current size (`currentsize` bytes) will have a smaller value than the maximum size. The MAXSIZE clause of the ALTER TABLESPACE statement can be used to increase the maximum size for this table space.
ADM6092W	An attempt was made to automatically increase the size of automatic storage table space `tsname` (ID `tsid`). This failed because all of the storage paths associated with the storage group are full or they do not have enough space to create a new container on them. New storage paths can be added to the storage group using the ALTER STOGROUP statement.
ADM6093W	An attempt was made to automatically extend container `container` in auto-resize table space `tsname` (ID `tsid`) but there is no space on the filesystem. As a result, the table space cannot increase in size any further. One way to resolve this is to make more space available on the filesystem. Alternately, a new stripe set can be added to the table space using the BEGIN NEW STRIPE SET clause of the ALTER TABLESPACE statement. When subsequent attempts to auto-resize the table space occur, only those newly added containers will be extended and the existing ones will remain as-is.
ADM6094W	A RESTORE DATABASE or ROLLFORWARD DATABASE command resulted in storage changes for auto-resize table space `tsname` (ID `tsid`). The effect is that the table space's maximum size had to be increased from `oldmaxsize` bytes to `newmaxsize` bytes on this partition. If there are multiple database partitions then the maximum size for the table space is now inconsistent between the database partitions. This will not cause any problems but it may not be desired. To resolve this use the ALTER TABLESPACE statement to set a new MAXSIZE value that is greater than or equal to the current size for each of the database partitions. Alternately, use the MAXSIZE NONE option to indicate that there is no maximum size.
ADM6095W	A rollforward operation encountered a log record associated with the ADD STORAGE clause of the ALTER DATABASE statement or the ADD clause of the ALTER STOGROUP statement. However, this log record was not replayed because the storage paths associated with the database were redefined during the previous database restore and it is assumed that the full set of storage paths were defined at that point. As a result, storage path `storagepath` was not added to the database.
ADM6096W	The rollforward operation encountered a log record that is attempting to alter the maximum size for auto-resize table space `tsname` (ID `tsid`). While this was successful at run-time, a new container configuration has been established during the process of restoring and rolling forward the database or table space and this maximum size is less than the current size of the table space. The effect is that the table space's maximum size is being set to `currentsize` bytes instead of `maxsize` bytes. If there are multiple database partitions then the maximum size for the table space is now inconsistent between them. This will not cause any problems but it may not be desired. This can be resolved after the rollforward has completed by using the ALTER TABLESPACE statement to set a new MAXSIZE value that is greater than or equal to the current size for each of the database partitions. Alternately, use the MAXSIZE NONE option to indicate that there is no maximum size for the table space.
ADM6097I	Table space `tsname` (ID `tsid`) was successfully extended by `extend` bytes in a new stripe set.
ADM6098W	Table space `tsname` (ID `tsid`) could not be extended because th e container map became too complex.
ADM6099W	Table space `tsname` (ID `tsid`) has reached the maxiumum size (`maxsize` bytes) for a tablespace of this type and page size. To add more storage to the database, add a new table space.
ADM6100W	While attempting to autoresize table space `tsname` (ID `tsid`), container `cname` could not be grown.
ADM6101W	While attempting to extend table space `tsname` (ID `tsid`), there were less than `freebytes` bytes free on `path`. This space is reserved for use by the database manager or the operating system.
ADM6102I	Table space `tsname` (ID `tsid`) was successfully extended by `extend` bytes.
ADM6103W	Table `table-name` cannot allocate a new page because the index with identifier `index-id` does not yet support large RIDs. The table space in which this table resides was converted to a large table space via the CONVERT TO LARGE clause of the ALTER TABLESPACE statement. The table itself cannot support large RIDs until all previously existing indexes on the table have been reorganized or rebuilt to support large RIDs. The index(es) must be reorganized or rebuilt to support future growth of this table.	The indexes can be reorganized using the rebuild mode of the REORG INDEXES ALL FOR TABLE `table-name`command. For partitioned tables ALLOW NO ACCESS must be specified. Alternatively, the table can be reorganized (classic REORG, not INPLACE) which will not only rebuild all indexes, but will enable the table to support greater than 255 rows per page.
ADM6104W	Table space `tbspace-name` is being converted from REGULAR to LARGE. Indexes on tables in this table space must be reorganized or rebuilt to support large RIDs. The table space being converted can, following COMMIT, support a storage capacity larger than that of a regular table space. The maximum page number for a data page in a regular table space is 0x00FFFFFF. A table which is allocated a page number above 0x00FFFFFF must have support from the indexes on the table to support such a page number. Until the indexes on a table are reorganized or rebuilt to support such a page number, allocation of such a page number to the table will result in an error.	The documentation for the ALTER TABLESPACE statement in the SQL Reference specifies the best practices when using the CONVERT TO LARGE option. Please follow these recommendations to be pro-active in reorganizing or rebuilding all indexes on all tables in this table space to prevent possible future failures to grow the tables.
ADM6105E	The storage paths associated with this storage group are inconsistent between database partition `X` and database partition `Y`. The database manager attempts to keep the storage paths consistent across all database partitions but there is now a discrepancy. While the database continues to function, it is recommended that the storage paths be made consistent across all of the partitions in the database. This is accomplished by backing up the database on each partition (unless backup images already exist) and restoring them. The catalog partition should be restored first, specifying the list of paths that each partition should use (using the RESTORE REDIRECT and SET STOGROUP PATHS commands). If the database is recoverable then a rollforward needs to be done after the database is restored on every partition.
ADM6106E	Table space `name` (ID = `id`) could not be created during the rollforward operation. The most likely cause is that there is not enough space to create the containers associated with the table space. Connect to the database after the rollforward operation completes and use the SET TABLESPACE CONTAINERS command to assign containers to the table space. Then, issue another ROLLFORWARD DATABASE command to complete recovery of this table space.
ADM6107E	Automatic storage table space `name` (ID = `id`) could not be created during the rollforward operation. The most likely cause is that there is not enough space on the storage group's storage paths to create the `size` byte table space. If this is the case then make more space available on the existing storage paths or add new storage paths using the ALTER STOGROUP SQL statement before issuing another ROLLFORWARD DATABASE command to recover this table space.
ADM6108I	A request was made to drop storage path `storage-path` from the storage group. Multiple instances of this path exist on this database partition and all instances of it are being dropped.	When a storage group on a database partition contains multiple instances of the specified storage path, a request to drop this storage path, using the ALTER STOGROUP statement, results in the dropping of all of the instances of this storage path in that storage group.	No response is necessary.
ADM6109I	A request was made to drop storage path `storage-path` from the storage group. The storage path will be dropped immediately.	No table space uses the storage path on this database partition. The storage path is being dropped immediately.	No response is necessary.
ADM6110I	A request was made to drop storage path `storage-path` from the storage group. The storage path will not be removed from this database partition until all containers residing on it have been dropped.	One or more automatic storage table spaces have containers on this storage path on this database partition. Therefore, the storage path is being placed into the "drop pending" state.	One of the following actions: Drop and recreate temporary automatic storage table spaces. Use the REBALANCE clause of the ALTER TABLESPACE statement to move data from the storage paths that are in the "drop pending" state. Drop table spaces that you do not need.
ADM6111I	No table space containers reside on storage path `storage-path` on this database partition. The storage path is in the "drop pending" state and will be removed from this database partition.	Because the storage path does not contain any data, it will be dropped immediately.	No response is necessary.
ADM6112I	Storage path `storage-path` was added to the storage group. The new storage path will not be used automatically.	Temporary, regular, or large automatic storage table spaces cannot automatically use new storage paths.	If you want temporary table spaces to use the new storage path, the database must be stopped and started again: If the database was explicitly activated, first deactivate the database by using the DEACTIVATE DATABASE command, then reactivate it by using the ACTIVATE DATABASE command. If the database was not explicitly activated, disconnect or force all users from the database and then connect to the database again. When the database is started, the temporary table spaces will use the new storage path. Alternatively, you can drop the temporary table space by using the DROP TABLESPACE statement, then recreate it by using the CREATE TABLESPACE statement. When it is recreated, the temporary table space will use the new storage path. Regular and large table spaces do not use a new storage path until a "disk full" condition occurs for an existing container. If you want to stripe the table space over all the storage paths (including new paths), use the ALTER TABLESPACE statement with the REBALANCE clause. This statement creates containers for each of the table space stripe sets, one for each path that does not already contain a container. You can determine the list of automatic storage table spaces in the database by issuing the following SQL statement: SELECT TBSP_NAME, TBSP_CONTENT_TYPE FROM SYSIBMADM.SNAPTBSP WHERE TBSP_USING_AUTO_STORAGE = 1 ORDER BY TBSP_ID
ADM6113I	Table space `tablespace` exceeded its maximum size.	A rebalance operation added data from one or more dropped storage paths to this table space. The rebalance operation was successful; however, the table space has exceeded its maximum size.	No user response is required.
ADM6500W	The connection for the DATALINK file server `fileServer` has failed. The server is blocked.
ADM6501W	The connection for the DATALINK file server `fileServer` has failed to restart.
ADM6502W	The connection for the DATALINK file server `fileServer` has failed.
ADM6510W	The DATALINK file server `fileServer` has not been registered.
ADM6511W	The DATALINK file server `fileServer` is not active.
ADM6512W	The database manager is unable to read from the DATALINK configuration file.
ADM6513W	The database manager is unable to create the DATALINK configuration file `fileName`.
ADM6514W	An error has occurred while the database manager was writing to the DATALINK configuration file.
ADM6515W	An error has occurred while the database manager was closing the DATALINK configuration file.
ADM6516W	The database manager is unable to open the DATALINK configuration file `fileName`.
ADM7000W	An invalid SEARCH discovery protocol, `fileName`, was specified in the DISCOVER_COMM registry variable.
ADM7001E	The DB2 function sqloinstancepath has failed. The instance path was not set. If you are on UNIX, check the DB2INSTANCE registry variable. If you are on Windows, check the DB2INSTANCE, DB2PATH, and DB2INSTPROF registry variables.
ADM7004E	An invalid value (`value`) was specified for the DB2COMM registry variable.
ADM7005W	The DISCOVER mode was set to SEARCH. However, the DISCOVER_COMM registry variable was not configured with any protocols.
ADM7006E	The SVCENAME DBM configuration parameter was not configured. Update the SVCENAME configuration parameter using the service name defined in the TCP/IP services file.
ADM7007E	The SVCENAME DBM configuration parameter, `socketAddress`, is configured with a port or a service name. When it is configured with a service name, the TCP/IP services files is used to map the service name to a port number. The port specified in this field is being used by another process. Resolve this problem by either deleting the process using the port or use another port.
ADM7008W	The DB2TCPCONNMGRS registry variable value, `userValue`, is invalid. A valid value is from 1 to 8. A default DB2TCPCONNMGRS value of `defaultValue` has been used.
ADM7009E	An error was encountered in the `protocolTCPIP` protocol support. A possible cause is that the maximum number of agents has been exceeded.
ADM7011E	The Sync Point Manager does not support the version of Microsoft SNA Server installed on this machine. Minimum requirement is Microsoft SNA Server V4 Service Pack 3.
ADM7012E	The SSL_SVR_KEYDB DBM configuration parameter was not configured. Update the SSL_SVR_KEYDB configuration parameter.
ADM7013E	The SSL_SVR_STASH DBM configuration parameter was not configured. Update the SSL_SVR_STASH configuration parameter.
ADM7014E	The SSL_SVCENAME DBM configuration parameter was not configured. Update the SSL_SVCENAME configuration parameter using the service name defined in the TCP/IP services file.
ADM7015I	The connection is using SSL version `version` and cipher spec `cipherspec`.
ADM7016I	The allowed SSLv3 cipher specs are `cipherspecs`. The allowed TLSv1 cipher specs are `cipherspecs`.
ADM7017E	TCP/IP and SSL cannot be configured on the same port number.
ADM7500W	A request was made to quiesce an instance with the following quiesce mode: `quiesce-mode`	You can force off all users of a database manager instance and put the instance and all databases in the instance into quiesce mode using the QUIESCE INSTANCE or the START DATABASE MANAGER commands (or the db2InstanceQuiece or db2InstanceStart APIs). This message is returned to acknowledge and log the quiesce mode of the request to quiesce an instance.	No user response is required.
ADM7501W	Instance quiesce request has completed successfully.
ADM7502E	Instance quiesce request has failed. The SQLCODE is `SQLCODE`.
ADM7503W	Instance unquiesce request has completed successfully.
ADM7504W	Instance unquiesce has been requested.
ADM7505E	Instance unquiesce request has failed. The SQLCODE is `SQLCODE`.
ADM7506W	A request was made to quiesce a database with the following quiesce mode: `quiesce-mode`	The database was requested to be put into quiesce mode using the QUIESCE DATABASE command or the db2DatabaseQuiesce API. This message is returned to acknowledge and log the quiesce mode of the request to quiesce a database.	No user response is required.
ADM7507W	Database quiesce request has completed successfully.
ADM7508E	Database quiesce request has failed. The SQLCODE is `SQLCODE`.
ADM7509W	Database unquiesce request has completed successfully.
ADM7510W	Database unquiesce has been requested.
ADM7511E	Database unquiesce request has failed. The SQLCODE is `SQLCODE`.
ADM7512E	A transaction resynchronization error has occurred, contact IBM Support for assistance.
ADM7513W	Database manager has started.
ADM7514W	Database manager has stopped.
ADM7515W	The concentrator has been enabled without directory caching support which may result in a performance penalty. To correct this problem, enable directory caching in the database manager configuration.	Directory caching is a feature with relatively low overhead that is enabled by default in the engine. There are only a few valid reasons why a user may want to disable it. The concentrator configurations are particularly sensitive to having directory caching turned off because the dispatcher processes, which are the bottleneck for concentrator, could be potentially required to go to disk with every new connection.	Enable directory caching, or run in a non-concentrator configuration.
ADM7516N	During automatic restart, DB2 cluster services failed to recover the database named `database-name` on the following DB2 member: `member-ID`	In a DB2 pureScale environment, if a database member fails, member crash recovery is automatically initiated for that member. In addition, if both cluster caching facilities fail at the same time, group crash recovery is automatically initiated. During member crash recovery, no connections are allowed against the database through that member. Attempted connections to the named database through the named DB2 member will fail until the database has been successfully recovered. This message is returned when DB2 cluster services fails to recover a database for a failed member during an automatic restart. An ALERT is set for the member on the host where the recovery failed.	Collect additional, related troubleshooting and diagnostic information by searching in the db2diag log files for this message identifier. Determine whether the database is in a backup pending, rollforward pending, or restore pending state by running the GET DB CONFIG command If the database is in a pending state, take the required actions to move the database out of the pending state. Manually recover the failed database by running the RESTART DATABASE command. The alert will automatically be cleared when the database is successfully recovered.
ADM7517W	When the concentrator is enabled, the maximum number of applications per application group in the database `databaseName` will be limited to `maxApp`. To correct this problem, decrease the value of the APPGROUP_MEM_SZ configuration parameter.
ADM7518C	The database manager has shut down the following database because a severe error has occurred: `database-name`.	This error is returned when there is a sudden, severe problem that might compromise the integrity of data during database access. Here is one example of the kind of scenario that could cause this error to be returned: If a database object unexpectedly becomes inaccessible during a transaction, all write operations to the database logs would stop and all operations on this database would be shut down. The database would need to undergo crash recovery when it is reactivated.	Collect the following diagnostic information and then contact IBM software support using tools such as the db2support tool: Contents of the directory identified by the diagpath database manager configuration parameter including the contents of the FODC_ForceDBShutdown directory.
ADM7519W	The database manager could not allocate an agent. The SQLCODE is `SQLCODE`.
ADM7520E	Mount unmounted filesystem(s) has failed on node `db-partition-number`. Manual remount is required before retrying migration. Check `errorFile` and remount the filesystems before retrying migration.
ADM7521E	Unmount mounted filesystem(s) has failed on node `db-partition-number`. Remount the unmounted filesystem(s) and try the database migration again.
ADM7522E	Remount unmounted filesystem(s) to new mount points has failed on node `db-partition-number`. Restart database migration is needed.
ADM7523E	The database manager was unable to allocate the application group memory set. This will cause database activation to fail. Reduce the APPGROUP_MEM_SZ DB configuration parameter and retry.
ADM7524W	The database manager has increased the amount of memory that is allocated for restart light recovery purposes to the minimum required size that is needed for starting the DB2 idle process.	The current calculated restart light memory size is too small to allocate enough memory to start the DB2 idle process. The restart light memory size is calculated using the instance_memory configuration parameter and the rstrt_light_mem configuration parameter, which specifies a percentage of instance_memory. The restart light memory size must be greater than or equal to the minimum required restart light memory size. The DB2 idle process needs to be started for DB2START processing to succeed, so the restart light memory size has been increased to the minimum required size.	Check the db2diag.log to find the values for: calculated restart light memory size minimum required restart light memory size Check the current values of the instance_memory and rstrt_light_mem configuration parameters and increase one (or both) of them so that the calculated restart light memory size is greater than or equal to the minimum required restart light memory size.
ADM7525E	The following member was unable to access the secondary CF to initiate catch up: `member-id`. Member host name: `host-name`. Secondary CF host name: `CF-host-name`.	After a secondary cluster caching facility, also known as CF, is added, and after a secondary CF host computer is restarted, the secondary CF must go through a process to join the cluster. Specifically, when the first database connection is made after a secondary CF joins a cluster, the secondary CF copies information from the primary CF. This copying of information is known as "catch up", and while the secondary CF is copying data from the primary CF, the secondary CF is in CATCHUP state. This message is returned when the member that is processing the first database connection after a secondary CF joins a cluster cannot access the secondary CF to initiate the catch up process. Possible reasons that a member cannot initiate the catch up process for a secondary CF include the following reasons: Network errors, such as problems with RDMA, prevent the member from accessing the secondary CF The host on which the secondary CF is located is unavailable The secondary CF server processes are not running	Perform the following troubleshooting steps: Verify that the member `member-id` can access the host on which the secondary CF is located, `CF-host-name` using the ping utility, for example. Look for messages related to the secondary CF server processes in the following diagnostic files: cfdump.out* files cfdiag.log files core files Investigate whether there are any RDMA communication problems.
ADM7526E	The database activation failed because the secondary CF failed to allocate required structures.	The cluster caching facility, also known as CF, contains the following structures: Group Buffer Pool (GBP) CF Lock Manager (LOCK) Shared Communication Area (SCA) The size of each of these structures, GBP, SCA, and LOCK can be configured online. One reason that this failure can happen is that an invalid size was calculated for one or more of the structures of the secondary CF during database activation. When this error occurs, detailed diagnostic information about this error is printed in the diagnostic (db2diag) log files.	Collect detailed diagnostic information about this error from the db2diag log files. Correct the cause of the problem. Retry the database activation.
ADM7527E	The database activation failed because the secondary CF server had insufficient memory to allocate one or more required structures.	The cluster caching facility, also known as CF, contains the following structures: Group Buffer Pool (GBP) CF Lock Manager (LOCK) Shared Communication Area (SCA) The size of each of these structures, GBP, SCA, and LOCK can be configured online. One reason that this failure can happen is that non-DB2 applications on the secondary CF host used a large amount of memory while the secondary CF was allocating memory for structures.	Respond to this error by performing one or more of the following steps: If there are non-DB2 applications running on the secondary CF server host in addition to the secondary CF itself, ensure there is sufficient memory to handle the secondary CF workload before activating the secondary CF. For example, configure the amount of memory specified by the CF_MEM_SZ database manager parameter for the secondary CF to be as large as or larger than the value of CF_MEM_SZ on the primary CF. Configure the secondary CF to use less total memory by specifying a smaller size for the following database configuration parameters: CF_SCA_SZ CF_GBP_SZ CF_LOCK_SZ CF_DB_MEM_SZ CF_MEM_SZ
ADM7528N	The database manager started with fewer Host Channel Adapter Adapters (HCAs) than configured for the cluster caching facilities (CFs).	The database manager encountered a non-critical error when starting. Communication could not be established with one or more HCAs on a CF, however each cluster caching facility (CF) is connected by at least one HCA. With fewer HCAs the CF has less throughput capacity. There is also a greater risk of downtime due to the reduced redundancy.	Review cluster alerts by running 'db2cluster -cm -list -alert' to see which HCAs are not responding. Follow the corrective actions given by the alerts to rectify any reported problem.
ADM7529I	Cluster caching facility (CF) has stopped.	The CF has successfully stopped.	No response is required.
ADM7530W	An unexpected cluster caching facility (CF) error occurred. CF recovery will be attempted.	The CF stopped because of an unexpected error. The database manager will perform a cleanup and restart the CF.	To avoid receiving this message in the future, check the db2diag.log and the cfdiag.cfid.log files to see if there are any messages around the time of the recovery attempt.
ADM7531I	A CF changed state. CF: `identifier`. New state: `state`.	The indicated CF is now in the indicated state.	No response is required.
ADM7532E	Cluster caching facility (CF) with identifier `identifier` is now in ERROR state.	The indicated CF could not be restarted.	Resolve the problem and manually clear the alert. You can use the db2instance and db2cluster commands to help you with this. After the problem has been resolved, attempt to start the CF.
ADM7533I	Cluster caching facility (CF) has started.	The CF has successfully started.	No response is required.
ADM7534W	During database upgrade the rebind operation failed for one or more packages. Log file: `log-file`.	The REBINDALL option was specified on the UPGRADE DATABASE command to rebind all the packages during database upgrade. The database was upgraded successfully, however, one or more packages failed to rebind. The errors and the package names are recorded in the generated log file.	Resolve the source of the problem by following the actions indicated by the messages that are recorded in the generated log file. Rebind the packages using the db2rbind command.
ADM7535W	The UPGRADE DATABASE command failed to refresh the table space attributes in the catalog table. However the database was upgraded successfully.	In DB2 V10 some new attributes are added in the catalog tables for each table space in the database. The database upgrade process failed to initialize these new attributes with appropriate values. See the file db2diag.log to determine the cause of failure. The database performance may not be optimal until the table space attributes are properly initialized.	Resolve the errors that caused the initialization of the tablespace attributes to fail during database upgrade. Execute the DATABASE UPGRADE command again to initialize the table space attributes.
ADM7536I	The status of adapter `adapter-name` was found to be: `ONLINE-or-OFFLINE-status`.	This message is returned to show whether adapters are online or offline.	No response is required.
ADM7537I	The status of the following adapter changed. Adapter name: `adapter-name`. New status: `ONLINE-or-OFFLINE`. Number of adapters that are currently online: `number`. Host name: `host-name`.	The cluster caching facility (CF) monitors adapters to determine whether those adapters are online or offline. This message is returned when the CF detects that an adapter has changed from online to offline or from offline to online.	No response is required.
ADM7538E	The database upgrade operation completed successfully. However there are tables in the upgraded database that are in load pending state. These tables cannot be used by the upgraded database.	This message is returned if the database upgrade operation found that a previous LOAD attempt on one or more tables in the database did not complete successfully. These tables cannot be accessed in the upgraded database.	To find out what tables are in a load pending state run the following command: `select <tabname> from SYSIBMADM.ADMINTABINFO where load_status is not NULL` In the previous release environment, restart or terminate the failed LOAD operation by issuing the LOAD command with the RESTART or TERMINATE option. Reload the table by performing the following steps: Unload the table from the previous release database. Drop and recreate the table in the upgraded database. Reload the table in the upgraded database, using the data that was unloaded from the previous release database.
ADM7539I	The database manager has completed processing the topology change that resulted in a backup pending state.	The database manager has completed processing a topology change that resulted in the dropping of some members, or a configuration change between ESE and DB2 pureScale instances. In both cases, for those members that were in the previous member topology for the database but are not in the current member topology, this might have resulted in the deletion of files from those member database directories.	No action required.