DB2 Server for VSE & VM: Data Restore Guide

Recovery From a Logical Error

If the Dbspace can be Dropped

You can:

• Either repair the database in the following way:
  1. Drop the dbspace for which there is a logical error
  2. Create the dbspace again
  3. Acquire the dbspace
  4. Reload all tables of the dbspace that you dropped previously using the Data Restore RELOAD with forward recovery from an archive, as described in From a Physical Error.
• Or restore the storage pool or the database as described in From a Physical Error. Depending on the number of tables in the dbspace in error, this may be the quicker way.

If LOGMODE=Y you cannot use forward recovery. However, the Data Restore feature does let you recover some data from the database with the SELECT command. The UNLOAD command cannot be used because it will end abnormally when it tries to read the corrupted data. The output from such a partially unloaded dbspace is not usable for the RELOAD process. Try to unload data using the SELECT command from the tables that reside in the dbspace, that report the error. The SELECT command ends at the point where it tries to read the data in error. Neither the Data Restore feature nor DB2 can bypass the damaged area and continue unloading the required data. Some of this unloaded data might be useful to help determine the differences between the table reloaded from the archive and the output of the previously executed SELECT.

If the Dbspace cannot be Dropped

There are cases where DB2 does not allow you to drop a dbspace but abnormally ends instead. In this situation, you can:

• Either restore the database from archive tapes and consecutive log files, including the current log. Follow the description in Recover from Directory Failure.
• Or disable the dbspace and contact the IBM Support Center for help. Acquire a new dbspace and Data Restore RELOAD and APPLYLOG the individual tables of this dbspace from an archive as described before.

  Warning: The tables must be reloaded with a new name, because you cannot have duplicate table names in the catalog. This means that applications, pointing to the tables in the disabled dbspace, will need to be changed, preprocessed and compiled.