OBIA 11 1 1 8 1 Upgrade Guide

ORACLE BI APPLICATIONS 11.1.1.8.
1 UPGRADE GUIDE
1
Table of Contents
Overview ....................................................................................................................................................... 5
Pre-requisites ................................................................................................................................................ 6
Part I - BI Applications Infrastructure, Metadata and Schema Upgrades ..................................................... 6
Downloading BI Applications 11.1.1.8.1 software and files ..................................................................... 6
Upgrading the BI Applications binaries to version 11.1.1.8.1................................................................... 6
Rolling back any latest BIFNDN patch ....................................................................................................... 8
Applying Fusion Middleware Platform Patches for BI Applications 11.1.1.8.1 ........................................ 8
Upgrading the JAZN file .......................................................................................................................... 11
Upgrading BIACOMP and BIACM_IO schemas........................................................................................ 11
Upgrading ATG, FSM and BIACM ........................................................................................................ 12
Upgrading the BIACM_IO Schema ...................................................................................................... 16
Granting Privileges to <prefix>_BIACM_IO schema............................................................................ 18
Enabling Deployment Changes to ATG and FSM in the BI Domain ........................................................ 18
Upgrading the RPD and Presentation Catalog ........................................................................................ 20
Correcting the Directory Name for Code Grants .................................................................................... 36
Applying Client-Side Patches .................................................................................................................. 37
Applying the ODI Patch to ODI Studio ................................................................................................ 37
Applying Patches to BI Administration Tool ....................................................................................... 37
Upgrading the ODI Repository ................................................................................................................ 38
Creating a Back up of the 11.1.1.7.1 ODI Repository.......................................................................... 38
Exporting Content from the 11.1.1.7.1 ODI Repository...................................................................... 38
Export Custom Folder ............................................................................................................................. 42
Export Customized Datastores................................................................................................................ 44
2
Noting the ID of the 11.1.1.7.1 ODI Repository .................................................................................. 45
Dropping the 11.1.1.7.1 ODI Repository Schema ............................................................................... 46
Creating the ODI Repository for BI Applications 11.1.1.8.1................................................................ 48
Connecting to the ODI Repository for 11.1.1.8.1................................................................................ 50
Changing the ID of the 11.1.1.8.1 ODI Repository .............................................................................. 50
Importing Content into the 11.1.1.8.1 ODI Repository ...................................................................... 53
Regenerating Load Plans ..................................................................................................................... 65
Part II - Business Analytics Warehouse Schema and Data Upgrades ......................................................... 65
Granting New Required Privileges to <prefix>_DW................................................................................ 66
Identifying the Upgrade Load Plans to Execute ...................................................................................... 66
Modifying the Upgrade Load Plans ......................................................................................................... 67
Upgrading the Business Analytics Warehouse Schema .......................................................................... 70
Running Domains-Only Load Plan(s) ....................................................................................................... 71
Performing Domain Member Mappings ................................................................................................. 72
Upgrading Data in the Business Analytics Warehouse (Data Migration) ............................................... 72
Synchronizing the Data Model ............................................................................................................ 72
Performing Pre-Upgrade Tasks ........................................................................................................... 73
Executing Upgrade Load Plan(s) to upgrade data in the Business Analytics Warehouse................... 79
Post-Upgrade Tasks................................................................................................................................. 81
Importing and Applying Customizations ............................................................................................. 82
Import Datastores ............................................................................................................................... 83
Import Customized ETL tasks .............................................................................................................. 87
Appendix ..................................................................................................................................................... 92
Creating a Connection in ODI to the 11.1.1.7.1 Back-up ODI Repository ............................................... 92
Post-Upgrade SQL Statements ................................................................................................................ 93
3
This document describes the steps to upgrade BI Applications 11.1.1.7.1 to version 11.1.1.8.1.
Overview
The Upgrade of BI Applications 11.1.1.7.1 to version 11.1.1.8.1 consists of the upgrade of the following
components, repositories (schema and content) and data:
1. Platform components
2. BI Applications binaries
3. JAZN, RPD and Presentation Catalog
4. BI Applications Component Repository (BIACOMP)
5. ODI Repository content (BIA_ODIREPO)
6. Business Analytics Warehouse (DW) - schema
7. Data Migration of existing data in the Business Analytics Warehouse
NOTE: The upgrade from BI Applications 7.9.6.x to BI Applications 11.1.1.8.1 is not supported. Upgrade
from BI Apps for Fusion Apps (11.1.1.5.x – 11.1.1.7.0, 11.1.1.8.0) is also not supported
Sequence of Steps
The sequence of the steps in the upgrade of BI Applications 11.1.1.1.7.1 to 11.1.1.8.1 is outlined below.
1. Complete Upgrade Pre-requsites.
2. Run the BI Applications 11.1.1.8.1 installer to upgrade the BI Application binaries from version
11.1.1.7.1 to 11.1.1.8.1.
3. Apply the FMW Middleware Patches for BI Applications 11.1.1.8.1.
4. Use the BI Update Metadata Tool to upgrade the JAZN
5. Use the BI Applications Upgrade Tool to upgrade the BIACOMP schema (ATGLite, FSM and
BIACM component upgrades). Use scripts to upgrade the BIACM_IO schema
6. Run scripts to enable deployment changes in BI Applications 11.1.1.8.1.
7. Upgrade the RPD and Presentation Catalog
4
8. Apply Client-Side Patches.
9. Upgrade the ODI Repository metadata (content).
10. Upgrade Business Analytics Warehouse schema and Migrate Data in Data Warehouse
Instructions for each step of the upgrade process are provided below.
Pre-requisites
Complete the following pre-requisites before performing the upgrade from BI Applications 11.1.1.7.1 to
BI Applications 11.1.1.8.1.
 Before upgrading your BI Applications 11.1.1.7.1 environment to version 11.1.1.8.1, you must
have applied the following patches. The ODI Cumulative Patch for BI Applications 11.1.1.7.1 is
available on My Oracle Support > Patches & Updates.
o Patch #1 – 17546359 (Services should be stopped)
o Patch #2 – 16873189 (Services should be stopped)
o Patch #3 - 17546336 ODI Cumulative Patch (Services should be started)
 Before starting the Upgrade process from BI Applications 11.1.1.7.1 to 11.1.1.8.1, you must have
executed at least one incremental run in addition to a full data load in your BI Applications
11.1.1.7.1 environment.
 Take the backup of MWHOME folder before upgrade
 Review the Certification Matrix for BI Applications version 11.1.1.8.1. The Certification Matrix is
available on the Fusion Middleware Certification Page on Oracle Technology Network (OTN).
Part I - BI Applications Infrastructure, Metadata and Schema Upgrades
Downloading BI Applications 11.1.1.8.1 software and files
5
Download the BI Applications 11.1.1.8.1 installer, the BI Applications Repository Creation Utility (RCU)
11.1.1.8.1 and the FMW Platform Patch zip files from the Oracle Business Intelligence Applications
11.1.1.8.1 Media Pack available on Oracle Software Delivery Cloud.
Upgrading the BI Applications binaries to version 11.1.1.8.1
1. Shut down the WebLogic Administration Server, BI and ODI Managed Servers, and Node
Manager. Shut down BI processes using Oracle Process Manager and Notification Server
(OPMN).
2. On the machine which hosts the Middleware Home and BI Oracle Home for the BI Applications
11.1.1.7.1 environment, run the BI Applications 11.1.1.8.1 installer.
On Windows:
setup.exe –jreLoc <JDK or JRockit location>
On Linux or UNIX:
./runInstaller -jreLoc <jdk or jrockit location>
The Installer displays the Welcome screen. Click Next.
3. The Prerequisites Check screen is displayed. Click Next.
4. The Specify Installation Location screen displays the MW_HOME and BI_ORACLE_HOME for your
existing BI Applications 11.1.1.7.1 environment. Verify the locations and click Next.
5. A Warning dialog is received asking if you wish to upgrade the existing BI_ORACLE_HOME. Click
Yes.
6
6. On the Summary screen, review the installation details and click the Install button to proceed.
7. Click Next on the Installation Progress screen when the installation is complete.
8. Click Finish on the Complete screen to complete the installation.
Do not start Weblogic servers and BI processes at this time.
Rolling back any latest BIFNDN patch

Webcat upgrade needs BIFNDN patch supplied as part of patch bundle, If environment has newer/one-
off patch of BIFNDN patch, than of
“BIFNDN_11_1_1_7_0OBIEEBP_LINUX_X64_131008_1224_5_17463376.zip”, It should be rolled back. If
BIFNDN patch newer than mentioned exists in environment, Webcat upgrade might fail.
NOTE: These newer BIFNDN patches can be applied post upgrade.
Applying Fusion Middleware Platform Patches for BI Applications 11.1.1.8.1
You must apply Fusion Middleware platform patches for BI Applications 11.1.1.8.1. The patches are
available for download as part of the Oracle Business Intelligence Applications 11.1.1.8.1 media pack.
The minimum version of Oracle BI EE supported for BI Applications 11.1.1.8.1 is BI EE 11.1.1.7.0 with
Bundle Patch 131017. The patches from Bundle Patch 131017 are included and will be applied to BI EE
11.1.1.7.0. If you have already applied BI EE Bundle Patch 131017 or higher to your BI EE environment
for BI Applications 11.1.1.7.1, then the BI EE patches will not be applied as part of this step.
7
The version of ODI used by BI Applications has not change between BI Applications 11.1.1.7.1 and
11.1.1.8.1. The version of ODI supported for BI Applications 11.1.1.8.1 is 11.1.1.7.0. An ODI patch is
applied to 11.1.1.7.0 as part of this FMW patch application step.
To apply platform patches:
NOTE: You will run a script to apply the patches. The script is a Perl script and is available in
<BI_Oracle_Home>/biapps/tools/bin/APPLY_PATCHES.pl.
The Perl script you will run to apply the patches requires a parameter input file
(apply_patches_import.txt). In this procedure, before you run the Perl script, you will update the
parameter input file to reflect the appropriate directory paths
1. Ensure that the WebLogic Administration Server, BI and ODI Managed Servers, Node Manager
and BI processes are shut down.
2. Download "Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence
Applications" and "Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence
Applications for <OS> from the Oracle Business Intelligence Applications 11.1.1.8.1 media pack
on Oracle Software Delivery Cloud. Download all parts.
3. Extract all .zip files into the same Patch Home directory, as follows:
Extract the contents of the downloaded .zip files containing the patches into the same directory,
for example, C:\patches or PATCH_HOME/patches.
Note: The directory structure of the extracted contents is not patches4fa/dist/ps6rc3. The
patches are contained in folders: biappsshiphome, odi, weblogic and oracle_common. You do
not have to unzip the individual patches.
4. Update the parameter input file (apply_patches_import.txt) to reflect the paths as specified in
the text file:
1. Create a writable directory where logs and temporary patch files will be stored. In the
apply_patches_import.txt file, you will set the WORKDIR parameter to point to the path
for this directory.
2. Open apply_patches_import.txt, which is located in the

<BI_Oracle_Home>/biapps/tools/bin directory.
3. Specify the following directory paths:
Directory Path
8
Directory Path
JAVA_HOME Path of the JDK. Example: <BI_ORACLE_HOME>/jdk
INVENTORY_LOC Path of the Oracle\Inventory directory.
For example:
C:\Program Files\Oracle\Inventory.
ORACLE_HOME Path of the BI Oracle Home.
MW_HOME Path of the Oracle Middleware Home directory.
COMMON_ORACLE_HOME Path of the oracle_common directory, which is under

the Middleware Home directory.
WL_HOME Path of the Oracle WebLogic Server Home directory.
ODI_HOME Path of the ODI Home directory.
WINDOWS_UNZIP_TOOL_EXE If the platform is Windows, specify the complete path

to the executable file of the unzip tool. For example:
C:\Program Files\7-Zip\7zFM.exe.
WORKDIR Path of a writable directory where logs and

temporary patch files are stored.
PATCH_ROOT_DIR Path of the patch directory.
It sIt should have both this generic patches directory,

and the platform specific directory; for example
patches64 (Linux 64)
For example:
C:\patches
or
PATCH_HOME/patches
9
Directory Path
5. To apply the patch, run the following command from <BI_Oracle_Home>/perl/bin:
<BI_Oracle_Home>/perl/bin/perl <BI_Oracle_Home>/biapps/tools/bin/APPLY_PATCHES.pl
<BI_Oracle_Home>/biapps/tools/bin/apply_patches_import.txt
6. Confirm that all patches have been applied successfully by reviewing the following log files in
the directory specified by WORDIR:
o final_patching_report.log (summary of patch application)
o biappshiphome_generic_patches.log
o biappshiphome_<OS specific>_patches.log
o odi_generic_patches.log
o oracle_common_generic_patches.log
o weblogic_patching.log
Do not start the Weblogic servers and BI processes at this time.
Upgrading the JAZN file
1. Create a writable directory where logs will be stored. For example,

C:\JAZN_UPGRADE_WORKDIR or WORKDIR_HOME/ JAZN_UPGRADE_WORKDIR
2. Perform the JAZN upgrade by running the following command:
BI_ORACLE_HOME/jdk/bin/java -d64 -cp BI_ORACLE_HOME/biapps/patch/biappspatch.jar

oracle.as.biapps.patch.update.UpdateBIAppsJAZNMetadata bi.oracle.home=<Path of the BI
Oracle Home> bi.domain.home=<Path of the BI Domain Home directory> log.file=<Path of the
work directory>/bi_jazn_patch.log work.dir=<Path of the work directory>
For example:
/Middleware_Home/Oracle_BI1/jdk/bin/java -d64 -cp /Middleware_Home

/Oracle_BI1/biapps/patch/biappspatch.jar
10
oracle.as.biapps.patch.update.UpdateBIAppsJAZNMetadata
bi.oracle.home=/Middleware_Home /Oracle_BI1
bi.domain.home=/Middleware_Home/user_projects/domains/bifoundation_domain
log.file=/WORKDIR_HOME/ JAZN_UPGRADE_WORKDIR /bi_jazn_upgrade/bi_jazn_patch.log
work.dir= /WORKDIR_HOME/ JAZN_UPGRADE_WORKDIR
Upgrading BIACOMP and BIACM_IO schemas
The <prefix>_BIACOMP schema contains tables for ATG, FSM and BIACM (Configuration Manager). The
<prefix>_BIACOMP schema is upgraded by updating these component schemas to version 11.1.1.8.1
individually. The <prefix>_BIACM_IO schema must also be upgraded to version 11.1.1.8.1. Details to
upgrade the <prefix>_BIACOMP and <prefix>_BIACM_IO schemas are described in this section.
Before performing the upgrades, first verify the versions of ATG , FSM and BIACM and BIACM_IO by
running the following command in the database hosting the <prefix>_BIACOMP and <prefix>_BIACM_IO
schemas:
SQL> select version, status,comp_id from schema_version_registry ;
The versions should match the values shown below:
VERSION STATUS COMP_ID
------------------------------ ----------- ------------------------------
11.1.1.7.0 VALID ATG
11.1.1.7.1 VALID BIACM
11.1.1.7.1 VALID BIACM_IO
11.1.1.7.1 VALID BIACOMP
11.1.1.7.0 VALID BIA_ODIREPO
11.1.1.7.0 VALID BIPLATFORM
11.1.1.7.1 VALID DW
11.1.1.7.0 VALID FSM
11.1.1.7.0 VALID MDS
9 rows selected.
11
Upgrading ATG, FSM and BIACM
The ATG, FSM and BIACM component schemas are upgraded using the BI Applications Repository
Upgrade Tool which is a command line utility. You must upgrade these component schemas in the order
described – that is, ATG first, then FSM and finally BIACM.
The BI Applications Repository Upgrade Tool (biappsrepositoryutil.jar) is located in

<BI_Oracle_Home>/biapps/tools/lib
1. Create a writable directory where logs will be stored. For example, C:\WorkRepoUtil or
WORKDIR_HOME/ workRepoUtil
2. Upgrade ATG
Run the following command:
BI_Oracle_Home/jdk/bin/java -jar /BI_Oracle_Home/biapps/tools/lib/biappsrepositoryutil.jar

upgradeATG <mandatory parameters>
Where the mandatory parameters are as follows:
Parameter Description
bi.oracle.home Full path of the Oracle BI home.
work.dir Working directory to be used for the run.
Log files will be created for each run and saved in this directory. The naming
convention for the SQL log file is atgUpgradeSQLYYYY-MM_DD_HH_MM.log. Log files
will be available only if they are not empty.
db.conn.sid.url Connection to the database that hosts the BIACOMP schema. The format is
host:port:SID.
For example: host.domain:1521:orcl
biacomp.user <prefix>_BIACOMP schema owner.
biacomp.password <prefix>_BIACOMP schema owner's password.
atg.db.seed.url URL used to connect to the <prefix>_BIACOMP schema. The format is
12
host:port/ServiceName. For example: host:port/orcl.mycompany.com.
db.sys.user Database system user name.
db.sys.password Database system user password.
Note: If this parameter is not passed in the command line, then the tool will request
the password at runtime.
Example:
/Middleware_Home/Oracle_BI1/jdk/bin/java -jar
/Middleware_Home/Oracle_BI1/biapps/tools/lib/biappsrepositoryutil.jar upgradeATG
bi.oracle.home=/Middleware_Home/Oracle_BI1/ work.dir=/WORKDIR_HOME/workRepoUtil
biacomp.user=DEV_BIACOMP biacomp.password=password db.conn.sid.url=dbhost:1521:orcl
atg.db.seed.url=dbhost:1521/orcl.mycompany.com db.sys.user=sysuser
db.sys.password=password
On Windows:
C:\MiddleWare_Home\Oracle_BI1\jdk\bin\java -jar
C:\MiddleWare_Home\Oracle_BI1\biapps\tools\lib\biappsrepositoryutil.jar upgradeATG
bi.oracle.home=C:\ Middleware_Home\Oracle_BI1 work.dir=C\WorkRepoUtil
atg.db.seed.url=dbhost:1521/orcl.mycompany.com db.sys.user=sysuser
3. Upgrade FSM

upgradeFSM <mandatory parameters>
13
convention for the SQL log file is fsmUpgradeSQLYYYY-MM_DD_HH_MM.log. Log
files will be available only if they are not empty.
db.conn.sid.url Connection to the database that hosts the <prefix>_BIACOMP schema. The format is
host:port:SID.
For example: host.domain:1521:orcl.
fsm.db.seed.url URL used to connect to the BIACOMP schema. The format is host:port/ServiceName.
For example: host:port/orcl.mycompany.com.
Example:
/Middleware_Home/Oracle_BI1/biapps/tools/lib/biappsrepositoryutil.jar upgradeFSM
fsm.db.seed.url=dbhost:1521/orcl.mycompany.com db.sys.user=sysuser
On Windows:
C:\MiddleWare_Home\Oracle_BI1\biapps\tools\lib\biappsrepositoryutil.jar upgradeFSM
bi.oracle.home=C:\Middleware_Home\Oracle_BI1 work.dir=C\WorkRepoUtil
14
fsm.db.seed.url=dbhost:1521/orcl.mycompany.com db.sys.user=sysuser
4. Upgrade BIACM

upgradeBIACM <mandatory parameters>
convention for the SQL log file is fsmUpgradeSQLYYYY-MM_DD_HH_MM.log. Log
files will be available only if they are not empty.
db.conn.sid.url Connection to the database that hosts the <prefix>_BIACOMP schema. The format is
host:port:SID.
For example: host.domain:1521:orcl.
biacm.db.seed.url URL used to connect to the <prefix>_BIACOMP schema. The format is

host:port/ServiceName. For example: host:port/orcl.mycompany.com.
15
Example:
/Middleware_Home/Oracle_BI1/biapps/tools/lib/biappsrepositoryutil.jar upgradeBIACM
biacm.db.seed.url=dbhost:1521/orcl.mycompany.com db.sys.user=sysuser
On Windows:
C:\MiddleWare_Home\Oracle_BI1\biapps\tools\lib\biappsrepositoryutil.jar upgradeBIACM
bi.oracle.home=C:\Middleware_Home\Oracle_BI1 work.dir=C\WorkRepoUtil
biacm.db.seed.url=dbhost:1521/orcl.mycompany.com db.sys.user=sysuser
Upgrading the BIACM_IO Schema
The BIACM_IO schema is upgraded to version 11.1.1.8.1 by running two scripts
 upgrade_grant_sysnonym_io.sql
 upgrade_synonym_io.sql
These scripts are located in

<BI_Oracle_Home>/biapps/admin/provisioning/update/11.1.1.8.1/from11.1.1.7.1/schema/oracle/obiac
m
To upgrade the BIACM_IO schema:
1. Connect to <prefix> _BIACOMP schema using SQL Plus.
Example:
sqlplus DEV_BIACOMP/password
2. Run the upgrade_grant_sysnonym_io.sql file with the input of <prefix>_BIACM_IO user name.
The <prefix> value is the same as the prefix for your BIACOMP schema.
Example:
16
SQL> @<path to script>/upgrade_grant_sysnonym_io.sql DEV_BIACM_IO
Where the path to the script is

<BI_Oracle_Home>/biapps/admin/provisioning/update/11.1.1.8.1/from11.1.1.7.1/schema/oracl
e/obiacm
Disconnect from the SQL Plus session once the script completes.
3. Connect to <prefix>_BIACM_IO schema using SQL Plus or an equivalent tool.
Example:
sqlplus DEV_BIACM_IO/password
4. Execute the upgrade_synonym_io.sql file with the input <prefix>_BIACOMP
Example:
SQL> @<path to script>/upgrade_synonym_io.sql DEV_BIACOMP
Where the path to the script is

<BI_Oracle_Home>/biapps/admin/provisioning/update/11.1.1.8.1/from11.1.1.7.1/schema/oracl
e/obiacm
Disconnect from the SQL Plus session once the script completes.
5. If above two scripts ran successfully, then perform the following step:
Log in as the System user to the database hosting the <prefix>BIACOMP schema using SQL Plus
or equivalent tool. Execute the command:
update schema_version_registry
set version = '11.1.1.8.1',
upgraded = 'Y',
start_time = sysdate,
status = 'VALID',
modified = sysdate
where owner = '<prefix>_BIACM_IO';
NOTE: The value of <prefix> for the <prefix>_BIACM_IO schema is the same prefix as that for
the <prefix>_BIACOMP schema.
17
Granting Privileges to <prefix>_BIACM_IO schema
Using SQL Plus or an equivalent tool, log in as <prefix>_BIACOMP and execute the following command:
grant select, references on C_PARAMETER_VALUE_FORMATTER_V to <prefix>_BIACM_IO;
Enabling Deployment Changes to ATG and FSM in the BI Domain
1. Start the Weblogic Administration Server and Node Manager. Start the BI processes using Oracle
Process Manager and Notification Server (OPMN).
2. Run the PS1_REL8_Upgrade_EnableATGAndFSMChanges.py script, which is available in the

<BI_ORACLE_HOME>/dwtools/script directory, using the Weblogic Scripting Tool (wlst) from the
<BI_ORACLE_HOME>/common/bin location as follows:
./wlst.sh
<BI_ORACLE_HOME>/dwtools/scripts/PS1_REL8_Upgrade_EnableATGAndFSMChanges.py --
DOMAIN_HOST <HOST_NAME> --DOMAIN_PORT <PORT_NUMBER> --DOMAIN_HOME_PATH
<DOMAIN_HOME_PATH> --DOMAIN_USERNAME <DOMAIN_USER>
Example:
./wlst.sh
/Middleware_Home/Oracle_BI1/dwtools/scripts/PS1_REL8_Upgrade_EnableATGAndFSMChang
es.py --DOMAIN_HOST BIDomainHost --DOMAIN_PORT 7001 --DOMAIN_HOME_PATH
/Middleware_Home/user_projects/domains/bifoundation_domain --DOMAIN_USERNAME
weblogic
On Windows:
wlst.cmd
C:\Middleware_Home\Oracle_BI1\dwtools\scripts\PS1_REL8_Upgrade_EnableATGAndFSMChan
ges.py --DOMAIN_HOST BIDomainHost --DOMAIN_PORT 7001 --DOMAIN_HOME_PATH
C:\Middleware_Home\user_projects\domains --DOMAIN_USERNAME weblogic
This script removes the 'TopologyManagerService' application and renames the ATG JNDI names.
3. Apply POSTREL8.1: BIAPPSINST 11.1.1.8.1 PATCH 2 or higher

18
4. Run the PS1_REL8_Upgrade_EnableODIDeployChanges.py script, which is available under
<BI_ORACLE_HOME>/dwtools/script directory, using the Weblogic Scripting Tool (wlst) from the
<BI_ORACLE_HOME>/common/bin location as follows:
./wlst.sh <ORACLE_HOME>/dwtools/scripts/PS1_REL8_Upgrade_EnableODIDeployChanges.py
--DOMAIN_HOST <HOST NAME> --DOMAIN_PORT <PORT NUMBER> --DOMAIN_HOME_PATH
<DOMAIN HOME PATH> --DOMAIN_USERNAME <DOMAIN USER> --ODI_SERVER_NAME
<ODI_SERVER_NAME> --ODI_HOME_PATH <ODI HOME PATH>
Example:
./wlst.sh
/Middleware_Home/Oracle_BI1/dwtools/scripts/PS1_REL8_Upgrade_EnableODIDeployChanges
.py --DOMAIN_HOST BIDomainHost --DOMAIN_PORT 7001 --DOMAIN_HOME_PATH
/Middleware_Home/user_projects/domains/bifoundation_domain --DOMAIN_USERNAME
weblogic --ODI_SERVER_NAME odi_server1 --ODI_HOME_PATH
/Middleware_Home/Oracle_ODI1
On Windows:
wlst.cmd
C:\Middleware_Home\Oracle_BI1\dwtools\scripts\PS1_REL8_Upgrade_EnableODIDeployChang
es.py --DOMAIN_HOST BIDomainHost --DOMAIN_PORT 7001 --DOMAIN_HOME_PATH
C:\Middleware_Home\user_projects\domains\bifoundation_domain --DOMAIN_USERNAME
weblogic --ODI_SERVER_NAME odi_server1 --ODI_HOME_PATH
C:\Middleware_Home\Oracle_ODI1
A new cluster for ODI will be created with name "bia_odi_cluster" and existing ODI servers and
ODI related applications are targeted to this cluster. Going forward, This cluster (
bia_odi_cluster) will be used by BI Applications.
If, In 11.1.1.7.1 environment, any cluster created for ODI, with name other than
“bia_odi_cluster” can be deleted from environment, by logging into admin console. Please make
sure no servers are targeted to the cluster (which is getting deleted)
5. Start BI and ODI Managed Servers using Weblogic Administration Console.
6. Follow the below steps for BIACM during the upgrade. Run the below SQL in BIACOMP schema
19
UPDATE c_migration_log
SET functional_setup_name = 'DATA_LOAD_PARAMETERS'
WHERE functional_setup_name = 'Data Load Parameters';
SET functional_setup_name = 'DOMAIN_MAPPINGS'
WHERE functional_setup_name = 'Domain Mappings';
SET functional_setup_name = 'SYSTEM_SETUPS'
WHERE functional_setup_name = 'System Setups';
SET functional_setup_name = 'LOAD_PLAN_DEFINITIONS'
WHERE functional_setup_name = 'Load Plan Definitions';
SET functional_setup_name = 'REPORTING_PARAMETERS'
WHERE functional_setup_name = 'Reporting Parameters';
COMMIT;
Upgrading the RPD and Presentation Catalog
1. To upgrade the RPD using the BI Update Metatdata Tool :
a. Take a back-up of the RPD.
b. Create a writable directory where logs will be stored. For example, C:\RPD_Upgrade or
WORKDIR_HOME/ RPD_Upgrade
c. Run the following command to upgrade the RPD:
20
<BI_Oracle_Home>/jdk/jre/bin/java -cp <BI_Oracle_Home>/biapps/patch/biappspatch.jar
oracle.as.biapps.patch.update.UpdateBIAppsMetadata bi.oracle.home=<BI Oracle Home>
bi.admin.url=<BI EM Admin URL> bi.admin.username=<bi EM Admin User> bi.admin.password=<BI
EM Admin User Password> only.apply=rpd log.file=<Work dir>/rpd.log log.level=INFO
work.dir=<writable work dir path>
Example:
/Middleware_Home/Oracle_BI1/jdk/jre/bin/java -cp
/Middleware_Home/Oracle_BI1/biapps/patch/biappspatch.jar
oracle.as.biapps.patch.update.UpdateBIAppsMetadata
bi.oracle.home=/Middleware_Home>/Oracle_BI1 bi.admin.url=http://host:7001
bi.admin.username=weblogic bi.admin.password=password only.apply=rpd
log.file=/WORKDIR_HOME/RPD_Upgrade/rpd.log log.level=INFO work.dir=/
WORKDIR_HOME/RPD_Upgrade
Eg: The password is prompted after the process is started –
Optional Parameters:
log.level - default is INFO. Valid values are FINEST, FINE, INFO, WARNING, SEVERE.
Follow the below steps if the upgraded RPD is a trimmed RPD and need a full RPD to be restored
RESTORING THE COMPLETE RPD
Introduction
The customer after using the system for a period of time may decide to add new projects to the
RPD . In this case he would require the complete RPD with all the projects. The process below
provides a mechanism for the user to add projects to the existing rpd while retaining the exisitng
projects and customizations, thereby creating/restoring the complete RPD.
Use-Cases:
 If the customer had made customizations to contents of their trimmed RPD those must be
preserved when putting back the other bits.
 If the customer has applied any patches from Oracle then the changes those patches made
(to both trimmed and untrimmed stuff) must not be lost.
21
 When the trimmed pieces are put back, any connection information in the RuntimeRPD
must only be available in Restored RPD
PREREQUISITE
1. A copy of the BI Oracle Home RPD also referred to as the Golden RPD.
This RPD is referred to the Golden RPD as this contains the orginal Oracle content including the
changes/fixes made to the content and shipped by Oracle.
2. A copy of the Runtime RPD
This RPD is instance RPD which was trimmed and uploaded as part of provisioning. This RPD
is patched with content shipped from Oracle, it also contains all the customizations made by the
customer.
3. Password of the Golden RPD
The password is Admin123
5. A working installation of AdminTool ver 320.
PROCESS
1. Create the following directory structure

a.
Work
Work\GoldenRPD
Work\RuntimeRPD
Work\ExtractRPD
Work\Patch
Work\RestoredRPD
Work\EqualizeRPD
Eg: C:\Work , C:\Work\GoldenRPD, C:\Work\Patch, C:\Work\RuntimeRPD,

C:\Work\ExtractRPD,C:\Work\RestoredRPD,C:\Work\EqualizeRPD
2. Copy the RPDs to the corresponding folders
a. Copy Golden RPD to C:\Work\GoldenRPD

Eg: C:\Work\GoldenRPD\GoldenRPD.rpd
b. Copy Runtime RPD to C:\Work\RuntimeRPD

Eg: C:\Work\RuntimeRPD\RuntimeRPD.rpd
22
3. Open the Runtime RPD
a. Start the Admin Tool
b. From the Menu section click on File
c. Next Select Open.
d. From the Open context menu Select Offline.
e. Navigate to the directory containing the RuntimeRPD

(C:\Work\RuntimeRPD\RuntimeRPD.rpd)
f. Select the RuntimeRPD.rpd and click Open
g. Enter the RuntimeRPD Password and Click OK to Confirm.
h. The RuntimeRPD is opened and loaded in the Admin Tool successfully.
4. Obtain the list of Projects in the Runtime RPD.
a. In the Admin Tool from the Menu section Click on Manage.
b. From the Open Manage context menu Select Projects
c. A pop-up widget with the list of Projects comes up.
d. Make a note of the the list of Projects in a text file.
Tip: To avoid typos, on the Projects popup double click on the Project, a new popup widget with
respect to the selected project comes up. Copy the Project name from here.
23
5. Extract Trimmed RPD from Golden RPD
a. Open the command Prompt.
b. Navigate to the bin directory of the AdminTool installation
Eg: C:\_CLIENT_INSTALL_DIR_\oraclebi\orahome\bifoundation\server\bin
c. Open the file bi_init.bat file
Eg: notepad bi_init.bat
d. copy the sections where the environment variables are being set.
Eg: Ctrl + C
set ORACLE_HOME=C:\RUP3\oraclebi\orahome
set ORACLE_INSTANCE=C:\RUP3\oraclebi\orainst
set ORACLE_BI_APPLICATION=coreapplication
e. Paste the copied content on the Command Prompt.

24
f. Open the list of projects obtained in Step 4 and use as input.
g. Run the extractprojects command in the command prompt using the following parameters
and values.
-B GoldenRPD.rpd Path_Name
-O ExtractRPD.rpd Path_Name
-I "Project 1" -I "Project 2" ...
-P Password of the GoldenRPD
Note: {-I "Project Name"} has to be repeated for as many projects as present in the project list.
Eg: C:\RUP3\oraclebi\orahome\bifoundation\server\bin>extractprojects.exe -B
C:\Work\GoldenRPD\GoldenRPD.rpd -O C:\Work\ExtractRPD\ExtractRPD.rpd -P Admin123 -I
"Fusion Incentive Compensation Transactional Analysis" -I "Fusion Marketing Transactional
Analysis" -I "Fusion Partner Transactional Analysis" -I "Fusion Sales Transactional Analysis" -I
"Marketing Analytics Fusion Edition" -I "Partner Analytics Fusion Edition" -I "Sales Analytics
Fusion Edition"
h. The output is an RPD which will be referred to as the ExtractRPD which has the same set of
projects as the Trimmed RPD.
6. Equalize the Runtime RPD and the Extracted RPD
a. Run the equalizerpd command in the command prompt using the following parameters and
values
-C ExtractRPD.rpd Path_Name
-B Password of the ExtractRPD
-F RuntimeRPD.rpd Path_Name
-E Password of the RuntimeRPD.rpd
-O EqualizeRPD.rpd Path_Name
Eg: C:\RUP3\oraclebi\orahome\bifoundation\server\bin>equalizerpds.exe -C
C:\Work\ExtractRPD\ExtractRPD.rpd -B Admin123 -F C:\Work\RuntimeRPD\RuntimeRPD.rpd
-E welcome1 -O C:\Work\EqualizeRPD\EqualizedRPD.rpd
25
b. The output is an RPD which will be referred to as the EqualizedRPD. This RPD is an
equalized version of the Runtime RPD.
7. Create a Patch
a. The patch being created is a diff between the EqualizedRPD and the ExtractedRPD, this patch
will contain the all the configuration and customization changes that have been made by the
customer.
b. Open the EqualizedRPD in the AdminTool.
c. From the File menu select the Compare option.
d. From the Compare Context Menu, Open the ExtractRPD as the Original Repository.
e. Enter the GoldenRPD password to Open the ExtractRPD. –
26
. The AdminTool opens the RPD and performs a Compare operation and shows a list of
differences between the two RPDs.
Select ‘No’ for pop up message ‘Do you want to mark differences in the repository immediately’
27
g. Click on the Create Patch Option, a new File-Directory menu comes up. –
h. Save the file as "Patch.xml" and store it in the Patch Folder Eg: C:\Work\Patch\patch.xml
8. Apply the Patch
a. Apply the patch obtained from Step 7 above using the biserverxmlexec command
28
b. Run the biserverxmlexec command in the command prompt using the following parameters
and values
-P Password of GoldenRPD
-I Path_Name of the Patch.xml file
-S Password of the RuntimeRPD
-B GoldenRPD.rpd Path_Name
-O RestoreRPD.rpd Path_Name
RestoreRPD.rpd referred here is the name of the Restored RPD
Eg: C:\RUP3\oraclebi\orahome\bifoundation\server\bin>biserverxmlexec.exe -P Admin123 -I

C:\Work\Patch\patch.xml -S welcome1 -B C:\Work\GoldenRPD\GoldenRPD.rpd -O
C:\Work\RestoreRPD\RestoreRPD.rpd
9. Upload the Restored RPD
a. Upload the RestoredRPD created in Step 8 using Enterprise Manager.
Please follow the below steps to upload the RPD if the RPD is size is greater than 50MB
1. Open EM page
29
2. Expand weblogic domain and click on bifoundation_domain.
Click on weblogic domain dropdown you see on the screen and select System MBean Browser
3.Under Application defined MBeans browser dropdown folder, expand oracle.biee.admin and
under that expand Domain: bifoundation_domain
In that expand BIDomain
You find 2 categories both names BIDomain
One of them contains Operations tab which you can see when you click on it.
The one which contains the Operations tab can be either first or second. (Order in which you find
BIDomain might differ)
Click on Operations tab.
30
4.Click on lock under operations tab.
5. Click on Invoke.
31
After the operation completes, Click return.
6. Click on BIDomain.BIInstance.Server Configuration. Go to operations tab and click on Upload

repository.
7. Copy the rpd to the location :
<Middleware Home>/user_projects/domains/bifoundation_domain/
And in the text box “rpdFilePath”, please give only the name of the repository. (Note that you should
not give the entire path as it will look only in the path specified above)
Give the password of the repository
Click invoke, and after its done successfully click return.
32
8. Come back to the BIDomain (That you clicked previously for lock operation). Go to operations tab and
click on first commit operation. Click on invoke and then Return like you did previously
33
Follow the below steps if RPD Upgrade is attempted using a full RPD of 11.1.1.7.1 . If not , skip this
step and go to step 2
Restore the full RPD of 11.1.1.7.1 using the steps in RESTORING THE COMPLETE RPD. Ensure
Windows BI Client of version is equal or above the below version:
Build: 11.1.1.7.1.BISERVER_11.1.1.7.0OBIEEBP_WINDOWS.X64_130919.2217
Release Version: Oracle Business Intelligence 11.1.1.7.1
Package: 130920.0113.000
This is the recommended version and is already part of the Upgrade doc under section - "Applying
Patches to BI Administration Tool "
Perform 3-way merge :
The commands to run to do 3-way merge manually with -A option so that the upgraded RPD
contains all Subject Areas-
In bash shell,
1. source
<BI_INSTANCE_HOME>/bifoundation/OracleBIApplication/coreapplication/setup/bi-init.sh
2. <BI_ORACLE_HOME>/bifoundation/server/bin/patchrpd -C <PS1_customer_RPD> -P
<PS1_customer_password> -G <PS1_Oracle_RPD> -Q Admin123 -I <8.1_Oracle_RPD> -S
Admin123 -O <Upgrade_81_RPD> -V <decision_file_path> -U -A
In 8.1 Binary upgraded env,
 PS1_customer_RPD - RPD loaded in the instance prior to RPD Upgrade

 PS1_customer_password - Password for the PS1_customer_RPD
 PS1_Oracle_RPD - If instancerpdbaseline is not present in
/scratch/aime/work/mw2102/instances/instance1/bifoundation/OracleBIServerComponen
t/instancerpdbaseline/OracleBIApps.rpd , then use backed up RPD from location :
BI_ORACLE_HOME/.biapps_patch_storage_11.1.1.7.1/OH_BACKUP/biapps/admin/pr
ovisioning/OracleBIServerComponent/rpdbaseline/OracleBIApps.rpd
 8.1_Oracle_RPD -
BI_ORACLE_HOME/biapps/admin/provisioning/OracleBIServerComponent/OracleBIA
pps.rpd
 Upgrade_81_RPD - Output RPD of the 3way merge. Will have same password as
Customer RPD
 decision_file_path - output csv file contains the default decision taken during 3way
merge
34
2.
Example : /scratch/aime/work/mw2102/Oracle_BI1/bifoundation/server/bin/patchrpd -C
/scratch/aime/RPD_81/PPG/OracleBIApps_cust.rpd -P Admin123 -G
/scratch/aime/RPD_81/PPG/OracleBIApps_PS1.rpd -Q Admin123 -I
/scratch/aime/RPD_81/PPG/OracleBIApps_81.rpd -S Admin123 -O
/scratch/aime/RPD_81/PPG/OracleBIApps_patched.rpd -V
/scratch/aime/RPD_81/PPG/patchrpd_decision_file.csv -U -A
3. Run validaterpd - <BI_ORACLE_HOME>/bifoundation/server/bin/validaterpd -C

<Upgrade_81_RPD> -P <Upgrade_81_RPD_password> -O <output_text_file>
output_text_file - Should not contain any ERROR . Can contain WARNINGS which can be ignored
(PS1 refers to 11.1.1.7.1 release)
3. To upgrade the Presentation Catalog using the Upgrade Metadata Tool :
a. Take a back-up of the Presentation Catalog.
b. Create a writable directory where logs will be stored. For example, C:\Webcat_Upgrade
or WORKDIR_HOME/ Webcat_Upgrade
c. Run the following command to upgrade the Presentation Catalog:
<BI_Oracle_Home>/jdk/jre/bin/java -cp <BI_Oracle_Home>/biapps/patch/biappspatch.jar

oracle.as.biapps.patch.update.UpdateBIAppsMetadata bi.oracle.home=<BI Oracle Home>
bi.admin.url=<BI EM Admin URL> bi.admin.username=<bi EM Admin User> bi.admin.password=<BI
EM Admin User Password> only.apply=webcat log.file=<Work dir>/webcat.log log.level=INFO
work.dir=<writable work dir path>
Example:
/Middleware_Home/Oracle_BI1/jdk/jre/bin/java -cp
/Middleware_Home/Oracle_BI1/biapps/patch/biappspatch.jar
oracle.as.biapps.patch.update.UpdateBIAppsMetadata
35
bi.oracle.home=/Middleware_Home>/Oracle_BI1 bi.admin.url=http://host:7001
bi.admin.username=weblogic bi.admin.password=password only.apply=webcat
log.file=/WORKDIR_HOME/Webcat_Upgrade/webcat.log log.level=INFO work.dir=/
WORKDIR_HOME/Webcat_Upgrade
Eg: The password is prompted after the process is started –
Optional Parameters:
log.level - default is INFO. Valid values are FINEST, FINE, INFO, WARNING, SEVERE.
4. Restart all BI processes using Oracle Process Manager and Notification Server (OPMN).
5. It is recommended to update GUIDS in OBIEE
Correcting the Directory Name for Code Grants
In the BI Applications 11.1.1.7.1 environment, the

Middleware_Home/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user
folder has a sub folder with name oracle.biacm_11.1.1.7.1. Code grants also have the same path.
During the upgrade to BI Applications 11.1.1.8.1, the code grant changes to a path
oracle.biacm_11.1.1.8.1. This path doesn’t exit. The code grant path has to be changed.
1. Log in to Enterprise Manager:
http://host:port/em
Example, http://BIDomainHost:7001/em
2. Navigate to Weblogic_Domain -> bifoundation_domain. Right Click and select Security > System
Policies
Change Codebase -
file:${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/oracle.biacm_11.1.1.8.1/-
36
To:
file:${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/oracle.biacm_11.1.1.7.1/-
Applying Client-Side Patches
Applying the ODI Patch to ODI Studio
The ODI patch is available in PATCH_ROOT_DIR\odi\generic or

PATCH_ROOT_DIR/odi/generic. For the location of your
PATCH_ROOT_DIR, see Section Rolling back any latest BIFNDN patch
Applying Fusion Middleware Platform Patches for BI Applications 11.1.1.8.1 above.
System administrators must provide this patch to developers who have installed ODI Studio on their
machines.
Follow the instructions in the Patch Readme to apply the patch on all instances of ODI Studio.
Note: If you installed ODI Studio on the BI Domain host machine, you do not
have to apply the patch, as the patch is applied as part of the procedure
Applying Fusion Middleware Platform Patches for BI Applications 11.1.1.8.1.
NOTE: VERSION OF ODI STUDIO DOES NOT CHANGE – IT WILL STILL BE 11.1.1.7.0
37
Applying Patches to BI Administration Tool
If you have applied the BI EE Bundle Patch 131017 as part of the procedure
Applying Fusion Middleware Platform Patches for BI Applications 11.1.1.8.1, or if you had applied
Bundle Patch 13107 earlier but had not applied the patch to your BI Administration Tool instances, then
you must patch BI Administration Tool as part of this procedure.
NOTE: If you have applied a Bundle Patch version higher than 131017 then ensure that BI Administration
Tool has been appropriately patched.
The BI EE Client Installer executable is delivered in patch

p17463403_111170_Generic. This patch is available in
PATCH_ROOT_DIR\biappsshiphome\generic or
PATCH_ROOT_DIR/biappsshiphome/generic. For the location of your
PATCH_ROOT_DIR, see Section Rolling back any latest BIFNDN patch
Applying Fusion Middleware Platform Patches for BI Applications 11.1.1.8.1 above.
System administrators must provide the BI EE Client Installer executable to developers who have
installed BI Administration Tool on Windows machines.
On Windows machines where BI Administration Tool has been installed:
Run biee_client_install_x64.exe obtained on unzip of the patch zip file. Select "Modify an existing
instance".
Note: If BI Clients have not been installed then provide the biee_client_install_x64.exe executable file in
the patch to developers to install the BI Clients. Run biee_client_install_x64.exe obtained on unzip of the
patch zip file. Select "Install a new instance"
38
Upgrading the ODI Repository
(NOTE: For customers on clustered ODI environments, please contact Oracle BI Applications support for
additional information on upgrading your environment with reference to bug number 19221613.)
This section describes the steps to upgrade an existing BI Applications ODI Repository from version
11.1.1.7.1 to 11.1.1.8.1.
In order to retain the existing topology and security configuration in ODI while at the same time
minimizing the impact on other tools that interact with ODI (that is, BI Applications Configuration
Manager and the BI Applications instance of Weblogic Server), the upgrade process has you export the
existing or pre-upgrade configurations from the ODI Master Repository, drop the existing pre-upgrade
ODI Work and Master Repositories, import the new upgrade ODI Work and Master Repositories into the
same schema, then import the pre-upgrade ODI Repository configurations.
This effectively replaces all content (interfaces, packages, models, knowledge modules, load plans, etc)
while retaining the configuration definitions.
The process also allows you to retain any customizations performed by exporting the customizations
from the pre-upgrade repository and importing them back in after the repository has been upgraded.
Creating a Back up of the 11.1.1.7.1 ODI Repository
Use the Oracle Database Export and Import utility of your choice to export the ODI Repository for BI
Applications 11.1.1.7.1 from the existing schema and import it into another schema. This will allow you
to connect to the 11.1.1.7.1 ODI repository in case you need to reference it. Refer to Appendix >
Creating a Connection in ODI to the 11.1.1.7.1 Back-up ODI Repository for information how to create a
new connection in ODI Studio to the back-up of the ODI Repository for 11.1.1.7.1 which is now in a new
database schema.
Removing Artifacts using Special Repository ID 490
If you have applied the patch any patch for (Subledger Accounting Analytics), remove the following
artifacts to mitigate the risk of id conflicts (if necessary, take a backup of the repository before this):
Task Folder:
Remove the task folder SDE_ORA_SLAJournalFact under the SDE_ORAR1213_Adaptor folder and
SIL_SLAJournalFact under the SILO folder.
Model:
Remove the following data stores:
39
- W_SLA_XACT_F (Oracle BI Applications -> Fact)
- W_SLA_XACT_FS (Oracle BI Applications -> Fact Stage)
- XLA_TRANSACTION_ENTITIES (EBS R12.1.3 -> Subledger Accounting)
Load Plan:
Remove the following load plans:
3 SDE Fact SLAJRNLS_FG EBS_12_1_3
3 SIL Fact SLAJRNLS_FG
Remove the step $${3 SDE Fact SLAJRNLS_FG} from 2 SDE Fact Group and step $${3 SIL Fact
SLAJRNLS_FG} from 2 SIL Fact Group.
Exporting Content from the 11.1.1.7.1 ODI Repository
1. Launch the ODI Studio client and connect to the ODI repository for BI Applications 11.1.1.7.1.
(Do not connect to the back-up of the ODI Repository).
2. Navigate to the Topology tab. From the Connect Navigator (Topology icon dropdown on the top
right side of the navigator pane), select Export. As part of the procedures described below, you
will export files to a local directory.
40
Exporting Connections
3. Launch the Smart Export wizard from the Export selection dialog
4. Drag the ‘Global’ context into the ‘Objects to be Exported’ window. Provide a meaningful name
for the export file. Click Export. This will export the logical and physical topology including
assigned Datasource Num ID values and database connect details.
41
Exporting Security
1. Navigate to Topology > Export and select the ‘Export Security Settings’ action.
42
2. Choose to export to a local file (directory). This action exports your user configurations.
Exporting Customizations
If you have introduced any customizations in your ODI repository, you will need to export these as well.
Export Custom Folder

Per the customization methodology, all custom and customized ETL tasks should be in a separate
CUSTOM folder. Right click the Custom Folder and select the ‘Export’ option. In the next window,
ensure the ‘Child Components Export’ box is checked.
43
44
Export Customized Datastores
Click the ‘Export…’ option from the navigator window.
Select the option to export multiple objects
Drag and drop your purely custom and customized datastores. Be sure the ‘Export child objects’ option
is checked. In the example below, WC_ALLOC_INV_BALANCES_F/FS are purely custom tables while
W_GL_OTHER_F/FS are out of the box tables that have been customized.
45
Noting the ID of the 11.1.1.7.1 ODI Repository
ODI requires the ID of the repository you import objects into be different from the ID of the repository
that objects were exported from. The ID of the 11.1.1.7.1 ODI Repository will need to be noted and
after the repository is replaced with the 11.1.1.8.1 repository, the repository ID will be updated to a
non-conflicting number.
The default value 500 is assigned to all repositories that are shipped by Oracle. If you have migrated the
repository across environments, the value could be different from this default value.
To note the ID of the ODI Repository for BI Applications 11.1.1.7.1:
1. Navigate to Topology -> Repositories -> Master Repository -> Right Click and select ‘Open’ ->
Version -> Information -> Internal ID.
2. Note the ID.
46
3. Do the same for the Work Repository. The Repository ID should have the same value.
Dropping the 11.1.1.7.1 ODI Repository Schema
47
Use the BI Applications RCU to drop the existing 11.1.1.7.1 ODI Repository schema. You can use either
the BI Applications 11.1.1.7.1 RCU or the 11.1.1.8.1 RCU. You will be prompted with a list of schemas
that have already been installed – select the schema where the ODI Repository for 11.1.1.7.1 exists.
Important – ONLY drop the <prefix>_BIA_ODIREPO. Do not drop any other schema.
1. Launch the BI Applications RCU. Select the Drop radio button.
2. In the Database Connection Details screen, provide the connection details to the database which
hosts the ODI Repository for BI Applications 11.1.1.7.1.
3. From the Prefix All Schema Owners dropdown, select the prefix for your BI Applications
11.1.1.7.1 schemas.
4. Select only the Oracle Data Integration Master and Work Repository from the Select
Components screen. Do NOT select any of the other schema components.
48
5. Click Drop to drop the ODI Repository schema for 11.1.1.7.1.
The following steps are the same as when installing a refresh ODI repository. The only difference is that
we select the option to restore the ODI Master and Work repositories only.
Creating the ODI Repository for BI Applications 11.1.1.8.1
You must run the BI Applications 11.1.1.8.1RCU to create the schema for the ODI Repository for
11.1.1.8.1. This schema will use the same name as the 11.1.1.7.1 ODI Repository schema that was just
dropped.
Important – You must select the option to use an existing prefix and re-use the same prefix that
was used by the schema that was previously dropped.
49
1. Unzip the BI Applications 11.1.1.8.1 RCU downloaded from the BI Applications 11.1.1.8.1 media
pack.
2. If you are not running RCU on the database host machine, then you must copy the obia_odi.dmp
file to a directory with global write access on the appropriate database server machine. (RCU
writes log files to this directory.) The .dmp file is located in
BIA_RCU_HOME/rcu/integration/biapps/schema.
3. Launch the BI Applications RCU for 11.1.1.8.1 from BIAPPS_RCU_HOME\bin:
UNIX: ./rcu
Windows: rcu.bat
4. Select the Create radio button.
5. In the Database Connection Details screen, provide the connection details to the database which
previously hosted the ODI Repository for BI Applications 11.1.1.7.1 which you dropped in the
previous procedure.
50
6. In the Select Components screen, from the Select an existing Prefix dropdown, select the same
prefix as that of your ODI Repository for 11.1.1.7.1. If you do not see the prefix as an existing
prefix then choose the Create a new Prefix radio button and enter the same prefix as you had
used before for the ODI Repository for 11.1.1.7.1.
7. Select the Oracle Data Integration Master and Work Repository. Do not select any other
component.
8. In the Value field in the Custom Variables screen, for the <prefix>_BIA_ODIREPO schema enter
the directory path of the folder on the database server that contains the obia_odi.dmp file. See
step 1 above.
Note: Do not include the name of the .dmp file in the directory path.
9. Complete the ODI Repository creation.
Connecting to the ODI Repository for 11.1.1.8.1
51
Create a connection in ODI Studio to the ODI Repository for 11.1.1.8.1 which you created in the previous
step. The repository is set to Internal Authentication. The user and password you use to connect to the
repository:
User: SUPERVISOR
Password: welcome
Changing the ID of the 11.1.1.8.1 ODI Repository
The ID of the repository has to be changed from the default to avoid conflicts when importing the
configurations, objects and customizations from the ODI Repository for 11.1.1.7.1. In the section
“Noting the ID of the 11.1.1.7.1 ODI Repository” above you made a note of the Repository ID for the
Master and Work repositories (default value is 500). In this procedure you will update the value in the
ODI Repository for 11.1.1.8.1 to a different value.
1. In ODI Studio, navigate to Topology -> Repositories -> Master Repository -> Right Click and select
‘Renumber’
2. On the Renumbering the repository – Step 1 dialog, click Yes.
52
3. On the Renumbering the repository – Step 2 dialog, enter a new ID that has not been used for
any of your existing ODI Repositories. Oracle suggests incrementing the value you noted in
section “Noting the ID of the 11.1.1.7.1 ODI Repository” by 1. Click OK.
Note that this incremented value should not be same number as the Repository ID of any
existing ODI Repository. The value you enter must be a numeric ID between 501 and 899.
4. Verify the new number by selecting the Master Repository. Right click and select Open to view
the Internal Id value that was set in the previous step.
53
5. Repeat for steps 1-4 to renumber the Work repository to the same value as the renumbered
Master repository.
54
Importing Content into the 11.1.1.8.1 ODI Repository
Importing Connection Details
1. Launch the ODI Studio client and connect to the ODI repository for BI Applications 11.1.1.8.1.
2. Navigate to the Topology tab. From the Connect Navigator (Topology icon dropdown on the top
right side of the navigator pane), select Import. As part of the procedures described below, you
will import the file created by exporting the ’Global’ context in step Exporting Connections
above.
3. In the Import Selection dialog, select Smart Import
55
4. In the File Selection screen, specify the export file created in step Exporting Connections above.
5. The default behavior of Smart Import is to Merge details in the target repository. Ensure that no
issues are reported – if issues are reported, resolve them to ensure the existing details are
replaced by the details being imported. Select the BIAPPS_DW and BIAPPS_BIACOMP Data
Servers and select the ‘Overwrite’ option and continue.
56
Verifying the Imported Details
As part of this procedure you will verify that the Physical Servers have the correct details and the
Physical Schemas have the correct Datasource Num ID value set in the DATASOURCE_NUM_ID flexfield.
1. In ODI Studio, navigate to Topology > Physical Architecture. Open the BIAPPS_DW physical
server.
2. Verify the User and Password are correctly populated under the Definition tab.
57
3. On the JDBC tab, verify that the JDBC URL is correctly set. If you used the default ‘Merge’ action
during the Smart Import, the User and Password will be updated but the JDBC URL will remain
unchanged.
4. Repeat steps 1-4 for the BIAPPS_BIACOMP physical server.
5. Verify the Physical schema for BIACOMP and DW are set as defaults. If they are not set as
defaults, Load Plans will fail.
1. In ODI Studio, navigate to Topology > Physical Architecture.
58
2. Open the physical schema under the BIAPPS_BIACOMP physical server.
3. Verify that the Default check box is checked on the Definition tab.
4. Check the Default check box if it is not checked. Save changes.
5. Repeat steps 2 to 4 for the physical schema under the BIAPPS_DW physical server.
59
6. Verify the source connection details. For example, if you need to extract from an instance of
eBusiness Suite 11.5.10, open the corresponding physical server (here named
EBS11510_DEFAULT) and verify the User/Password and JDBC.
7. Also verify the associated physical schema. Navigate to the Flexfields tab and verify the
DATASOURCE_NUM_ID flexfield is set to the value you originally assigned. This value of the
DATASOURCE_NUM_ID must match the value in BI Applications Configuration Manager for this
source connection.
60
8. Open the corresponding logical schema and verify the DATASOURCE_NUM_ID flexfield is also
set with the same value.
61
Importing Security
As part of this procedure you will import the Security settings that you exported in step Exporting
Security above. The import of Security settings is done using the Insert/Update option.
1. In the Topology tab, from the Connect Navigator (Topology icon dropdown on the top right side
of the navigator pane), select Import.
2. In the Import Selection dialog, select Import Security Settings.
62
3. In the Import Security Settings dialog, select Synonym Mode INSERT_UPDATE for the Import
Mode. Select the Import from a Folder radio button. Enter the directory location to which you
had exported the Security settings in step Exporting Security above.
4. Click Yes in the Confirmation dialog.
63
After the import is complete, the SUPERVISOR user may no longer be enabled. To ensure you can still
connect to the ODI repository in case of any issues, you should enable this user by ensure the
‘Supervisor’ property is set and this user does not have an expiration date. Once external authentication
is complete, you can log in with another administrative user and disable the Supervisor user.
5. Restart the ODI Managed Server using Weblogic Administration Console.
Once logged out of ODI Studio, you will have to log in with the administrative user configured in the
prior ODI repository. For example, if your administrative user that you previously used to connect to the
pre-upgrade ODI repository was named Administrator1, you would log in with this user. Follow these
steps to enable this user for external authentication.
In order to be able to log into the ODI Repository as the administrative user, the ODI Repository for BI
Applications 11.1.1.8.1 has to be configured for External Authentication, as described below.
Reconfiguring External Authentication
1. Disconnect from the ODI Repository by selecting the ODI menu and then the Disconnect
“<User>” menu item.
64
2. From the ODI menu select the Switch Authentication Mode menu item
3. Enter the database connection details on the Login screen. Click Next.
4. On the Credentials screen click Finish
The following Information dialog is displayed to indicate that the repository was successfully switched to
External Authentication. You should see at least two users are matched. Note that the SUPERVISOR user
defined in ODI will not be matched to anything in the security store.
65
You can now connect to ODI using externally authenticated users; for example, the BI Applications
Administrator User.
If you receive the following error when switching to External Authentication, then you have not
configured the security files required for external authentication on the instance of ODI Studio you are
using.
To configure user access, see section 3.3.9.2 Configuring User Access for ODI Studio in the BI
Applications Installation Guide for 11.1.1.8.1.
5. If required, create a connection in ODI Studio to the ODI Repository for 11.1.1.8. The repository
is set to External Authentication. The credentials you use to connect to the repository are those
of the BI Applications Administrator user.
6. You should now connect as this user and disable access for the SUPERVISOR user.
66
NOTE:
a) When switching from ODI internal to FMW security, Make sure that the ODI users had no expiry
dates (including SUPERVISOR)
b) If users had expiry dates , Change the expiry dates and make sure none of the users were disabled,
after doing the security import
Regenerating Load Plans
Load Plans that were originally generated in the ODI Repository for 11.1.1.7.1 do not exist in the ODI
Repository for 11.1.1.8.1. The steps to transfer content from the 11.1.1.7.1 Repository to the 11.1.1.8.1
Repository do not include transferring the original load plans. The load plans will not reflect any changes
introduced as part of the upgrade so a new load plan must be generated.
Configuration Manager retains the Load Plan definitions on upgrade even though any metadata
associated with this load plan that was stored in ODI is no longer available. Use these existing
definitions in Configuration Manager to regenerate load plans including Domains Only Load Plans. Note
that any tasks that had previously executed pre-upgrade will execute in incremental mode post-upgrade
while any new tasks that may be introduced in the generated load plan will initially execute in full mode.
1. Log into BI Applications Configuration Manager as the BI Applications Administrator user.
2. Navigate to Manage Load Plans.
3. Regenerate all Load Plans including the Domains-Only Load Plans.
Refer to the Configuration Manager online help for the Manage Load Plans screen and the BI
Applications ETL Guide for 11.1.1.8.1 for more details on how to regenerate the load plan with
the existing load plan definition.
Part II - Business Analytics Warehouse Schema and Data Upgrades
 This section outlines the steps to perform a warehouse schema and data upgrade from
11.1.1.7.1 to 11.1.1.8.1. Before performing the steps outlined in this section of the document,
you must have completed all steps described in section Part I - BI Applications Infrastructure,
Metadata and Schema UpgradesBefore starting the Upgrade process from BI Applications
67
11.1.1.7.1 to 11.1.1.8.1, you must have executed at least one incremental run in addition to a
full data load in your BI Applications 11.1.1.7.1 environment.
 Take the backup of MWHOME folder before upgrade
 Review the Certification Matrix for BI Applications version 11.1.1.8.1. The Certification Matrix is
available on the Fusion Middleware Certification Page on Oracle Technology Network (OTN).
Part I - BI Applications Infrastructure, Metadata and Schema Upgrades.
The upgrade of the Business Analytics Warehouse schema and data upgrade are achieved by executing
predefined Upgrade Load Plans in ODI Studio. You need to select the appropriate Load Plan, based on
the source version deployed.
NOTE: The Upgrade Load Plans can only be executed from ODI Studio.
Granting New Required Privileges to <prefix>_DW
BI Applications 11.1.1.8.1 requires that the <prefix> _DW schema/user be granted the CREATE JOB
privilege.
Work with your Database Administrator to grant the CREATE JOB privilege to the <prefix> _DW
schema/user.
68
This privilege must be granted before you can execute the Upgrade Load Plans described later in this
section.
Identifying the Upgrade Load Plans to Execute
You will run an Upgrade Load Plan for each source you have registered in your BI Applications. You must
first identify which Upgrade Load Plans you need to execute:
1. Log into ODI Studio using the connection for the BI Applications Administrator user.
2. Navigate to Designer tab > Load Plans and Scenarios.
3. Expand the Predefined Load Plans folder and then the Upgrade folder.
4. From the list of Upgrade Load Plans, determine and note which Upgrade Load Plans you will run
based on the transactional systems from which you are sourcing data into BI Applications.
You will later run an Upgrade Load Plan for each source registered in your BI Applications.
Modifying the Upgrade Load Plans
As part of this procedure you will modify the Upgrade Load Plans which you have identified in section
Identifying the Upgrade Load Plans to Execute above.
In preparation for executing the Upgrade Load Plans, you must
1. In ODI Studio > Designer tab > Load Plans and Scenarios > Predefined Load Plans > Upgrade,
select an Upgrade Load Plan which you will be executing. Double-click the Load Plan to open for
editing.
69
2. Navigate to the Steps tab, and select the highest level node (example, EBS_1150 as shown in the
screenshot). Open the Property Inspector, which displays in the lower pane.
3. In the Properties Inspector, select the variable named BIAPPS.DATASOURCE_NUM_ID. Uncheck

the Overwrite option for this variable.
4. If you are modifying the BIApps 111171 to 111180 EBS 11510 Load Plan, then perform the
action documented in this step. If you are not modifying the BIApps 111171 to 111180 EBS
11510 Load Plan then move to step 5 below.
On the Upgrade BIApps 111171 to 111180 EBS 11510 Load Plan > Steps tab:
a. Navigate to the Upgrade_DW step. Expand this node.
70
b. Expand the Upgrade_DW_Copy node
c. Select the GENERATE_UPGRADE_DDL_COPY_TABLES scenario under the

Upgrade_DW_Copy node.
d. Open the Property Inspector, if not open.
e. Navigate to the Scenario Variables pane.
f. For the variable BIAPPS.UTIL_GENDDL_SCRIPT_LOCATION, uncheck the checkbox for the

Overwrite column.
5. If you are modifying any of the following Upgrade Load Plans, then perform the actions
documented in this step. If you are not modifying any of these Load Plans then move to step 6
below.
 Upgrade BIApps 111171 to 111180 EBS 11510

71
On the Upgrade Load Plan (noted above) > Steps tab:
a. Navigate to the UPGRADE_DIMENSIONS step. Expand this node.
b. Select the ‘Is PROJECTS enabled’ case statement. Check the check box in the Enabled
column
6. Save all changes made to the Upgrade Load Plan being modified.
7. Repeat steps 1 through 6 for each Upgrade Load Plan you will execute.
Upgrading the Business Analytics Warehouse Schema
In this procedure, you will make a copy of each Upgrade Load Plan you will run based on the
transactional systems from which you are sourcing data into BI Applications. The copied Load Plans will
72
then be modified to include only the step that upgrades the Business Analytics Warehouse schema. You
will run a copied and modified Upgrade Load Plan for each source registered in your BI Applications.
To upgrade the Business Analytics Warehouse schema:
In ODI Studio, select an Upgrade Load Plan you modified in section
1. Modifying the Upgrade Load Plans above.
2. Right-click and select Duplicate Selection.
73
3. In the Confirmation dialog, click Yes.
4. A copy of the Upgrade Load Plan is created with prefix “Copy of” added to the name of the
original Upgrade Load Plan.
5. Select the copied Upgrade Load Plan and double-click to open for editing.
6. Navigate to the Steps tab and disable all steps below the Upgrade_DW step by unchecking the
check box in the Enabled column.
7. Save the changes made to the copied Load Plan.

74
8. Execute the copied Load Plan.
Repeat steps 1 through 8 for each Upgrade Load Plan you modified in section
9. Modifying the Upgrade Load Plans above.
Running Domains-Only Load Plan(s)
Before you run the Upgrade Load Plans to upgrade the data in the Business Analytics Warehouse, you
must first execute the Domains-Only Load Plans. This loads any new source domains into Configuration
Manager.
Note: Before running Domain-Only Load Plans. You must first execute “Upgrade BIApps 111171 to
111180 BIA11 Internal Tables” predefined load plan in order to upgrade the data warehouse domain
specific internal tables.
75
Load plan should be available under the below location
Predefined Load Plans----> Upgrade---->
2. In the Tasks pane of Oracle BI Applications Configuration Manager, select Manage Load Plans,
which appears under the Load Plans Administration heading.
3. The Manage Load Plans page displays the list of generated Load Plans including the Domains-
Only Load Plans.
NOTE: If you have not regenerated the Load Plans as described in section NOTE:
a) When switching from ODI internal to FMW security, Make sure that the ODI users had no expiry
dates (including SUPERVISOR)
b) If users had expiry dates , Change the expiry dates and make sure none of the users were disabled,
after doing the security import
Regenerating Load Plans above then you must do so before you can execute the Domains-Only
Load Plans.
4. Execute the Domains-Only Load Plans. If you have more than one Domain-Only Load Plan then
you must execute all of them.
76
Performing Domain Member Mappings
Perform domain member mappings for any new conformed domains that have been introduced in
BI Applications Configuration Manager. See the BI Applications Configuration Guide for 11.1.1.8.1.
Also, map externally conformed domains as described in section 4.7 Mapping Externally Conformed
Domains of the BI Applications Installation Guide
Upgrading Data in the Business Analytics Warehouse (Data Migration)

Synchronizing the Data Model
In this step, you execute SQL statements (DML and DDL) in order to synchronize the Business
Analytics Warehouse.
Execute the SQL statements listed below against the Business Analytics Warehouse (<prefix_DW).
These statements must be executed before you run the Upgrade Load Plans to upgrade the data in
warehouse.
/* execute the following SQL statements prior to executing the upgrade

load plan */
ALTER TABLE W_APPL_EVENT_F MODIFY HIRING_MGR_HR_ASSG_WID NUMBER(10) NULL;

ALTER TABLE W_APPL_ACC_SNP_F MODIFY HIRING_MGR_HR_ASSG_WID NUMBER(10) NULL;
create table c0w_hr_person_leg_d

as select * from w_hr_person_leg_d;
update w_hr_person_leg_d
set integration_id = integration_id || '~' || legislation_code
where integration_id <> '0'
and exists
(select 1 from w_ora_wevt_asg_ps x
where x.datasource_num_id = w_hr_person_leg_d.datasource_num_id);
commit;
/* Run before upgrade or when error is encountered upgrading W_WRKFC_SNP_F */

CREATE TABLE W0WRKFC_SNP_F AS SELECT * FROM W_WRKFC_SNP_F;
TRUNCATE TABLE W_WRKFC_SNP_F;
77
ALTER TABLE W_FLEX_COLUMN_G ADD (COLUMN_CONTEXT_CASE VARCHAR2(4000 CHAR));
ALTER TABLE W_FLEX_COLUMN_G ADD (ATTRIBUTE_CATEGORY VARCHAR2(30 CHAR));
ALTER TABLE W_FLEX_COLUMN_G ADD (COMPONENT_VALUE VARCHAR2(30 CHAR));
ALTER TABLE W_FLEX_COLUMN_G ADD (DISPLAY_SEQUENCE NUMBER(10));
delete from w_domain_member_map_g

where trg_domain_code = 'W_UOM' and src_domain_member_code IN ('Miles', 'HOURS');
commit;
DELETE FROM W_QA_RESULTS_F

WHERE CHAR_WID =0;
COMMIT;
Performing Pre-Upgrade Tasks
Identifying Data Source Number for a Registered Source
When executing the Upgrade Load Plan in a later step, you will need to provide the Data Source Number
for the source. During the set up of BI Applications 11.1.1.7.1, you provided a Data Source Number for
each registered source in BI Applications Configuration Manager. As part of this step, you will identify
the Data Source Number for each source:
2. In the navigation pane, select the Define Business Intelligence Applications Instance link.
3. In the Source Systems tab, in the Source Systems table, for each enabled registered source, note
the Data Source Number.
Updating ETL Parameters (Required for Supply Chain and Order Management Analytics for
EBS and JDE sources)
You must perform the tasks described in this section if you have deployed Supply Chain and Order
Management Analytics. If you have not deployed Supply Chain and Order Management Analytics then:
78
 Skip to section Noting Variable Value (Required if your source is PeopleSoft versions 9.0, 9.1 or
9.2) below if you are sourcing data from PeopleSoft version 9.0, 9.1 or 9.2.
Skip to section
 Executing Upgrade Load Plan(s) to upgrade data in the Business Analytics Warehouse below if
you are not sourcing data from PeopleSoft version 9.0, 9.1 or 9.2.
If you have deployed Supply chain and Order Management Analytics in BI Applications 11.1.1.7.1 and
have enabled the Customer Status History Fact Group (OM_CUSTSTATHISTFG), then you must update
the certain ETL parameters prior to executing the Upgrade Load Plans to upgrade data in the
warehouse.
To update the ETL parameters:
1. In ODI Studio, open the Upgrade Load Plan.
2. Navigate to the UPGRADE_FACTS step. Expand this node.
3. Navigate to Is ORDER MANAGEMENT enabled > When Value = Y > ORDER MANGEMENT >
OM_SERIAL > OMCUSTSTATIST_FG
79
4. Open the Property Inspector.
You will update the following variables as described in the next steps:
BIAPPS.CURRENT_DATE
BIAPPS.CURRENT_DATE_WID
BIAPPS.PERIOD
80
5. The value of the CURRENT_DATE variable depends on the last incremental run. To obtain the
value that this variable should be set to and to update the variable:
a. Run the following query against the <prefix>_DW schema
SELECT TO_CHAR(CALENDAR_DATE, 'YYYY-MM-DD HH:MM:SS') FROM W_DAY_D WHERE

W_CURRENT_CAL_DAY_CODE='Current';
b. In ODI Studio, update the value of the BIAPPS.CURRENT_DATE variable to the value
returned by the above query.
6. The value of the CURRENT_DATE_WID variable depends on the last incremental run. To obtain
the value that this variable should be set to and to update the variable:
a. Run the following query against the <prefix>_DW schema
81
SELECT ROW_WID FROM W_DAY_D WHERE W_CURRENT_CAL_DAY_CODE='Current';
b. In ODI Studio, update the value of the BIAPPS.CURRENT_DATE_WID variable to the

value returned by the above query.
7. The value of the PERIOD variable depends on the last incremental run. To obtain the value that
this variable should be set to and to update the variable:
a. Run the following query against the <prefix>_BIACOMP schema
SELECT PARAM_VALUE FROM C_PARAMETER_VALUE_FORMATTER_V

WHERE
PARAM_CODE = 'PERIOD' AND
GROUP_CODE = 'OMCUSTSTATHIST_FG' AND
DATASOURCE_NUM_ID=999;
b. In ODI Studio, update the value of the BIAPPS.PERIOD variable to the value for
PARAM_VALUE returned by the above query.
8. Save the changes to the Upgrade Load Plan.
Noting Variable Value (Required if your source is PeopleSoft versions 9.0, 9.1 or 9.2)
You must perform the tasks described in this section if you are sourcing data from PeopleSoft version
9.0, 9.1, or 9.2. If you are not sourcing data from PeopleSoft version 9.0, 9.1 or 9.2 then skip to section
Executing Upgrade Load Plan(s) to upgrade data in the Business Analytics Warehouse below
If you are sourcing data from PeopleSoft version 9.0, 9.1, or 9.2 then you must complete the tasks
described in this section.
82
When upgrading BI Applications sourcing from PSFT 9.0, 9.1, 9.2, the W_INT_ORG_D dimension requires
a special set of parameters to be passed while starting the Upgrade Load Plans. These parameters will
take values depending on your configuration.
Determine the values for these parameters by running queries against the BI Applications Components
schema (<prefix>_BIACOMP) as described below. The query to obtain the values for these parameters is
of the format:
select * from C_PARAMETER_VALUE_FORMATTER_V where param_code = '<Variable name from the

above list>' and group_code = 'INTORG_DIM';
1. For each variable noted column A in the table below, run the SQL Query noted in column B
against the <prefix>_BIACOMP schema.
2. In the query results, select the value for the row with the correct DATASOURCE_NUM_ID value.
The DATASOURCE_NUM_ID should match DSN value you identified for your PeopleSoft source
in step Identifying Data Source Number for a Registered Source above.
3. Note the value. Column C shows the format of the value.
A B C
Variable SQL Query (against <prefix>_BIACOMP Value (returned from query run
and for the DATASOURCE_NUM_ID for in your environment
the source)
TREE_CURRENT_VERSION_ONLY select * from (Value is Y or N, without quotes)

C_PARAMETER_VALUE_FORMATTER_V
where param_code = '
TREE_CURRENT_VERSION_ONLY ' and
group_code = 'INTORG_DIM';
TREE_SETID_NAME_LIST_DEPT select * from (Value should of the format

C_PARAMETER_VALUE_FORMATTER_V 'A~A1','B~B1' )
TREE_SETID_NAME_LIST_DEPT' and
TREE_STRUCT_ID_LIST_DEPT select * from (Value should be of the format

C_PARAMETER_VALUE_FORMATTER_V 'A','B' format)
TREE_STRUCT_ID_LIST_DEPT ' and
83
TREE_SETID_NAME_LIST_COMPANY select * from (Value should be like

C_PARAMETER_VALUE_FORMATTER_V 'A~A1','B~B1' format)
TREE_SETID_NAME_LIST_COMPANY'
and group_code = 'INTORG_DIM';
TREE_STRUCT_ID_LIST_COMPANY select * from (Value should be like 'A','B'

C_PARAMETER_VALUE_FORMATTER_V format)
TREE_STRUCT_ID_LIST_COMPANY’ and
The screen shot below shows the result from the <prefix>_BIACOMP for the
‘TREE_SETID_NAME_LIST_DEPT' variable.
Executing Upgrade Load Plan(s) to upgrade data in the Business Analytics Warehouse
As part of this procedure, you will execute Upgrade Load Plans to upgrade the data in the Business
Analytics Warehouse.
You will execute the Upgrade Load Plans based on the transactional systems and versions that are
sources of data for your BI Applications. You identified the Upgrade Load Plans you need to run in
section Identifying the Upgrade Load Plans to Execute above.
To execute the Upgrade Load Plans:

84
4. From the list of Upgrade Load Plans, select the Upgrade Load Plan which you will run.
NOTE: You must have completed the modifications described in section Modifying the Upgrade
Load Plans above to the Upgrade Load Plan you will execute.
5. Double-click the selected Load Plan to open.
6. Click on the Execute icon.
When the execute button is clicked a Start Load Plan dialog window appears. You will provide
Start Up Values for variables in this dialog.
7. Enter the value for the BIAPPS.DATASOURCE_NUM_ID variable. This value is the Data Source
Number that you identified for the source in section Identifying Data Source Number for a
Registered Source above.
85
Note that it is critical to provide the correct DATASOURCE_NUM_ID (DSN) which matches the
value for DSN entered in Configuration Manager for this source. This DSN is a composite key
used to update the Warehouse tables.
8. If you are running an Upgrade Load Plan for PeopleSoft source version 9.0, 9.1 or 9.2, then
additionally enter the values for the following variables:
TREE_CURRENT_VERSION_ONLY
TREE_SETID_NAME_LIST_DEPT
TREE_STRUCT_ID_LIST_DEPT
TREE_SETID_NAME_LIST_COMPANY
86
TREE_STRUCT_ID_LIST_COMPANY
The values for these variables were identified in step Noting Variable Value (Required if your
source is PeopleSoft versions 9.0, 9.1 or 9.2) above.
9. Click OK to start the execution.
The relevant steps in the Upgrade Load Plan are executed based on the BI Applications Offerings
that are enabled in Configuration Manager.
10. When the Load Plan completes execution, repeat steps 4 to 9 for each additional Upgrade Load
Plan you had identified to execute.
87
Post-Upgrade Tasks
After you have completed execution of the Upgrade Load Plan(s), you need to execute a set of SQL
statements. For the SQL Statements that need to be run, see Appendix > Post-Upgrade SQL Statements
Importing and Applying Customizations

Once the DDL and Data Upgrade steps are complete, it is time to import the customizations into the
post-upgrade repository.
If you have separate ODI repositories for Development (DEV), Testing (TEST) and Production (PROD),
there is a difference in the steps for getting the customizations into the post-upgrade DEV repository
and into the post-upgrade TEST or PROD repository. Assuming that only DEV is open to developers to
make changes and TEST and PROD instances are locked down so content can only be migrated, the
following summarizes the steps.
DEV TEST/PROD
Imports Customizations using Regular Migrate Customizations using Smart

Export/Import Export/Import
Pre-Upgrade Dev Repo Post-Upgrade Dev Repo
 Export Custom Folders  Smart Export of Custom Folders
 Export Custom Datastores
Test/Prod Repo
Post-Upgrade Dev Repo  Smart Import of Custom Folders
 Version Model
 Version Model again
 Import Custom Datastores
 Import Custom Folders
 Reapply Customizations
 Generate Custom Scenarios
88
 Apply Customizations to Generated Load
Plan
The following sections describe the process to import the customizations previously exported from the
pre-upgrade repository into the post-upgrade DEV repository. Refer to the T2P ODI Migration
document for the steps to migrate the customizations from the DEV repository to TEST and PROD
repositories.
An important difference in the two processes is the use of Regular and Smart import. Smart import’s
default behavior is to overwrite the target while Regular import allows us to merge with the target.
Smart import brings a lot of extra objects while Regular import just brings the objects you specified.
When moving from pre-upgrade to post-upgrade, we want to move only the customized objects. Using
Smart import would bring almost all objects from the pre-upgrade repository and by default overwrite
the objects in the post-upgrade repository. As the post-upgrade repository includes bug fixes and
enhanced functionality, we would lose all of that and replace it with the legacy pre-upgrade objects.
Regular import does not bring these extra objects with it.
When moving from DEV to TEST, the objects in the DEV repository should be replacing the objects in
TEST as they represent the bug fixes and enhanced functionality. For migrating, we use Smart Import to
bring all objects as these objects should always take precedence and overwrite what is in the target.
Very important! The following steps are implemented in the DEV repository only. For migrating
changes to TEST and PROD repositories, you follow the T2P Migration document.
Import Datastores
It is important to import the datastores first prior to importing the customized ETL tasks.
To import the customizations:
1. Launch the ODI Studio client and connect to the ODI Repository for BI Applications 11.1.1.8.1.
2. Navigate to Designer -> Models -> Oracle BI Applications (folder) -> Oracle BI Applications
(Model)
3. Create Original and Custom versions of the model
a. Right click the model, select Version -> Create Version. Create an initial version.
89
b. Perform these steps again to create the version with customizations.
c. Once the second version is complete, the two versions will match. However, after the
customizations are imported, the two will no longer match. The original version reflects
the out-of-the-box datastores while the new version reflects the merged datastores,
allowing comparison between the two.
4. Import the customized datastores
 Right click the Oracle BI Applications model.
 Select the ‘Import…’ – ‘Import Datastore…’ option
 In the Import Datastore window, ensure ‘Import Type’ is ‘Synonym Mode INSERT’. Update
mode will update existing columns to reflect their pre-upgrade state while Insert/Update
90
mode will delete columns that were introduced in the upgrade repository but do not exist in
the pre-upgrade repository.
 Navigate to the directory where you previously exported the custom datastores
 Check the boxes for each datastore to be imported and click ‘OK’
If prompted to declare the repository ID and continue with the import, select ‘Yes’. You may see this
prompt multiple times, click ‘Yes’ each time.
When the import completes, you should see a summary report similar to the following.
91
The upgrade datastores will now be merged with the pre-upgrade customizations.
Review the customized out-of-the-box datastores that have been imported.
Navigate to the ‘Columns’ tab
In INSERT mode, the import will bring in the custom columns into datastore. In the 7.1 repository, these
are usually the last columns. In the 8.1 repository, Oracle may have added columns and these will have
a conflicting position ID. Or a column simply may have moved between 7.1 and 8.1. These columns will
92
appear to have the same position number but this does not cause any issues. As an optional step, you
can have ODI recalculate the position numbers.
Double click on any column in the datastore. Without making any changes, now select another column.
ODI will automatically recalculate the position numbers. Save the datastore.
Import Customized ETL tasks

1. Launch the ODI Studio client and connect to the ODI Repository for BI Applications 11.1.1.8.1.
2. Navigate to Designer -> Projects -> BI Apps Project -> Mappings
3. Right Click ‘Mappings’ and select ‘Import…’ – ‘Import Sub Folder…’
93
 In the Import Sub-Folder window, ensure ‘Import Type’ is ‘Synonym Mode INSERT’
 Navigate to the directory where you previously exported the custom folders
 Check the boxes for each folder to be imported and click ‘OK’
94
When the import completes, you can see your custom folder and its corresponding customized objects.
At this point, it is necessary to merge any customizations with any changes that may have been
introduced in the upgrade repository. For example, a column may have been added to a table that was
customized (as in the W_GL_OTHER_F example earlier) or bug fixes applied or content otherwise
changed by Oracle.
There is no automatic merge mechanism available. The customized and out-of-the-box ETL tasks must
be inspected for changes and the changes manually incorporated into the other. The recommended
approach is to re-copy the out-of-the-box ETL task and re-apply the customizations to this new copy.
Since you are far more familiar with the changes you have made it should be easier to incorporate these
into the new copy rather than figure out the changes Oracle made and incorporate these into your
original copy.
1. Rename the customized ETL task to reflect the pre-upgrade version it was based on.
2. Duplicate the out-of-the-box ETL task per the customization methodology and move to the
Custom folder
95
Inspect the customized ETL task. The custom columns are populated but any new columns
introduced by Oracle are not.
Below is an example of a customized interface. Make a note of the customizations made.
96
Below is the copied interface where the new columns introduced by Oracle are populated but
the custom columns are not. Apply the customizations noted previously in this interface.
97
Generate a Scenario for the newly customized ETL task. Ensure the Scenario Name matches the
out-of-the-box Scenario Name but use a Version Number that is larger than any previously used
Version Number. The BI Apps Load Plans are configured to run the scenario with the largest
number. By retaining the same scenario name and assigning the largest scenario version
number, you do not have to make any changes to the load plan.
98
Apply Customizations to the Generated Load Plans as per the Customization methodology.
Appendix
Creating a Connection in ODI to the 11.1.1.7.1 Back-up ODI Repository
This section describes how to create a new connection in ODI Studio to the back-up of the ODI
Repository for 11.1.1.7.1 which is now in a new database schema. See section Creating a Back up of the
11.1.1.7.1 ODI Repository above for reference.
To create a new connection in ODI Studio to the back-up of the ODI Repository for 11.1.1.7.1:
99
Configure the connection to use the same ODI user you used before. Configure the connection as a
Master Repository connection. Connect to the repository and navigate to Topology -> Repositories ->
BIAPPS_WORKREP. Edit the repository to change the database user details used by the Work Repository
to use the new schema.
Disconnect from the repository, reconfigure the connection to include the Work Repository, connect
and verify all details are correct.
Post-Upgrade SQL Statements
/* Run after upgrade */

INSERT INTO W_WRKFC_SNP_F (
100
ASSIGNMENT_ID,
WRKFC_SNP_WID,
SNAPSHOT_EFFECTIVE_DT,
MANAGER_ROLE_IND,
HOME_ASSIGNMENT_ID,
PERSON_INTEGRATION_ID,
CHANGE_EVENT_TYPE,
EVENT_YEAR,
ASSIGNMENT_NUMBER,
ASSIGNMENT_TYPE,
EVENT_DT_WID,
EVENT_MONTH_WID,
EVENT_QTR_WID,
EVENT_YEAR_WID,
EMPLOYEE_WID,
HR_ASSIGNMENT_WID,
HR_PERSON_WID,
HR_PERSON_LEG_WID,
HR_ORG_WID,
HR_ORG_PRV_WID,
JOB_WID,
JOB_PRV_WID,
PAY_GRADE_WID,
PAY_GRADE_PRV_WID,
HR_POSITION_WID,
HR_POSITION_PRV_WID,
LOCATION_WID,
LOCATION_PRV_WID,
SUPERVISOR_WID,
SUPERVISOR_PRV_WID,
SUP_HR_PERSON_WID,
EMPLOYMENT_WID,
SUP_HR_ASSIGNMENT_WID,
ESTABLISHMENT_WID,
HR_BUSINESS_UNIT_WID,
SUP_HR_PERSON_PRV_WID,
SUP_HR_PERSON_LEG_WID,
COMPANY_ORG_WID,
EVENT_TYPE_RSN_WID,
EMP_POSTN_DH_WID,
INTL_ASSGN_WID,
AGE_BAND_WID,
PERFORMANCE_BAND_WID,
PERFORMANCE_BAND_PRV_WID,
PRD_OF_WRK_BAND_WID,
101
ENTERPRISE_WID,
COST_CENTER_WID,
COMPARATIO_BAND_WID,
SALARY_BAND_WID,
HIRE_DT,
LAST_HIRE_DT,
POW_START_DT,
BIRTH_DT,
ORG_ENTRY_DT,
JOB_ENTRY_DT,
GRD_ENTRY_DT,
POS_ENTRY_DT,
LOC_ENTRY_DT,
LAST_PROM_DT,
LAST_SAL_INCR_DT,
HEADCOUNT,
HEADCOUNT_ASG,
FTE,
FTE_ASG,
SALARY_ANNL,
SALARY_MONTH,
SALARY_DAY,
SALARY_HOUR,
SALARY_ANNL_ASG,
SALARY_MONTH_ASG,
SALARY_DAY_ASG,
SALARY_HOUR_ASG,
COMPARATIO,
TOTAL_SERVICE_DAYS,
CURRENT_SERVICE_DAYS,
CURRENT_SERVICE_MONTHS,
AGE_IN_MONTHS,
NRMLSD_PERF_RATING,
NRMLSD_PERF_RATING_ASG,
ORIG_PERF_RATING,
STD_HOURS_MONTH,
STD_HOURS_DAY,
IASG_ALLCTN_FACTOR,
EMP_IND,
CWK_IND,
DOC_CURR_CODE,
LOC_CURR_CODE,
LOC_EXCH_RATE_TYPE,
LOC_EXCHANGE_RATE,
EXCHANGE_DT,
102
GLOBAL1_EXCHANGE_RATE,
CREATED_BY_WID,
CHANGED_BY_WID,
CREATED_ON_DT,
CHANGED_ON_DT,
AUX1_CHANGED_ON_DT,
AUX2_CHANGED_ON_DT,
AUX3_CHANGED_ON_DT,
AUX4_CHANGED_ON_DT,
EFFECTIVE_FROM_DT,
EFFECTIVE_TO_DT,
DELETE_FLG,
W_INSERT_DT,
W_UPDATE_DT,
DATASOURCE_NUM_ID,
ETL_PROC_WID,
INTEGRATION_ID,
TENANT_ID,
X_CUSTOM)
select
ASSIGNMENT_ID,
WRKFC_SNP_WID,
SNAPSHOT_EFFECTIVE_DT,
MANAGER_ROLE_IND,
HOME_ASSIGNMENT_ID,
PERSON_INTEGRATION_ID,
CHANGE_EVENT_TYPE,
EVENT_YEAR,
ASSIGNMENT_NUMBER,
ASSIGNMENT_TYPE,
EVENT_DT_WID,
EVENT_MONTH_WID,
EVENT_QTR_WID,
EVENT_YEAR_WID,
EMPLOYEE_WID,
HR_ASSIGNMENT_WID,
HR_PERSON_WID,
HR_PERSON_LEG_WID,
HR_ORG_WID,
HR_ORG_PRV_WID,
JOB_WID,
JOB_PRV_WID,
PAY_GRADE_WID,
103
PAY_GRADE_PRV_WID,
HR_POSITION_WID,
HR_POSITION_PRV_WID,
LOCATION_WID,
LOCATION_PRV_WID,
SUPERVISOR_WID,
SUPERVISOR_PRV_WID,
SUP_HR_PERSON_WID,
EMPLOYMENT_WID,
SUP_HR_ASSIGNMENT_WID,
ESTABLISHMENT_WID,
HR_BUSINESS_UNIT_WID,
SUP_HR_PERSON_PRV_WID,
SUP_HR_PERSON_LEG_WID,
COMPANY_ORG_WID,
EVENT_TYPE_RSN_WID,
EMP_POSTN_DH_WID,
INTL_ASSGN_WID,
COALESCE(AGE_BAND_WID, -2),
PERFORMANCE_BAND_WID,
PERFORMANCE_BAND_PRV_WID,
COALESCE(PRD_OF_WRK_BAND_WID, -1),
ENTERPRISE_WID,
COST_CENTER_WID,
COMPARATIO_BAND_WID,
SALARY_BAND_WID,
HIRE_DT,
LAST_HIRE_DT,
POW_START_DT,
BIRTH_DT,
ORG_ENTRY_DT,
JOB_ENTRY_DT,
GRD_ENTRY_DT,
POS_ENTRY_DT,
LOC_ENTRY_DT,
LAST_PROM_DT,
LAST_SAL_INCR_DT,
HEADCOUNT,
HEADCOUNT_ASG,
FTE,
FTE_ASG,
SALARY_ANNL,
SALARY_MONTH,
SALARY_DAY,
SALARY_HOUR,
104
SALARY_ANNL_ASG,
SALARY_MONTH_ASG,
SALARY_DAY_ASG,
SALARY_HOUR_ASG,
COMPARATIO,
TOTAL_SERVICE_DAYS,
CURRENT_SERVICE_DAYS,
CURRENT_SERVICE_MONTHS,
AGE_IN_MONTHS,
NRMLSD_PERF_RATING,
NRMLSD_PERF_RATING_ASG,
ORIG_PERF_RATING,
STD_HOURS_MONTH,
STD_HOURS_DAY,
IASG_ALLCTN_FACTOR,
EMP_IND,
CWK_IND,
DOC_CURR_CODE,
LOC_CURR_CODE,
LOC_EXCH_RATE_TYPE,
LOC_EXCHANGE_RATE,
EXCHANGE_DT,
CREATED_BY_WID,
CHANGED_BY_WID,
CREATED_ON_DT,
CHANGED_ON_DT,
AUX1_CHANGED_ON_DT,
AUX2_CHANGED_ON_DT,
AUX3_CHANGED_ON_DT,
AUX4_CHANGED_ON_DT,
EFFECTIVE_FROM_DT,
EFFECTIVE_TO_DT,
DELETE_FLG,
W_INSERT_DT,
W_UPDATE_DT,
DATASOURCE_NUM_ID,
ETL_PROC_WID,
INTEGRATION_ID,
TENANT_ID,
X_CUSTOM
from W0WRKFC_SNP_F;
commit;
105
UPDATE W_PROJ_COST_LINE_F
SET PRVDR_ENTERPRISE_GL_DT_WID =
TO_NUMBER(SUBSTR(PRVDR_ENTERPRISE_GL_DT_WID, LENGTH(PRVDR_GL_MCAL_CAL_WID)+ 1, 8))
WHERE PRVDR_ENTERPRISE_GL_DT_WID <> 0;
COMMIT;
UPDATE W_ETL_LOAD_DATES
SET COMMITTED = '0'
WHERE TARGET_TABLE_NAME IN ('W_PROJ_COST_A','W_PROJ_COST_LINE_TMP','W_PROJ_COST_A_TMP');
COMMIT;
UPDATE W_ETL_LOAD_DATES
SET COMMITTED = '0'
WHERE PACKAGE_NAME LIKE '%SDE_ORA_DOMAINGENERAL_PROJECTSTATUS'
OR PACKAGE_NAME LIKE '%SDE_ORA_STATUSDIMENSION_PROJECTSTATUS';
COMMIT;
106

OBIA 11 1 1 8 1 Upgrade Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OBIA 11 1 1 8 1 Upgrade Guide

Uploaded by

Copyright:

Available Formats

ORACLE BI APPLICATIONS 11.1.1.8.

Part I - BI Applications Infrastructure, Metadata and Schema Upgrades ..................................................... 6

Downloading BI Applications 11.1.1.8.1 software and files ..................................................................... 6

Upgrading the BI Applications binaries to version 11.1.1.8.1................................................................... 6

Rolling back any latest BIFNDN patch ....................................................................................................... 8

Applying Fusion Middleware Platform Patches for BI Applications 11.1.1.8.1 ........................................ 8

Upgrading the JAZN file .......................................................................................................................... 11

Upgrading BIACOMP and BIACM_IO schemas........................................................................................ 11

Upgrading ATG, FSM and BIACM ........................................................................................................ 12

Upgrading the BIACM_IO Schema ...................................................................................................... 16

Granting Privileges to <prefix>_BIACM_IO schema............................................................................ 18

Enabling Deployment Changes to ATG and FSM in the BI Domain ........................................................ 18

Upgrading the RPD and Presentation Catalog ........................................................................................ 20

Correcting the Directory Name for Code Grants .................................................................................... 36

Applying Client-Side Patches .................................................................................................................. 37

Applying the ODI Patch to ODI Studio ................................................................................................ 37

Applying Patches to BI Administration Tool ....................................................................................... 37

Upgrading the ODI Repository ................................................................................................................ 38

Creating a Back up of the 11.1.1.7.1 ODI Repository.......................................................................... 38

Exporting Content from the 11.1.1.7.1 ODI Repository...................................................................... 38

Export Custom Folder ............................................................................................................................. 42

Export Customized Datastores................................................................................................................ 44

Dropping the 11.1.1.7.1 ODI Repository Schema ............................................................................... 46

Creating the ODI Repository for BI Applications 11.1.1.8.1................................................................ 48

Connecting to the ODI Repository for 11.1.1.8.1................................................................................ 50

Changing the ID of the 11.1.1.8.1 ODI Repository .............................................................................. 50

Importing Content into the 11.1.1.8.1 ODI Repository ...................................................................... 53

Regenerating Load Plans ..................................................................................................................... 65

Part II - Business Analytics Warehouse Schema and Data Upgrades ......................................................... 65

Granting New Required Privileges to <prefix>_DW................................................................................ 66

Identifying the Upgrade Load Plans to Execute ...................................................................................... 66

Modifying the Upgrade Load Plans ......................................................................................................... 67

Upgrading the Business Analytics Warehouse Schema .......................................................................... 70

Running Domains-Only Load Plan(s) ....................................................................................................... 71

Performing Domain Member Mappings ................................................................................................. 72

Upgrading Data in the Business Analytics Warehouse (Data Migration) ............................................... 72

Synchronizing the Data Model ............................................................................................................ 72

Performing Pre-Upgrade Tasks ........................................................................................................... 73

Importing and Applying Customizations ............................................................................................. 82

Import Datastores ............................................................................................................................... 83

Import Customized ETL tasks .............................................................................................................. 87

Creating a Connection in ODI to the 11.1.1.7.1 Back-up ODI Repository ............................................... 92

Post-Upgrade SQL Statements ................................................................................................................ 93

3. JAZN, RPD and Presentation Catalog

4. BI Applications Component Repository (BIACOMP)

5. ODI Repository content (BIA_ODIREPO)

6. Business Analytics Warehouse (DW) - schema

7. Data Migration of existing data in the Business Analytics Warehouse

1. Complete Upgrade Pre-requsites.

3. Apply the FMW Middleware Patches for BI Applications 11.1.1.8.1.

4. Use the BI Update Metadata Tool to upgrade the JAZN

6. Run scripts to enable deployment changes in BI Applications 11.1.1.8.1.

7. Upgrade the RPD and Presentation Catalog

9. Upgrade the ODI Repository metadata (content).

o Patch #1 – 17546359 (Services should be stopped)

o Patch #2 – 16873189 (Services should be stopped)

o Patch #3 - 17546336 ODI Cumulative Patch (Services should be started)

 Take the backup of MWHOME folder before upgrade

Part I - BI Applications Infrastructure, Metadata and Schema Upgrades

Downloading BI Applications 11.1.1.8.1 software and files

Upgrading the BI Applications binaries to version 11.1.1.8.1

setup.exe –jreLoc <JDK or JRockit location>

./runInstaller -jreLoc <jdk or jrockit location>