Loading...

DB2 Agent Restore Frequently Asked Questions

Table of Contents

Can we perform out-of-place restores of databases created in another directory?

Can we perform out-of-place restores of databases with non-default parameter values?

How do I prevent a command line restore from taking place during an online backup?

Can we restore a job that had started automatically and on waiting mode for available resource if that resource is used by data restore?

Can I restore an IntelliSnap backup image on a disk using CommCell Console?

Do I need to delete the online logs when performing a point-in-time restore?

Can we run a restore operation for DB2 encrypted databases?

Can we perform out-of-place restores of databases created in another directory?

If you defined your own directory for the database instead of using the DB2 default location when you created the database, you cannot restore this database to either a new database or another instance in the conventional manner.

Can we perform out-of-place restores of databases with non-default parameter values?

If the DBHEAP, UTIL_HEAP, and/or APP_CTL_HEAP_SZ configuration parameters for the (source) database that you want to restore contain a value other than the default value, you cannot restore this database to either a new database or another instance in the conventional manner.

How do I prevent a command line restore from taking place during an online backup?

In DB2 9.7 and later, by default, a full online DB2 database backup includes the transaction log files to ensure that there is a consistent backup image. DB2 includes all the required logs in the backup image when the transaction spreads across many log files, even when a log file backup exists. If the backed up log files are deleted, DB2 will submit a log restore request to the DB2 Agent.

There are three parameters that you use to control the log files actions:

Note: If you set both the max_log parameter and num_log_span parameter to 0, DB2 uses unlimited log space.

  1. The LOGPRIMARY parameter sets the storage amount that the software allocates for log files. Make sure that all uncommitted transactions are logged in the LOGPRIMARY number of log files. This prevents the DB2 application from sending a log file retrieval request for the archived files.
  2. The max_log parameter limits the percentage of log space that one transaction can use. Set this to 0 to have no limit of one transaction. To limit the space, set the value to the percentage that you want the limit to be.
  3. The num_log_span parameter limits the number of log files that one transaction spans. Set this to 0 to have no limit of one transaction. To limit the number of files, set this parameter to the number of files.

Can we restore a job that had started automatically and on waiting mode for available resource if that resource is used by data restore?

when you try to restore a database after updating the archive logs  with new changes in a database, the new restore job automatically starts and hangs displaying the status as waiting with the following error:

The media is already reserved by some other jobs.

Since the main restore job is not yet completed, the current restore job will wait for the main restore job to complete.

You can restore the current job by configuring the bDisableRestoreCaching registry key's dword value as 1 on CommServe under the Resource Manager.

Can I restore an IntelliSnap backup image on a disk using CommCell Console?

No. Currently, you cannot restore an IntelliSnap backup image on a disk using CommCell Console. You can only restore a regular backup image to a location on a disk.

Do I need to delete the online logs when performing a point-in-time restore?

Yes, before performing a point-in-time restore, you must delete the online logs or the restore will fail.

Can we run a restore operation for DB2 encrypted databases?

Yes, you can run a restore operation for DB2 encrypted databases.

Consider the following conditions before running a restore operation:

  • An in-place restore operation works fine if you change the database name.
  • An in-place restore operation goes to pending state if you do not change the database name. To resolve this issue, drop the existing database, and then resume the restore operation.
  • An out-of-place restore operation goes to pending state. To resolve this issue, enable encryption on the destination instance database management configuration parameters, and then resume the restore operation.

Last modified: 1/9/2018 2:00:06 PM