Resets an area's inconsistent indication flag, thus allowing you
 to use the database.

Additional information available:

FormatMoreExamples

 ─┬───>────┬─> 
C
O
N
S
I
S
T
E
N
T ─┬─> storage-area-name ───┬─>
  └> 
M
A
K
E ─┘               └─> storage-area-number ─┘

Additional information available:

storage-area-namestorage-area-number

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

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

 When an area is restored from backup on  a  per-area  basis,  it
 will  not  reflect  data that has been updated since the backup.
 The  transaction  level  of  the  restored  area  reflects   the
 transaction  level of the backup file, not the transaction level
 of the  database.   Therefore,  the  transaction  level  of  the
 restored  area differs from that of the database.  Rdb/VMS marks
 the area by setting a flag in the area file to inconsistent.

 You can perform a recovery by area to  upgrade  the  transaction
 level   of   the   restored   area  to  that  of  the  database.
 (After-image journaling must be enabled in order to  restore  by
 area.) If you know for certain that no updates have been made to
 the database since the backup, you can use  the  MAKE_CONSISTENT
 command  in  RdbALTER  to  change  the  setting of the flag from
 inconsistent to consistent.

 Example 1

 The  following  example  resets   the   indication   flag   from
 inconsistent to consistent for the area JOBS.

 RdbALTER> MAKE_CONSISTENT JOBS

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

  BEWARE ATTEMPTING TO MAKE CONSISTENT A STORAGE AREA
  WITHOUT FIRST VERIFYING IT.

  A RdbALTER ROLLBACK COMMAND WILL LEAVE THIS AREA
  MARKED INCONSISTENT SO THAT YOU CAN PERFORM A VERIFY
  TO INSURE THAT IT IS ACTUALLY CONSISTENT.

 Area JOBS now marked consistent.)