Cause: For table space restore, the backup must have been taken during the current log sequence of the database. The log file sequence is determined by the database that has been restored previously or the log files that have been processed. In addition, the backup must have been taken after the last time the database was enabled for roll forward recovery.
Table space restore has stopped.
Action: Resubmit the command with a correct backup image.
Cause: Changes have been made to the recovery history file since the file was open for a scan. The data read may not be consistent.
Action: If it is essential to have consistent data from the scan, close the recovery history file and resubmit the command.
Cause: Eight recovery history file scans in this process are already open. No more than eight open scans are allowed.
The command cannot be processed.
Action: Issue one or more CLOSE RECOVERY HISTORY FILE SCAN commands and resubmit the command.
Cause: An error was encountered during an access to the recovery history file. The utility is able to recover the file from an alternate copy. The utility continues processing.
Action: The utility continues processing successfully. The user should take appropriate precautions to ensure the recovery history file is not damaged again.
Cause: An error was encountered during an access to the recovery history file. The utility is not able to recover the file. The utility stops processing.
Action: To continue processing, the user may remove the recovery history file and resubmit the command. The utility will regenerate a new file. Any data from the corrupted file are lost. The user may look at the corrupted file to see if any information can be saved. The user should take appropriate precautions to ensure the recovery history file is not damaged again.
Cause: The SQLUHINFO structure was not large enough to hold the entry that was to be returned (including all of its TABLESPACES). The value of the SQLN field of the SQLUHINFO structure should be at least as large as the SQLD field returned.
The command cannot be processed.
Action: Increase the value of the SQLN field in the SQLUHINFO structure to the value indicated by the SQLD field (making sure the SQLUHINFO structure is large enough to support that amount) and resubmit the command.
Cause: The utility has encountered an entry with the same identifier (timestamp to the second) in the recovery history file while writing to it. The write to the recovery history file terminates. Database manager ensures the uniqueness of the recovery history file identifiers and makes provisions for it even if there are more than one request per second. However, there may be cases where it will fail if numerous requests come in within a few seconds.
Action: Check the First Failure Service Log (db2diag.log) for additional information. If the applications are running utilities (such as backup, quiesce, load) that generate numerous entries to the history file, try to pace the utility requests to prevent the problem.
Cause: The entry specified to be updated in the recovery history file does not exist in the file. The utility stops processing.
Action: Resubmit the command with a valid entry.
Cause: The utility has encountered an error writing to the recovery history file. This warning does not affect processing.
Action: Check the First Failure Service Log (db2diag.log) for additional information. Correct the error condition to prevent future warnings.