Upgrade OUAW Components

This page details how to upgrade the database, ETL, admin tool, and dashboard components for Oracle Utilities Analytics Warehouse v2.8.0.2.0.

On this page:

Upgrade the Database Component

This section details the steps to upgrade the Oracle Utilities Analytics Warehouse database component.

Copy and Decompress the Install Media

  1. Download Oracle Utilities Analytics Warehouse v2.8.0.2.0. Oracle Database part file (Oracle Utilities Analytics v2.8.0.2.0. Oracle Database Multiplatform.zip) from Oracle Software Delivery Cloud onto the target database server.  

  2. Create a temporary directory (example: </OUA/temp> for a Linux machine).  This directory (referred to as <TEMPDIR> below) must be located outside any current working Oracle Utilities application environment. All files that are placed in this directory as a part of the installation can be deleted after completing a successful installation.

  3. Unzip Oracle Utilities Analytics Warehouse v2.8.0.2.0. Oracle Database Multiplatform.zip to <TEMPDIR> using any zip utility.

  4. Execute the SQL below before installing the RELADM, MDADM, and DWADM Schemas. This provides the required permissions to the users created.

    Copy
    Usersgrants.sql in <TEMPDIR>/BI2802/Scripts/Usersgrants.sql

Back to Top

Install the RELADM Schema

  1. Log in to the target database server.

  2. Navigate to the temporary directory into which the Oracle Utilities Analytics Warehouse v2.8.0.2.0. Oracle Database Multiplatform zip file was extracted.

    Copy
    cd database/BI2802/RELADM/Install-Upgrade

  3. Review Storage.xml to ensure the RELADM user has quota on the mentioned tablespace in file. If not, edit the file with correct tablespace name. 
  4. Add JAVA_HOME/bin to the PATH variable. 
  5. Set CLASSPATH pointing to the location where OraDBI.jar and all dependency jars exist.

    Copy
    export CLASSPATH=<TEMPDIR>/BI2802/RELADM/Jarfiles/*

  6. Execute the command below. Once complete, the utility creates the RELADM schema and system data definitions.

    Copy
    java com.oracle.ouaf.oem.install.OraDBI -d jdbc:oracle:thin:@<DATABASE SERVER>:<DATABASE PORT>/<ORACLE SERVICENAME>,RELADM,<Password of RELADM User>,,,,,RELADM -l 1,2 -o -q true

    Note: If an error occurs while executing an SQL or another utility, it logs and displays the error message and allows you to re-execute the current step.

  7. To generate database statistics after connecting to sys user, run the statement below:

    Copy
    exec DBMS_STATS.GATHER_SCHEMA_STATS('RELADM')

Back to Top

Install the MDADM Schema

  1. Log in to the target database server.

  2. Navigate to the temporary directory into which the Oracle Utilities Analytics Warehouse v2.8.0.2.0. Oracle Database Multiplatform zip file was extracted.

    Copy
    cd database/BI2802/MDADM/Install-Upgrade

  3. Review Storage.xml to ensure the MDADM user has quota on the mentioned tablespace in file. If not, edit the file with correct tablespace name. 

  4. Add JAVA_HOME/bin to the PATH variable. 

  5. Set CLASSPATH pointing to the location where OraDBI.jar and all dependency jars exist.

    Copy
    export CLASSPATH=<TEMPDIR>/BI2802/MDADM/Jarfiles/*

  6. Execute the command below. When completed, the utility creates the MDADM schema and system data definitions.

    Copy
    java com.oracle.ouaf.oem.install.OraDBI -d jdbc:oracle:thin:@<DATABASE SERVER>:<DATABASE PORT>/<ORACLE SERVICENAME>,MDADM,<Password of MDADM User>,,,,,MDADM -l 1,2 -o -q true

    7. Note: If an error occurs while executing an SQL or another utility, it logs and displays the error message and allows you to re-execute the current step.

  7. To generate database statistics after connecting to sys user, run the statement below:

    Copy
    exec DBMS_STATS.GATHER_SCHEMA_STATS('MDADM');

Back to Top

Install the DWADM Schema

  1. Log in to the target database server.

  2. Navigate to the temporary directory into which the Oracle Utilities Analytics Warehouse v2.8.0.2.0 Oracle Database Multiplatform.zip file was extracted.

    Copy
    cd database/BI2802/DWADM/Install-Upgrade

  3. Review Storage.xml to ensure the DWADM user has quota on mentioned tablespace in file. If not, edit the file with correct tablespace name. 

  4. Add JAVA_HOME/bin to the PATH variable. 

  5. Set CLASSPATH pointing to the location where OraDBI.jar and all dependency jars exist.

    Copy 
    export CLASSPATH=<TEMPDIR>/BI2802/DWADM/Jarfiles/*

  6. Execute the command below. When completed, the utility creates the DWADM schema and system data definitions.

    Copy
    java com.oracle.ouaf.oem.install.OraDBI -d jdbc:oracle:thin:@<DATABASE SERVER>:<DATABASE PORT>/<ORACLE SERVICENAME>,DWADM,<Password of DWADM User>,DWUSER,DWREAD,DW_USER,DW_READ,DWADM -p <Password of  DWUSER>,<Password of DWREAD> -l 1,2 -o -q true

    Note: If an error occurs while executing an SQL or another utility, it logs and displays the error message, allowing you to re-execute the current step.

  7. To generate database statistics after connecting to sys user, run the statement below:

    Copy
    exec DBMS_STATS.GATHER_SCHEMA_STATS('DWADM');

Back to Top

Upgrade the ETL Component

Prerequisites

Before installing the OUAW ETL component, verify the following:

  • Ensure latest Java version (Example: 1.8.391) is installed on the application server.

  • Ensure Oracle Fusion Middleware Infrastructure 12.2.1.4 installation and patches are applied on the target application server.

  • Ensure Oracle Data Integrator (ODI) 12.2.1.4 and patches are applied on the target application server.

  • Ensure GoldenGate MANAGER, JAGENT, PMSRVR process is running in both the source and the target database servers. Do not start any EXTRACT and REPLICATS.

  • Ensure ODI domain admin and managed servers are in stopped state.

  • Purge all the ODI operator logs.

Install the OUAW ETL Component

  1. Log in to the application server.

  2. Navigate to the temporary directory where the OUAW installer is downloaded.

    Example: <TEMPDIR/application>.

  3. Set the JAVA HOME and add PATH.

    Copy
    export JAVA_HOME=<JAVA HOME>
    export PATH=$JAVA_HOME/bin:$PATH

  4. Launch the OUAW installer by running the command below. The OUAW installer Welcome page appears.

    Copy 
    java -jar OUAW_2.8.0.2.0_ETL_generic.jar -logLevel finest

    Note: For an AIX Operating System, set the following environment variable before starting the Oracle Utilities Analytics Warehouse installation:

    Copy 
    export IBM_JAVA_OPTIONS="-Xmx2g -XX:PermSize=64m -XX:MaxPermSize=3200m"

  5. Review the information before you begin the installation. Click Next to continue.

    Note: If you are installing Oracle software on the server for the first time, provide central inventory details such as the inventory directory location and operating system group.

  6. On the Installation Location page, define the installation location in the Oracle Home field and click Next.

    Note: The specified Oracle home directory must be an empty directory.

    Installation location section where the user is to browse for an empty directory to store the ETL component

    Field Name and Description

    Value

    Oracle Home: The directory where the Oracle Utilities Analytics Warehouse ETL is going to be installed. 

    Note: This directory location is called the  ETL Home. Keep track of it, as it will be used during some deployment steps.

    Example: <ETL Home>

    </u01/ouaw/deployment/OUA_ETL>

  1. On the Languages Selection page, select English and click Next.

    Languages Selection section that shows the available languages on the left column and the selected languages on the right

    Field Name and Description

    Value

    Language Selection: The language for the installation process.

    English

  1. On the Database and Java Home Details page, enter the following and click Next.

    Database and Java Home Details page where the user is to enter the values provided.

    Field Name and Description

    Value

    Database Client Home: The Oracle Database Client installed location or Database Home location in the case where the same server is being used for both the application and database server.

    Example: <Database Client> or <ORACLE_HOME>

    </u01/ouaw/dbclient> or </u01/ouaw/database>

    Java Home: The location used for the Java install.

    Example: <JAVA HOME>

    </u01/ouaw/java>

  1. On the Target Database Connection Details page, populate the fields as detailed in the table below, and click Next.

    Target Database Connection Details page where the user is to populate several text fields.

    Field Name and Description

    Value

    Host: The target database server where database resides.

    Target Database server host name.

    <dbserver.hostname>

    Port: The target database server port number.

    Target Database port.

    Example: <1521>

    Service Name: The target database service name.

    <Database service name>

    Target Schema Password: Password for the target schema (DWADM).

    <DWADM user password>

    Confirm Target Schema Password: Confirm password for the target schema (DWADM).

    <DWADM user password>

    Target Schema Password: Password for the metadata schema (MDADM).

    <MDADM user password>

    Confirm Target Schema Password: Confirm password for the metadata (MDADM) schema.

    <MDADM user password>

  1. On the ODI Home and Schema Details page, populate the fields as detailed in the table below, and click Next.

    ODI Home and Schema Details page where the user is to populate several text fields.

    Field Name and Description

    Value

    ODI Home: The directory where Oracle Data Integrator (ODI) is installed.

    Location of new FMW Home

    Example: </u01/ouaw/middleware>

    Supervisor User: Name of the Oracle Data Integrator Supervisor.

    SUPERVISOR

    Supervisor Password: The Supervisor Password and store it for future reference.

    <Supervisor user password >

    Confirm Supervisor Password: Enter same as Supervisor Password.

    <Supervisor user password >

    Master Repository Schema Name: Oracle Data Integrator master repository schema name.

    OUA_MASTER

    Master Repository Schema Password: Master Repository schema password.

    <OUA_MASTER user password>

    Confirm Master Repository Schema Password: Confirm password of the Oracle Data Integrator master repository schema.

    <OUA_MASTER user password>

    Work Repository Schema Name: Oracle Data Integrator work repository schema name.

    OUA_WORK

    Work Repository Schema Password: Work Repository schema password.

    <OUA_WORK user password>

    Confirm Work Repository Schema Password: Confirm password of Oracle Data Integrator work repository schema.

    <OUA_WORK user password>

  1. On the Oracle Data Integrator Agent and Repository Details page, populate the fields as detailed in the table below, and click Next.

    ODI Agent and Repository Details page where the user is to enter a host and a port.

    Field Name and Description

    Value

    ODI Agent Host: The application server hostname where the ODI application server is installed.

    Example:

    <appserver.hostname>

    ODI Agent Port: The Oracle Data Integrator WebLogic Managed Server port. Make sure that you use the same port while creating Oracle Data Integrator managed server.

    Example: <11002>

  1. On the Target GoldenGate Details page, populate the fields as detailed in the table below, and click Next.

    Target GoldenGate Details page where the user is to populate several text fields.

    Field Name and Description

    Value

    GoldenGate Host: The Target database hostname where GoldenGate is installed.

    Target database server host name

    Example: <dbserver.hostname>

    GoldenGate Home: The GoldenGate installed location.

    Example: <GoldenGate Home.>

    Target Database Home: The target database installed location.

    Example: <ORACLE HOME>

    GoldenGate Manager Port: The Oracle GoldenGate Manager port which is running on the database server host.

    <The default value is 7830>

    GoldenGate Algorithm: The algorithm configured in Oracle GoldenGate on the target database server

    The default value is "BLOWFISH".

    GoldenGate Encryptkey: The Encrypt Key configured in Oracle GoldenGate on the target database server.

    The default value is “DEFAULT”

    GoldenGate Shared Secret: Shared secret key configured in Oracle GoldenGate on the target database server.

    Go to the Oracle GoldenGate prompt and run the command:

    encrypt password <password of MDADM user>, encryptkey DEFAULT 

    Provide the result of the above command as the value.

  1. On the Target JAgent Details page, populate the fields as detailed in the table below and click Next.

    Target JAgent Details page where the user is to populate several text fields.

    Field Name and Description

    Value

    JAgent Host: The Target database hostname where GoldenGate JAgent is configured.

    The target database server host name

    Example: <dbserver.hostname>

    JAgent GoldenGate Home: The target database server GoldenGate Home installed location.

    Example: <GoldenGate Home>

    JAgent Port: The JAgent RMI port defined in the config properties file.

    Example: <5557>

    JAgent User: The OS user that installed the JAgent.

    Example: <oracle>

    JAgent Wallet Password: The JAgent Wallet password which was generated in the above steps.

    <JAGENT Wallet password>

    Confirm JAgent Wallet Password: The same password as above.

    <JAGENT Wallet password>

  1. On the Java Home Location page, populate the fields as detailed in the table below and click Next.

    Java Home Location page where the user is to browse for the corresponding directory.

    Field Name and Description

    Value

    Java Home: The Java installed location (on the Application server).

    Example: </u01/ouaw/java>

  1. On the Installation Summary page, a summary is displayed. Click the Install button to proceed.

    Installation Summary page, which contains information about the install location, the disk space, and the feature sets to install.

    An Installation Progress page displays to track the installation.

    Installation Progress page that shows the percentage of progress of the install.

  2. On the Installation Complete page, note the displayed details and click Finish to close the installer wizard. The ETL is now installed.

  3. Start ODI Admin and Managed servers.

    Copy 
    nohup ./startWebLogic.sh > startWebLogic.log 2>&1 &
    nohup ./startManagedWebLogic.sh <ODI_server1> > StartManagedWeblogic.log 2>&1 &

Back to Top

Upgrade the Administration Tool Component

Prerequisites

To remove the previously created Apex workspace from the database: 

  1. Connect to the target database as SYSTEM user. 

    Copy

    export ORACLE_HOME=<ORACLE_HOME>
    export ORACLE_SID=<DATABASE SERVICE NAME>
    export PATH=$ORACLE_HOME/bin:$PATH
    sqlplus system/<system user password>@<DATABASE SERVICE NAME>
                    

  2. Run the following PL/SQL procedure. 

    Copy 

    BEGIN
    APEX_INSTANCE_ADMIN.REMOVE_WORKSPACE('OBIU_ADM');
    END;
    /
                

  3. Make sure no workspace with “OBIU” exists in the database. 

    Copy
    select WORKSPACE from APEX_WORKSPACES where WORKSPACE like '%OBIU%';

    Note: No rows should be returned from this query. 

  4. Start apex Admin and Managed server.
    Copy
    nohup ./startWebLogic.sh > startWebLogic.log 2>&1 &
    nohup ./startManagedWebLogic.sh <apex_server1> > StartManagedWeblogic.log 2>&1 &
  5.  Remove ords.war and i.war apps from APEX WebLogic console.
    1. Log in to APEX WebLogic console. 
    2. Navigate to Deployments > Control. 
    3. Click Stop and select Force Stop Now. 
    4. Click Yes. 
    5. On the Configuration tab, click Lock and Edit. 
    6. Under Deployments, select both i and ords. 
    7. Click Delete. 
    8. Confirm the deletion and click Activate Changes. 
  6. Uninstall the existing ords.war from the database by navigating to ords unzip location on the application server and executing the commands below.

    Copy

    cd </u01>/<ords>
    export JAVA_HOME=<JAVA HOME>
    export PATH=$JAVA_HOME/bin:$PATH
    java -jar ords.war uninstall                                                            
                            

    Note: Provide the necessary inputs for this command and use JDK1.8 to run it. 

  7. Download Apex 22.1 from Oracle and place it under a temporary directory in both the OUAW database and application servers.
    Example: </u01/temp>

  8. Download ORDS 21.1.3 from Oracle and place it under a temporary directory in the application server.
    Example: </u01/temp>

  9. Download the Admin tool (Oracle Utilities Analytics Warehouse v2.8.0.2.0 Multiplatform.zip) file from the edelivery and place it under a temporary directory in the OUAW database server.
    Example: </u01/temp>

Back to Top

Admin Tool Installation Steps

  1. Log in to the target database server and navigate to the Apex extracted directory. 
    Example: cd </u01/ouaw/apex>

  2. Connect to the Oracle Utilities Analytics Warehouse Database with sys user and execute the following commands in order:

    Copy
    export ORACLE_HOME=<ORACLE_HOME> 
    export ORACLE_SID=<DATABASE SERVICE NAME> 
    export PATH=$ORACLE_HOME/bin:$PATH 
    sqlplus sys/<sys user password>@<database service name> as sysdba  
    @apxrtins.sql <Tablespace name> <Tablespace name> <Temp Tablespace name> /i/
                    

    Example:

    @apxrtins.sql <CISTS_01> <CISTS_01> <TEMP> /i/

  3. Set Apex Admin account and password. Execute the following:
    Copy
    @apxchpwd.sql
  4. Run the following to install Apex for the first time:

    Copy

    EXEC DBMS_XDB.SETHTTPPORT(0);
    SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;
                        

    Note: This query should result in zero (0).

  5. Run the following SQL:

    Copy

    ALTER USER APEX_PUBLIC_USER ACCOUNT UNLOCK;
    ALTER USER APEX_PUBLIC_USER IDENTIFIED BY APEX_PUBLIC_USER;
    @apex_rest_config.sql

    Note: Make sure to note the password for these two users: APEX_LISTENER user and APEX_REST_PUBLIC_USER. 

Back to Top

Configure APEX Workspace for OUAW

To import the Admin tool to configure Oracle Data Integrator:

  1. Download and unzip the Oracle Utilities Analytics Warehouse v2.8.0.2.0 Multiplatform.zip file, which includes the AdminTool folder.

  2. Copy the Multiplatform zip file into a temp directory within the target database server.

    Example: </u01/temp>

  3. Navigate to the TEMP directory and connect to the database using the system user.

    Copy
    cd </u01/temp/AdminTool>
    sqlplus system/<system user password>@<DATABASE SERVICE NAME>

    1. Create a workspace and configure the users.

      Copy
      @CreateAppWorkspace.sql

    2. Import the application.

      Copy
      @DeployAdminApp.sql

Back to Top

Install ORDS on the Application Server

  1. Navigate to the ORDS extracted directory on the application server and make sure that the APEX extracted directory is available in the location where the Admin tool is set up.

    Example:  </u01/ouaw/ords>

  2. Create a directory on the application server to configure Apex.

    Example:  mkdir -p </u01/ouaw/apex_configuration>

  3. Navigate back to the ords directory where Oracle REST Data Source (ORDS) was extracted.

    Example:  cd </u01/ouaw/ords>

  4. To perform an advanced installation, execute the following commands:

    Copy
    export JAVA_HOME=</u01/ouaw/java> 
    export PATH=$JAVA_HOME/bin:$PATH 
    java -jar ords.war install advanced 

    Note: Use JDK1.8 or a later version to run this command.

    See below an example of the command prompt, in which default options will appear enclosed in square brackets []. Use these options, or provide the necessary inputs for your requirements.

    Enter the location to store configuration data: </scratch/ouacicd/apex_configuration>
    Specify the database connection type to use.
    Enter number for [1] Basic  [2] TNS  [3] Custom URL [1]:
    Enter the name of the database server [localhost]:<dbserver.hostname>
    Enter the database listen port [1521]:<dbserver.port>
    Enter 1 to specify the database service name, or 2 to specify the database SID [1]:
    Enter the database service name:<database service name>
    Enter 1 if you want to verify/install Oracle REST Data Services schema or 2 to skip this step [1]:
    Enter the database password for ORDS_PUBLIC_USER:
    Confirm password:
    Requires to login with administrator privileges to verify Oracle REST Data Services schema.

    Enter the administrator username:sys
    Enter the database password for SYS AS SYSDBA:
    Confirm password:
    Connecting to database user: SYS AS SYSDBA url: jdbc:oracle:thin:@//<dbserver.hostname>:1521/<database service name>

    Retrieving information.
    Enter the default tablespace for ORDS_METADATA [SYSAUX]:
    Enter the temporary tablespace for ORDS_METADATA [TEMP]:
    Enter the default tablespace for ORDS_PUBLIC_USER [SYSAUX]:
    Enter the temporary tablespace for ORDS_PUBLIC_USER [TEMP]:
    Enter 1 if you want to use PL/SQL Gateway or 2 to skip this step.
    If using Oracle Application Express or migrating from mod_plsql then you must enter 1 [1]:
    Enter the PL/SQL Gateway database user name [APEX_PUBLIC_USER]:
    Enter the database password for APEX_PUBLIC_USER:
    Confirm password:
    Enter 1 to specify passwords for Application Express RESTful Services database users (APEX_LISTENER, APEX_REST_PUBLIC_USER) or 2 to skip this step [1]:
    Enter the database password for APEX_LISTENER:
    Confirm password:
    Enter the database password for APEX_REST_PUBLIC_USER:
    Confirm password:
    Enter a number to select a feature to enable:
       [1] SQL Developer Web  (Enables all features)
       [2] REST Enabled SQL
       [3] Database API
       [4] REST Enabled SQL and Database API
       [5] None
    Choose [1]:
    2021-12-08T16:43:47.300Z INFO        reloaded pools: []
    Installing Oracle REST Data Services version 21.1.3.r1531102
    ... Log file written to /scratch/gbuora/ords_install_core_2021-12-08_164347_00407.log
    ... Verified database prerequisites
    ... Created Oracle REST Data Services proxy user
    ... Created Oracle REST Data Services schema
    ... Granted privileges to Oracle REST Data Services
    ... Created Oracle REST Data Services database objects
    ... Log file written to /scratch/gbuora/ords_install_datamodel_2021-12-08_164359_00711.log
    ... Log file written to /scratch/gbuora/ords_install_apex_2021-12-08_164401_00030.log
    Completed installation for Oracle REST Data Services version 21.1.3.r1531102. Elapsed time: 00:00:15.52

    Enter 1 if you wish to start in standalone mode or 2 to exit [1]:2

  5. Navigate to the ORDS directory.

    Example:  cd </u01/ouaw/ords>

  6. Run the following command after setting JAVA HOME:

    Copy 
    java -jar ords.war static </u01/ouaw/apex>/apex/images

    Note: The command above will create an i.war file in the ords folder.

Back to Top

Install the ords.war and i.war files

  1. Log in to <apex domain> WebLogic administration console and click the Lock & Edit button located in the Change Center.
  2. On the Domain Structure panel, select Deployments, then click Install.

    Domain Structure panel showing the apex domain options. Deployments, the second option, is selected here.

  3. Enter the appropriate path and then select the ords.war file. Click Next.

    Example: </u01/ouaw/ords>

  4. Select the deployment target as <apex_server1>.

    Install Application Assistant page, where the user is to define the deployment target.

  5. On the application assistant, populate the fields as detailed in the table below.

    Install Application Assistant, where the user is to arrange the security and source accessibility settings.

    Field Name and Description

    Value

    Name: Enter the deployment name.

    ords

    Security: Select the security model to be used.

    Select the Custom Roles option.

    Source accessibility: Select the source accessibility option.

    Select the Use the defaults defined by the deployment's targets option.

  1. The location of ords.war file and target will appear on the Summary section. Click Finish.

    Install Application Assistant showing the Additional Configuration and Summary sections.

  2. After saving the ords.war deployment, click the Activate Changes button located in the Change Center. 

  3. Repeat the steps above to deploy the i.war file.

  4. On the WebLogic administration console, navigate to Deployment and then Control.

  5. Select i and ords.

  6. Click Start and then Servicing All Requests.

  7. Restart the administration and managed servers.

Back to Top

Access the AdminTool

Use this URL to access the administration tool: 

http://<hostname>:<apex_server1_port>/ords/f?p=104

  1. Provide the following credentials to access the Admintool:
    Username:  Admin
    Password:  Admin_123

    Oracle Utilities Analytics Administration login page where the user is to enter username and password.

    Note: After logging in to the application for the first time, you will be requested to change the password.

  2. After logging in, you can access the ETL Configuration and ETL Job Execution through the respective tabs.

    Administration tool home page showing the ETL Configuration, the NMS Configuration, and the ETL Job Execution menus.

Back to Top

Change the Default Password of Admin User

This section describes the APEX API used to change the admin user's password.

The script below should be run after connecting to the database as user SYSTEM.

Note: Replace the string 'New password' with the new password for the admin account before running the script. 

Copy 
begin
wwv_flow_api.set_security_group_id(p_security_group_id=>nvl(wwv_flow_application_install.get_workspace_id,2090606133849294));
end;
/
begin
apex_util.edit_user(
p_user_id => '1467765078687596',
p_user_name => 'ADMIN',
p_web_password => 'New password',
p_new_password => 'New password'
);
end;
/
commit;
/

Note: It is strongly recommended to change the default password after logging in.

Back to Top

Upgrade the Dashboards Component

Prerequisites

Before you begin installing the OUAW Dashboards component, note the following:

  • A single OS user must install all required software.

  • All required software (such as Java, Oracle Database Client, Oracle Fusion Middleware, Oracle Analytics Server) must be installed.

  • The Oracle Analytics Server (OAS) domain must be installed and configured, and all domain paths must be available. 

  • Verify that the OUAW Dashboards Components are unzipped and available in the <TEMPDIR>/application directory on the application server.

Set Up the Dashboard Environment 

  1. Log in to the application server.
  2. Create a Dashboard Home directory.

    Example:  mkdir -p </u01/ouaw/deployment/OUAW_DASHBOARD>

    Note: In the documentation, this directory location is referred to as Dashboards Home. Keep note of it because it will be used during some deployment steps.

  3. Copy catalog, WriteBackTemplates, and rpd folders from <TEMPDIR/application> to Dashboard Home folder.

    Copy
    cp -rp <TEMPDIR>/application/<OAS Version>/*  </u01/ouaw/deployment/OUAW_DASHBOARD>

Back to Top

Deploy the Web Catalog

On the Oracle Analytics Server, you can deploy the latest catalogs into the environment using the online mode.

Note: In case you want to take a backup of the deployed catalog, follow the OAS Doc ID 2724149.1 in My Oracle Support.

  1. Navigate to <DOMAIN DOMAIN>/<OAS_DOMAIN>/bitools/bin.
  2. Create a new credentials file called boot.txt and add the following contents to it:

    Copy
    login=<OAS Weblogc admin user>
    pwd=<OAS Weblogic admin password>

  3. For each catalog present under <Dashboards Home>/catalog directory, run the following command from the <OAS DOMAIN HOME>/bitools/bin location. Replace all parameters enclosed in <> with the appropriate values. 

    Copy 
    ./runcat.sh -cmd unarchive -folder "/shared" -online http://<OAS SERVER Host>:<OAS Managed SERVER PORT>/analytics-ws/saw.dll -credentials boot.txt -inputFile "<Dashboards Home>/Catalog/<Catalog Name>" -overwrite all

    Note: The inputFile parameter must be in double quotes, and the catalog file name must include spaces.

  4. Deploy the 'Spatial Metadata Catalog' on the System folder. Replace all parameters enclosed in <> with the appropriate values.

    Copy
    ./runcat.sh -cmd unarchive -folder "/system" -online http://<OAS SERVER Host>:<OAS Managed SERVER PORT>/analytics-ws/saw.dll  -credentials boot.txt -inputFile "<Dashboards Home>/catalog/Spatial Metadata.Catalog" -overwrite all

    Note: The inputFile parameter must be in double quotes, and the catalog filename must include spaces.

Back to Top

Deploy the Merged RPD File

To merge the customized 2.7.0.2.1 RPD file with the 2.8.0.2.0 RPD, which contains the database changes required:

  1. Copy both 2.8.0.2.0 and 2.7.0.2.1 RPD files to the Windows machine where Oracle Analytics Client Tool 7.0 is installed, then merge it.

    Note: RPD file merge steps can be found here:  Merging Repositories

  2. Once the RPD file merge is complete, copy the modified RPD back to the <install dir>/rpd/UtilitiesBusinessAnalytics.rpd, where <install_dir> is the Oracle Utilities Analytics Warehouse Dashboard Component installation directory. 

Upload the RPD File

  1. Log in to the target application server where OAS is installed. 

  2. Navigate to <DOMAIN HOME>/<OAS DOMAIN>/bitools/bin.

  3. Run the following command to deploy the RPD: 

    Copy 
    ./datamodel.sh uploadrpd -I <Dashboards Home>/rpd/UtilitiesBusinessAnalytics.rpd -W <rpd password, defaultpassword is oracle123> -U <Weblogic user name of OAS domain> -P <Weblogic password of OAS domain> -SI ssi 

  4. Run the following commands from the <OAS_DOMAIN>/bitools/bin directory to stop and start the OAS domain services respectively.

    Copy
    ./stop.sh 
    ./start.sh 

Back to Top

Deploy Writeback Templates

  1. Log in to the application server and run the following commands to deploy writeback templates:

    Copy

    mkdir -p <FMW Home>/bi/bifoundation/web/msgdb/l_en/custommessages
    cp -rp <Dashboards Home>/WriteBackTemplates/*  <FMW Home>/bi/bifoundation/web/msgdb/l_en/custommessages/

  2. Restart the Oracle Analytics Server services after deploying these writeback templates in the specified path.

    Copy

    cd <OAS DOMAIN>/bitools/bin
    ./stop.sh
    ./start.sh

Back to Top

Configure MapViewer for OUAW

To work with OUAW Analytics, there are a few changes that need to be made in the mapViewerConfig file. The file is located in <OAS DOMAIN>/config/fmwconfig/mapviewer/conf.  Ensure you take a backup before updating it.

Note: Skip this task on AIX/Solaris platforms. The Mapviewer URL is not supported in AIX/Solaris environments.

Update the MapViewer configuration from the MapViewer Admin Console

Note: Ignore these steps in case the mapViewerConfig.xml file was restored during OAS domain upgrade.

  1. Log in to MapViewer (http://<Server>:<port>/mapviewer)
  2. Navigate to MapViewer > Administration > Configuration to edit the mapViewerConfig.xml file. If the customer environment runs behind the proxy, then insert the list of host names for all the third-party service providers in the security_config node.

    Example:
    <proxy_enabled_hosts>
    elocation.oracle.com
    </proxy_enabled_hosts>

  3. Add the following ns_data_provider node:

    Copy
    <ns_data_provider id="obieeNsdp" class="com.oracle.utilities.birdseye.BirdseyeNSDP" />

  4. Add the current map_tile_server with the following map_tile_server node:

    Copy

                    <map_tile_server>
                    <tile_storage default_root_path="/mytilecache/"/>
                    </map_tile_server>
                    

  5. Add the following map data source code in the mapViewerConfig.xml with the appropriate values as the database server details:

    Copy 

    <map_data_source name="mapconn"
    jdbc_host="<DB server name>"
    jdbc_sid="//<DB Service name>"
    jdbc_port="1521"
    jdbc_user="DWADM"
    jdbc_password="!<DWADM user password>"
    jdbc_mode="thin"
    number_of_mappers="32"
    allow_jdbc_theme_based_foi="true"
    />
                        

  6. Click Save and Restart.

Back to Top

Configure Spatial Data

  1. Log in to the target database server.

  2. Navigate to the temporary directory where the Oracle Utilities Analytics Warehouse v2.8.0.2 Oracle Database Multiplatform.zip file was extracted.

    Copy
    cd database/BI2802/Spatial-Metadata

  3. Set the following environment variables.

    Copy

    export ORACLE_SID=<DATABASE SERVICE NAME>
    export ORACLE_HOME=<ORACLE HOME>
    export PATH=$ORACLE_HOME/bin:$PATH
                            

  4. Create the database directory in the database after connecting to sys user.

    Copy

    sqlplus sys/<sys user password>@<DATABASE SERVICE NAME>

    Example: Create the directory <dump_dir> as '</u01/dumps>'.

  5. Copy the user_sdo.dmp dumpfile from the temporary directory <TEMPDIR>/database/BI2802/Spatial-Metadata to the database directory <dump_dir> location.

    Example: </u01/dumps>

  6. Execute the impdp command to import the USER_SDO* tables data.

    Copy
    impdp directory=dump_dir dumpfile=user_sdo.dmp logfile=impdp_user_sdo.log schemas=DWADM remap_tablespace=cists_01:<tablespace_name>

  7. Provide DWADM username password when prompted.

    Note:  Ensure to change the tablespace_name to the name on which DWADM has the quota. If DWADM user have quota on cists_01 tablespace, then exclude the whole remap_tablespace clause from the command.

  8. Review the impdp_user_sdo.log file to ensure the tables are imported successfully.
  9. After importing the tables, run the following SQL scripts from the <TEMPDIR>/BI2802/Spatial-Metadata directory. 

    Copy

    sqlplus dwadm/<dwadm user password>@<database service name>
    @copy_spatial_metadata.sql
    @clean_sdo_release_tbls.sql
                    

  10. Review the log files.

Back to Top

Post-Upgrade Steps

Run Post-Upgrade Steps

Note:  Steps 2, 3, 8, 11, 12, and 13 are only valid for the Oracle Utilities Network Management System (NMS) Source. Ignore these steps for Oracle Utilities Customer Care and Billing, Meter Data Management, Customer To Meter, and Work and Asset Management.

  1. Change the value of the parameter Maximum Table Name Length to 128.
    1. In ODI studio, navigate to Topology > Physical Architecture > Technologies.
    2. Right-click Oracle and select Open.
    3. Navigate to the Advanced tab and change the parameter Maximum Table Name Length to 128.
    4. Click Save.
  2. Perform the steps below in accordance with the upgraded NMS version in ODI Studio.

    Note:

    • The following steps are only valid for the NMS source application.
    • Ignore these steps in case the names for scenarios, dimensions, or facts are already set to the ones defined throughout this process.

    3. For NMS Versions 2.6.0.0 and Later:

    1. Navigate to Load Plans and Scenarios > Framework > Data correction.
    2. Right-click the B1_UPD_NMS_SCEN_FROM_260 scenario.
    3. Click Run.
    4. Set Context as "Global".
    5. Click OK.

    For NMS Versions after 2.5.0.2 and below 2.6.0.0:

    1. Navigate to Load Plans and Scenarios > Framework > Data correction.
    2. Right-click the B1_UPD_NMS_SCEN_FROM_2502_UNDER_260 scenario.
    3. Click Run.
    4. Set Context as "Global".
    5. Click OK.

    For NMS Versions after 2.4.0.1 and below 2.5.0.2:

    1. Navigate to Load Plans and Scenarios > Framework > Data correction.
    2. Right-click the B1_UPD_NMS_SCEN_FROM_2401_UNDER_2502 scenario.
    3. Click Run.
    4. Set Context as "Global".
    5. Click OK.

    For NMS Versions below 2.4.0.1:

    1. Navigate to Load Plans and Scenarios > Framework > Data correction.
    2. Right-click the B1_UPD_NMS_SCEN_UNDER_2401 scenario.
    3. Click Run.
    4. Set Context as "Global".
    5. Click OK.
  3. Rename the Account Dimension View scenario by performing the following steps:
    1. Navigate to Load Plans and Scenarios > Oracle Utilities BI > Shared > Dimensions > Account Dimension.
    2. On the Definition tab, double-click B1_NMS_D_ACCT_VW_UPTO_24013 Version 001 and rename it to B1_NMS_D_ACCT_VW Version 001.
    3. Click Save.
  4. Make sure that MANAGER, JAGENT, and PMSRVR are running on Source and Target GoldenGate. Do not start any EXTRACT and REPLICAT processes.
  5. Run the source configuration in UPGRADE mode for the configured context.
  6. Make sure that the pump processes transfer all the changes to the target server. Lag at the Chkpt and Time Since Chkpt should be zero (0). This can be confirmed through the info all command after connecting to the ggsci prompt.
  7. Stop the Golden Gate REPLICAT processes in the target server.

  8. Purge any synchronized data from the new NMS tables that are replicated after the upgrade.

    Note:  Ignore this step if any of the tables listed below are not already present in the NMS Replication schema.

    Copy 
    DELETE FROM <NMS_REPLICATION_SCHEMA>.MERGED_EVENTS;
    DELETE FROM <NMS_REPLICATION_SCHEMA>.NMS_ALARM_LOG;
    DELETE FROM <NMS_REPLICATION_SCHEMA>.NMS_ACCOUNTS_HISTORY;
    COMMIT;        
                

  9. Run B1_SYNC_CONTEXT Version 001 in ODI studio for the configured product context.
  10. Start the Golden Gate REPLICAT processes in the target server.
  11. Perform the following steps for Backfilling of Storm changes in the NMS Star Schema in accordance with the upgraded NMS version.

    For NMS Versions 2.6.0.0 and Later:

    1. Navigate to ODI Designer > Load Plans and Scenarios > Framework > Data correction.
    2. Right-click B1_STORM_DATA_FIX_2802 Version 001.
    3. Click Run.

      Note: Select the appropriate context. If multiple contexts are configured, execute for each context separately.

    For NMS Versions 2.6.0.0 below:

    1. Navigate to ODI Designer > Load Plans and Scenarios > Framework > Data correction.
    2. Right-click B1_NMS_FACT_STORM_KEY_UPD_2702 Version 001.
    3. Click Run.

      Note: Select the appropriate context. If multiple contexts are configured, execute for each context separately.

  12. Disable all NMS facts and dimensions (including B1_BR_SW_PLAN_JOBS). This can be ensured by checking that there is no record for any entity in B1_READY_VW view in MDADM schema.

    Copy 
    select distinct entity_name from mdadm.b1_ready_vw;

  13. For Account Dimension (NMS) related changes, perform an incremental or complete load of the data FROM NMS_ACCOUNTS_HISTORY table into Account Dimension.

    Option 1: Incremental Data Load

    CD_ACCT dimension will load only the incremental data FROM NMS_ACCOUNTS_HISTORY table. The data which is already loaded in the dimension FROM CES_CUSTOMERS_HISTORY table will not be modified or updated and remains the same. The dependent facts will not be impacted while performing initial load.

    1. Ensure the NMS_ACCOUNTS_HISTORY is present in replication layer with data.

    2. Stop the GoldenGate REPLICAT.

    3. Navigate to Load Plans and Scenarios > Oracle Utilities BI > Shared > Dimensions > Account Dimension to load all the initial and incremental data FROM CES_CUSTOMERS_HISTORY table into the dimension.

    4. On the Definition tab, double-click B1_PKG_NMS_CD_ACCT_UPTO_24013 Version 001 and rename it to B1_PKG_NMS_CD_ACCT Version 001.

    5. On the Definition tab, double-click B1_NMS_D_ACCT_VW_UPTO_24013 Version 001 and rename (if not already done) it to B1_NMS_D_ACCT_VW Version 001.

    6. Click Save.

    7. Run the View generation script for the configured NMS Context.

    8. Enable the entity active flag for CD_ACCT dimension and B1_RUN_ALL to load the Account dimension. This loads data from CES_CUSTOMERS_HISTORY until latest checkpoint.

    9. Ensure that the CD_ACCT dimension data loads are completed until the checkpoint date. The output of below queries should result in same date:

      Copy
      SELECT MAX (SLICE_END_DTTM) FROM MDADM.B1_JOBS_VW WHERE CONTEXT_CD= <NMS_context_code> AND ENTITY_NAME='CD_ACCT';
      SELECT LAST_UPDATE_TS FROM MDADM.B1_CHECKPOINT WHERE GROUP_NAME LIKE 'NMS%';

    10. Revert the changes for scenario names for CD_ACCT dimension upon completion of the job loads by navigating to Load Plans and Scenarios > Oracle Utilities BI > Shared> Dimensions > Account Dimension.

    11. On the Definition tab, double-click B1_PKG_NMS_CD_ACCT Version 001 and rename it to B1_PKG_NMS_CD_ACCT_UPTO_24013 Version 001.

    12. On the Definition tab, double-click B1_NMS_D_ACCT_VW Version 001 and rename it to B1_NMS_D_ACCT_VW_UPTO_24013 Version 001.

    13. Click Save.
    14. Stop B1_RUN_ALL from ODI Studio.
    15. Start the GoldenGate REPLICAT.
    16. Load the incremental data into CD_ACCT dimension FROM NMS_ACCOUNTS_HISTORY table by navigating to Load Plans and Scenarios > Oracle Utilities BI > Shared> Dimensions > Account Dimension.
    17. On the Definition tab, double-click B1_PKG_NMS_CD_ACCT_FROM_24013 Version 001 and rename it to B1_PKG_NMS_CD_ACCT Version 001.
    18. On the Definition tab, double-click B1_NMS_D_ACCT_VW_FROM_24013 Version 001 and rename it to B1_NMS_D_ACCT_VW Version 001.
    19. Click Save.
    20. Run the View generation for the Configured Context.
    21. Enable B1_RUN_ALL and load the Account dimension. At this point, the data is loaded from NMS_ACCOUNTS_HISTORY.
    22. Enable all other dimensions and facts, and perform incremental loads.

    Option 2: Complete Data Load

    CD_ACCT dimension will load the complete data FROM NMS_ACCOUNTS_HISTORY table. The data which is already loaded in the dimension FROM CES_CUSTOMERS_HISTORY table will be updated. All the dependent facts will also be updated with the latest ACCT_KEY values FROM CD_ACCT table. Once the loads are done, the older records in the account dimension (All the data loaded form CES_CUSTOMERS_HISTORY table) will be deleted.

    1. Stop B1_RUN_ALL from ODI studio. Run this query to ensure no ETL jobs are in the "Running" state:

      Copy
      SELECT * FROM   MDADM.B1_JOBS_VW WHERE  STATUS_FLG in ('W','P', 'R');

      Note: If there are entries found, wait for the jobs to finish.

    2. Ensure that the NMS_ACCOUNTS_HISTORY table is present and with data in the replication layer.
    3. Ensure the scenario names for the existing CD_ACCT NMS Dimension are renamed (if not already done) with suffix 'UPTO_24013' in ODI by navigating to Load Plans and Scenarios > Oracle Utilities BI > Shared> Dimensions > Account Dimension.
    4. On the Definition tab, double-click B1_PKG_NMS_CD_ACCT Version 001 and rename it to B1_PKG_NMS_CD_ACCT_UPTO_24013 Version 001.
    5. On the Definition tab, double-click B1_NMS_D_ACCT_VW Version 001 and rename it to B1_NMS_D_ACCT_VW_UPTO_24013 Version 001.
    6. Click Save.
    7. Rename the scenario name for the new CD_ACCT NMS Dimension by navigating to Load Plans and Scenarios > Oracle Utilities BI > Shared> Dimensions > Account Dimension.
    8. On the Definition tab, double-click B1_PKG_NMS_CD_ACCT_FROM_24013 Version 001 and rename it to B1_PKG_NMS_CD_ACCT Version 001.
    9. On the Definition tab, double-click B1_NMS_D_ACCT_VW_FROM_24013 Version 001 and rename it to B1_NMS_D_ACCT_VW Version 001.
    10. Click Save.
    11. Run the View generation for the Configured NMS Context.
    12. Run the B1_ACCT_DIM_UPD_28020 scenario for the configured NMS Context by navigating to Load Plans and Scenarios > Framework > Data Correction > B1_ACCT_DIM_UPD_28020.
    13. Enable the entity active flag of CD_ACCT dimension.
    14. Enable B1_RUN_ALL and load the Account dimension, where data is loaded from NMS_ACCOUNTS_HISTORY.
    15. Run the B1_F_ACCT_KEY_UPD_28020 scenario for the configured NMS Context by navigating to Load Plans and Scenarios > Framework > Data Correction > B1_F_ACCT_KEY_UPD_28020.
    16. Run the B1_ACCT_DIM_DEL_KEYS_28020 scenario for the configured NMS Context by navigating to Load Plans and Scenarios > Framework > Data Correction > B1_ACCT_DIM_DEL_KEYS_28020.
    17. Enable all other dimensions and facts, and perform incremental loads.

Back to Top