Just_Corrupt
This qualifier replaces the Just_Pages qualifier beginning in
Oracle Rdb V7.0.
Allows you to restore the corrupt pages and areas in the
database as recorded in the corrupt page table (CPT). The CPT
is maintained in the .rdb file. (Note that if the corrupt page
table becomes full, the area with the highest number of corrupt
pages is marked corrupt and the individual pages for that area
are removed from the CPT.)
Often, only one or a few pages in the database are corrupted
due to hardware or software faults. The Just_Corrupt qualifier
allows you to recover that database in minimal time with minimal
interference; availability of the uncorrupted data is unaffected.
It allows you to restrict the restoration to the pages (or areas)
logged as corrupt in the corrupt page table.
The Just_Corrupt qualifier is a positional qualifier. If you use
it in the global position, RMU Restore restores all the corrupt
pages and all the corrupt areas as logged in the corrupt page
table. If you use it in the local position, RMU Restore restores
only the corrupt pages (or the entire area) of the area name it
modifies.
It is possible to mix restoration of complete areas and just
corrupt pages in the same command. The following example restores
all of AREA_1 (regardless of whether or not it is corrupt), but
just the corrupt pages (logged to the CPT) in AREA_2.
$ RMU/RESTORE/AREA backup_file AREA_1, AREA_2/JUST_CORRUPT
Note that when the Just_Corrupt qualifier is used globally, all
the corrupt pages logged to the CPT for the areas specified
are restored. For example, the following command restores all
the corrupt pages logged to the CPT for AREA_1 and AREA_2.
(However, if one of the areas specified contains no corruptions,
an informational message is displayed and that area is not
restored.)
$ RMU/RESTORE/JUST_CORRUPT backup_file /AREA AREA_1, AREA_2
Restoration of corrupt pages and area can be performed on line.
Online operations lock only the corrupt pages or areas for the
duration of the restore operation. The remainder of the storage
area can be read or updated by an application. When an entire
area is restored on line, applications are locked out of the
entire area for the duration of the restore operation.
There are some restrictions on the use of the Just_Corrupt
qualifier:
o The backup file must be a full backup file that contains the
selected area.
o When space area management (SPAM) pages are restored, RMU
Restore rebuilds the SPAM page using information from the
range of data pages that the SPAM page manages.
o Area bit map (ABM) pages can be restored, but their content
is not reconstructed. If ABM pages have been corrupted,
regenerate them with the RMU Repair command.
o A by-page restore operation is like a by-area restore
operation in that after-image journal (AIJ) recovery is
required to make the restored data consistent with the rest
of the database.
Once the pages are restored, access to these restored pages is
prohibited until they are made consistent. Inconsistent pages
are stored in the corrupt page table (CPT) and have their
timestamp field flagged by Oracle Rdb.
o You can also use the Just_Corrupt qualifier in a restore
options file. However, you cannot use any of the following
qualifiers with the Just_Corrupt qualifier (neither within an
options file nor on the command line):
- Blocks_Per_Page
- Extension
- File
- Incremental
- Read_Only
- Read_Write
- Snapshot
- Spams
- Thresholds
You can use the Just_Corrupt qualifier in conjunction with
the Journal=file qualifier to greatly speed up processing of
a large tape backup file. When you use the Journal qualifier,
only those tapes containing corrupt pages, areas, or both, are
mounted and processed.