6 Upgrade Argus Mart

Argus Mart upgrade process has been moved from Schema Creation Tool to Liquibase.Liquibase is a refactoring tool that is utilized to enable a silent installation.

6.1 Prepare for the Database Upgrade

  1. Recreate the Safety RO User of Argus Mart.

  2. Recreate the DB_LINK_ARGUS manually, from Argus Mart to Argus Safety (see Section 2.3.1, "From Argus Mart to Argus Safety (manually).").

6.2 Upgrade the Database

  1. Log in to Argus Mart Web Server.

  2. Navigate to Programs > Oracle > Argus Mart > Database > DBInstaller.

  3. Open DBInstaller.properties file.

  4. Modify the following parameters:

    • Mart Database:

      • db_connect_string—connects to the Argus Mart database.

        Syntax: db_connect_string=<host>:<port>/<SID>

        For example, db_connect_string=server.us.xx.com:1521/AM82MT

        Or, db_connect_string=server.us.xx.com:1521/AM82MT.us.xx.com

      • dba_user—specifies the name of the Install user to run Argus Mart Liquibase Install.

        See Section 2.2.3, "Create the Install User."

    • Mart User of each schema, where password is optional:

      • appschema_sm_mart

      • appschema_sm_stage

      • appschema_sm_app

      • appschema_etl_user

      • appschema_rls_user

      • appschema_bi_user

    • Safety Database:

      • safety_db—Argus Safety database instance name

      • safety_ro_user—Argus Mart read-only user created in Argus Safety

    Note:

    For more information on these parameters, see Section 2.1, "Overview of the dbinstaller.properties file."
  5. From the command prompt, go to DBInstaller directory.

  6. Type dbinstaller.bat, and press Enter.

    The Liquibase upgrade begins, and the parameters (as entered) appear on the command prompt screen with password in the hidden mode (****).

  7. Keep monitoring the Liquibase progress by querying the Liquibase Log table mart_dbchangelog, created in AM_MART_USER schema.

  8. When the process is complete, a confirmation message appears with the latest version of Argus Mart.

  9. Validate Schema using the schema validation control file VLDN_AM_8.2.CTL.

    See Section 2.2.5, "Validate the Schema."