Monday

11.1.1.1 -> 11.1.1.3 Fusion Middleware Upgrade

I've been meaning to post this awhile.. How long, well I believe 11.1.1.5 is out now.   I took a quick look at the upgrade documentation tho and the overall process doesn't seem to have changed much.  (I did see some extra post-upgrade steps depending on which version you start from..)

The biggest hurdle seems to be upgrading from 11.1.1.1 to 11.1.1.2...   I spent a fair bit of time trying to understand the documentation and perform the upgrade.   The process as described in the documentation didn't seem to make any sense to me.   After talking to Oracle support they found it difficult to follow as well and said they would file a request to get it reviewed.    We decided at that time to do a fresh install of 11.1.1.2 and upgrade it to 11.1.1.3.

I haven't checked back on the documentation to see if the sections were clarified.  If you followed or have seen my 11.1.1.1 installation guide you have an idea of my setup.    If you haven't, a quick review:

- Two Tier Environment
- VM18 has the IDM stack and Database installed.
- VM17 has Portal, SOA and SSO installed.

As I said above, instead of upgrading from 11.1.1.1 to 11.1.1.2 and patching to 11.1.1.3 we did a fresh install of 11.1.1.2.   The installation process for 11.1.1.2 is almost identical to 11.1.1.1 so I used the install guide I had already created as a base for the install.    From there I followed the steps below to patch up to 11.1.1.3

Note: The steps below only cover upgrading the products to 11.1.1.3.   Since we performed a fresh install it doesn't cover topics such as migrating data (example, OID accounts), domains hosting 3rd party software, portal data (transport sets), configuration (load balancers, reverse proxies, ..), etc.

Patch Weblogic from 10.2.2 to 10.2.3

  1. Download the Upgrade Installer from Oracle Support.
    1. see "Downloading an Upgrade Installer From My Oracle Support"
  1. Launch the install:
    1. [oracle@vm18 STAGE]$ $JAVA_HOME/bin/java -jar wls1033_upgrade_generic.jar
clip_image002[4]
clip_image004[4]
clip_image006[4]
clip_image008[4]
clip_image010[4]
clip_image012[4]
clip_image014[4]

Upgrading IDM


clip_image016[4]
clip_image018[4]
clip_image020[4]
clip_image022[4]
clip_image024[4]
clip_image026[4]
clip_image028[4]

Portal Patchset Install


clip_image030[4]
clip_image032[4]
clip_image034[4]
clip_image036[4]
clip_image038[4]

  • Prompted to run oracleRoot.sh

clip_image040[4]

SOA Patchset Install


clip_image042[4]
clip_image044[4]
clip_image046[4]
clip_image048[4]
clip_image050[4]

Updating Schemas with Patch Set Assistant


  • Startup the database, ensure aq_tm_processes parameter is > 0
  • In each home for Portal, SOA and IDM there is a Patch Set Assistant utility which was installed as part of the 11.1.1.3 patchset.

IDM psa

[oracle@vm18 bin]$ ./psa -dbConnectString //vm18:1521/FMW.world -dbaUserName sys -schemaUserName ODS
Oracle Fusion Middleware Patch Set Assistant 11.1.1.3.0
Enter the database administrator password for "sys":
Enter the schema password for schema user "ODS":
Log file is located at: /u01/app/oracle/product/mid11g3/Oracle_IDM1/upgrade/logs/psa2010-08-13-15-00-47PM.log
Updating the Oracle Fusion Middleware Metadata Schema to release 11.1.1.3.0.
Updating schema for component Oracle Internet Directory.
The command completed successfully


Start IDM
[oracle@vm18 bin]$ ./opmnctl startall
opmnctl startall: starting opmn and all managed processes...
[oracle@vm18 bin]$ pwd
/u01/app/oracle/product/mid11g3/IDMasinst_1/bin

Portal PSA


[oracle@vm17 bin]$ ./psa -dbConnectString //vm18:1521/FMW.world -dbaUserName sys -schemaUserName UPG_PORTAL
Oracle Fusion Middleware Patch Set Assistant 11.1.1.3.0
Enter the database administrator password for "sys":
Enter the schema password for schema user "UPG_PORTAL":
Log file is located at: /u01/app/oracle/product/mid11g3/PORTALas_1/upgrade/logs/psa2010-08-13-15-06-02PM.log
Updating the Oracle Fusion Middleware Metadata Schema to release 11.1.1.3.0.
Updating schema for component Oracle Portal.
The command completed successfully

SOA PSA


[oracle@vm17 bin]$ ./psa -dbConnectString //vm18:1521/FMW.world -dbaUserName sys -schemaUserName UPG_SOAINFRA
Oracle Fusion Middleware Patch Set Assistant 11.1.1.3.0
Enter the database administrator password for "sys":
Enter the schema password for schema user "UPG_SOAINFRA":
Log file is located at: /u01/app/oracle/product/mid11g3/SOAHome_1/upgrade/logs/psa2010-08-13-15-29-49PM.log
Updating the Oracle Fusion Middleware Metadata Schema to release 11.1.1.3.0.
Updating schema for component Oracle SOA.
---Redirecting sql log to /u01/app/oracle/product/mid11g3/SOAHome_1/upgrade/logs/psa2010-08-13-15-29-49PM.out
Executed SOAINFRA upgrade script.
The command completed successfully

Verify the PSA


SQL> select owner, version, status from schema_version_registry;
OWNER VERSION STATUS
------------------------------ ------------------------------ -----------
ODS 11.1.1.3.0 VALID
UPG_PORTAL 11.1.1.3.0 VALID
UPG_SOAINFRA 11.1.1.3.0 VALID

Check for Invalid objects and recompile:


SQL> select count(*) from dba_objects where status = 'INVALID';
COUNT(*)
----------
12
SQL> @?/rdbms/admin/utlrp

Post-patching tasks for the System Components:


(You may have to perform the steps below for the other products as well (IDM, SOA), not just for IDM.   I made note of it a while back but since we did the upgrade almost a year ago, I have misplaced it.)

/u01/app/oracle/product/mid11g3/PORTALasinst_1/bin
[oracle@vm17 bin]$ ./opmnctl unregisterinstance
Command requires login to weblogic admin server (vm17.rcpsc.edu):
Username: weblogic
Password:
Unregistering instance
Command succeeded.

[oracle@vm17 bin]$ ./opmnctl redeploy
Command requires login to weblogic admin server (vm17.rcpsc.edu):
Username: weblogic
Password:
Redeploying NonJ2EEManagement Application...weblogic.Deployer invoked with options: -adminurl vm17.rcpsc.edu:7001 -username weblogic -name NonJ2EEManagement -source /u01/app/oracle/product/mid11g3/PORTALas_1/opmn/applications/NonJ2EEManagement.ear -redeploy -upload -noexit
<Aug 13, 2010 4:20:54 PM EDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, NonJ2EEManagement [archive: /u01/app/oracle/product/mid11g3/PORTALas_1/opmn/applications/NonJ2EEManagement.ear], to configured targets.>
Task 0 initiated: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Task 0 completed: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Target state: redeploy completed on Server AdminServer
Done
Command succeeded.

[oracle@vm17 bin]$ ./opmnctl registerinstance;
Command requires login to weblogic admin server (vm17.rcpsc.edu):
Username: weblogic
Password:
Registering instance
Command succeeded.


Update Version Number String shown in OEM


/u01/app/oracle/product/mid11g3/IDMasinst_1/bin
[oracle@vm18 bin]$ ./opmnctl updatecomponentregistration -componentName oid1 -Sport 3131 -Port 3060
Command requires login to weblogic admin server (192.168.80.148):
Username: weblogic
Password:

6 comments:

suma said...

Hi,

I found this site when i was googling.This site seems to be very informative regarding the installation of IDE.This site had cleared some of my issues.Thanks a lot.

Oracle R12 Upgrade.

Barry Ghotra said...

I couldn't agree with you anymore. I've been trying to upgrade our OID/OVD to 11.1.1.5 and yes indeed the biggest hurdle is to understand the documentation that Oracle put out there with so much discrepancies between various versions.

The key question I have for you is that if you did a fresh install of 11.1.1.2, how did you manage to get all your setup/configuration/LDAP and scheama over from 11.1.1.0 to 11.1.1.3?

I would very much appreciate some feedback on it. I am trying to get to 11.1.1.2 as the starting point by using the install-do not configure and then use the Patch assistant.. but have so many questions....

Barry Ghotra said...

Thank You.

Dave said...

So for the domains, portal, SOA, etc we re-setup everything from scratch. I don't manage it all so I can't speak every product but in general it wasn't too bad.

For LDAP we used ldiff to bring the data over and turned on our sync processes.

Barry Ghotra said...

Thank you for the update. I was able to get through that after almost pulling all my hair (leftovers) out. I am at the stage of going from 11.1.1.2 to 11.1.1.5 and all seems to have gone fine, but one thing I don't understand and can't find any reference is to what is happening to the ODSSM schema? How does that get ugraded?

Sridevi Koduru said...

Regards
Sridevi Koduru (Senior Oracle Apps Trainer Oracleappstechnical.com)
LinkedIn profile - https://in.linkedin.com/in/sridevi-koduru-9b876a8b
Please Contact for One to One Online Training on Oracle Apps Technical, Financials, SCM, Oracle Manufacturing, OAF, ADF, SQL, PL/SQL, D2K at sridevikoduru@oracleappstechnical.com | +91 - 9581017828.