Learn about Database Integrity Utility
- Last UpdatedMar 03, 2025
- 1 minute read
Lists improper or invalid data within the AVEVA Mobile Operator database that may cause problems with operation of the current version or with the upgrade process. Where possible, the recommended solution for each problem in the following list, which is sorted in alphabetical order, is provided.
Note: If a listed "Resolution" involves a SQL command that returns the error "Subquery returned more than 1 value…" then you must disable the triggers in the table affected by the query in order
to successfully run the SQL command.
For example, the "Resolution" for the "Procedures with invalid (Dup Refs) chains"
causes the error quoted above. The command begins with "update ismgt_profiles," so
we will open the ISMGT_PROFILES table and disable its triggers.
To do so, open SQL Server Management Studio and connect to the database. Expand ISMGT_PROFILES
and its list of triggers.
Right-click each trigger listed and select Disable. Then, run the SQL command again.
If it succeeds, you may proceed with any remaining "Resolution" steps before re-enabling
the trigger(s).
If it fails, or if you are uncomfortable taking the above steps, contact Technical
Support for assistance.
Related Links
- Active Directory Users with Local Password
- Assets - Duplicate names
- Bad Data In Work Request Items
- Deprecated Peripheral Integrations
- Identify and Fix the Procedures Linked to ‘All Bases’
- Identify and Update Invalid Parent Group Of Tasks
- Indexes - Remove indexes and statistics prior to upgrade
- Imported Assets with No Application Item ID
- Invalid Artifacts in Procedures - Cross Reference
- Invalid Categories - Cross Reference
- Invalid Crews - Cross Reference
- Invalid Groups - Cross Reference
- Invalid Roles - Cross Reference
- Invalid Shift Groups - Cross Reference
- Invalid Settings Not Belonging To Standard
- Invalid UOM - Cross Reference
- Invalid WOR Response Lists
- List of Tasks Configured with Invalid Datetime Display Formats
- Procedure Conditions - Duplicate Sequence Numbers
- Procedure Revisions with Incorrect Item Count
- ResponseListItems - Duplicate sequence numbers
- Response List Items with Duplicate Application-ApplicationItem
- StatusListItems - Duplicate Sequence Numbers
- Standard settings missed post upgrade to Enterprise version
- Standard settings missed in prior release (5.1.2 and below)
- Task Group and Task Item - Duplicate Sequence Numbers
- WOR Fields Application Item ID - Value configured is missing in Response List table