11 Install Argus Safety Database

11.1.1 Prepare to Install Schema Creation Tool

11.1.2 Install the Schema Creation Tool

1. Log in as the Administrator on the system where Argus Safety is being installed.

2. Copy the installation package to the local directory of the target machine.

3. Open the Argus Safety folder and click setup.exe.

4. In the Argus Safety Setup screen and click Next >.

   The Argus Safety Solution Components dialog box appears.

5. Select the Schema Creation Tool and click Next.

   The Setup Status screen appears with the installation progress.

   When the installation process is complete, the Setup Completed screen appears.

6. Click Finish.

   The required files are copied to the system.

7. Click OK to reboot the system.

8. For silent install use DBInstaller.zip shipped with the software.

11.1.3 Run Create DBA User Script

You must run the Create DBA User scripts to create a new DBA user or grant required privileges to the existing DBA or SYSTEM user. Use this new DBA user account when running the Schema Creation Tool to create the Argus Safety Schema.

The DBA user created by this script can perform the actions as done by the SYSTEM user. All the manual grants which used to be assigned to the SYSTEM user (prior to the Argus Safety 8.1 release), are now part of this script. The term SYSTEM mentioned in this chapter can be replaced with the new DBA user. If you use the newly created DBA User to execute the Argus Safety Schema Creation Tool functionalities (such as Schema Creation, Upgrade), then the Validation File might display extra or missing privileges for the SYSTEM or the newly created DBA user.If you do not wish to create a new DBA user, you may enter SYSTEM when running the script.

To create the DBA user:

1. From the command prompt, run the batch file:

   C:\Program Files (x86)\Oracle\Argus\DBInstaller\Utilities\Create_Dba_User\create_dba_user.bat

2. Enter the following parameters:

   1. TNSName of the database where the Schema Creation Tool will be run

   2. SYSDBA username

   3. Password for SYS account

   4. Name for the new DBA User account that will be created

   5. Password for the new account

3. Follow the remaining steps to complete the script.

4. You may also run the script from the DBInstaller.zip:

   • For Windows—execute the script from DBInstaller.zip\Utilities\Create_Dba_User\create_dba_user.bat

   • For Linux—execute the script from DBInstaller.zip\Utilities\Create_Dba_User\create_dba_user

11.1.4 Create Tablespaces (Optional)

The schema creation tool creates the tablespaces if they do not exist with default parameter settings.

You can create tablespaces as per your parameter requirements before installing Argus Safety. The following is the list of tablespaces that is required for the Argus Safety installation:

11.1.5 Prerequisites to Create the Schema

• Create the Cryptographic Key, refer to the chapter Argus Password Management—Cryptography Tool.

• The Schema Creation Tool is installed.

• A blank Oracle database instance is available.

• A DBA-privileged or a SYSTEM user account is available.

• The Oracle database is available from the machine where the schema creation tool is installed.

• Java is installed and JCE policy is applied. See Section 11.1.1.2, "Install Java."

• Set database semantics to CHAR.

  The Argus Safety Database requires the Database semantics to be CHAR and not BYTE. Follow the steps below:

  1. Log in to the database as the SYS user.

  2. Execute: ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR SCOPE=BOTH;

  3. Shutdown and Startup the database after applying the above statement.

11.1.6 Validate the Database Setup Properties File

Make sure the dbinstaller.properties file that contains the information for the Argus Safety Database setup has correct data. If not, edit the file.

The file is located on the database server at C:\Program Files (x86)\Oracle\Argus\DBInstaller.

• #DB Connection Details

  • db_connect_string=<host name>:<port>/<db name>

  • dba_user=<argus dba user or system user>

• #Application Type

  • application_type=MULTI (for multi-tenant setup) or SINGLE (for single-tenant setup)

  • enterprise_name=DEFAULT

  • enterprise_short_name=DEFAULT

• #Complete path of Argus Secure Key ini file

  • argus_securekey_path=C:/windows

  • url—URL for the database connection

  • dbaUser—SYSTEM or DBA privileged user

• #Argus DB Schemas—Schema Name and Password (optional). If the password is left blank, it will be prompted at run-time.

  • To prompt for each password on the screen:

    • appSchema_argus_schema=argus_app

    • appSchema_argususer=argususer

    • appSchema_argus_login=argus_login

    • appSchema_vpd_schema=vpd_owner

    • appSchema_bip_schema=bip_owner

    • appSchema_esm_login=esm_login

    • appSchema_esm_schema=esm_owner

    • appSchema_esmquery_schema=esm_query

    • appSchema_dlp_schema=dlp_owner

    • appSchema_dlp_esmquery_schema=dlp_esm_query

  • To avoid prompt for each password on the screen, set up the password as the login password for each user:

    • appSchema_argus_schema=argus_app/<password>

    • appSchema_argususer=argususer/<password>

    • appSchema_argus_login=argus_login/<password>

    • appSchema_vpd_schema=vpd_owner/<password>

    • appSchema_bip_schema=bip_owner/<password>

    • appSchema_esm_login=esm_login/<password>

    • appSchema_esm_schema=esm_owner/<password>

    • appSchema_esmquery_schema=esm_query/<password>

    • appSchema_dlp_schema=dlp_owner/<password>

    • appSchema_dlp_esmquery_schema=dlp_esm_query/<password>

• #Argus DB Roles—Enter the names of the database roles you need to be required. If this is an upgrade, list the roles under For upgrade. If this is a fresh installation, enter the roles under For the new setup in the file.

• #Argus Data Tablespaces—Define the tablespace and datafile details.

  Similarly ESM and DLP sections Define Data and Index datafiles.

• #Default and Temporary table spaces

  • default_ts=USERS

  • temp_ts=TEMP

• #TableSpace parameters

  • tablespace_encryption=<blank>

  • tablespace_initial_size=10M

  • tablespace_autoextend=ON

  • tablespace_next_size=10M

  • tablespace_block_size=8K

  • securefile=<blank>

• #Logging level parameters

  • log_level=info

    Logs the entire history of changes applied to the database. This is the default value.

  • log_level=debug

    Logs the entire history of changes applied to the database along with additional debug information.

11.1.7 Create the Schema on Windows from the User Interface

1. Open the schema creation tool and click Create/Upgrade DB.

   The Database Installer dialog box appears.

   
   

2. Enter the parameters and click Next Step.

   Argus Safety - Database Setup screen appears.

   
   

3. Enter the parameters, select the Application Type, and click Next.

   • Single Tenant—Select this option to allow the database to support only single tenant. The options to create multiple tenants in the safety system is disabled.

   • Multi-Tenant—Select this option to allows the database to support multiple tenants. Users are able to create multiple tenants using the Global Enterprise setup screens.

4. Create new tablespaces or use the existing tablespaces.

   • Under Complete Path and Data File Name, enter the database server path (complete path including the filename) where the data file is placed.

     Instead of entering path for each tablespace, you can set up a common folder path. To do so, in the text box, enter the datafile folder path, and click Set Datafile Folder.

     
     

   • If the data file does not exist, the system creates a data file.

   • If the data file exists, to use the current data file, click Yes in the confirmation dialog box.

     Note:

     When you have existing tablespaces, you may use them; you are not required to create new ones. The system will not regenerate the tablespaces.

   • Click Next.

5. Verify the Setup Parameters and click Execute.

   When execution is complete, a message appears in the Execution Log on screen 3 - Liquibase Update Successful.

6. To view the execution status or errors, open the schema creation log file with the latest timestamp from:

   C:\Program Files (x86)\Oracle\Argus\DBInstaller\logs

11.1.8 Create the Schema on Windows from a Batch file

1. Make sure the dbinstaller.properties are set up correctly. (See Validate the Database Setup Properties File.)

2. From Start menu, select Run, type cmd, and click OK.

3. In the command prompt, go to the following path:

   cd C:\Program Files (x86)\Oracle\Argus\DBInstaller
   

4. Type DBInstaller.bat and press Enter.

5. Monitor the execution log and progress on the running window.

6. To view the log file, go to:

   C:\Program Files (x86)\Oracle\Argus\DBInstaller\logs

11.1.9 Create the Schema on Linux or Unix

1. Make sure the dbinstaller.properties are set up correctly.

   (See, Validate the Database Setup Properties File.)

2. Copy the DBInstaller.zip file in the DBInstaller directory.

   You must have privileges to execute and create files in this directory and /tmp directory.

3. Unzip the DBInstaller. zip file in the same directory.

4. Open a terminal, log in as the Argus Safety DBA user, and execute the following command:

   cd <path>/DBInstaller

5. Type DBInstaller and press Enter.

6. Type the DBA user password and press Enter.

7. View logs in <path>/DBInstaller/logs.

11.4.1 Validate Argus Safety Database on Windows from a User Interface

1. From the Schema Creation Tool, click Schema Validation.

2. Enter the SYSTEM or DBA user password, the database name, and click OK.

3. In the Schema Validation dialog box:

   1. Validate the values in the fields.

   2. In the Validation CTL File section, click Browse to open the Selection Path for CTL File dialog box.

4. Locate and select the correct folder and CTL file for the database being validated, and click OK.

5. In the Validation Log Files section, and click Browse to open the Selection Path for Creating Log Files dialog box.

6. Choose the folder where you want the system to create the log files and click OK.

7. Click Validate Schema.

8. On the command prompt, press Enter.

9. On the Oracle Sql*Plus window, press Enter.

10. Note the path of the log files created during processing.

11. Exit from the Schema Creation Tool.

12. Check the files for errors.

11.4.2 Validate Argus Safety Database on Windows from a Batch file

1. From Start menu, select Run, type cmd, and click OK.

2. In the command prompt, go to the following location:

   C:\Program Files (x86)\Oracle\Argus\DBInstaller\SchemaValidation

3. Type SchemaValidation.bat and press Enter.

4. Enter the following parameters:

   1. TNSNAMES entry to connect to the Argus database: <AS812DB>

   2. DBA username in Argus database: <argus_dba>

   3. Password for the DBA user

   4. Validation CTL file [Example VLDN_812.CTL]

   5. Log files folder: <full path to log files folder, for example C:\Program Files (x86)\Oracle\Argus\DBInstaller>

   6. Schema difference log file [Default SV_Schema_Diffs_qcas8003.log]

   7. CTL loader log file [Default SV_CTLFile_qcas8003.log]

5. Check the log file for errors.

11.4.3 Validate Argus Safety Database on Linux or Unix

1. Copy the DBInstaller.zip file in your Linux or Unix directory.

   You must have privileges to execute and create files in this directory and /tmp directory.

2. Unzip the DBInstaller. zip file in the same directory.

3. Open a Linux or Unix terminal, and execute the following command:

   cd <path>/DBInstaller

4. Type SchemaValidation and press Enter.

5. Type the DBA user password and press Enter.

6. View logs in <path>/DBInstaller/logs.

11.5.1 Prerequisites

Before enabling or disabling DLP, make sure that:

• the Schema Creation Tool is installed

• an Oracle Argus database instance is available

• a DBA-privileged user or a SYSTEM user account is available

• the dlpsetup.properties is correctly updated

11.5.2 Enable DLP

• For Windows, execute the enableDLP.bat file from:

  C:\Program Files (x86)\Oracle\Argus\DBInstaller\Utilities\DLP_Setup

• For Linux or Unix, execute the enableDLP shell script

11.5.3 Disable DLP

Make sure that no one is logged on to the Argus Safety database before beginning the Disable DLP procedure.

• For Windows, execute the disableDLP.bat file from:

  C:\Program Files (x86)\Oracle\Argus\DBInstaller\Utilities\DLP_Setup

• For Linux or Unix, execute the disableDLP shell script

11.6.1 Set Up the Base Database

1. Set up an Argus Safety 8.1.2 multi-tenant or single-tenant database.

   Enable DLP on the Argus Safety 8.1.2 database from Schema Creation Tool > Argus DLP. This sets up the initial DLP infrastructure on the Argus database for all existing enterprises.

2. Validate the schema from Argus Safety 8.1.2 Schema Creation Tool > Schema Validation by selecting the compatible CTL file.

   If any MISSING object exists in schema validation log, fix it before proceeding to the next step.

3. Populate new Argus Safety cases into the existing enterprise of a DLP enabled multi-tenant or single-tenant Argus Safety system from a non-DLP system.

   Or, create new enterprise in a DLP enabled multi-tenant Argus Safety system using data migration or merge to multi-tenant utility.

11.6.2 Enable DLP on Specific Enterprise or Delta Cases

To enable DLP on a specific enterprise or delta cases in a specific enterprise, make sure that you use the correct login credentials and set up the appropriate enterprise context.

1. Extract the custom DLP Enable Enterprise Specific script from the following location into a machine's local folder where Argus Safety 8.1.2 is installed:

   C:\Program Files\Oracle\Argus\DBInstaller\Utilities\DLP_Enable_Enterprise_Specific

2. Double-click DLP_Enable_Enterprise.bat from:

   C:\Program Files\Oracle\Argus\DBInstaller\Utilities\DLP_Enable_Enterprise_Specific\Argus\DLP\

   This batch file execution handles the following scenarios to populate DLP data on newly created Argus Safety cases:

   • process all cases merged in Argus Safety system due to creation of new enterprise by merge process

   • process of delta cases merged in an enterprise due to any migration activity

3. Enter a name and location for the log file.

   For example, DLP_Enable_Enterpirse_Specific.log

4. Enter values at the prompts.

   A confirmation message appears.

5. Press Enter.

   The values you entered are displayed.

6. Verify that the details entered are correct and press Enter.

7. Check the log file for errors. If there are errors, the execution process pauses. Fix the errors and continue the process from another SQL window.

8. Check the log file to see if there are any Argus Safety cases missing in DLP.

   \DLP_Enable_Enterprise_Specific\Argus\DLP\DLP_ENABLE_Missing_Cases_in_DLP_log.log

11.6.3 Validate the Schema

After enabling DLP Enterprise Specific to Argus Safety 8.1.2, validate the schema.

1. Double-click on ArgusDBInstall.exe file from C:\Program Files\Oracle\Argus\DBInstaller.

2. Click Schema Validation.

Extra objects related to table DLP_ENABLE_CASE_HISTORY are ignored in schema validation log file.

The following table and related objects are ignored in Schema Validation if Argus Safety 8.1.2 DLP Enabled system with DLP_Enable_Enterprise_Specific scripts is applied:

• Owner—DLP

• Table—DLP_ENABLE_CASE_HISTORY

• Index—PK_DLP_ENABLE_CASE_HISTORY

• Reason for extra object—Objects are part of Enable DLP Enterprise Specific implementation.

11.7.1 Set Up the Copy Configuration Tool

1. The Copy Configuration Tool creates a database directory in order to execute. Make sure to create a physical directory on the database server where export and import dump files are created and copied respectively. The physical path of these directories is required while performing the export and import.

2. Validate Schema on the source database using Schema Validation Tool.

   Make sure that there are no extra or missing objects exist in Schema Validation log file. Messages for extra custom objects created should be ignored.

3. Copy the Copy Configuration Tool utility files recursively from C:\Program Files (x86)\Oracle\Argus\DBInstaller\Utilities\Copy_Config to the C:\CONFIG_EXP_IMP folder.

11.7.2 Use the Copy Configuration Tool

1. Export the Source database by running the batch file and following the prompts:

   C:\CONFIG_EXP_IMP\Data_ExportConfigOnly.bat

2. Copy ArgusSecureKey.ini (working with source database) from the .\Windows folder, and save it with generated source database file.

   In case you do not have ArgusSecureKey.ini, follow the steps listed in the Section 21.2.6, "Reset the Environment if ArgusSecureKey.ini is Lost."

3. Move the dump files generated on the source Database Server (physical path provided while performing the export) to the target Database Server (physical path where import will be done).

4. To perform the import on the client machine, in the Directory Path on DB Server where dump files are placed for import parameter, use the same folder as entered in the DB Directory Path for export dump files while executing the export process for logs.

   Or move the contents of the export logs folder provided to the Directory including full path for log/script files parameter while executing the export process, in the folder being used for the import process for log generation.

5. Create a new database (with or without TDE enabled) using the Schema Creation tool.

6. Import into Target database by running the batch file, and follow the prompts:

   C:\CONFIG_EXP_IMP\Data_ImportConfigOnly.bat

   Ignore any "ORA-28101: policy already exists" errors.

7. Validate Schema on the target database using Schema Validation Tool.

8. Copy ArgusSecureKey.ini from the source database folder and paste it in the .\Windows folder of application server(s) which are intended to be used with the target database.