The first step recovering deleted partition data is to restore your most recent backup of your production database to a temporary location.

When you restore your backup, you may want to protect the restored database from updates by other users. You achieve this by placing the database in a restricted access mode. You can enable restricted access to the database by adding the -dbrestrict parameter to the PROREST command. The syntax is:

prorest db-name...[ -dbrestrict restrict-type]

where restrict-type is one of the following values:

  • rollforward — Indicating that the next allowable activity on this database is rolling forward after-image files
  • partitioncopy — Indicating that the next allowable activity on this database is copying data with the PROUTIL PARTITIONMANAGE COPY utility
Note: All other prorest parameters are valid. Adding -dbrestrict to the prorest command enables the same restrictions as PROUTIL DBRESTRICT. See PROUTIL DBRESTRICT qualifier for details of the restrictions.

The restriction you place on your database during the restore is determined by your use of after-imaging:

  • If you use after-imaging, your next step in copying your data is applying after-image files to your restored database. Choose the value rollforward for restrict-type.
  • If you don't use after-imaging, your next step in copying your data is executing the PROUTIL PARTITIONMANAGE COPY. Choose partitioncopy as the value for restrict-type.
Restricting access to the restored database ensures that no changes can be made to the database before the copy completes. If you don't restrict access, a user could connect and make changes, resulting in restoring incorrect data to your production database.
Note: During the partition data recovery, DBRESTRICT is enabled offline. You can then start the database in the multi-user mode with the restriction enforced. The database must then be shut down to remove the restriction.