3 Create the Argus Insight Data Mart Structure

3.3.1 Database Parameters

Table 3-1 lists the database parameters and the values that must be set for Argus Insight.

For those parameters that require a numeric value, Table 3-1 lists the minimum value recommended. You may need to increase the value depending on your system configuration and the number of cases. It is the responsibility of the database administrator to monitor the system and adjust the database parameters as necessary.

3.3.2 Database I/O Configuration

3.3.3 Recommended Configuration for the Database Server

3.4.1 Prerequisites

Make sure:

• an Oracle client with Administrator option is installed on the server.

• database TNS entry should be added in the TNSNAMES.ora file.

• login machine user should have administrative privileges.

To install Java:

1. Download the jce_policy-8.zip file on your local machine from the following link:

   .http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html (download jce_policy-8.zip).

2. Unzip the jce_policy-8.zip.

3. Replace local_policy.jar and US_export_policy.jar files present in all the Java JRE installation security folders with the local_policy.jar and US_export_policy.jar shipped in jce_policy-8.zip.

   For example:

   Location of Java JRE 64-bit.

   C:\Program Files\Java\jre1.8.0_161\lib\security

4. From the command prompt verify that Java is properly installed by executing:

   java -version

   If no Java version appears, check the environment variables settings and path system variables have correct Java installation path set.

To set Java Installation Path:

1. Right-click the My Computer (or Computer) icon, and from the drop-down menu select Properties.

2. From the left-pane, select Advanced system settings.

   The System Properties dialog box with Advanced tab appears.

3. In the Startup and Recovery section, click Environment Variables.

4. From the System variables section, scroll-down to Path variable, and double-click.

   The Edit System Variable dialog box appears.

5. In the Variable value: field, enter the location where Java will be installed, and end it with a semi-colon (;).

6. Click OK to close the Edit System Variable dialog box.

7. Click OK to close the System Properties dialog box.

3.4.2 Create Users in the Argus Safety Database

1. To create the Safety Read-only user for Insight, execute the following script from the folder <Argus Release Media>\Database\Argus Insight\Utilities\Create_Safety_Ro_User:

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

   • For Linux—Use the shell script ai_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 Insight

   • Password of the 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. Review the log file from the following path, and check for any errors, when a confirmation message appears.

   <Argus Release Media>\Database\ArgusInsight\Utilities\Create_Safety_Ro_User\AI_AS_RO_User_MMDDYYYY_HH24MISS.log

3.4.3 Create the DBA User

To create a DBA user that has privileges same as the SYSTEM user for installation:

1. Execute the following script from the folder <Argus Release Media>\Database\ArgusInsight\Utilities\Create_Dba_User:

   • For Windows—Use the batch script ai_create_dba_user.bat

   • For Linux—Use the shell script ai_create_dba_user

2. When prompted, enter the following parameters:

   • Argus Insight Database instance name

   • SYS or an equivalent SYSDBA user on this database

   • SYSDBA user password

   • Name of the DBA User—For example, AI_DBA_USER

   • DBA 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:

   Created DBA user &dba_user

3. Press Exit.

4. Verify the log files for status information from:

   <Argus Release Media>\Database\ArgusInsight\Utilities\Create_Dba_User\AI_DBA_User_ MMDDYYYY_HH24MISS.log

DROP USER <INSTALL_USER> CASCADE;

3.4.4 Create Fresh Argus Insight Schema

1. Log in to the 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 Argus Insight database.

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

       For example, server.us.xx.com:1521/AI821MT

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

       See Section 3.4.3, "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_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—Argus Safety database instance name

     • safety_ro_user—Argus Insight Read-only user created in Argus Safety

   Note:

   For more information on these parameters, see Section 3.2, "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.

8. When the process is complete, a confirmation message appears with the latest version of 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 ARGUS_APP of Safety

     • From MART_USER of Argus Insight to ARGUS_APP of Safety

     • From MART_APP_USER of Insight 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.

     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.

3.4.5 Validate the Schema

1. Navigate to <Argus Release Media>\Database\ArgusInsight\ValidateSchema.

2. Run the batch script validate_schema.bat.

3. When prompted, enter the following parameters:

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

   • Enter DBA User Name: <DBA user of Argus Insight>

   • Enter Password for DBA User: <DBA User password in Argus Insight>

   • Enter Validation Data File Name: The validation control file name:

     <VLDN_APR_AI_8.2.1.CTL>

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

     <Argus Release Media\Database\ArgusInsight\ValidateSchema>

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

     <VLDN_APR_AI_8.2.1_diff.log>

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

     <VLDN_APR_AI_8.2.1.log>

4. Enter the password for the Argus Insight SYSTEM or DBA user, and press Enter.

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

   The log files are created at the following location:

   <Argus Release Media>\Database\ArgusInsight\ValidateSchema\

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

3.4.6 Create Argus Insight Read-only User

1. Open <Argus Release Media>\Database\ArgusInsight\Utilities\ Create_Insight_Ro_User file.

   • For Windows—execute the batch script ai_ro_user.bat

   • For Linux—execute the shell script ai_ro_user

2. When prompted, enter the following parameters:

   • Enter TNSNAME Entry to connect to the ARGUS INSIGHT Database: < ARGUS INSIGHT Database name>

   • Enter the name of Custom DBA user in Insight Database: < Argus Insight Install user>

   • Enter password for install user in Insight Database: <Install user password>

   • Enter Mart schema owner name in Insight Database: <Mart User of Insight>

   • Enter Argus Insight History schema owner name in Insight Database: <Mart Hist User of Insight>

   • Enter Read Only user to be created in Insight Database: <Read-only user to be created in Insight>

   • Enter password for Read Only user of Insight Database: <Insight Read-only user password>

3. Press Exit.

4. Verify the log files for status information from:

   <Argus Release Media>\Database\Argus Insight\Utilities\Create_Insight_Ro_User\AI_RO_User_MMDDYYYY_HH24MISS.log

3.5.1 From Argus Safety to Argus Insight Database

This link allows real-time updates of some of the values from Argus Console to Argus Insight data mart.

1. Create the reverse DB Link by executing the script file from <Argus Release Media>\Database\Argus Insight\Utilities\Database_Links\argus_to_mart.

   • For Windows—execute the batch script ai_argus_db_link_setup.bat

   • For Linux—execute the shell script ai_argus_db_link_setup

2. When prompted, enter the following parameters:

   • Enter the Argus Safety Database Tns Name: <Safety Database Instance Name>

   • Enter the name of Argus Safety schema owner in Safety Database Instance: <user account that owns the Argus Safety schema>

   • Enter the password for Argus Safety schema owner: <password of Argus Schema owner>

   • Enter the name of Argus Safety Role: < Argus Safety role>

   • Enter the name of Read only user in Safety Database: <Insight Read-only role, created in Argus Safety>

     For example, <INSIGHT_RO_USER>

   • Enter the Argus Insight Database Tns Name: <Argus Insight database>

   • Enter the name of link user in Insight Database.: <link user of Argus Insight>

   • Enter the password for user Link user: <link user password>

3. Verify that the script is successfully connected as <Safety schema owner/Safety schema password>@<Argus Safety Database Name>, and press Enter.

4. When the confirmation message appears, press Enter.

   Wait until a message Created <Insight DB Global Name> @ARGUS_TO_MART appears. This link name gets stored in the key DB_LINK_ARGUS_TO_MART of CMN_PROFILE_GLOBAL of the Argus Safety database.

5. Press Exit to close the window.

6. Verify the log files for status from:

   <Argus Release Media>\Database\Argus Insight\Utilities\Database_Links\argus_to_mart\ ARGUS_TO_MART_DB_LINK_MMDDYYYY_HH24MISS.log

3.5.2 From Argus Insight to Argus Safety (manually)

During Fresh installation, the database link from Argus Insight 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 <Argus Release Media>\Database\Argus Insight\Utilities\Database_Links\db_link_argus.

   • For Windows—execute the batch script ai_create_db_link_argus.bat

   • For Linux—execute the shell script ai_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 Insight Database instance: <Insight Database Instance Name>

   • Enter the name of DBA User in Insight DB: <Insight dba user>

   • Enter the password for user &dba_user: <Insight dba user pwd>

   • Enter the name of the Read Only User in Safety DB: <Safety Read Only user for Insight>

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

   • Enter the name of the stage owner in Insight: <Stage user of Insight>

   • Enter the password for Stage user: <Stage user password>

   • Enter the name of the mart owner in Insight: <Mart user of Insight>

   • Enter the password for Mart owner: <Mart user password>

   • Enter the name of the mart app owner in &insight_db: <App user of Insight>

   • Enter the password for app owner: <App user password>

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

   Wait until a message Created <Safety DB Global Name> @DB_LINK_ARGUS appears for each Stage, Mart, and App user. This link name is stored in the key DB_LINK_ARGUS of CMN_PROFILE_GLOBAL in the Argus Insight database.

   For example, a typical DB link is:

   • SAF821DB@DB_LINK_ARGUS

   • SAF821DB.US.CORP.COM@DB_LINK_ARGUS

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

5. Verify the log files for status from:

   <Argus Release Media>\Database\Argus Insight\Utilities\Database_Links\db_link_argus\DB_LINK_ARGUS_MMDDYYYY_HH24MISS.log