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
_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 _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 .......................................................................................... 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
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 _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 .......................................................................................... 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 On Linux or UNIX: ./runInstaller -jreLoc 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 /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 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 /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 /perl/bin: /perl/bin/ perl /biapps/tools/bin/ APPLY_PATCHES.pl /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__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= bi.domain.home= log.file=/bi_jazn_patch.log work.dir= 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 _BIACOMP schema contains tables for ATG, FSM and BIACM (Configuration Manager). The _BIACOMP schema is upgraded by updating these component schemas to version 11.1.1.8.1 individually. The _BIACM_IO schema must also be upgraded to version 11.1.1.8.1. Details to upgrade the _BIACOMP and _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 _BIACOMP and _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 /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
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
_BIACOMP schema owner.
biacomp.password _BIACOMP schema owner's password. atg.db.seed.url
URL used to connect to the _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
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 _BIACOMP schema. The format is host:port:SID. For example: host.domain:1521:orcl.
biacomp.user
_BIACOMP schema owner.
biacomp.password _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
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 _BIACOMP schema. The format is host:port:SID. For example: host.domain:1521:orcl.
biacomp.user
_BIACOMP schema owner.
biacomp.password _BIACOMP schema owner's password. biacm.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 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 /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 _BIACOMP schema using SQL Plus. Example: sqlplus DEV_BIACOMP/password
2. Run the upgrade_grant_sysnonym_io.sql file with the input of _BIACM_IO user name. The value is the same as the prefix for your BIACOMP schema. Example: SQL> @/upgrade_grant_sysnonym_io.sql DEV_BIACM_IO Where the path to the script is /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 _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 _BIACOMP Example: SQL> @ upgrade_synonym_io.sql DEV_BIACOMP Where the path to the script is /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 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 = '_BIACM_IO'; NOTE: The value of for the _BIACM_IO schema is the same prefix as that for the _BIACOMP schema.
Granting Privileges to _BIACM_IO schema
Using SQL Plus or an equivalent tool, log in as _BIACOMP and execute the following command: grant select, references on C_PARAMETER_VALUE_FORMATTER_V to _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 /dwtools/script directory, using the Weblogic Scripting Tool (wlst) from the /common/bin location as follows: ./wlst.sh /dwtools/scripts/ PS1_REL8_Upgrade_EnableATGAndFSMChanges.py -DOMAIN_HOST --DOMAIN_PORT --DOMAIN_HOME_PATH
--DOMAIN_USERNAME 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 /dwtools/script directory, using the Weblogic Scripting Tool (wlst) from the /common/bin location as follows:
./wlst.sh /dwtools/scripts/ PS1_REL8_Upgrade_EnableODIDeployChanges.py --DOMAIN_HOST --DOMAIN_PORT --DOMAIN_HOME_PATH
--DOMAIN_USERNAME --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:
/jdk/jre/bin/ java -cp /biapps/patch/biappspatch.jar oracle.as.biapps.patch.update.UpdateBIAppsMetadata bi.oracle.home= bi.admin.url= bi.admin.username= bi.admin.password= only.apply=rpd log.file=
dir>/rpd.log log.level=INFO work.dir= 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:
/jdk/jre/bin/ java -cp /biapps/patch/biappspatch.jar oracle.as.biapps.patch.update.UpdateBIAppsMetadata bi.oracle.home= bi.admin.url= bi.admin.username= bi.admin.password= only.apply=webcat log.file=/webcat.log log.level=INFO work.dir= 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 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/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 customizations in your yo ur 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 folders using the ODI Smart Export 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.
