ADSM V3R1 Messages

Part 2. Server Messages: Common and Platform Specific

 

Chapter 3. Database and Recovery Log (0130-0399)


Message numbers in range ANR0100-0120, and any with 9999 (with the exception of message ANR9999D) (See Chapter 7. "Server Operations (0900-0999, and 9999D)" for a description of message ANR9999D.) are not published in this manual. They are considered severe errors and should be recorded and included in a problem report when contacting the service representative.


ANR0130E diagnosticid: Server LOG space exhausted.
Explanation: There is no space to write data to the server recovery log.
System Action: The activity that generated this error fails.
User Response: To increase the amount of log space available to the server, an authorized administrator can add log volumes by using the DEFINE LOGVOLUME command, and extend the size of the log by using the EXTEND LOG command.


ANR0131E diagnosticid: Server DB space exhausted.
Explanation: There is no space to write data to the server database.
System Action: The activity that generated this error fails.
User Response: To increase the amount of database space available to the server, an authorized administrator can add database volumes by using the DEFINE DBVOLUME command, and extend the size of the database by using the EXTEND DB command.


ANR0132E diagnosticid: Memory allocation failed: object object name, size size.
Explanation: The server cannot obtain enough memory to create the object named.
System Action: The activity that generated this error fails.
User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory".


ANR0200I Recovery log assigned capacity is size megabytes.
Explanation: The amount of space allocated to the recovery log is shown.
System Action: None.
User Response: None.


ANR0201I Database assigned capacity is size megabytes.
Explanation: The amount of space allocated to the database is shown.
System Action: None.
User Response: None.


ANR0202W Database volume volume name varied offline due to excessive read errors.
Explanation: The database volume shown has been varied offline because too many read errors have been encountered.
System Action: If available, a mirrored copy of the volume is used.
User Response: Correct the cause of the read errors.


ANR0203W Database volume volume name varied offline due to excessive write errors.
Explanation: The database volume shown has been varied offline because too many write errors have been encountered.
System Action: If available, a mirrored copy of the volume is used.
User Response: Correct the cause of the write errors.


ANR0204W Recovery log volume volume name varied offline due to excessive read errors.
Explanation: The recovery log volume shown has been varied offline because too many read errors have been encountered.
System Action: If available, a mirrored copy of the volume is used.
User Response: Correct the cause of the read errors.


ANR0205W Recovery log volume volume name varied offline due to excessive write errors.
Explanation: The recovery log volume shown has been varied offline because too many write errors have been encountered.
System Action: If available, a mirrored copy of the volume is used.
User Response: Correct the cause of the write errors.


ANR0206W Partial write detected on database volume volume name, logical page logical page number (physical page physical page number).
Explanation: During a write of a database page, an error occurred so that the page was not completely written to disk.
System Action: The failed I/O operation is retried on a mirrored volume.
User Response: See accompanying messages for information about the volume in error.


ANR0207E Page address mismatch detected on database volume volume name, logical page logical page number (physical page physical page number); actual: logical page number.
Explanation: During a read of a database page, the page does not contain the expected page address.
System Action: The failed I/O operation is retried on a mirrored volume.
User Response: See accompanying messages for information about the volume in error.


ANR0208W Partial write detected on recovery log volume volume name, logical page logical page number (physical page physical page number).
Explanation: During a write of a recovery log page, an error occurs so that the page is not completely written to disk.
System Action: The failed I/O operation is retried on a mirrored volume.
User Response: See accompanying messages for information about the volume in error.


ANR0209E Page address mismatch detected on recovery log volume volume name, logical page logical page number (physical page physical page number); actual: logical page number.
Explanation: During a read of a recovery log page, the page does not contain the expected page address.
System Action: The failed I/O operation is retried on a mirrored volume.
User Response: See accompanying messages for information about the volume in error.


ANR0210S Inconsistency found in LVM data page page number - partial write detected.
Explanation: During a write of an LVM internal page, an error occurs so that the page is not completely written to disk.
System Action: The failed I/O operation is retried on a mirrored volume.
User Response: See accompanying messages for information about the volume in error.


ANR0211S Inconsistency found in LVM data page page number - page address mismatch (actual page number).
Explanation: During a read of an LVM internal page, the page does not contain the expected page address.
System Action: The failed I/O operation is retried on a mirrored volume.
User Response: See accompanying messages for information about the volume in error.


ANR0212E Unable to read disk definition file file specification.
Explanation: At startup, the server cannot read the indicated file in order to obtain a list of disk volumes to mount.
System Action: Server initialization fails.
User Response: Use a text editor to recreate the file; it should contain one line with the name of a single log or database volume. Then restart the server.


ANR0213W Unable to rewrite disk definition file.
Explanation: An error occurs trying to update the disk definition file.
System Action: None.
User Response: Attempt to determine the cause of the write error and correct it.


ANR0214W Database volume volume name is in the offline state - VARY ON required.
Explanation: At system startup, the server finds that the specified database volume is in the offline state.
System Action: The volume is not accessed.
User Response: Determine the reason for the volume being offline; if possible, vary it online.


ANR0215W Recovery log volume volume name is in the offline state - VARY ON required.
Explanation: At system startup, the server finds that the recovery log volume shown is in the offline state.
System Action: The volume is not accessed.
User Response: Determine the reason for the volume being offline; if possible, vary it online.


ANR0216I Database volume volume name is in the "stale" state - synchronization process started.
Explanation: At system startup, the server finds that the database volume shown is not synchronized.
System Action: A process is started to synchronize the volume.
User Response: None.


ANR0217I Recovery log volume volume name is in the "stale" state - synchronization process started.
Explanation: At system startup, the server finds that the recovery log volume shown is not synchronized.
System Action: A process is started to synchronize the volume.
User Response: None.


ANR0218I Unable to install database volume volume name - capacity must be at least 5 megabytes.
Explanation: An attempt has been made to add a database volume that is smaller than the server minimum.
System Action: The volume is not added.
User Response: Increase the size of the volume or supply another larger volume.


ANR0219I Unable to install recovery log volume volume name - capacity must be at least 5 megabytes.
Explanation: An attempt has been made to add a recovery log volume that is smaller than the server minimum.
System Action: The volume is not added.
User Response: Increase the size of the volume or supply another larger volume.


ANR0220I Synchronization of database volume volume name started as process process id.
Explanation: A background process was started to synchronize the contents of the database volume shown with its copy volume. The background process was assigned the process ID shown.
System Action: The background process starts to synchronize the volume and server operation continues.
User Response: The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command.


ANR0221I Synchronization of recovery log volume volume name started as process process id.
Explanation: A background process was started to synchronize the contents of the recovery log volume shown with its copy volume(s). The background process was assigned the process ID shown.
System Action: The background process starts to synchronize the volume and server operation continues.
User Response: The administrator may query the status of the background process by using the QUERY PROCESS command, or cancel the process by using the CANCEL PROCESS command.


ANR0222E Error action disk definition file file specification.
Explanation: An error occurred creating or changing the disk definition file.
System Action: None.
User Response: Attempt to determine the cause of the write error and correct it.


ANR0223E Error writing list of disks to disk definition file.
Explanation: The disk definition file cannot be written.
System Action: Installation ends.
User Response: Determine the cause of the write error and correct it.


ANR0224E Volume volume name is specified more than once - server installation failed.
Explanation: The specified volume name was specified more than once in the server installation execution.
System Action: Installation ends.
User Response: Reinitialize the server install specifying a unique name for each database and recovery log volume.


ANR0230E Synchronization process failed for database volume volume name.
Explanation: The process that was attempting to synchronize the database volume shown has failed.
System Action: The volume is in the stale state.
User Response: See accompanying messages for more information.


ANR0231E Synchronization process failed for recovery log volume volume name.
Explanation: The process that was attempting to synchronize the recovery log volume shown has failed.
System Action: The volume is in the stale state.
User Response: See accompanying messages for more information.


ANR0232I Synchronization process canceled for database volume volume name.
Explanation: The process that was attempting to synchronize the database volume shown has been canceled.
System Action: The volume is in the stale state.
User Response: If desired, issue a VARY ONLINE command to start another synchronize process.


ANR0233I Synchronization process canceled for recovery log volume volume name.
Explanation: The process that was attempting to synchronize the database volume shown has been canceled.
System Action: The volume is in the stale state.
User Response: If desired, issue a VARY ONLINE command to start another synchronize process.


ANR0234I Synchronization complete for database volume volume name.
Explanation: The synchronization process for the database volume named has finished successfully.
System Action: The volume is varied online.
User Response: None.


ANR0235I Synchronization complete for recovery log volume volume name.
Explanation: The synchronization process for the recovery log volume named has finished successfully.
System Action: The volume is varied online.
User Response: None.


ANR0240E Deletion process failed for database volume volume name.
Explanation: The process that was attempting to delete the database volume shown has failed.
System Action: The volume is not deleted.
User Response: See accompanying messages for more information.


ANR0241E Deletion process failed for recovery log volume volume name.
Explanation: The process that was attempting to delete the recovery log volume shown has failed.
System Action: The volume is not deleted.
User Response: See accompanying messages for more information.


ANR0242I Deletion process canceled for database volume volume name.
Explanation: The process that was attempting to delete the database volume shown has been canceled.
System Action: The volume is not deleted.
User Response: None.


ANR0243I Deletion process canceled for recovery log volume volume name.
Explanation: The process that was attempting to delete the recovery log volume shown has been canceled.
System Action: The volume is not deleted.
User Response: None.


ANR0244I Deletion complete for database volume volume name.
Explanation: The delete process for the database volume named has finished successfully.
System Action: The volume is deleted.
User Response: None.


ANR0245I Deletion complete for recovery log volume volume name.
Explanation: The delete process for the recovery log volume named has finished successfully.
System Action: The volume is deleted.
User Response: None.


ANR0246E Error reading logical page logical page number (physical page physical page number) from database volume volume name.
Explanation: An error has been encountered when attempting to read a page from the specified database volume.
System Action: The failed I/O operation is retried on a mirrored volume, if available.
User Response: See accompanying messages for information about the volume in error. If the error persists and another mirrored copy of the volume is available, the failing volume should be taken offline by using the VARY OFF command, and repaired. Otherwise, halt the server and repair the volume. Then restart the server.


ANR0247I Database page logical page number successfully read from an alternate copy on volume volume name.
Explanation: After a read error, the server is able to read the desired page from another synchronized mirrored volume.
System Action: Processing continues.
User Response: None.


ANR0248E Unable to read database page logical page number from any alternate copy.
Explanation: After a read error, the server is unable to read the desired page from another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.
System Action: Processing is ended.
User Response: You can repair the failed volume by halting the server and correcting the volume errors.


ANR0249E Error reading logical page logical page number (physical page physical page number) from recovery log volume volume name.
Explanation: An error has been encountered when attempting to read a page from the specified recovery log volume.
System Action: The failed I/O operation is retried on a mirrored volume, if available.
User Response: See accompanying messages for information about the volume in error. If the error persists and another mirrored copy of the volume is available, the failing volume should be taken offline, by using the VARY OFF command, and repaired.


ANR0250I Recovery log page logical page number successfully read from an alternate copy on volume volume name.
Explanation: After a read error, the server is able to read the desired page from another synchronized mirrored volume.
System Action: Processing continues.
User Response: None.


ANR0251E Unable to read recovery log page logical page number from any alternate copy.
Explanation: After a read error, the server is unable to read the desired page from another mirrored volume because no other mirrored volume was in the synchronized state. This message is normally preceded by a message indicating which volume failed.
System Action: Processing is ended.
User Response: You can repair the failed volume by halting the server and correcting the volume errors.


ANR0252E Error writing logical page logical page number (physical page physical page number) to database volume volume name.
Explanation: An error has been encountered when attempting to write a page to the specified database volume.
System Action: If a mirrored volume is available then the failing volume is forced into the offline state.
User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.


ANR0253E Unable to write database page logical page number to any alternate copy.
Explanation: After a write error, the server is unable to write the desired page to another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.
System Action: Processing is ended.
User Response: Repair the failed volume.


ANR0254E Error writing logical page logical page number (physical page physical page number) to recovery log volume volume name.
Explanation: An error has been encountered when attempting to write a page to the specified recovery log volume.
System Action: If a mirrored volume is available, the failing volume is forced into the offline state.
User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.


ANR0255E Unable to write recovery log page logical page number to any alternate copy.
Explanation: After a write error, the server is unable to write the desired page to another mirrored volume because no other mirrored volume is in the synchronized state. This message is normally preceded by a message indicating which volume failed.
System Action: Processing is ended.
User Response: You can repair the failed volume by halting the server and correcting the volume errors.


ANR0256E Error writing physical page physical page number to restart/checkpoint area on database volume volume name.
Explanation: An error has been encountered when attempting to write a page to the specified database volume.
System Action: If a mirrored volume is available, the failing volume is forced into the offline state.
User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.


ANR0257E Error writing physical page physical page number to restart/checkpoint area on recovery log volume volume name.
Explanation: An error has been encountered when attempting to write a page to the specified database volume.
System Action: If a mirrored volume is available, the failing volume is forced into the offline state.
User Response: Repair the failing volume, and then use the VARY ON command to bring the volume back online.


ANR0258E Unable to write complete restart/checkpoint information to disk.
Explanation: While writing restart/checkpoint information to disk, the server encounters an error writing to a database or recovery log volume for which no synchronized mirrored copy is available. This message is normally preceded by a message indicating which volume failed.
System Action: Processing is ended.
User Response: Repair the failing volume.


ANR0259E Unable to read complete restart/checkpoint information from any database or recovery log volume.
Explanation: During server restart, the server is unable to read a complete set of restart/checkpoint information from any of the defined database or recovery log volumes.
System Action: Server restart is ended.
User Response: Ensure that all defined database and recovery log volumes are available for use by the server.


ANR0260I Database page logical page number successfully resynchronized.
Explanation: After detecting a partially-written database page, the server is able to rewrite the page by using a synchronized mirror copy.
System Action: Processing continues.
User Response: None.


ANR0261I Recovery log page logical page number successfully resynchronized.
Explanation: After detecting a partially-written recovery log page, the server is able to rewrite the page by using a synchronized mirror copy.
System Action: Processing continues.
User Response: None.


ANR0265E Log disk processing failed: sufficient memory is not available.
Explanation: At server installation, the server is unable to process the server log disks due to insufficient memory.
System Action: Server installation stops.
User Response: Restart the server installation process with more memory available.


ANR0266E Database disk processing failed: sufficient memory is not available.
Explanation: At server installation, the server is unable to process the server database disks due to insufficient memory.
System Action: Server installation stops.
User Response: Restart the server installation process with more memory available.


ANR0267E Log volume volume name is not available.
Explanation: The specified volume cannot be found during installation.
System Action: Server installation stops.
User Response: Determine the reason the disk is unavailable, and correct the problem. Restart the server installation process.


ANR0268E Database volume volume name is not available.
Explanation: The specified volume cannot be found during installation.
System Action: Server installation stops.
User Response: Determine the reason the disk is unavailable, and correct the problem. Restart the server.


ANR0269E Process for Log volume volume name terminated - thread resource not available.
Explanation: During installation for the indicated volume, the server cannot start a thread to service I/O requests.
System Action: Server installation stops.
User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory". Restart the server installation process.


ANR0270E Process for Database volume volume name terminated - thread resource not available.
Explanation: During installation for the indicated volume, the server cannot start a thread to service I/O requests.
System Action: Server installation stops.
User Response: Allocate additional storage to the server. For details, issue HELP MEMORY to display the information online or see "Appendix A. Allocating Additional Server Memory". Restart the server installation process.


ANR0271E Maximum number of recovery log volumes exceeded.
Explanation: More recovery log volumes have been specified than the server can manage.
System Action: Server installation stops.
User Response: Reduce the number of recovery log volumes specified. Restart the server installation process.


ANR0272E Maximum number of database volumes exceeded.
Explanation: More database volumes have been specified than the server can manage.
System Action: Server installation stops.
User Response: Reduce the number of database volumes specified. Restart the server installation process.


ANR0301I Recovery log format in progress; count megabytes of count.
Explanation: The amount of the server recovery log shown has been successfully formatted.
System Action: Formatting continues.
User Response: None.


ANR0302I Recovery log formatting took mseconds milliseconds.
Explanation: Formatting of the recovery log has completed and took the number of milliseconds shown.
System Action: None.
User Response: None.


ANR0303I Format rate: rate pages/second.
Explanation: During formatting, the formatter processed the number of pages indicated each second.
System Action: None.
User Response: None.


ANR0304I Page service time: rate ms.
Explanation: During formatting, the formatter required the number of milliseconds indicated to process each page.
System Action: None.
User Response: None.


ANR0305I Recovery log format complete.
Explanation: Formatting of the server recovery log completed successfully.
System Action: None.
User Response: None.


ANR0306I Recovery log volume mount in progress.
Explanation: During restart, the server is mounting required recovery log volumes.
System Action: None.
User Response: None.


ANR0307I Recovery log extend in progress; count megabytes of count formatted.
Explanation: As a result of an EXTEND LOG command, the additional recovery log pages are being formatted.
System Action: Formatting continues.
User Response: None.


ANR0309I Recovery log extend terminated - process canceled.
Explanation: The process started as a result of an EXTEND LOG command and has been canceled.
System Action: The EXTEND command is ended.
User Response: None.


ANR0311I Recovery log reduce in progress; count megabytes of count moved.
Explanation: As a result of a REDUCE LOG command, the amount of data from the recovery log shown has been moved.
System Action: The REDUCE LOG command continues.
User Response: None.


ANR0314W Recovery log usage exceeds utilization percentage %% of its assigned capacity.
Explanation: This message is issued to notify the administrator that ADSM recovery log utilization exceeds 90% or more of its assigned capacity.
System Action: Server operation continues.
User Response:


ANR0350I Recovery checkpoint started.
Explanation: During server initialization, the process of bringing the server database back to a state of consistency has begun.
System Action: None.
User Response: None.


ANR0351I Recovery checkpoint complete.
Explanation: During server initialization, the process of bringing the server database back to a state of consistency has completed successfully.
System Action: None.
User Response: None.


ANR0352I Transaction recovery complete.
Explanation: During server initialization, the process of recovering any incomplete transactions has completed successfully.
System Action: None.
User Response: None.


ANR0353I Recovery log analysis pass in progress.
Explanation: During server initialization, the process of analyzing the server recovery log has begun.
System Action: None.
User Response: None.


ANR0354I Recovery log redo pass in progress.
Explanation: During server initialization, the process of committing incomplete transactions has begun.
System Action: None.
User Response: None.


ANR0355I Recovery log undo pass in progress.
Explanation: During server initialization, the process of rolling back incomplete transactions has begun.
System Action: None.
User Response: None.


ANR0356I Recovery log compression started.
Explanation: The process of removing unneeded data from the server recovery log has begun.
System Action: None.
User Response: None.


ANR0357I Recovery log compression ended.
Explanation: The process of removing unneeded data from the server recovery log has completed.
System Action: None.
User Response: None.


ANR0358E Database initialization failed: sufficient memory is not available.
Explanation: During server initialization, the server database fails initialization because sufficient server memory is not available.
System Action: Initialization fails.
User Response: Make more memory available to the server.


ANR0359E Database initialization failed: unable to read database restart record.
Explanation: During server initialization, the server database initialization fails because the required restart record cannot be read.
System Action: Initialization fails.
User Response: Contact your service representative.


ANR0360E Database initialization failed: database size mismatch; LVM size = size, expected size = size.
Explanation: During server initialization, the server database initialization fails because the size of the database does not match its prior size.
System Action: Initialization fails.
User Response: Contact your service representative.


ANR0361E Database initialization failed: error initializing database page allocator.
Explanation: During server initialization, the server database initialization fails because the page allocator cannot be started.
System Action: Initialization fails.
User Response: Contact your service representative.


ANR0362W Database usage exceeds utilization percentage %% of its assigned capacity.
Explanation: This message is issued to notify the administrator that ADSM database utilization exceeds 80% or more of its assigned capacity.
System Action: Server operation continues.
User Response: Depending upon the size of your database, add database volumes, or extend the database, or both, before it fills completely. The server expiration process may also free up database space making it available to other server processes. Refer to the EXPIRE INVENTORY, DEFINE DBVOL, and EXTEND DB commands for more information on these operations.


ANR0363I Database was automatically upgraded to the server program level.
Explanation: This message is issued to notify the administrator that the ADSM server database was automatically upgraded to the current server program level. The upgrade is performed when the UPGRADEDB parameter is specified at server start-up and the server is started over a database that was written by a down-level version of the server program.
System Action: Server operation continues.
User Response: None. The UPGRADEDB parameter does not need to be specified during future server start-ups.


ANR0380W The database buffer pool recovered from an overcommit of number of pages pages. Consider increasing your buffer pool size by kilobytes needed kilobytes under current server load.
Explanation: During normal processing, additional buffer pool space is required beyond that specified in the BUFPOOLSIZE in the server options file. The additional kilobytes of buffer pool space that are required are indicated in the message.
System Action: Server operation continues; the additional buffer pool space is obtained from available server memory.
User Response: If the current server load is typical, consider increasing the size specified for your BUFPOOLSIZE option by the number of kilobytes specified in the message. To do this, you must halt the server, change the options file, and then restart the server.


ANR0381I Bufferpool statistics were successfully reset.
Explanation: Bufferpool statistics, such as the Cache Hit Ratio, have been reset by the RESET BUFPOOL command.
System Action: Server operation continues.
User Response: The QUERY DB command (FORMAT=DETAILED) can be used to to display the current values for the buffer pool statistics.


ANR0382I The database maximum utilization statistic was successfully reset.
Explanation: The database maximum utilization statistic has been reset by the RESET DBMAXUTILIZATION command to the current utilization.
System Action: Server operation continues.
User Response: The QUERY DB command (FORMAT=DETAILED) can be used to to display the current value for the maximum utilization.


ANR0383I The recovery log maximum utilization statistic was successfully reset.
Explanation: The recovery log maximum utilization statistic has been reset by the RESET LOGMAXUTILIZATION command to the current utilization.
System Action: Server operation continues.
User Response: The QUERY LOG command (FORMAT=DETAILED) can be used to to display the current value for the maximum utilization.


ANR0384I The recovery log consumption statistic was successfully reset.
Explanation: The recovery log consumption statistic has been reset by the RESET LOGCONSUMPTION command.
System Action: Server operation continues.
User Response: The QUERY LOG command (FORMAT=DETAILED) can be used to to display the current value for recovery log consumption.


ANR0390W A server database deadlock situation has been encountered: lock request for transaction transaction id will be denied to resolve the deadlock.
Explanation: The server detected a deadlock situation between a number of processes attempting to access database information. A lock request for one of the processes will be denied to resolve the database deadlock. When server processes encounter a database deadlock, they usually reattempt the function that was in progress when the deadlock was encountered. Not all process can explicitly re-try an operation. For example, migration and reclamation will eventually retry. However, something like a delete volume run in a macro will only retry if the delete command is re-issued either in the macro or the command line.
System Action: A lock request fails for one of the deadlocked processes. Server operation continues.
User Response: If a process can retry (like migration), then monitor the re-try attempt to see if it succeeds or not. If it fails, contact a service representative. If the process or command is not able to retry on it's own, then re-issue the command or macro that caused the action to occur. If it fails again, contact a service representative for further assistance to better isolate the deadlock condition.

[ Top of Page | Previous Page | Next Page | Table of Contents ]