Select an entry from the list
Change the media information if necessary
Manually enter the backup image information
OK
Show Command
Cancel
Backup image page
Select an entry from the list
Change the media information if necessary
Manually enter the backup image information
OK
Show Command
Cancel
Select an entry from the list
Click on this radio button to use one of the listed backup images to restore the database or database partition.
Change the media information if necessary
This control, and its associated fields, is only displayed if you select a backup image from the list of available images from the list box above it (that is, Select an entry from the list is selected). If you know that the information displayed in the Media Type column for that backup image is not correct, you can change this information by specifying the correct media of the backup image in the Media Type box. The choices are as follows:
You can specify more than one path to the backup image if the database or database partition was backed up to more than one location. In this situation, the backup image will be listed in multiple locations, and all the images will have the same time stamp. All portions of the backup image must be concurrently available for the restore operation to complete.
To display the list of DLL names, click on Browse.
| Note: | You cannot use the Control Center to restore backup images that were taken previous to DB2 Version 6. |
Manually enter the backup image information
This control and its associated fields are only displayed if you do not select a backup image from the list of available images from the list box above it (that is, Select an entry from the list is not selected). Specify the media of the backup image in the Media Type box. The choices for this field are as follows:
You can use the Browse push button to list the available
directories.
You can specify more than one path to the backup image if the database or database partition was backed up to more than one location. In this situation, the backup image will be listed in multiple locations, and all the images will have the same time stamp. All portions of the backup image must be concurrently available for the restore operation to complete.
The remaining fields for this group of controls are as follows:
You can either type the date, or you can click on the arrow to open a calendar on which you select the date. Click on the arrows at the top of the calendar to display the month that you want, then on a date to select it. The calendar closes, and the date you selected will be displayed in the field.
Notes:
Table spaces page
Use full database
Use selected table spaces only
Available table spaces
Use table spaces
>>, >, <, <<
OK
Show Command
Cancel
Use full database
Click on this radio button to restore all table spaces to the state they were in at the time that the backup image was taken. This is the default.
| Note: | Restoring all table spaces is not the same as performing a full restore of
the database or database partition. When
you restore the full database or database partition, the following also
occurs:
|
Use selected table spaces only
Click on this radio button to restore only those table spaces that you selected in the Available table spaces box. When you restore a subset of table spaces, you can do the operation either online, or offline. The following considerations apply to the partitioned database environment:
Notes:
In a partitioned database system, if you intend to roll forward a table space
(or table spaces) to the end of the logs, you do not have to restore it at
each database partition. You only need
to restore it at the database partitions that require recovery.
In a partitioned database environment, if you want to roll forward a table
space to a point in time, you must restore the table
space partition at each database partition that contains a portion of the
table space, and roll forward each table space partition individually to the
same point in time. This ensures that the table space is consistent at
each node.
Available table spaces
This box displays all the table spaces that are currently available in the backup image. This information is recorded in the recovery history file for the database or the database partition.
Use table spaces
This box displays all the table spaces that you want to have restored to the state they were in when the backup image was created.
>>, >, <, <<
Click on these push buttons to change the list of table spaces displayed in the Available table spaces and Use table spaces boxes:
Containers page
Redirect table space containers
Allow new container creation during
roll-forward
Table spaces
Container name
Add
Change
Remove
OK
Show Command
Cancel
Redirect table space containers
Click on this check box to perform a redirected restore. When you select this check box, you must select another control on the Containers page to specify the type of container modification that you want to do.
You may not be able to perform a restore operation because a container is in the not valid state. In this situation, you must modify the container. You can either change the container's path or remove the container, then, if you want, perform an add operation to replace the deleted container with another container.
The state of the container is rolled up into that of its table space. To display the container that is in the not valid state, select the table space whose state is not valid. That table space's containers will be displayed in the Container name box, and their states will also be displayed. Select the container that you want, then specify the container modification.
Allow new container creation during roll-forward
Select this check box to allow the information in the Containers field of the Table spaces box to be modified by the roll-forward phase of the restore operation. If any create, remove, or alter container operations are recorded in the database logs, these operations will be reapplied during the roll-forward phase.
Containers are re-created only for table spaces that are selected for restore.
If you are not performing roll-forward recovery, this option has no effect.
Table spaces
This box displays the table spaces that were selected for restore on the Table spaces page. The columns are:
If the state of a table space is not valid, at least one of its containers has an invalid path. You cannot restore the database or database partition if a container is in an inconsistent state. In this situation, you must modify the container. You can either change the container's path or remove the container, then, if you want, perform an add operation to replace the deleted container with another container.
To display the container that is in the not valid state, select the table space whose state is not valid. That table space's containers will be displayed in the Container name box, and their states will also be displayed. Select the container that you want, then specify the container modification.
Container name
This box displays all the containers for the table space that is selected in the Table spaces box. For a system-managed space (SMS), the absolute path and the state of the container are displayed. For a database-managed space (DMS), the absolute path, file size, and the state of the container are displayed. The states are as follows:
You cannot restore the database or database partition if the container is in this state: you must modify the container. You can either change the container's path or remove the container, then, if you want, perform an add operation to replace the deleted container with another container.
Add
Click on this push button to open a container editor window, in which you specify the container to add. The type of container editor window that opens will be the same as that of the table space:
| Note: |
In a partitioned database environment, if you want to add a new container,
the path must exist at each node where the container will be stored.
|
Change
Click on this push button to open a window in which you can change the name, drive, and path of the selected container.
Notes:
In a partitioned database environment, if you want to change the path of an
existing container, the path must exist at each node where the container will
be stored.
Remove
Click on this push button to delete the selected container.
Roll-Forward page
Roll-Forward
Overflow directory
Leave in roll-forward pending state
Alternate log path
OK
Show Command
Cancel
Roll-Forward
Click on this check box to perform roll-forward recovery. There are two types of roll-forward recovery:
| Note: |
If you need to restore a single database partition, you can perform
roll-forward recovery to the end of the logs to bring it up to the same level
as the other database partitions in the database.
|
| Note: |
In a partitioned database environment, the database is located across many
nodes. In this environment, if you are performing point-in-time
roll-forward recovery, all database partitions must be rolled forward to
ensure that all partitions are at the same level.
|
You can either type the date, or you can click on the arrow to open a calendar on which you select the date. Click on the arrows at the top of the calendar to display the month that you want, then on a date to select it. The calendar closes, and the date you selected will be displayed in the field.
Overflow directory
The roll-forward operation checks for logs in the location specified by the logpath database configuration parameter. If you have moved any logs from the location specified by the logpath parameter, use the Overflow directory field to specify the path to the logs that you moved.
To display the list of available directories, click
.
Leave in roll-forward pending state
Click on this check box to leave the database or database partition in the roll-forward pending state at the end of the restore operation. This is the default.
A database or database partition in the roll-forward pending state cannot be used. To turn the roll-forward pending state off and make the database or database partition usable, you can:
For a single-partition database, select Stop Roll-Forward from the
pop-up menu for the database.
For a partitioned database,
Alternate log path
The logpath database configuration parameter specifies the location of logs. The value in the Alternate log path field overwrites the default location of the logs, for the current roll-forward operation and for any subsequent operations.
If you want to overwrite the default location of logs, type a string of up
to 242 bytes, or, to search for and select a path, click:
The string can point to either a path name, or to a raw device. If the string points to a path name, it must be a fully qualified path name, not a relative path name.
| Note: | In a partitioned database environment, the node number is automatically appended to the path. This is done to maintain the uniqueness of the path in multiple logical node configurations. |
To specify a device, specify a string that the operating system identifies as a device. For example:
| Note: | You must have Windows NT Version 4.0 with Service Pack 3 installed to be able to write logs to a device. |
| Note: | You can only specify a device on AIX, Windows NT, and Solaris platforms. |
The new setting does not become the value of logpath until both of the following occur:
When the first new connection is made to the database, the database manager
will move the logs to the new location specified by logpath.
Options page
Process while
Performance
OK
Show Command
Cancel
Process while
Select one of the following radio buttons to specify whether the restore operation is to be done online or offline.
| Note: | Restoring all table spaces is not the same as doing a full restore of the
database or database partition. When you restore the full database or
database partition, the following also occurs:
|
Performance
Use the following fields to specify the number and size of the buffers to be used for the restore operation. You can increase the number of buffers or the size of each buffer (or both) to cause the restore operation to complete faster. Note that increasing the value specified for either option causes the restore operation to use more memory.