Update the Oracle Analytics database account for Oracle Empirica Topics

You can upgrade Oracle Empirica Topics from version 2025.4.x or a version earlier than 2025.4.01.

Upgrade from a version earlier than 2025.4.01

If your environment does not contain any customizations to the Oracle BI Repository (RPD) or the database schema, Oracle recommends dropping the existing OBIEE_TOPIC_WORKFLOW account and recreating it by following the instructions in Chapter 3Prepare the Oracle Empirica Signal database server for Oracle Analytics.

If your environment includes customizations in the data model or schema, please contact Oracle Consulting for assistance in reapplying them to the default model.

Upgrade from 2025.4.x

1. On the Oracle Empirica Signal application server, unzip the Database.zip file.
2. Execute this step only if you have enabled Signal Review reporting and you are upgrading from 2025.4.01:
   1. Open update_obiee_2025.4.01_to_2025.4.02.sql in a text editor and update the SIGNAL variable if your Signal master database account uses a name other than the default.
   2. Execute update_obiee_2025.4.01_to_2025.4.02.sql in SQL*Plus while connected as the Signal Review reporting user (OBIEE_SIGNAL_MGT). You can connect using the proxy account. For example:

      sqlplus proxy_user[OBIEE_SIGNAL_MGT]@<database conn> @2025.4.01_to_2025.4.02.sql

3. Using a text editor, open the update_obiee_2025.4_to_2026.sql file and modify the following properties as needed for your environment:

   
   DEFINE SIGNAL_ACCT='<Signal account>'; --DEFAULT: WEBVDME
   DEFINE TOPIC_WORKFLOW_ACCT=’<topic workflow account>’; --DEFAULT: TOPIC_WORKFLOW
   DEFINE SIGNAL_OBIEE_USER=’OBIEE_SIGNAL_MGT’; 
   DEFINE TOPIC_OBIEE_USER='OBIEE_TOPIC_WORKFLOW_0'; 
   DEFINE TOPIC_WORKFLOW_CONFIG_ID='0';
   

   Note:

   TOPIC_OBIEE_USER specifies the reporting account associated with a Topic Workflow configuration.

   • If your environment contains multiple Topic Workflow configurations and the reporting accounts follow the naming convention OBIEE_TOPIC_WORKFLOW_<config_id>, set UPDATE_ALL_TOPIC_SCHEMAS='TRUE'. The script will automatically upgrade all matching reporting accounts.
   • If the reporting accounts do not follow this naming convention, leave UPDATE_ALL_TOPIC_SCHEMAS='FALSE' (the default). Then run update_obiee_2025.4_to_2026.sql once for each reporting account, updating the values of TOPIC_OBIEE_USER and TOPIC_WORKFLOW_CONFIG_ID for each execution.
4. In a command prompt window, execute the create_topics_user_obiee.sql script as the Oracle SYS user:

   $ sqlplus sys@<database_server_TNS name> as sysdba
   @update_obiee_2025.4_to_2026.sql

   A password prompt appears.

5. Enter the password for the Oracle SYS account.
6. After the script runs, the update_obiee_2025.4_to_2026.log file is created and can be checked for errors.