Create Fresh Oracle Argus Insight Schema

1. Log in to the 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, server.us.xx.com:1521/AI841MT

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

       See Create the DBA User.

     • default_datafile_directory—default location on the database server, where datafiles will be created.
   • 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_login_user

     Note:

     The appschema_ai_apr_user parameter should not be modified in the dbinstaller.properties file.
   • 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.

   It is recommended that you preserve the default names for tablespaces and roles.

5. From the command prompt, go to DBInstaller directory.
6. Type dbinstaller.bat, and press Enter.

   The Liquibase install 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.

   Note:

   For Oracle Argus Insight 8.4.1 Fresh Schema creation on 19c, if you encounter the error Could not release lock, follow the workaround:

   1. Clear/Release the liquibase lock (login as as_dba_user)
   2. Truncate apr_mart.insight_dbchangeloglock table
   3. Rerun installer.
8. When the process is complete, a confirmation message appears with the latest version of Oracle Argus Insight.

   The following is created as per the values specified in the dbinstaller.properties file:

   • Users
     • MART_USER
     • STAGE_USER
     • MART_APP_USER
     • MART_HIST_USER
     • AI_LINK_USER
     • RLS_USER
     • AI_APR_USER
     • AI_LOGIN_USER
   • Roles
     • AI_ROLE
     • AI_APP_ROLE
     • AI_LINK_ROLE
   • Factory Data
     • Out of the box Factory data is loaded into tables such as ETL_PROCEDURES, CMN_PROFILE_GLOBAL, etc.
   • Database Links, DB_LINK_ARGUS:
     • From STAGE_USER of Argus Insight to INSIGHT_RO_USER of Safety
     • From MART_USER of Argus Insight to INSIGHT_RO_USER of Safety
     • From MART_APP_USER of Insight to INSIGHT_RO_USER of Safety
   • Tablespaces

     Note that the tablespace names begin with APR. The Argus Power Reports (APR) product was renamed to Oracle Argus Insight.

     STAGE Schema Tablespaces	MART Schema Tablespaces	HIST Schema Tablespaces	APR User Tablespaces
     APR_STAGE_DATA_01	APR_MCAS_DATA_01	APR_MCAS_HIST_DATA_01	APR_USER_DATA_01
     APR_STAGE_INDEX_01	APR_MCAS_INDEX_01	APR_MCAS_HIST_INDEX_01	APR_USER_INDEX_01
     APR_STAGE_LOB_01	APR_MCAS_LOB_01	APR_MCAS_HIST_LOB_01	APR_USER_LOB_01
     APR_SESM_DATA_01	APR_MCFG_DATA_01	APR_MFACT_HIST_DATA_01	--
     APR_SESM_INDEX_01	APR_MCFG_INDEX_01	APR_MFACT_HIST_INDEX_01	--
     APR_SESM_LOB_01	APR_MCFG_LOB_01	APR_MCFG_HIST_LOB_01	--
     APR_SWHOC_DATA_01	APR_MEDM_DATA_01	--	--
     --	APR_MEDM_INDEX_01	--	--
     --	APR_MEDM_LOB_01	--	--
     --	APR_MWHOC_DATA_01	--	--

9. Press Exit.