Go to primary content

Oracle Product Lifecycle Analytics Installation and Setup Guide Release 3.6.1 E83715-03 |
| Contents

Previous | Next |

# 4 Upgrade Considerations

## 4.1 Upgrading from OPLA 3.6.0.0.0 to OPLA 3.6.1.0.0

Follow the steps in this section to upgrade from OPLA 3.6.0.0.0 to OPLA 3.6.1.0.0.

### 4.1.1 Backing up Database Schemas and Files

Important: At a later time you may want to back out from this patch installation. In order to do so, you must have performed the following steps before installing this patch. Oracle recommends that you back up certain database schemas and files.

To backup database schemas and files, perform the following steps:

1. Export the following database schemas and store them in a backup location:

   - ODI Work Repository

   - Stage or ODM Schema

   - MDS Schema

2. Copy your existing RPD file to a backup location.

3. Copy your existing Web Catalog file to a backup location.

If at any time you need to back out of this patch installation, and you have backed up the above database schemas and files, then go to "Backing Out from the Patch Installation" for instructions.

### 4.1.2 Patch Installation Steps

WARNING: You can only apply this patch in your environment once! Repeatedly installing the patch can cause an ETL failure.

To complete the patch installation, perform the following steps:

1. If you have not already done so, before starting the patch installation, ensure that the following are stopped:

   - ODI Agents

   - Scheduler Agent

   - ETL tasks

2. On the computer where OPLA is installed, create a temp folder.

   Copy the OPLA36100.zip file to the temp folder and unzip jar -xvf OPLA36100.zip

   It will extract the following two zip files:

   OPLA36100_DM.zip

   OPLA36100_BI.zip

3. Set the environment variable to point to the Oracle PLA home directory, that is, where the existing Oracle PLA software, the MDS ETL, and the Schema are installed.

   - Example in Windows:

     `Set OPLA_Home = D:\OPLA`

   - Example in Linux and Solaris:

     `export OPLA_HOME=/home/oracle/OPLA`

4. Copy the OPLA36100_DM.zip file to the Oracle PLA home directory.

5. Unzip content from OPLA36100_DM.zip file, and extract the contents of the zip file, by entering the following command:

   `jar -xvf OPLA36100_DM.zip`

   After you extract the files, the %OPLA_Home% folder or the $OPLA_Home folder displays the following folder structure:

   - bin

   - install

   - lib

   - Patches

6. Execute the batch/shell script to apply the schema changes.

   Note: Use the command prompt, or shell prompt terminal to go to the `%OPLA_Home%\bin` directory (for windows) or to the `$OPLA_Home/bin` directory (for Linux and Solaris).

   Windows:

   - %OPLA_Home%\bin must be present in the Operation System Path.

   Linux/Solaris:

   - $OPLA_Home\bin must be present in the Operating System Path.

   - The ImportSchemaComponents_OPLA36100.sh must have Executive privileges.

7. Navigate to OPLA_HOME/bin folder and execute ImportSchemaComponents_OPLA36100.bat (Windows) and ImportSchemaComponents_OPLA36100.sh (Linux/Solaris). Log file will be generated in the folder OPLA_HOME/logs/ as 'PatchOPLA36100_SchemaComponents.log'. Please review the log file for errors if any.

8. Execute the batch/shell script to apply the ETL changes.

   Note: Use the command prompt, or shell prompt terminal to go to the %OPLA_Home%\bin directory (for windows) or to the $OPLA_Home/bin directory (for Linux and Solaris).

   Note: If log file contains the error message/s as ”ODI-10093: You are importing an object from another repository with the same identifier”, then OdiImport_A9_Oracle_36100.bat/ OdiImport_A9_Oracle_36100.sh will not import ETL components. Please renumber master and work repository IDs to different number, then execute ODI components batch/shell file.

   Note: IF the ORACLE DB Version is 12c and OPLA is installed on ODI 11g then need to set sqlnet.ora as follows: Add SQLNET.ALLOWED_LOGON_VERSION=8 in the oracle_home/network/admin/sqlnet.ora file.

   Windows:

   - %OPLA_Home%\bin must be present in the Operation System Path.

   Linux/Solaris:

   - $OPLA_Home\bin must be present in the Operating System Path.

   - The OdiImport_A9_Oracle_36100.sh must have Executive privileges

9. Navigate to OPLA_HOME/bin folder and execute OdiImport_A9_Oracle_36100.bat (Windows) and OdiImport_A9_Oracle_36100.sh (Linux/Solaris). Log file will be generated in the folder OPLA_HOME/logs as ODIImport_stage_36100.log. Please review the log file for any errors.

10. After applying this patch, execute the FULL ETL Load.

### 4.1.3 RPD Deployment

Please note that for existing customers, customizations will be lost and they must be done again.

WARNING: Only OBIEE12c users should apply this patch.

1. Copy the OPLA36100_BI.zip file from temp folder to the PLM_BI_Home.

2. Unzip content from OPLA36100_BI.zip file, and extract the contents of the zip file, by entering the following command:

   jar -xvf OPLA36100_BI.zip

3. Navigate to PLMBI_HOME/bin folder and execute PLMBI_12213.bat (Windows) and PLMBI_12213.sh (Linux/Solaris). Log file will be generated in the folder PLMBI_HOME/logs as BIInstall.log. Please review the log file for any errors.

## 4.2 Post Installation Steps

After the patch is installed you must modify the Heap size in ODI to improve ETL performance.

### 4.2.1 Modifying the Heap Size in ODI

To enhance the ETL performance you must modify the Heap size in ODI.

To increase the Heap size, follow these steps:

After installing the ODI software, to avoid slow client performance, edit these properties in the following files:

1. `<ODI_HOME>/oracledi/client/odi/bin/odi.conf`

   Change:

   `AddVMOption -XX:MaxPermSize=256M`

   To:

   `AddVMOption -XX:MaxPermSize=1024M`

2. `<ODI_HOME>oracledi/client/ide/bin/ide.conf`

   Change:

   `AddVMOption -Xmx640M`

   `AddVMOption -Xms128M`

   To:

   `AddVMOption -Xmx2048M`

   `AddVMOption -Xms512M`

Note: The values you set for Heap size depends on how much memory space is on your local machine. If you have 2 GB of available memory, you can set AddVMOption -Xms128M to AddVMOption -Xms512M

For more information, see ODI documentation located on the Oracle Technology Network.

### 4.2.2 Backing Out from the Patch Installation

If, for any reason, you need to back out of this patch installation, and you have backed up the database schemas and files (as mentioned in "Backing up Database Schemas and Files"), perform the following steps:

1. Restore the following schemas by importing the previously backed up database export dumps to schemas with the same username and password:

   1. ODI Work Repository

   2. Stage or ODM Schema

   3. MDS Schema

2. Remove the temp tables (i$, j$ and C$) from all the schemas.

3. Restore the RPD file by importing it from its backup location.

4. Change the ETL configuration to run Data Mart or Stage and MDS in FULL load mode.

5. Restore the Web Catalog file by importing it from its backup location.

## 4.3 Deploying OPLAWebcatalog in OBIEE 11g

Note: You can find the webcatalog at the following location: <OPLA_ HOME>\Patches\OPLA35\OBIEE11g\webcatalog

To deploy the OBIEE 11g Webcatalog:

1. Copy PLMA_11g (11g catalog) to the location:

   `<OBIEEHomeDirectory>\instances\instance1\bifoundation\OracleBIPresentatio nServicesComponent\coreapplication_obips1\catalog`

   If you are using Windows 2008, follow this step:

   Copy PLMA_11g (11g catalog) to the location:

   `<OBIEEHomeDirectory>\instances\instance1\bifoundation\OracleBIPresentatio nServicesComponent\coreapplication_obips1\catalog`

2. Open the Enterprise Manager and enter the WebLogic username and password.

3. Click Business Intelligence and select Coreapplication.

4. Click the Lock and Edit Configuration tab. The Deployment tab is displayed.

5. Close the confirmation window displaying the following message:

   Lock and Edit Configuration - Completed Successfully.

6. Choose Deployment > Repository.

7. Enter the following location for PLMA_11g in the Catalog Location field located in the BI presentation Catalog section.

   $ORACLE_

   INSTANCE/bifoundation/OracleBIPresentationServiceComponent/$COMPONE NT_NAME/catalog/

8. Click Apply (displayed in the top right corner of the screen).

9. Choose Change Center, and then click Activate Changes.

10. Close the confirmation window displaying the following message:

    Activate Changes - Completed Successfully.

11. To restart the services and apply the changes, in the Overview page select Restart.

12. After completing the restart process, check the status of the presentation services using the URL `http://localhost:7001/analytics`.

## 4.4 Upgrading Repositories

For Repository upgrade, refer to the "Merging Oracle BI Repositories” section in the OBIEE Server Administration Guide.

## 4.5 Upgrading Webcatalog and Permissions in the Presentation Layer

For Webcatalog and Presentation Layer upgrade, refer to the ”Managing Presentation Catalog Using Oracle BI Catalog Manager” section in the OBIEE Presentation Services Administration Guide.