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

Upgrade Database

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJul 22, 2024
  • 4 minute read

The database must first be upgraded to at least version IntelaTrac 5.1.(SP2) prior to upgrading to this version.

Important: The following are some of the important points that you must consider before upgrading to this release:
- You must plan ahead for the upgrades, as database updates are very intensive operations and can take several hours.
- On upgrading from IntelaTrac 5.1 SP2 to this release, the application will not retain the password history data from the earlier releases. This means that after the upgrade, the application will "forget" the earlier passwords of all the users. The current password of the user will continue to work and any password update after the upgrade will be stored in the Password History. To know more about the Password History feature, see the "Configuring Security Settings" topic in the AVEVA Mobile Operator Web Help.

Before You Begin:

  • Before upgrading, we recommend you to create a backup copy of the IntelaTrac 5.1 (SP2) or later databases.

  • Run the Database Report Utility (DBIntegrity.exe file available in the Utilities folder) before the upgrade.

    Running the Database Report utility before upgrade is extremely important, as it will highlight and present solutions to problems that can prevent upgrade script completion, and others that can cause undesired results. Refer to Database Utility Guide for more information on this utility.

  • Copy the DatabaseScript.exe from the "\Products\DatabaseScripts" folder, and all of its contents, from the Installation media to a desired location on the local machine. For more information about Database script, see the topic Database script.

  • Change the compatibility level of the database to SQL server 2016 or higher. For more information, see the Microsoft documentation.

  • We recommend you to use Force Protocol Encryption on the SQL Server. For more information, see the Microsoft documentation on configuring SQL Server Database Engine for encrypting connections.

Steps:

  1. Launch the Database Scripts Installation Utility by double-clicking the ‘DatabaseScript.exe’ from the folder.

  2. On the Run Scripts tab, click the ellipsis button () to the right of the Connection String text field to display the Data Link Properties window

  3. In the Data Link Properties window, on the Provider tab, select Microsoft OLE DB Driver for SQL Server and then click Next.

    Note: If you have not installed the drivers, then download Microsoft OLE DB Driver 18 for SQL Server (x64) from the Microsoft website.

  4. Select All tab and set the value of DataTypeCompatibility to 80.

  5. On the Connection tab, enter the server name as appropriate to SQL. Next, check the box marked Allow saving password.

  6. Click Test Connection, and then click OK to close the Data Link Properties window.

    If the connection is successfully established, a confirmation message appears.

  7. On the Run Scripts tab, from the Install Type section, select Upgrade Database.

  8. Select the upgrade option for upgrading from an earlier version.

    Note: You must have at least IntelaTrac 5,1 (SP2) to upgrade to the current version of 6.0.x.

  9. Select the required language from the Language drop-down box (if not already selected).

  10. Select the required timezone from the Time zone drop-down box.

  11. To run the configured scripts, click the Execute button.

    If the scripts have run successfully, it will return the "Scripts ran successfully." message.

    If errors were encountered during the upgrade, the message will instead state the number of errors that occurred, e.g. "Scripts ran with 2 errors."

    Important: Be sure to check the "Script Trace" tab after running any scripts to check for errors.

    Note:
    - To check for any update issues on AttachedProperties, ConvertSignaturesFromEmfToPng, and MigratePasswordHashes, refer to following files for detail log information and problems:
    - log-AttachedPropertiesMigration.txt: Check this file for any time to process and migration issues for Attached Properties.
    - log-PasswordHashMigrator.txt: Check this file for any migration issues related to passwords.
    - SignatureConversionLog.txt: Check this file for any migration issues related to signature when converting from EMF to PNG format.
    - It is recommend to use SQL Authentication for Database upgrade.

    When the upgrade is successful, you will see the following:

    • All the data and datetime offset are mapped to the selected time zone.

    • In the database, a tenant is added to the ismgt_base table.

    • All the existing data is mapped to the Default Plant.

      After the upgrade, it is recommended to set a strong password for the database. To know the recommendations for setting a strong password, see the topic 'Configuring Security Settings' in the help of the AVEVA Mobile Operator web application.

What's Next?

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