Install the Oracle Argus Mart signal configuration

You must install the Oracle Argus Mart signal configuration.

Perform these steps using the non-privileged user account on the application server.

1. If it does not already exist on the Oracle Empirica Signal application server, create the following directory:
   /u01/stage/projects
2. Copy the Argus_Prep_3_0_0_1_xxx.zip file from the distribution media to:
   /u01/stage/projects
3. Unpack the Argus_Prep_3_0_0_1_xxx.zip file into a temporary directory, for example:
   $ unzip Argus_Prep_3_0_0_1_xxx.zip -d /u01/stage/projects/

   The /argus_prep subdirectory is created.

4. Navigate to the /argus_prep directory, for example:
   $ cd /u01/stage/projects/argus_prep
5. Execute the following command to give execute permissions to all .sh files:
   $ chmod u+x common/*.sh sigdet/*.sh site/*.sh
6. Navigate to the /argus_prep/sigdet directory, for example:
   $ cd /u01/stage/projects/argus_prep/sigdet
7. Execute the following command to give write permissions to the db directory:
   $ chmod u+w db
8. Execute the main_install_sigmgt.sh script to initiate the installation:
   $ ./main_install_sigmgt.sh < signal database account name >@<TNS_name>

   where < signal database account name > is the Oracle Empirica Signal database user account name, for example, webvdme. <TNS_name> is the TNS name that the application server uses to access the database server.

   A password prompt appears.

9. Enter <password>, where <password> is the Oracle Empirica Signal database user account password.

   A second password prompt appears.

10. Reenter <password>.

    The database tables for the Oracle Argus Mart signal configuration are populated. The install_sigmgmt.log file is created in the sigdet/sigmgt/install/log subdirectory.

    Note:

    If you enter the password incorrectly, an error such as this appears in the install_sigmgmt.log file: Error returned from execution of "sqlplus /NOLOG @db/connect webvdme @db/fetch_next_config_id".

    If the Argus Signal Mgmt project already exists, error messages may appear, including the following:

    ERROR at line 1:ORA-xxxxx: unique constraint (WEBVDME.UC_PROJECTS1) violated

    ERROR at line 1:ORA-xxxxx: table or view does not exist

    ERROR at line 1:ORA-xxxxx: sequence does not exist

    You can disregard these errors.