CHECK (Data Integrity Checking)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : CHECK (Data Integrity Checking)

Function:

Starts the integrity checking of the databases specified.

Description:

•

Using the CHECK command from within an AVEVA E3D™ project, you can check:

•

The System, Miscellaneous and Comms databases

•

One or more named databases

•

All the databases in a project

For information about using DICE (the AVEVA E3D™ Data Integrity Checker) as a stand-alone program, see Stand-Alone DICE.

Stand Alone DICE

In a Global Project, both Primary and Secondary databases can be DICE checked. This enables you to check a number of locations to find, for example, a valid version of a database which has been corrupted at its primary location. To check a database at a remote location, prefix the CHECK command with REMOTE <loc> command, where <loc> is the Location identifier. See the REMOTE command for examples.

Note:

Remote checking uses stand-alone DICE.

When a DICE report indicates that buckets have been lost, normally this would require the master database to be patched. However in a global project, this error is non-fatal if there are working extracts. These databases 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 master db.

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: The System DB The Comms DB The Misc DB The user-accessible DBs, which are checked team by team
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 AVEVA E3D™ 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 E3D™ module:


.------<----. / \| >- CHEck -+- DBs --*-- dbname ---+----------------------------------. \| \| \|- SYStemdb ----------------------------------------------\| \| \| \|- GLOBaldb ----------------------------------------------\| \| \| \|- COMMdb ------------------------------------------------\| \| \| \|- MISCdb ------------------------------------------------\| \| \| ‘- PROject -----------------------------------------------+->

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. See the REMOTE command for examples.

In stand-alone mode:


.-------<------. / \| >--- CHEck --- FIles --*--- filename ---+--->

Related Commands:

CHECKOPTION