Friday

Portal Upgrade 11.1.1.3 to 11.1.1.6



A few months ago we upgraded our Fusion Middleware Portal environment from 11.1.1.3 to 11.1.1.6.   The upgrade went pretty smoothly, especially compared to our 11.1.1.1 to 11.1.1.3 upgrade.   It seems that Oracle has replaced alot of the manual post-upgrade tasks with scripts.   It seemed much easier this time around.

Below is the upgrade.   I'll post a followup shortly with some of the issues I encountered and how they were resolved.

1.  Shutdown Portal
   a.  $FUSION_HOME/PORTALasinst_1/bin/opmnctl stopall;
 
   b.  $DOMAIN_HOME/bin/stopManagedWebLogic.sh WLS_PORTAL
        $DOMAIN_HOME/bin/stopWebLogic.sh

2.  Backup application and Database

3.  If you haven't already download the patchset from Oracle and extract it.
       Portal 11.1.1.6:  
             https://updates.oracle.com/download/13517084.html
       WebLogic 10.3.6:

            http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html

4.  Update WebLogic
    $JAVA_HOME/bin/java -jar wls1036_upgrade_generic.jar

clip_image002[4]
clip_image004[4]


Prompted for Configuration manager, Bypassed…

clip_image006[4]
clip_image008[4]
clip_image010[4]
clip_image012[4]

5.  Upgrade Portal
   a. $STAGEDIR/Disk1/runInstaller.sh


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

 Upgrade Portal Schema using the Patch Set Assistant

   1. Recompile any INVALID objects:
            @?/rdbms/admin/utlrp.sql

   2. Verify aq_tm_proccesses > 0

        show parameter aq_tm_processes;
        alter system set aq_tm_processes=1 scope=both;

  3.  Run the PSA utility
         $ORACLE_HOME/oracle_common/bin/psa

clip_image028[4]
clip_image030
clip_image032
clip_image034

After you put in the database credentials click on the Connect button to select the Portal schema, enter the password and click on Next:

clip_image036
clip_image038
clip_image040
clip_image044
clip_image046

clip_image048

4.  Recompile any INVALID objects following same steps as above.
5 . Verify upgrade was successful
SQL> SELECT OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY;
OWNER        VERSION       STATUS   U
DEV_PORTAL        11.1.1.6.0       VALID   Y




Post-Patching Tasks If Your Starting Point is Release 11.1.1.3.0
1 . Upgrading System Components
a.  Startup the Weblogic Admin server for the Portal Domain
Check to see if Config is locked
b.   ORACLE_HOME=/u01/app/oracle/product/fmw11g/PORTALas_1
c.  Start OPMN Instance
$FUSION_HOME/PORTALasinst_1/bin/opmnctl start
d.   Execute upgradenoj2eeapp.sh from $ORACLE_HOME/opmn/bin
[oracle@myserver bin]$ ./upgradenonj2eeapp.sh -oracleInstance /u01/app/oracle/product/fmw11g/PORTALasinst_1 -adminHost myserver -adminPort 7001 -adminUsername weblogic
Unregister instance...
Command requires login to weblogic admin server (myserver):
  Username: weblogic
  Password: 
Unregistering instance
Command succeeded.
redeploy NonJ2EEManagement.ear...
Command requires login to weblogic admin server (myserver):
  Username: weblogic
  Password: 
Redeploying NonJ2EEManagement Application...weblogic.Deployer invoked with options:  -adminurl myserver:7001 -username weblogic -name NonJ2EEManagement -source /u01/app/oracle/product/fmw11g/PORTALas_1/opmn/applications/NonJ2EEManagement.ear -redeploy -upload -noexit
 
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.
re-register instance...
Command requires login to weblogic admin server (myserver):
  Username: weblogic
  Password: 
Registering instance
Command succeeded.
Successfully upgraded NonJ2EEManagement.ear and the registeration.
e.   Resolving JDBC Errors in Oracle Reports and Oracle Portal
You must perform the following in order to avoid these JDBC error messages:
Go to the bin directory inside your DOMAIN_HOME.
Edit the setDomainEnv.sh (on UNIX operating systems) or setDomainEnv.cmd (on Windows operating systems) file and search for EXT_PRE_CLASSPATH.
Change the definition to match the following:
On UNIX operating systems:
EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar
export EXT_PRE_CLASSPATH
For example:
if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
   if [ "${PRE_CLASSPATH}" != "" ] ; then
      EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar // add this line
      export EXT_PRE_CLASSPATH                           // add this line
      PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
      export PRE_CLASSPATH
   else
      EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar  // add this line
      export EXT_PRE_CLASSPATH                            // add this line
      PRE_CLASSPATH="${EXT_PRE_CLASSPATH}"
      export PRE_CLASSPATH
   fi
fi
f.   Updating Fusion Middleware Shared Libraries
Run the upgradeJRF() command on the node or system where the Administration Server is located for each domain you want to update. Your domain location is passed as a parameter:
FUSION_HOME/oracle_common/common/bin/wlst.sh
wls:/offline> upgradeJRF('/u01/app/oracle/product/fmw11g/user_projects/domains/PortalDomain')

g . Updating Configurations and Stores
wls:/offline> upgradeOpss(jpsConfig="/u01/app/oracle/product/fmw11g/user_projects/domains/PortalDomain/config/fmwconfig/jps-config.xml", jaznData="/u01/app/oracle/product/fmw11g/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml")  
{auditStore=null, password=null, user=null, url=null, jdbcDriver=null, jaznData=/u01/app/oracle/product/fmw11g/oracle_common/modules/oracle.jps_11.1.1/domain_config/system-jazn-data.xml, jpsConfig=/u01/app/oracle/product/fmw11g/user_projects/domains/PortalDomain/config/fmwconfig/jps-config.xml}
Starting upgrade of opss configuration and security stores.
Aug 23, 2012 11:55:38 AM oracle.security.jps.internal.audit.dynamic.AuditStoreFactory getInstance
WARNING: file /u01/app/oracle/product/fmw11g/user_projects/domains/PortalDomain/config/fmwconfig/audit-store.xml was not found
WLS ManagedService is not up running. Fall back to use system properties for configuration.
Upgrade of opss configuration and security stores is done.
NOTE: Ignore Warning above.  See Note:  1435333.1
h . Optimizing Performance for WebLogic Server Domains on 64-Bit Platforms
Modify $DOMAIN_HOME/bin/setDomainEnv.sh and add:
before line:

# Had to have a separate test here BECAUSE of immediate variable expansion on windows

if [ "${JAVA_USE_64BIT}" = "true" ] ; then
        if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
                EXTRA_JAVA_PROPERTIES="-XXcompressedRefs:enable=TRUE
${EXTRA_JAVA_PROPERTIES}"
                export EXTRA_JAVA_PROPERTIES
        fi
fi
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
        EXTRA_JAVA_PROPERTIES="-XX:+UseLargePagesForHeap
${EXTRA_JAVA_PROPERTIES}"
        export EXTRA_JAVA_PROPERTIES
fi
EXTRA_JAVA_PROPERTIES="-Djps.auth.debug=false ${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES 

2 comments:

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.

Sujitkumar said...

Nice blog. Really helpful information about Oracle …. Please keep update some more…………