Indicates which pages, storage areas, or snapshot files are
corrupt or inconsistent by displaying the contents of the corrupt
page table (CPT). Corrupt pages are logged to the CPT, which is
maintained in the database root file.
1 – Format
(B)0[m RMU/Show Corrupt_Pages root-file-spec
[4mCommand[m [4mQualifiers[m x [4mDefaults[m
x
/Options=({Normal|Debug|Full}) x /Options=(Normal)
/Output[=file-name] x /Output=SYS$OUTPUT
2 – Parameters
2.1 – root-file-spec
The root file specification of the database for which you want
the corrupt or inconsistent storage areas or snapshot files
logged to the CPT to be displayed.
3 – Command Qualifiers
3.1 – Options
Options=Normal
Options=Full
Options=Debug
Specifies the type of information you want displayed, as follows:
o Normal
Displays the active CPT entries and the corrupt or
inconsistent areas sorted by area and page.
o Full
Displays the same information as Normal plus the disks on
which the active CPT entries and the corrupt or inconsistent
areas or snapshot files are stored-sorted by disk, area, and
page.
o Debug
Provides a dump of the entire CPT and lists all the storage
areas.
Options=(Normal) is the default qualifier.
3.2 – Output
Output[=file-name]
Specifies the name of the file where output is sent. The default
is SYS$OUTPUT. The default output file extension is .lis, if you
specify only a file name.
4 – Usage Notes
o To use the RMU Show Corrupt_Pages command for a database, you
must have the RMU$BACKUP, RMU$RESTORE, or RMU$VERIFY privilege
in the root file access control list (ACL) for the database or
the OpenVMS SYSPRV or OpenVMS BYPASS privilege.
o You can repair and remove a corrupt snapshot file from
the CPT by issuing the RMU Repair command with the
Initialize=(Snapshots) qualifier. Using the Repair command
in this case is faster than performing a restore operation.
See Repair for details.
5 – Examples
Example 1
The following example shows the output from the RMU Show Corrupt_
Pages command when page 1 in area 3 is marked as corrupt:
$ RMU/SHOW CORRUPT_PAGES MF_PERSONNEL
*-------------------------------------------------------------------
* Oracle Rdb V7.0-00 8-JUL-1996 13:46:20.77
*
* Dump of Corrupt Page Table
* Database: USER1:[DB]MF_PERSONNEL.RDB;1
*
*--------------------------------------------------------------------
Entries for storage area EMPIDS_MID
-----------------------------------
Page 1
- AIJ recovery sequence number is -1
- Area ID number is 3
- Consistency transaction sequence number is 0:0
- State of page is: corrupt
*-------------------------------------------------------------------
* Oracle Rdb V7.0-00 8-JUL-1996 13:46:21.17
*
* Dump of Storage Area State Information
* Database: USER1:[DB]MF_PERSONNEL.RDB;1
*
*--------------------------------------------------------------------
All storage areas are consistent.