Resets   the   area's   corruption   indication   flag    (FILID
 CORRUPT_FLG),  thus allowing you to use the uncorrupted sections
 of a corrupted storage  area.   Storage  areas  are  most  often
 corrupted  by  attempting  a VAX Rdb/VMS (not RdbALTER) rollback
 with  one  or  more  storage  areas   opened   in   batch-update
 transaction mode.

Additional information available:

FormatMoreExamples

 UNCORRUPT ──┬─> storage-area-name ───┬─>
             └─> storage-area-number ─┘

Additional information available:

storage-area-namestorage-area-number

 Specifies an area of the current database by storage area  name,
 which is the name given by the AREA clause in the schema.

 Specifies an area of the current database by  the  storage  area
 number,  which  is  assigned when the database is created and is
 given on the first line of a page display.

 The UNCORRUPT command allows you to access a database that is in
 an  uncertain  condition.  Accordingly, the following message is
 displayed when you issue it:

    BEWARE ATTEMPTING TO UNCORRUPT A STORAGE AREA
    WITHOUT FIRST VERIFYING IT USING THE RMU/VERIFY
    COMMAND.

 The following example resets the  EMPIDS_LOW  area's  corruption
 indication flag.

 RdbALTER> UNCORRUPT EMPIDS_LOW

                 ***** WARNING! *****

    BEWARE ATTEMPTING TO UNCORRUPT A STORAGE AREA
    WITHOUT FIRST VERIFYING IT USING THE RMU/VERIFY
    COMMAND.

    AN RdbALTER ROLLBACK COMMAND WILL LEAVE THIS
    AREA MARKED CORRUPT.

  Area EMPIDS_LOW now marked uncorrupt.