Using Data Checker and Setting Up One-Click Maintenance

Data Checker

Use the Data Checker to validate the quality of your industry model data. For example, define any set of consistency checks that can be executed after data has been imported into an industry model.

Data Check is available for Oracle enterprise industry models only. It is not supported for SQL Server or for file-based industry models.

You can start the data checker either manually on demand or on a scheduled basis. For example, you run a set of checks when you are ready to change the job state.

When you start the Data Checker, the result of the checks is displayed in the feature explorer, for example, features with wrong or inconsistent data. Optionally, you generate a report that logs the inconsistencies.

In a scheduled mode, the result is provided as a report that is sent via email to a specified recipient. Then, you can resolve the conflicts on the whole.

One-Click Maintenance

The 1-Click Maintenance tool runs several basic industry model database maintenance checks in one click. We recommend that you use this tool to check your industry models on a regular basis.

Note: Some of these checks are also available in the data model explorer from the Industry Model node context menu. See Industry Model Context Menu.

1-Click Maintenance performs all or a selection of database checks, and automatically fixes issues as shown in the following table.

Invalid Database Objects	Detects and recompiles invalid database objects, such as triggers and views.
Dictionary	Fixes or removes invalid entries in TB_DICTIONARY.
Indices And Constraints	Checks the naming of the indices and constraints.
Spatial Configuration	Creates valid spatial indices and meta data for all feature classes.
TB_UFID	Cleans up TB_UFID, and adds missing FIDs.
Sequences	Fixes the NextVal of the system sequences.
Form Check	Removes unnecessary forms and controls.
Gather Statistics	Renews the statistics of feature classes and tables. Industry Model node > Optimization > Optimize Feature Classes
Log Tables	Cleans up the system log tables.
Database Checks Without Fixing Capabilities
Report Check	Checks whether the scriptcode that is used in reports is valid.
Geometry Validation	Validates the geometries of all feature classes. Detected issues cannot be fixed automatically.
View Definition	Checks whether the feature classes based on views are defined correctly. Detected issues cannot be fixed automatically.

Steps in this workflow: