Upgrade 11.1.1.5 to 11.1.1.6 Linux X86 64

Question

Hi,
Just upgraded from 11.1.1.5 to 11.1.1.6. Here you have my detailed upgrade procedure based on links below. Hope it will help some of you.
Guides:
http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads
http://docs.oracle.com/cd/E23943_01/bi.1111/e16452/bi_plan.htm#BABECJJH
http://docs.oracle.com/cd/E16764_01/doc.1111/e14495/install_screens.htm
http://gerardnico.com/wiki/dat/obiee/patch_11g_111160 (it's about windows installation but still helpful)
1) Check prerequisites
Check your web logic version (need to be 10.3.5 or 10.3.6) -> In the WebLogic console, in the left navigation tree, click on "Environment", then "Servers". Then click on one of the servers in the list. Then click on the "Monitoring" tab. Look at the "WebLogic Version" field.
If you like, check detailed requirements:
http://docs.oracle.com/cd/E23943_01/doc.1111/e16793/patch_set_installer.htm#BGBBHDJA
http://docs.oracle.com/html/E18558_01/fusion_requirements.htm
2) Stop services
Stop OBIEE services OMPN: /mnt/data/obi11g/instances/instance1/bin/opmnctl stopall
Stop Weblogic: /mnt/data/obi11g/user_projects/domains/bifoundation_domain/bin/stopWebLogic.sh
Confirm that weblogic is not running: ps aux | grep java
3) use putty with XMING (if you run inslallation remotely)
download from: http://sourceforge.net/projects/xming/
guide: http://qiu.bioweb.hunter.cuny.edu/index.php?option=com_content&view=article&id=110
Maybe you will need to install "/usr/bin/xdpyinfo" to make it work
4) start installer
Run installer with oracle account (Anyway installer script won't let you run it from root account).
/mnt/data/OBI_11116_installer_unp/bishiphome/Disk1/runInstaller
-> Skip software updates
-> Next
-> Software Install only
-> Next
5) make all prerequisites passed / sometimes warnings are accepted
In our case:
A) to pass "check operating system certification" needed to change "/etc/oracle-release" from “Oracle 6.1” to just “6” (so it match one of allowed versions)
B) to pass "checking recommended operating system packages" -> needed to install several packages (it's more convinient to use prerequisite log than read packages names from installer window, in our case log was located in: /tmp/OraInstall2012-03-06_02-43-06PM/prereq/linux64/ias_prereq_results.xml)
C) Even after installing all packages prerequisites check didn't pass for 2 of them, so finally "checking recommended operating system packages" got warning, however we were sure that packages are in place in system
6) Provide Oracle Middleware home and Oracle Home Directory
How to find it out: http://docs.oracle.com/cd/E11857_01/install.111/e16847/preparing_for_install.htm#BACIGBGF
In our case:
Middleware Home: /mnt/data/obi11g
BI Oracle Home: Oracle_BI1
7) Finish instalation
After installation is finishes close installer.
In our case with no issues and it took about 15 minutes.
8) Check schemas
see http://docs.oracle.com/cd/E23943_01/doc.1111/e16793/patch_set_assistant.htm#BABHFEGH
In our case database is located on separate server, so needed to connect to it from my local windows machine with PL-SQL developer as "sys" user and verify if 2 expected schemas are in place with version 11.1.1.5
SELECT t.* FROM SCHEMA_VERSION_REGISTRY t;
9) Update Schemas with Patch Set Assistant
Connect to server with putty with Xming (as when starting installation)
Run patch set assistant separately for each of 2 schemas: /mnt/data/obi11g/Oracle_BI1/bin/psa
xxx_MDS (The prefix_MDS schema must be updated first, in fact installer won't let you do it in wrong order)
xxx_BIPLATFORM
Both times tyou need to check prerequisites check boxes: "Database backup completed" and "Database version is certified...".
You need to provide connection string. As mentioned in my case it was different IP than OBI server itself.
As given in installer example DBA User name: "sys as sysdba"
Then provide your schema user and password (e.g. schema password for sample oracle installation is "Admin123")
10) validate patch set installation
again connect as "sys" user and run query: SELECT t.* FROM SCHEMA_VERSION_REGISTRY t;
for both xxx_BIPLATFORM and xxx_MDS you get "11.1.1.6" ... "VALID"
11) Upgrading System Components
http://docs.oracle.com/cd/E23943_01/doc.1111/e16793/patch_set_installer.htm#PATCH250
http://docs.oracle.com/cd/E23943_01/doc.1111/e16793/patch_set_installer.htm#CBHJHJCF
A) start administration service:
nohup /mnt/data/obi11g/user_projects/domains/bifoundation_domain/bin/startWebLogic.sh
B) check if there are no issues in : /home/obi/nohup.out
C) set oracle home / confirm that it is set
export ORACLE_HOME=/mnt/data/obi11g/Oracle_BI1
env | grep ORACLE_HOME
D) start obiee services
/mnt/data/obi11g/instances/instance1/bin/opmnctl startall
E) verify that obiee services are alive
/mnt/data/obi11g/instances/instance1/bin/opmnctl status -l
F) run upgrade
http://docs.oracle.com/cd/E23943_01/doc.1111/e16793/patch_set_installer.htm#PATCH250
http://docs.oracle.com/cd/E23943_01/doc.1111/e16793/patch_set_installer.htm#CBHJHJCF
/mnt/data/obi11g/Oracle_BI1/opmn/bin/upgradenonj2eeapp.sh
-oracleInstance /mnt/data/obi11g/instances/instance1 -adminHost localhost -adminPort 7001 -adminUsername xxx
in default oracle installation xxx = "weblogic", you will need to provide password few times during install.
12) Updating Fusion Middleware Shared Libraries
http://docs.oracle.com/cd/E23943_01/doc.1111/e16793/patch_set_installer.htm#PATCH685
A) Stop all running instances, Managed Servers, Administration Server, and Node Manager in the domain.
/mnt/data/obi11g/instances/instance1/bin/opmnctl stopall
/mnt/data/obi11g/user_projects/domains/bifoundation_domain/bin/stopWebLogic.sh
B) confirm that weblogic is not running
ps aux | grep java
C) run WLST
/mnt/data/obi11g/oracle_common/common/bin/wlst.sh
wlst> upgradeJRF("/mnt/data/obi11g/user_projects/domains/bifoundation_domain")
In our case we got "skip, JRF is up-to-date"
13) Updating Configurations and Stores
http://docs.oracle.com/cd/E23943_01/doc.1111/e16793/patch_set_installer.htm#PATCH721
A) Start weblogic and opmnctl
B) run WLST
/mnt/data/obi11g/oracle_common/common/bin/wlst.sh
wlst> upgradeOpss(jpsConfig=”/mnt/data/obi11g/user_projects/domains/bifoundation_domain/config/fmwconfig/jps-config.xml”, jaznData="/mnt/data/obi11g/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml")
14) "Updating Oracle Business Intelligence Code Grants" & "Updating Oracle Business Intelligence Catalogs"
Boths this steps can be skipped for 11.1.1.5 to 11.1.1.6 upgrade, as I understood from Oracle upgrade guide.
15) Reinstall windows client "biee_client_install.exe"
A) uninstall previous version (in my case 11.1.1.4)
B) download and install "Oracle Business Intelligence Developer Client Tools Installer (11.1.1.6.0)"
First glance issues after installation (to be investigated next days...):
- does not work at all with my chrome browser
- issue with existing dashboard prompts (list of available values is not displayed combo box, however can use "search" to pick it from list)
- some of existing navigation links stopped to work
Regards,

Answer 1

Hi,
rafaelfm wrote:
If I got it right, you suggest using the Method proposed on the first message, without Data Guard.
I too would prefer not to touch production database until I test all the procedure. I would just run the pre-upgrade in production and use production backups during the tests phase.The guys here gave great suggestions but I'd do in a different way.
1) Execute pre-upgrades scripts and checks
2) Backup current database with RMAN and make backup files available to the new host
3) Install Grid Infrastcure 11.2.0.2 on new cluster
4) Configure ASM on new Cluster
5) Install Oracle Database RAC 11.2.0.2 on new cluster
6) Create the RAC Database (using DBCA) with the same DBNAME of the original database. (this save a lot work)
7) Create the Database Services (if exists)
8) Shutdown Database / Remove Database (only files controlfile/datafiles/redo) - Easy way is drop directory on ASM. Leave configuration of Network/OCR in place.
9) Create a new PFILE from production SPFILE. Change parameter of SPFILE of new RAC using PFILE.
10) RESTORE CONTROLFILE AND DATABASE
11) RECOVER DATABASE and execute 'ALTER DATABASE OPEN RESETLOG' the error ORA-39700 will be raised and database will shutdown leave database down.
12) Using DBUA perfom UPGRADE to 11.2.0.2.
13) remove extra undo tablespaces e redo log threads
You also suggest to use DBUA. Is it possible to use DBUA when you are restoring the database to the other cluster where the new version is installed?Yes.. You must perform recover and open resetlogs database, the error (ORA-39700: database must be opened with UPGRADE option) will be raised and database will shutdown, leave database down and perform upgrade using DBUA.
Regards,
Levi Pereira
Edited by: Levi Pereira on May 20, 2011 11:59 PM