Apply upgrade scripts to Oracle Empirica Signal 9.1.x schemas (upgrade only)

Schema upgrade is incremental. If you are upgrading from a version prior to Signal 9.2.3.x, multiple scripts need to be executed.

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

1. If you use the Oracle Empirica Topics feature, perform the following steps to upgrade the Oracle Empirica Topics schema:
   • If you are upgrading from Signal 9.1.x:
     1. Using a text editor, open the update_twc_9_1_to_9_2.sql file.
     2. Update WEBVDME_ACCOUNT and TOPIC_WORKFLOW_USER.
     3. As the SYS database user, execute the update_twc_9_1_to_9_2.sql script to update TWC schema from 9.1.x to 9.2, for example:

        $ sqlplus SYS@<TNS_NAME> as sysdba @update_twc_9_1_to_9_2.sql

        A password prompt appears.

     4. Enter the SYS database account password.
     5. Once the execution completed, verify update_twc_9_1_to_9_2.log.
2. Perform the following steps to upgrade database schemas to 9.2.0.
   1. Navigate to the Database folder, for example:
      $ cd /u01/stage/Database
   2. Using a text editor, open the update_9_1_to_9_2.sql file.
   3. Update WEBVDME_USER and TOPIC_WORKFLOW_USER to actual value.
   4. As the SYS database user, execute the update_9_1_to_9_2.sql script to update the schema from 9.1.0.x to 9.2, for example:
      $ sqlplus SYS@<TNS_NAME> as sysdba @update_9_1_to_9_2.sql

      A password prompt appears.

   5. Enter the SYS database account password.
   6. Once the execution completes, verify that there are no errors in the log files update_9_1_to_9_2.log and update_all_smcs.log.

      Note:

      When verifying the logs, ignore any messages caused by dropping an object that does not exist, such as User or role 'DATA_ADMIN' does not exist.
3. Perform the following steps to upgrade database schemas to 9.2.1.
   1. Navigate to the Database folder, for example:
      $ cd /u01/stage/Database
   2. As the WEBVDME database user, execute the update_9_2_to_9_2_1.sql script to update the schema from 9.2.0.x to 9.2.1, for example:
      $ sqlplus webvdme@<TNS_NAME> @update_9_2_to_9_2_1.sql

      A password prompt appears.

   3. Enter the WEBVDME database account password.
   4. Once the execution completes, verify that there are no errors in the log files update_9_2_to_9_2_1.log and update_all_smcs.log.
4. Perform the following steps to upgrade database schemas to 9.2.2.
   1. Navigate to the Database folder, for example:
      $cd /u01/stage/Database
   2. Using a text editor, open the update_9_2_1_to_9_2_2.sql file.
   3. Update WEBVDME_USER to actual value.
   4. As the SYS database user, execute the update_9_2_1_to_9_2_2.sql to update the schema from 9.2.1.x to 9.2.2, for example:
      $sqlplus SYS@<TNS_NAME> as sysdba @update_9_2_1_to_9_2_2.sql
      A password prompt appears.
   5. Enter the SYS database account password.
   6. Once the execution completes, verify that there are no errors in any of the log files, such as update_9_2_1_to_9_2_2.log.
5. Perform the following steps to upgrade database schemas to 9.2.3.
   1. Navigate to the Database folder, for example:
      $cd /u01/stage/Database
   2. Using a text editor, open the update_9_2_2_to_9_2_3.sql file.
   3. Update WEBVDME_USER to actual value.
   4. As the SYS database user, execute the update_9_2_2_to_9_2_3.sql to update the schema from 9.2.2.x to 9.2.3, for example:
      $sqlplus SYS@<TNS_NAME> as sysdba @update_9_2_2_to_9_2_3.sql
      A password prompt appears.
   5. Enter the SYS database account password.
   6. Once the execution completes, verify that there are no errors in any of the log files, such as update_9_2_2_to_9_2_3.log.
6. Perform the following steps to upgrade database schemas to 2025.4.01.
   1. Navigate to the Database folder, for example:
      $cd /u01/stage/Database
   2. As the WEBVDME database user, execute the update_9_2_3_to_2025_4_01.sql script to update the schema from 9.2.3 to 2025.4.01, for example:

      $ sqlplus webvdme@<TNS_NAME> @update_9_2_3_to_2025_4_1.sql

      A password prompt appears.
   3. Enter the WEBVDME database account password.
   4. Once the execution completes, verify that there are no errors in any of the log files, such as update_9_2_3_to_2025_4_1.log