Quick Reference For BIEE12c Upgrade From 12.2.1 to 12

APPLIES TO: 

Business Intelligence Suite Enterprise Edition - Version 12.2.1.0.0 and later
Information in this document applies to any platform.

PURPOSE

This document is intended to supplement (with screen shots), act as a bridge and be used as a quick searchable reference to the Oracle® Fusion Middleware Upgrading Oracle Business Intelligence documentation. It does not supersede the documentation.

This document is a reference to quickly upgrade a test, development or demonstration environment. See the Enterprise Deployment Guide for Oracle Business Intelligence for a reference production architecture.

This document was written and tested by upgrading OBIEE 12.2.1.0 to 12.2.1.1. At that time, OBIEE 12.2.1.2 had not been released yet but the same steps apply for the upgrade from 12.1.1.0 to 12.2.1.2.

Once your upgrade is complete, you may want to review OBIEE 12c: Quick Reference For Architecture, Lifecycle Managment and File Locations (Doc ID 2067527.1)

SCOPE

This document can be useful for anyone preparing an upgrade of Oracle Business Intelligence Enterprise Edition 12c including administrators, consultants, sales, partners, deployment engineers, architects, support.

DETAILS

You must read and understand the important information in Preparing to Upgrade Oracle Business Intelligence before you begin the upgrade process. It identifies important tasks and checks to be performed to ensure that your environment is properly prepared for upgrading the Oracle Business Intelligence:

• Oracle Fusion Middleware Pre-Upgrade Checklist
• Creating a Complete Backup
• Cloning Your Production Environment for Testing
• Verifying Certification and System Requirements
• Updating Policy Files when Using Enhanced Encryption (AES 256)
• Purging Unused Data
• Creating a Non-SYSDBA User to Run Upgrade Assistant
• Disabling Internal SSL
• Creating a Baseline Report with the Oracle BI Baseline Validation Tool

 

Example Linux upgrade (assumes OBIEE 12c is previously installed and configured)

• Copy installation files or create a mount point for your installation files.
  
  
• Ensure you have method for graphical user interface (e.g. VNC or local xterm)
  
  
• JDK: configure JDK in your PATH and JAVA_HOME
  
  For example:
  
  
  export JAVA_HOME=/[path to your jdk]/jdk8
  export PATH=/[path to your jdk]/jdk8/bin:$PATH
  which java
  /../jdk8/bin/java
  java -version
  java version "1.8.0_92"
  Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
  Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)
   

 

The best practice going forwards is to have different Oracle homes for the different versions and the domain directory separated from the Oracle home as shown below:

 

Note: The example in this document shows the Oracle home and the domain home together as the purpose is to demonstrate the upgrade process in a test environment.

 

Disabling Internal SSL

 

You must disable SSL on the internal communication links before you start the upgrade process.

../Oracle_Home/user_projects/domains/bi/bitools/bin/stop.sh

../Oracle_Home/user_projects/domains/bi/bitools/bin/ssl.sh internalssl false

Logging to: ../Oracle_Home/user_projects/domains/bi/bilogs/sslcommand.log

Reading domain
Setting protocol to http for server bi_server1
Internal BIEE communications have been configured to not use SSL.
Sensitive information will be transmitted in the clear.

Startup all BIEE servers to consume the new configuraton. For example run the start[.sh] command line tool in the same directory as this ssl tool.

./start.sh

 

 

Installing Fusion Middleware Infrastructure Release 12.2.1.1

 

[path to jdk8/bin]/java -jar fmw_12.2.1.1.0_infrastructure.jar

 

 

 

 

 

 

 

 

 

 

After installing Fusion Middleware Infrastructure Release 12.2.1.1 the following directories are created under ../Oracle_Home_12.2.1.1:

drwxr-x--- 4 oracle oracle 4096 Jun 23 17:15 cfgtoollogs
drwxr-x--- 5 oracle oracle 4096 Jun 23 17:13 coherence
drwxr-x--- 8 oracle oracle 4096 Jun 23 17:14 em
drwxr-x--- 2 oracle oracle 4096 Jun 23 17:15 install
drwxr-x--- 19 oracle oracle 4096 Jun 23 17:16 inventory
drwxr-x--- 12 oracle oracle 4096 Jun 23 17:14 OPatch
drwxr-x--- 23 oracle oracle 4096 Jun 23 17:14 oracle_common
-rw-r----- 1 oracle oracle 130 Jun 23 17:15 oraInst.loc
drwxr-x--- 8 oracle oracle 4096 Jun 23 17:15 oui
drwxr-x--- 7 oracle oracle 4096 Jun 23 17:13 wlserver

 

Installing Oracle Business Intelligence Release 12.2.1.1

 

cd /[path to your software download]
unzip fmw_12.2.1.1.0_bi_linux64_Disk1_1of2.zip
unzip fmw_12.2.1.1.0_bi_linux64_Disk1_2of2.zip
./bi_platform-12.2.1.1.0_linux64.bin

 

 

 

 

 

 

 

 

 

 

Running the Readiness Check

 

The instance must be running to run the Readiness Check as the Upgrade Assistant connects to the domain:

../Oracle_Home_12.2.1.1/oracle_common/upgrade/bin/ua -readiness

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Examine the readiness report and take action as needed. The report is available under:

../Oracle_Home_12.2.1.1/oracle_common/upgrade/logs

Here is a sample Readiness Report file

 

Upgrading Schemas with the Upgrade Assistant

 

Stop the instance and run the Upgrade Assistance:

../Oracle_Home/user_projects/domains/bi/bitools/bin /stop.sh | .cmd

../Oracle_Home_12.2.1.1/oracle_common/upgrade/bin /ua

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Backing up the mapViewerConfig.xml File

 

The mapViewerConfig.xml file is overwritten by the reconfiguration templates when you run the Reconfiguration Wizard. Therefore, you must back up the mapViewerConfig.xml file before reconfiguring your 12.2.1.0 domain.

cd ../Oracle_Home/user_projects/domains/bi/config/fmwconfig/mapviewer/conf
cp mapViewerConfig.xml mapViewerConfig.xml.orig

 

 

Reconfiguring the BI Domain with the Reconfiguration Wizard

 

../Oracle_Home_12.2.1.1/oracle_common/common/bin /reconfig.sh

 

 

 

 

 

 

 

 

 

 

 

 

Restoring the mapViewerConfig.xml File

 

cd ../Oracle_Home/user_projects/domains/bi/config/fmwconfig/mapviewer/conf
cp mapViewerConfig.xml.orig mapViewerConfig.xml

 

 

Upgrading the Configuration with the Upgrade Assistant

 

 

 

 

 

 

 

 

 

 

Enabling Internal SSL

 

After the upgrade is complete, enable internal SSL communication and start the instance:

../Oracle_Home/user_projects/domains/bi/bitools/bin/ssl.sh internalssl true
Logging to: ../Oracle_Home/user_projects/domains/bi/bilogs/sslcommand.log

Reading domain
Setting protocol to https for server bi_server1
Rebinding channel certificates for server bi_server1
Checking certificate exists for endpoint: BI-SECURITY-SOAP.bi_server1 http://demobi.us.oracle.com:9505/bi-security/service - custom channel bi_internal_channel1
No new certificates required.
Internal BIEE communications have been configured to use SSL with certificates
matching the current listening addresses. Rerun if you change the addresses.
To achieve end to end security you also need to review the SSL configuration
of other components, including the external ports of WebLogic servers.

All certificates have more than 30 days to expiry.

Startup all BIEE servers to consume the new configuration. For example run the start[.sh] command line tool in the same directory as this ssl tool.

./start.sh

 

 

Testing the Upgrade

 

Log in to Analytics and check the new OBIEE version:

 

After upgrading OBIEE the following directories are under ../Oracle_Home_12.2.1.1 new Oracle Home:

../Oracle_Home_12.2.1.1
-bash-4.2$ ls -l
total 132
drwxr-x--- 19 oracle oracle 4096 Jun 23 19:11 bi
drwxr-x--- 2 oracle oracle 4096 Jun 23 19:12 bin
drwxr-x--- 4 oracle oracle 4096 Jun 23 17:15 cfgtoollogs
drwxr-x--- 5 oracle oracle 4096 Jun 23 17:13 coherence
drwxr-x--- 4 oracle oracle 4096 Jun 23 19:10 crs
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:10 css
-rw-r----- 1 oracle oracle 217 Jun 23 21:42 domain-registry.xml
drwxr-x--- 8 oracle oracle 4096 Jun 23 17:14 em
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:10 has
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:12 install
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:12 instantclient
drwxr-x--- 19 oracle oracle 4096 Jun 23 19:12 inventory
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:10 jdbc
drwxr-x--- 2 oracle oracle 4096 Jun 23 19:10 jlib
drwxr-x--- 5 oracle oracle 4096 Jun 23 19:10 ldap
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:12 lib
drwxr-x--- 8 oracle oracle 4096 Jun 23 19:12 network
drwxr-x--- 5 oracle oracle 4096 Jun 23 19:10 nls
drwxr-x--- 12 oracle oracle 4096 Jun 23 17:14 OPatch
drwxr-x--- 25 oracle oracle 4096 Jun 23 19:10 oracle_common
drwxr-x--- 4 oracle oracle 4096 Jun 23 19:10 oracore
-rw-r----- 1 oracle oracle 130 Jun 23 17:15 oraInst.loc
drwxr-x--- 8 oracle oracle 4096 Jun 23 17:15 oui
drwxr-x--- 5 oracle oracle 4096 Jun 23 19:10 plsql
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:12 plugins
drwxr-x--- 5 oracle oracle 4096 Jun 23 19:10 precomp
drwxr-x--- 8 oracle oracle 4096 Jun 23 19:10 rdbms
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:10 slax
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:10 sqlplus
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:10 srvm
drwxr-x--- 3 oracle oracle 4096 Jun 23 19:28 user_projects
drwxr-x--- 7 oracle oracle 4096 Jun 23 17:13 wlserver
drwxr-x--- 4 oracle oracle 4096 Jun 23 19:10 xdk

There is an empty directory created by the installer under the user_projects directory of the new Oracle Home but it can be ignored:

../Oracle_Home_12.2.1.1/user_projects/domains

 

as the "bi" domain is still under the upgraded directory:

-bash-4.2$ ls -l
../Oracle_Home/user_projects/domains

-bash-4.2$ ls -l
total 4
drwxr-x--- 29 oracle oracle 4096 Jun 23 22:21 bi
-bash-4.2$ cd bi
-bash-4.2$ ls -l
total 260
drwxr-x--- 2 oracle oracle 4096 Mar 15 14:49 autodeploy
drwxr-x--- 5 oracle oracle 4096 Mar 15 15:05 bidata
drwxr-x--- 4 oracle oracle 4096 Jun 23 15:25 bilogs
drwxr-x--- 6 oracle oracle 4096 Jun 23 21:41 bin
drwxr-x--- 2 oracle oracle 4096 Jun 23 21:42 BipJmsStore
drwxr-x--- 2 oracle oracle 4096 Jun 23 22:25 BipJmsStore_auto_1
drwxr-x--- 3 oracle oracle 4096 Mar 15 15:05 bisysman
drwxr-x--- 3 oracle oracle 4096 Mar 15 14:53 bitools
drwxr-x--- 2 oracle oracle 4096 Jun 23 22:15 biupgrade
-rw-r----- 1 oracle oracle 1 Mar 15 14:57 blankLine.txt
drwxr-x--- 3 oracle oracle 4096 Mar 15 15:14 common
drwxr-x--- 13 oracle oracle 4096 Jun 23 22:21 config
drwxr-x--- 2 oracle oracle 4096 Mar 15 14:49 console-ext
-rw-r----- 1 oracle oracle 21523 Jun 23 22:30 createDDL.jdbc
-rw-r----- 1 oracle oracle 87061 Jun 23 20:59 debugMagicThreadDumpFile
-rw-r----- 1 oracle oracle 226 Jun 23 22:23 derby.log
-rw-r----- 1 oracle oracle 122 Jun 23 20:59 derbyShutdown.log
-rw-r----- 1 oracle oracle 4038 Jun 23 22:30 dropDDL.jdbc
drwxr-x--- 2 oracle oracle 4096 Jun 23 22:25 DssJmsStore_auto_1
-rw-r----- 1 oracle oracle 139 Jun 23 22:21 edit.lok
-rw-r----- 1 oracle oracle 328 Mar 15 14:49 fileRealm.properties
drwxr-x--- 2 oracle oracle 4096 Mar 15 15:17 generated_classes
drwxr-x--- 3 oracle oracle 4096 Jun 23 21:43 init-info
drwxr-x--- 2 oracle oracle 4096 Jun 23 22:25 JRFWSAsyncFileStore_auto_1
drwxr-x--- 2 oracle oracle 4096 Mar 15 14:49 lib
drwxr-x--- 5 oracle oracle 4096 Jun 23 22:31 nodemanager
drwxr-x--- 3 oracle oracle 4096 Jun 23 22:21 orchestration
drwxr-x--- 3 oracle oracle 4096 Mar 15 15:23 precompiled
-rw-r----- 1 oracle oracle 27 Mar 15 14:55 readme.txt
drwxr-x--- 2 oracle oracle 4096 Sep 24 2015 resources
drwxr-x--- 2 oracle oracle 4096 Jun 23 21:42 security
drwxr-x--T 9 oracle oracle 4096 Mar 15 15:18 servers
-rw-r----- 1 oracle oracle 821 Jun 23 21:42 startManagedWebLogic_readme.txt
-rwxr-x--- 1 oracle oracle 277 Jun 23 21:42 startWebLogic.sh
drwxr-x--- 3 oracle oracle 4096 Mar 15 14:53 store
drwxr-x--- 8 oracle oracle 4096 Jun 23 21:42 sysman
drwxr-x--- 7 oracle oracle 4096 Mar 15 15:16 system_components
drwxr-x--- 5 oracle oracle 4096 Jun 23 22:31 tmp

 

Start and stop scripts to use are also under the upgraded domain directory:

../Oracle_Home/user_projects/domains/bi/bitools/bin/start.sh
../Oracle_Home/user_projects/domains/bi/bitools/bin/stop.sh

 

  

Keep in mind that this directory structure is only for demonstration purposes of the upgrade process and best practice going forward is to have different Oracle homes for the different versions and the domain directory separated from the Oracle home.

  

REFERENCES

NOTE:2067527.1  - OBIEE 12c: Quick Reference For Architecture, Lifecycle Management and File Locations
NOTE:2064302.1  - OBIEE 12c: Quick Reference For Oracle Business Intelligence Enterprise 12c (12.2.1) Installation
NOTE:2162794.1  - OBIEE 12c: Error During Upgrade to 12.2.1.1 After Starting Reconfig Step - CFGFWK-64254 java.lang.Exception: java.lang.OutOfMemoryError: GC overhead limit exceeded