Upgrade Database

  1. Log in to Oracle Argus Insight Transaction Server.
  2. Navigate to Argus Release Media\Database\Argus Insight.
  3. Open the dbinstaller.properties file.
  4. Modify the following parameters:
    • Insight Database:
      • db_connect_string—connects to the Oracle Argus Insight database.

        Syntax: db_connect_string=<host>:<port>/<service name>

        For example, db_connect_string=Dbname.us.xx.com:1521/AI823MT

        Or, db_connect_string=Dbname.us.xx.com:1521/AI823MT.us.xx.com

      • dba_user—specifies the name of the DBA user to run Oracle Argus Insight Liquibase Install.

        See Create the DBA User.

    • Insight User of each schema, where password is optional:
      • appschema_mart_user
      • appschema_stage_user
      • appschema_mart_app_user
      • appschema_mart_hist_user
      • appschema_ai_link_user
      • appschema_rls_user
      • appschema_ai_apr_user
      • appschema_ai_login_user
    • Insight Roles:
      • ai_role—specifies Mart User roles
      • ai_app_role—specifies App User roles
      • ai_link_role—specifies Link User roles
    • Secure Key:
      • argus_securekey_path—path of the file insight.ini in the middle-tier machine from where the DBInstaller.bat is executed.
    • Safety Database:
      • safety_db—Oracle Argus Safety database instance name
      • safety_ro_user—Oracle Argus Insight Read-only user created in Oracle Argus Safety

    Note:

    For more information on these parameters, see Configure 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 insight_dbchangelog, created in APR_MART schema.
  8. When the process is complete, a confirmation message appears with the latest version of Oracle Argus Insight.
  9. Validate Schema using the schema validation control file VLDN_APR_AI_8.2.3.CTL.