2 Creating the Argus Mart Database Structure

2.2.1 Pre-requisites

You must check the following settings before you run the Argus Mart installation:

• GLOBAL_NAMES is set to FALSE to enable the Argus Mart application to create the database links.

• NLS_LENGTH_SEMANTICS is set to CHAR for the Argus Mart Schema Creation Tool to run.

• TNS Name for the Argus Safety Database must be present in the Oracle Database Client > tnsnames.ora file at the following path:

  ...\network\admin\tnsnames.ora.

2.2.2 Creating User for the Argus Safety Database

1. To create the Safety Read-only user for Mart, execute the following script from the folder DBInstaller\Utilities\Create_Safety_Ro_User:

   • For Windows—Use the batch script sm_argus_read_only{user}.bat

   • For Linux—Use the shell script sm_argus_read_only{user}

2. When prompted, enter the following parameters:

   • Name of the Safety Database instance

   • Name of DBA User in Safety Database

   • DBA user password in Safety Database

   • Name of the Safety Read Only User to be created for Mart

   • Password of the Safety Read Only User

   • Role to be associated with Safety Read-only User

   • Default Tablespace for Safety Read-only User—For example, USERS

   • Temporary Tablespace for Safety Read-only User—For example, TEMP

   The  process of creating a Safety Read-only user begins.

3. When a confirmation message appears, review the log file and check for any errors from:

   \DBInstaller\Utilities\Create_Safety_RO_User

2.2.3 Creating the Install User

To create an Install user that has privileges same as the SYSTEM user for installation:

1. Execute the following script from the folder DBInstaller\Utilities\Create_Dba_User:

   • For Windows—Use the batch script am_create_dba_user.bat

   • For Linux—Use the shell script am_create_dba_user

2. When prompted, enter the following parameters:

   • Argus Mart Database instance name

   • SYS or an equivalent SYSDBA user on this database

   • SYSDBA user password

   • Name of the Install User—For example, SYSTEM or AM_DBA_USER

   • Install user password

   If you provide a non-existing user name, then the script creates this as a new user, and provides the necessary grants to this user.

   If you provide an already existing user name, then the script provides the necessary additional grants to the existing user.

   When done, a message appears as:

   Install User created.

3. Press Exit.

DROP USER <INSTALL_USER> CASCADE;

2.2.4 Creating Fresh Argus Mart Schema

1. Log in to the Argus Mart Server with administrator privileges.

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

3. Open Dbinstaller\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, server.us.xx.com:1521/AM811MT

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

       See Section 2.2.3, "Creating the Install User."

     • default_datafile_directory—default location on the database server, where datafiles will be created.

   • 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."

   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 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.

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

   • Users

     • AM_MART_USER

     • AM_STAGE_USER

     • AM_APP_USER

     • AM_ETL_USER

     • AM_VPD_USER

     • AM_BI_USER

   • Roles

     • AM_VPD_ADMIN_ROLE

   • Factory Data

     • Out of the box Factory data is loaded into tables such as ETL_SIGNAL_TABLE_MAPPING, RM_CMN_PROFILE_GLOBAL, etc.

   • Database Links, DB_LINK_ARGUS:

     • From AM_STAGE_USER of Argus Mart to ARGUS_APP of Safety

   • Tablespaces

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

     The Schema Creation Tool creates the following tablespaces for the Argus Mart database, when you create Argus Mart schema:

     AM_APP_DATA_01	AM_APP_INDEX_01	AM_APP_LOB_01
     AM_MART_DATA_01	AM_MART_INDEX_01	AM_MART_LOB_01
     AM_STAGE_DATA_01	AM_STAGE_INDEX_01	AM_STAGE_LOB_01

     
     

2.2.5 Validating the Schema

1. Navigate to Database > DBInstaller > ValidateSchema.

2. Run the batch script validate_schema.bat.

3. When prompted, enter the following parameters:

   • Enter instance name: <Argus Mart Database Instance name>

   • Enter DBA User Name: <Install user of Argus Mart>

   • Enter Password for DBA User: <Install user password in Argus Mart>

   • Enter Validation Data File Name: The validation control file name (without the .CTL extension)

     For example, VLDN_AM_8.1.1

   • Enter the destination where the log file is to be placed:

     <C:\AM_811\Database\DBInstaller\ValidateSchema>

   • Enter the log file name for recording the schema differences:

     <VLDN_AM_8.1.1_diff.log>

   • Enter Validation Output File Name: The validation output file name to record the validation progress:

     <VLDN_AM_8.1.1_out.log>

4. Enter the password for the Argus Mart SYSTEM or Install user, and press Enter.

5. When the validation process is complete, a confirmation message appears.

   • To view any schema discrepancies, such as missing objects, use the Difference Log File.

   • To view the list of errors, which occurred during schema validation, use the Output Log File.

2.3.1 From Argus Mart to Argus Safety (manually)

During Fresh installation, the database link from Argus Mart to Argus Safety (DB_LINK_ARGUS) is created as a part of the installation process. However, you can manually recreate the link DB_LINK_ARGUS.

1. Navigate to DBInstaller\Utilities\Create_Safety_RO_User:

   • For Windows—execute the batch script sm_create_db_link_argus.bat

   • For Linux—execute the shell script sm_create_db_link_argus

2. When prompted, enter the following parameters:

   • Enter the name of the Safety Database instance: Safety Database Instance Name

   • Enter the name of the Mart Database instance: Mart Database Instance Name

   • Enter the name of DBA User in Mart DB: Mart Install user

   • Enter the password for user Mart DBA User: Mart Install user password

   • Enter the name of the Read Only User in Safety DB: Safety Read-only user for Mart

   • Enter the password for Read Only user in Safety: Read-only user password

   • Enter the name of the stage owner in Mart: Stage user of Mart

   • Enter the password for Stage user: Stage user password

3. Verify that the script is successfully connected as <Mart Install user/Mart Install user pwd>@<Argus Mart>, and press Enter.

   Wait until a message Created DB_LINK_ARGUS appears for each Stage, Mart, and App user.

4. Press Exit to close the Mart to Argus Database Link Creation window.

5. Verify the log files for status from:

   DBInstaller\Utilities\Create_Safety_RO_UserDB_LINK_ARGUS_MMDDYYYY_HH24MISS.log

2.3.2 From Argus Mart to Argus Insight

1. When Argus Insight and Argus Mart are on different database instances, execute the script from the folder DBInstaller\Utilities\Database_Links\ ai_am_db_link:

   • For Windows—execute the batch script am_insight_db_link_setup.bat

   • For Linux—execute the shell script am_insight_db_link_setup

2. When prompted, enter the following parameters:

   • Enter the Argus Mart Database Instance name

   • Enter the INSTALL user name in Argus Mart, like AM_DBA_USER

   • Enter the password for the above user

   • Enter the Argus Mart application user name, like AM_APP_USER

   • Enter the password for the above user

   • Enter the Argus Mart Schema user name, like AM_MART_USER

   • Enter the password for the above user

   • Enter the Argus Insight Database Name

   • Enter the Argus Insight Application User name, like APR_APP

   • Enter the Password for the above user

   • Enter the Argus Insight Readonly User name, like APR_LINK_USER

   • Enter the Password for the above user

   The process of creating the database links begins.

3. The following database links are created (by dropping the existing links if any, with the same name.

   • DB_LINK_INSIGHT—From Argus Mart AM_APP_USER > Argus Insight APR_APP

   • ARGUS_MART_TO_INSIGHT_MART—From Argus Mart AM_MART_USER > Argus Insight APR_LINK_USER

4. Review the following log file, and check for any errors, when a confirmation message appears.

   MART_TO_INSIGHT_DB_LINK_MMDDYYYY_HH24MISS.log