Upgrade Oracle Application Server to 10.1.3.4 (10g R3 patchset 4)

-

Overview of applying Oracle Application Server 10g R3 patchset 4 (10.1.3.4) on existing 10g R3 (10.1.3)



Key Points for 10.1.3.4 Upgrade

1. Patch Number for OAS 10g R3 patchset 4 (10.1.3.4) is 7272722

2. 10g R3 patchset 4 (10.1.3.4.0 - 7272722) is cumulative and includes all fixes from 10.1.3.0, 10.1.3.1, 10.1.3.2 and 10.1.3.3

3. 10g R3 patchset 4 (10.1.3.4.0) is NOT complete software, you need to install in on top of one of existing software i.e. 10.1.3.n (10.1.3.0, 10.1.3.1, 10.1.3.2 or 10.1.3.3)

4)10g Rel 3 patchset 1 (10.1.3.1.0) is starting point for Oracle SOA Suite (BPEL, ESB…) and 10g Rel 3 patchset 2 (10.1.3.2.0) is starting point for WebCenter Suite (ContentDB, WebCenter Services). If you are using Oracle SOA Suite or Oracle Web Center then you need to do additonal steps before upgrade like

– upgrade_10131_10134_oracle.sql (10.1.3.1) or

– upgrade_10133_10134_oracle.sql (10.1.3.3) (For BPEL from ORABPEL schema)

– upgrade_10133_10134_oracle.sql (For ESB from ORAESB schema)

5) 10.1.3.4 patch set updates DSA (Application Server Guard) ports so if you have edited dsa.conf , reset it back after 10.1.3.4 patch set. - Oracle is moving away from ASGuard/DSA; try not to use it * More information coming soon …

6) It is NOT possible to upgrade from 10g Rel2 (10.1.2.X) to 10g Rel3 (10.1.3.X) Application Server (Till date)

Top Level Steps

1. If you are using BPEL; Run upgrade_10131_10134_oracle.sql (10.1.3.1) or upgrade_10133_10134_oracle.sql (10.1.3.3) from ORABPEL schema

2. If you are using ESB; Run upgrade_10133_10134_oracle.sql from ORAESB schema

3. Install 10.1.3.4 Software in same ORACLE_HOME (as of 10g R3, 10.1.3.X)

For exact steps follow read me of patch 7272722

Comments

Post a Comment

Popular posts from this blog

jstatd error : Could not create remote object : access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write)

-
While running "./jstatd -J-Djava.security.policy=jstatd.all.policy &" command , below error is getting encountered Error :- Could not create remote object access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) java.security.AccessControlException: access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:536) at java.lang.System.setProperty(System.java:699) at sun.tools.jstatd.Jstatd.main(Jstatd.java:122) Cause :- The "access denied" error is expected, because "jstatd" requires a security policy file specified with the "java.security.policy" system property, if there is no security manager running on the machine. Solution :- 1) cd $ORACLE_HOME/jdk
Read more

Weblogic server is not starting up ; java.lang.AssertionError

-
  If the weblogic server is not starting up and giving the below error , please follow the below solution :- Error :- #Aug 18, 2014 12:34:29 AM PDT# #Notice# #WebLogicServer# #BEA-000365# #Server state changed to STARTING# #Aug 18, 2014 12:34:29 AM PDT# #Info# #WorkManager# #BEA-002900# #Initializing self-tuning thread pool# #Aug 18, 2014 12:34:29 AM PDT# #Notice# #Log Management# #BEA-170019# #The server log file /u01/app/oracle/config/domains/Vinay/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.# #Aug 18, 2014 12:34:29 AM PDT# #Critical# #WebLogicServer# #BEA-000386# #Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine. java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.                 a
Read more

ORA-22990: LOB locators cannot span transactions

-
Below is the error reported in BPEL opmn logs :- ############ <2010-02-07 10:50:59,852> <:logerror>Error while invoking bean "cube engine": Cannot update lob column.The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid. sql statement: BEGIN INSERT INTO cube_scope( cikey, domain_ref, scope_bin ) VALUES ( ?, ?, '0' ) RETURNING scope_bin INTO ?; END; ORABPEL-04040 Cannot update lob column. The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Oth
Read more