Вы находитесь на странице: 1из 72

Oracle BI Applications 11.1.1.8.

1
Upgrade Guide (Doc ID 1673221.1)

Contents
Contents ........................................................................................................................................................ 1
Overview ....................................................................................................................................................... 3
Pre-requisites ................................................................................................................................................ 4
Part 1 - BI Applications Infrastructure, Metadata and Schema Upgrades .................................................... 4
Downloading BI Applications 11.1.1.8.1 software and files ..................................................................... 4
Upgrading the BI Applications binaries to version 11.1.1.8.1................................................................... 4
Applying Fusion Middleware Platform Patches for BI Applications 11.1.1.8.1 ........................................ 6
Upgrading the JAZN file ............................................................................................................................ 8
Upgrading BIACOMP and BIACM_IO schemas .......................................................................................... 9
Upgrading ATG, FSM and BIACM ........................................................................................................ 10
Upgrading the BIACM_IO Schema ...................................................................................................... 14
Granting Privileges to <prefix>_BIACM_IO schema ............................................................................ 15
Enabling Deployment Changes to ATG and FSM in the BI Domain ........................................................ 16
Upgrading the RPD and Presentation Catalog ........................................................................................ 17
Correcting the Directory Name for Code Grants .................................................................................... 19
Applying Additional Patches ................................................................................................................... 20
Applying the Dynamic Monitoring Service Patch................................................................................ 20
Applying the ODI Patch to ODI Studio ................................................................................................ 20
Applying Patches to BI Administration Tool ....................................................................................... 20
Upgrading the ODI Repository ................................................................................................................ 21
Creating a Back up of the 11.1.1.7.1 ODI Repository.......................................................................... 21
Exporting Content from the 11.1.1.7.1 ODI Repository...................................................................... 22
Noting the ID of the 11.1.1.7.1 ODI Repository .................................................................................. 28
Dropping the 11.1.1.7.1 ODI Repository Schema ............................................................................... 30
Creating the ODI Repository for BI Applications 11.1.1.8.1 ................................................................ 31
Connecting to the ODI Repository for 11.1.1.8.1................................................................................ 33
Changing the ID of the 11.1.1.8.1 ODI Repository .............................................................................. 33
Importing Content into the 11.1.1.8.1 ODI Repository ...................................................................... 36
Regenerating Load Plans ..................................................................................................................... 49
Part II - Business Analytics Warehouse Schema and Data Upgrades ......................................................... 49
Granting New Required Privileges to <prefix>_DW ................................................................................ 50
Identifying the Upgrade Load Plans to Execute ...................................................................................... 51
Modifying the Upgrade Load Plans ......................................................................................................... 51
Upgrading the Business Analytics Warehouse Schema .......................................................................... 54
Running Domains-Only Load Plan(s) ....................................................................................................... 55
Performing Domain Member Mappings ................................................................................................. 56
Upgrading Data in the Business Analytics Warehouse (Data Migration) ............................................... 56
Synchronizing the Data Model ............................................................................................................ 56
Performing Pre-Upgrade Tasks ........................................................................................................... 57
Executing Upgrade Load Plan(s) to upgrade data in the Business Analytics Warehouse ................... 62
Post-Upgrade Tasks ................................................................................................................................. 64
<End Statements> .......................................................................................... Error! Bookmark not defined.
Appendix ..................................................................................................................................................... 65
Creating a Connection in ODI to the 11.1.1.7.1 Back-up ODI Repository ............................................... 65
Post-Upgrade SQL Statements ................................................................................................................ 66



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.
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)
6. Run scripts to enable deployment changes in BI Applications 11.1.1.8.1.
7. Upgrade the RPD and Presentation Catalog.
8. Upgrade the ODI Repository metadata (content).
9. 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, at minimum, applied Patch 17546336 ODI Cumulative Patch #1. The ODI Cumulative Patch
for BI Applications 11.1.1.7.1 is available on My Oracle Support > Patches & Updates.

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.

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 1 - BI Applications Infrastructure, Metadata and Schema Upgrades

Downloading BI Applications 11.1.1.8.1 software and files

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. 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.
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.
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.s
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
JAVA_HOME Path of the JDK. Example:
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.
For example:
C:\patches
Directory Path
or
PATCH_HOME/patches

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
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.
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
host:port/ServiceName. For example: host:port/orcl.mycompany.com.
Parameter Description
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
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
3. Upgrade FSM
Run the following command:
BI_Oracle_Home/jdk/bin/java -jar /BI_Oracle_Home/biapps/tools/lib/biappsrepositoryutil.jar
upgradeFSM <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
Parameter Description
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.
biacomp.user <prefix>_BIACOMP schema owner.
biacomp.password <prefix>_BIACOMP schema owner's password.
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.
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 upgradeFSM
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
fsm.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 upgradeFSM
bi.oracle.home=C:\Middleware_Home\Oracle_BI1 work.dir=C\WorkRepoUtil
biacomp.user=DEV_BIACOMP biacomp.password=password db.conn.sid.url=dbhost:1521:orcl
fsm.db.seed.url=dbhost:1521/orcl.mycompany.com db.sys.user=sysuser
db.sys.password=password
4. Upgrade BIACM
Run the following command:
BI_Oracle_Home/jdk/bin/java -jar /BI_Oracle_Home/biapps/tools/lib/biappsrepositoryutil.jar
upgradeBIACM <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 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.
biacomp.user <prefix>_BIACOMP schema owner.
biacomp.password <prefix>_BIACOMP schema owner's password.
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.
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 upgradeBIACM
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
biacm.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 upgradeBIACM
bi.oracle.home=C:\Middleware_Home\Oracle_BI1 work.dir=C\WorkRepoUtil
biacomp.user=DEV_BIACOMP biacomp.password=password db.conn.sid.url=dbhost:1521:orcl
biacm.db.seed.url=dbhost:1521/orcl.mycompany.com db.sys.user=sysuser
db.sys.password=password
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:
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.

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. 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>
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
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

The script checks whether High Availability is configured or not. If an ODI cluster is configured
already then the script starts all the managed servers which were stopped in the previous script
execution.
If High Availability is not configured then the script deploy the required ODI templates,
configures an ODI cluster, redeploys the 'oraclediagent' using with new deployment plan and
starts all the managed servers.

4. Start BI and ODI Managed Servers using Weblogic Administration Console.

Upgrading the RPD and Presentation Catalog

1. To upgrade the RPD using the Upgrade 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:
<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
NOTE: Secure handling of passwords
The bi.admin.password is a required parameter but it should not be included on the
command line. Instead it should be passed to Std.In, followed by a line break, after the
process is started. This is so that the password does not appear when the current processes
are listed.

Optional Parameters:
apply.update Optional parameter. Default is true; set to false if you want to detect
conflicts without doing the actual apply or any orchestration tasks
log.level - default is INFO. Valid values are FINEST, FINE, NFO, WARNING, SEVERE.

2. To upgrade the Presentation Catalog using the Upgrade Metatdata 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
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
NOTE: Secure handling of passwords
The bi.admin.password is a required parameter but it should not be included on the
command line. Instead it should be passed to Std.In, followed by a line break, after the
process is started. This is so that the password does not appear when the current processes
are listed.

Optional Parameters:
apply.update Optional parameter. Default is true; set to false if you want to detect
conflicts without doing the actual apply or any orchestration tasks
log.level - default isINFO. Valid values are FINEST, FINE, NFO, WARNING, SEVERE.
upgrade.mode - Used by webcat update, system to decide whether to FailOnConflict or
Overwrite the content on conflict (default is 'Overwrite').
3. Restart all BI processes using Oracle Process Manager and Notification Server (OPMN).
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.8.1, the code grant changes to a path
oracle.biacm_11.1.1.8.1. This path doesnt 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/-
To:
file:${domain.home}/servers/${weblogic.Name}/tmp/_WL_user/oracle.biacm_11.1.1.7.1/-

Applying Additional Patches

Applying the Dynamic Monitoring Service Patch

BI EE Bundle Patch 131017 requires the application of the Dynamic Monitoring Service patch 16569379
to your BI system.
This patch is available on My Oracle Support > Patches & Updates. Download the patch for your
operating system and apply the Dynamic Monitoring Service patch 16569379 to your BI system
following the instructions in the patch readme file.

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 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.
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 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"

Upgrading the ODI Repository

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.

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.



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.


Exporting Security

1. Navigate to Topology > Export and select the Export Security Settings action.



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.
The BI Apps Customization methodology has you place all custom interfaces in separate Custom
adaptor folders. You will export these folders using the ODI Smart Export option. This option exports
the object itself and any used objects that the exported object depends on. Note any non-custom
objects that may be included in the export as these will need to be merged with the code in the upgrade
repository.
1. Navigate to the Designer tab. From the Connect Navigator (Designer icon dropdown on the top
right side of the navigator pane), select Export.

2. Select Smart Export from the Export selection dialog.


3. Export your custom folders.


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.

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

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.

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.

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.

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

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.1to 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.

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.


5. Repeat for steps 1-4 to renumber the Work repository to the same value as the renumbered
Master repository.



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



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.




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.



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 source connection destails. 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.




6. 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.


7. Open the corresponding logical schema and verify the DATASOURCE_NUM_ID flexfield is also
set with the same value.


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.


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.


After the import is complete, the SUPERVISOR user will no longer be enabled.

Once logged out of ODI Studio, you will have to log in with the administrative user configured in the
prior ODI repository. In order to do so, 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.

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.

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.

Importing Customizations

The ODI Smart Import will be leveraged to import the customizations which were exported from the ODI
Repository for 11.1.1.7.1 as part of step Exporting Customizations above into the ODI Repository for
11.1.1.8.1.
The types of customization that can be imported are as follows:
Changes to an Interface that has been copied into a separate Custom Adaptor folder per the
Customization methodology with the following limitations:
o Interfaces where neither the datastore extracted from or populated have been
customized may be imported.
o Interfaces that extract from or populate customized datastores where the datastore has
NOT changed in the post-upgrade repository may be imported.
o Interfaces that extract from or populate customized datastores where the datastore has
changed in the post-upgrade repository may not be imported as the custom datastore
cannot be imported.

Changes to a Package that that has been copied into a separate Custom Adaptor folder per the
Customization methodology
Changes to the Custom Fact and Dimension Load Plan Components
Changes to a Datastore where the Datastore has NOT changed in the post-upgrade repository
(due to limitations with 3-way merge). Interfaces that extract from and/or populate these
datastores may be imported.

The following types of customizations cannot be imported and must be manually reapplied in the post-
upgrade repository:
Customized datastore where the datastore has changed in the post-upgrade repository. For
example, the original pre-upgrade datastore has 10 columns, an 11
th
column was introduced as
a customization and an 11
th
column was introduced in the post-upgrade datastore.
Interfaces that extract from or populate such a customized datastore cannot be imported.
If you have custom content that was exported as part of step Exporting Customizations above then this
content needs to be imported in the ODI Repository for 11.1.1.8.1.
As per the customization methodology, the Oracle BI Applications model folder is initially versioned to
reflect the pre-customized model and versioned again for the customizations. With these two versions,
it is possible to compare the two to see what changes have been introduced.
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. Right click, select Version -> Create Version. Create an initial version. Perform the steps again to
create the version with customizations.

4. Perform a Smart Import of the file you created previously in step Exporting Customizations
above. Resolve any conflicts. Note that ODIs default behavior is to perform an Overwrite
operation so the custom content being imported will overwrite the upgrade content. Select the
appropriate options to ensure upgrade content is retained.
Validating Connections

After completing the import of connections, security and customizations into the ODI Repository for 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.

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.


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.8.1. Before performing the steps outlined in this section of the document, you must have
completed all steps described in section 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.

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 1 - 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.
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.

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.
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
Upgrade BIApps 111171 to 111180 EBS 120
Upgrade BIApps 111171 to 111180 EBS 1211
Upgrade BIApps 111171 to 111180 EBS 1212
Upgrade BIApps 111171 to 111180 EBS 1213

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 10 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
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
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:
5. Log into ODI Studio using the connection for the BI Applications Administrator user.

6. Navigate to Designer tab > Load Plans and Scenarios.

7. Expand the Predefined Load Plans folder and then the Upgrade folder.

8. 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.

1. Modifying the Upgrade Load Plans above.

2. Right-click and select Duplicate Selection.



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.

8. Execute the copied Load Plan.

Repeat steps 1 through 8 for each Upgrade Load Plan you modified in 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:
9. Log into ODI Studio using the connection for the BI Applications Administrator user.

10. Navigate to Designer tab > Load Plans and Scenarios.

11. Expand the Predefined Load Plans folder and then the Upgrade folder.

12. 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.

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.
1. Log into BI Applications Configuration Manager as the BI Applications Administrator user.

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 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.

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;

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:
1. Log into BI Applications Configuration Manager as the BI Applications Administrator user.

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:
Skip to section Noting Variable Value (Required if your source is PeopleSoft versions 9.0, 9.1 or
9.2) below if 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



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



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

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.
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
Variable
B
SQL Query (against <prefix>_BIACOMP
and for the DATASOURCE_NUM_ID for
the source)
C
Value (returned from query run
in your environment
TREE_CURRENT_VERSION_ONLY select * from
C_PARAMETER_VALUE_FORMATTER_V
where param_code = '
TREE_CURRENT_VERSION_ONLY ' and
group_code = 'INTORG_DIM';
(Value is Y or N, without quotes)
TREE_SETID_NAME_LIST_DEPT select * from
C_PARAMETER_VALUE_FORMATTER_V
where param_code = '
TREE_SETID_NAME_LIST_DEPT' and
group_code = 'INTORG_DIM';
(Value should of the format
'A~A1','B~B1' )
TREE_STRUCT_ID_LIST_DEPT select * from
C_PARAMETER_VALUE_FORMATTER_V
where param_code = '
TREE_STRUCT_ID_LIST_DEPT ' and
group_code = 'INTORG_DIM';
(Value should be of the format
'A','B' format)
TREE_SETID_NAME_LIST_COMPANY select * from
C_PARAMETER_VALUE_FORMATTER_V
where param_code = '
TREE_SETID_NAME_LIST_COMPANY'
and group_code = 'INTORG_DIM';
(Value should be like
'A~A1','B~B1' format)
TREE_STRUCT_ID_LIST_COMPANY select * from
C_PARAMETER_VALUE_FORMATTER_V
where param_code = '
TREE_STRUCT_ID_LIST_COMPANY and
group_code = 'INTORG_DIM';
(Value should be like 'A','B'
format)

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:
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, 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.

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
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.
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

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:
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 (
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,
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,
GLOBAL1_EXCHANGE_RATE,
GLOBAL2_EXCHANGE_RATE,
GLOBAL3_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,
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,
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,
GLOBAL1_EXCHANGE_RATE,
GLOBAL2_EXCHANGE_RATE,
GLOBAL3_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
from W0WRKFC_SNP_F;
commit;
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;