CHECK (Data Integrity Checking)
- Last UpdatedJan 30, 2025
- 3 minute read
Function:
Starts the integrity checking of the Database (DB) specified.
Description:
-
Using the CHECK command from within a Project, the administrator can check:
-
The System, Miscellaneous and Comms DBs.
-
One or more named DBs.
-
All the DBs in a Project.
-
For information about using the Data Integrity Checker (DICE) as a stand-alone program, refer to Stand-Alone DICE.
Stand-Alone DICE
In a Global Project, both Primary and Secondary DBs can be DICE-checked. This enables the administrator to check a number of Locations to find, for example, a valid version of a DB which has been corrupted at its Primary Location. To check a DB at a remote Location, prefix the CHECK command with the REMOTE <loc> command, where <loc> is the Location identifier. For examples, refer to REMOTE.
Note:
Remote checking uses stand-alone DICE.
When a DICE report indicates that buckets have been lost, normally this would require the MDB to be patched. However, in a Global Project, this error is non-fatal if there are working extracts. These DBs are non-propagating and only exist at the Primary Location of their extract owner. This results in the error report, since the buckets for working extracts are not accessible at the Primary Location of the MDB.
Examples:
|
CHECK DBS MASTER/DESI MASTER/CATA Checks the integrity of a single named DB or a series of DBs within the Project. Up to ten DBs may be specified in each command. CHECK SYSTEMDB Checks the integrity of the Project’s System DB. In a Global Project, the current administered System DB is checked. |
|
CHECK COMMDB Checks the integrity of the Project’s Comms DB. CHECK MISCDB Checks the integrity of the Project’s Misc DB. CHECK GLOBALDB Checks the integrity of the Project’s Global DB. |
|
CHECK PROJECT Checks the integrity of all DBs in a Project, including the System DB, Comms DB and Misc DB (but not the virgin DBs). The DBs are checked automatically by DICE in the following order:
|
|
CHECK FILES /%TRA000%/tra003 /%TRA000%/tra001 Checks the integrity of one or more DBs by specifying the names of the files in which the DBs are held. Up to ten files may be specified in each command. This version of the command is usually used in stand-alone mode. (A list of DBs in a Project, together with the names of the corresponding files in which they are stored, can be produced by using the LIST FILES command.) |
Note:
If DICE is being used within the AVEVA base product and the CHECK FILES option is used, then no external reference checking can be done for that file and
EXTERNAL NOCHECK will be assumed.
Command Syntax
From an AVEVA base product module:
|
.------<----. |
Note:
All the CHECK syntax except CHECK GLOBALDB can be applied to a remote Location in a Global Project by prefixing the command
by REMOTE <loc>, where <loc> is the Location identifier. Refer to REMOTE for examples.
In stand-alone mode:
|
.-------<------. |
Related Commands: