Administrator User Guide
Data Integrity Checking : Using DICE : Using the Patch Option
Using the Patch Option
By default, DICE checks the integrity of the selected database(s), but does not attempt to correct any inconsistencies that it may find. Some errors reported by a DICE check can be corrected by using the PATCH option. Such errors are reported as FATAL STRUCTURAL ERRORS. However, if Attempt to patch database problems is check marked (which sets this option to ON) then certain inconsistencies are corrected automatically. For example:
•
When a child extract recorded in the system database is not listed in the database header, the extract is added to the database header.
•
When a child extract is listed in the database header but not recorded in the system database, the extract is removed from the database header.
•
When a claimed element is not recorded as claimed in the parent extract’s claim list, the element is claimed from the parent extract.
•
When an element that is not claimed is recorded as claimed in the parent extract’s claim list, the element is released in the parent extract.
•
When an element is recorded as being claimed to an extract that is not a child extract, the element is released.
•
Too many members in a LIMBOSPEC in a catalogue database.
In these cases, the error message is written as a warning. If the patch is successful, this will then be followed by a message indicating the corrective action that has been taken. If the attempt to patch fails for any reason (for example, if it is not possible to obtain write access to the database) then an error message indicating this will be written instead.
Note:
DICE may report inconsistencies in Global projects when things are out of synchronisation. Usually these are flagged as being acceptable in a Global project. However databases are more likely to need patching in a Global project.
Note:
Any list of patchable DICE errors is always going to be incomplete. And unfortunately we not infrequently come across problems which cannot be resolved by either Patch or Reconfiguration.
Limitations of the Patch option
The Patch option will not resolve inconsistencies arising from operations on an extract hierarchy, such as EXTRACT FLUSH. These should be resolved using appropriate Extract control utilities (EXTRACT FLUSH, EXTRACT DROP, EXTRACT ISSUE etc).
Not all structural problems can be resolved using the Patch option. Some problems require the database to be reconfigured.
AVEVA support should be contacted if a problem persists after suitable corrective action has been taken.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo