Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Mobile Operator

TABLE OF CONTENTS

Run the Database Utility

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJan 21, 2025
  • 4 minute read

You can perform the following steps to run the Database Integrity utility against the database.

  1. From the Installation media, navigate to the Utilities folder and copy the DBIntegrity folder to your machine.

  2. Run the utility.

  3. When prompted, provide the following details:

    1. Database Server

    2. Database Name

    3. Username

    4. Password

The following sql scripts automatically run as part of the integrity report.

  • MissedStandardSettings.sql: This script will list the number of systems settings that were missed in the earlier or current version of IntelaTrac (5.1.2). For more information, see the topic Standard settings missed in prior release (5.1.2 and below).

  • InvalidArtifactsinProcedures_CrossReference.sql: This script will provide list of broken links between UOM and Procedures. For more information, see the topic Invalid Artifacts in Procedures - Cross Reference .

  • InvalidCategories_CrossReference.sql: This script will verify the cross-references have been corrected. For more information, see the topic Invalid Categories - Cross Reference.

  • InvalidCrews_CrossReference.sql: This script will run to check if the Crews are associated with Shift Groups in other Plants, or used by a procedure that belongs to another plant. For more information, see the topic Invalid Crews - Cross Reference.

  • InvalidGroups_CrossReference.sql: This script will run to check if the Groups are associated with Group Permissions and Roles in other Plants. For more information, see the topic Invalid Groups - Cross Reference.

  • InvalidRoles_CrossReference.sql: This script will run to check if the Roles are associated with Users and User Groups in other Plants. For more information, see the topic Invalid Roles - Cross Reference.

  • InvalidShiftGroups_CrossReference.sql: This script will run to check if the Shift Groups are associated with Bases in other Plants or if any Shift Groups are used in Procedures in other Plants. For more information, see the topic Invalid Shift Groups - Cross Reference.

  • InvalidSettings_NotBelongingToStandard.sql: This script will list the number of system settings that are not created by AVEVA Mobile Operator. For more information, see the topic For more information, see the topic Invalid Settings Not Belonging To Standard

  • InvalidUOM_Procedures_CrossReference.sql:This script will return invalid procedure which has broken links between UOM and tasks in procedures. For more information, see the topic Invalid UOM - Cross Reference.

  • InvalidWORResponseLists.sql: This script will run to check the WOR Template Questions referencing multiple response lists with the same name. For more information, see the topic Invalid WOR Response Lists .

  • IdentifyAndUpdateInvalidParentgroupOfTasks.sql: This script will identify the incorrect parent group listed for a task in a report (SSRS and Auditor Plus) and will correct the report automatically. For more information, see the topic Identify and Update Invalid Parent Group Of Tasks .

  • FindWORFieldsWithInvalidResponseList.sql: This script will return the list of Work Order Request Template questions referencing the invalid Response lists. For more information, see the topic WOR Fields Application Item ID - Value configured is missing in Response List table.

  • FindTaskConfiguredWithInvalidDisplayFormats.sql: This script lists all procedures having tasks configured with deprecated datetime display formats. For more information, see the topic List of Tasks Configured with Invalid Datetime Display Formats.

  • FindResponseListNItemWithDuplicateApplicationIdNApplicationItemId.sql: This script will return the response list items having duplicate application or application item ID. The response lists with blank ID might cause issues during imports. You must manually fix the items with duplicate application or application item ID. For more information, see the topic Response List Items with Duplicate Application-ApplicationItem.

  • FindImportedAssetsWithNoApplicationItemId.sql: This script will return list of assets with blank application item ID in the database. The assets with blank ID might cause issues during imports. You must manually fix the assets having blank application item ID. For more information, see the topic Imported Assets with No Application Item ID .

  • FindDeprecatedPeripheralIntegrations.sql: This script will return list of Procedures that are using the deprecated peripherals. For more information, see the topic Deprecated Peripheral Integrations.

  • EnterpriseStandardSettingsMissed.sql: This script will list the number of system settings that were missed when upgrading to the current version of AVEVA Mobile Operator 2020 and the system settings that have no value. For more information, see the topic Standard settings missed post upgrade to Enterprise version.

  • DuplicateAssetsDBIntegrity.sql: Provides a list of duplicate Assets in all the Plants. For more information, see the topic Assets - Duplicate names.

  • DuplicateSequenceNumbersProcedureConditions.sql: Provides a list of Procedure Conditions that contain duplicate sequence numbers. For more information, see the topic Procedure Conditions - Duplicate Sequence Numbers.

  • DuplicateSequenceNumbersStatusListItems.sql: Provides a list of Status List items that contains duplicate sequence number. For more information, see the topic StatusListItems - Duplicate Sequence Numbers.

  • DuplicateSequenceNumbersResponseListItems.sql: Provides a list of Response List items that contains duplicate sequence number. For more information, see the topic ResponseListItems - Duplicate sequence numbers.

  • DuplicateSequenceNumbersTaskGroupAndItems.sql: Provides a list of Tasks or Task Group items that contains duplicate sequence number. For more information, see the topic Task Group and Task Item - Duplicate Sequence Numbers.

  • CaptureIndexesAndStatistics.sql: This script will capture the Indexes and Statistics that are not owned by AVEVA Mobile Operator. For more information, see the topic Indexes - Remove indexes and statistics prior to upgrade.

  • BadDataInWorkRequestItems.sql:This script will identify the bad data in work request items table. For more information, see the topic Bad Data In Work Request Items.

  • AllBasesProcedures.sql: This script will identify the Procedures that are linked to 'All Bases'. For more information, see the topic Identify and Fix the Procedures Linked to ‘All Bases’.

  • ADUserWithLocalPassword.sql: This script provides a list of Active Directory users using local password to access AVEVA Mobile Operator. For more information, see the topic Active Directory Users with Local Password.

TitleResults for “How to create a CRG?”Also Available in