Upgrade Oracle SOA Suite from 10.1.3.x to 10.1.3.5 on Windows

* Download Download patchset number 8626084 from Metalink.
* Unzip into a temp directory.
* See ‘readme.html’ for detailed upgrade instructions.
* Steps documented here are for upgrade a fresh install of 10.3.1.x. If not a fresh install, see ‘readme.xml’ for extract steps to upgrade applications.

cd Disk1\install\soa_schema_upgrade\bpel\scripts
sqlplus /nolog
connect orabpel/welcome1
@upgrade_10131_10135_oracle.sql

cd Disk1\install\soa_schema_upgrade\esb\sql\other
sqlplus /nolog
connect oraesb/welcome1
@upgrade_10131_10135_oracle.sql

*Restart Oracle DB instance.

cd Disk1\install\soa_schema_upgrade\bpel\scripts
sqlplus /nolog
connect orabpel/welcome1
@upgrade_10133_10135_oracle.sql

cd Disk1\install\soa_schema_upgrade\esb\sql\other
sqlplus /nolog
connect oraesb/welcome1
@upgrade_10133_10135_oracle.sql

* Restart Oracle DB instance.

* If oraesb schema is not updated, you’ll get following error message when you try to deploy ESB application:

Entity Deployment Failederror code: 1001 : 5 summary: Failed to create Service “ESBService”. Fix: Ensure that the (a) Repository is available. (b) The Connection information for the Repository is Valid. Verify the detailed cause of error if available. Contact Oracle Support if error not fixable.

See this post for more details.

* Backup(zip) original install.

* Login AS
* Got to: Cluster Topology -> default_group -> home -> Applications -> EJB3.0 application
* Click undeploy

* Ensure the following values are set in the ORACLE_HOME/owsm/bin/install.properties file:

install.http.host=hostname
install.http.port=7777

* Note, I left mime as

install.http.host=myhost.my.com
install.http.port=80

ORACLE_HOME/opmn/bin/opmnctl status
 
Processes in Instance: soaas.myhost.my.com
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
ASG                              | ASG                |     N/A | Down
OC4JGroup:default_group          | OC4J:oc4j_soa      |     592 | Alive
OC4JGroup:default_group          | OC4J:home          |     856 | Alive
HTTP_Server                      | HTTP_Server        |    3616 | Alive

* Double click ‘Disk1\setup.exe’

Destination
Name: oracleas1
Path: C:\product\10.1.3.1\OracleAS_2

oc4jadmin Password: welcome1

Hostname: localhost
Port: 1521
Service Name: orcl
ORAWSM password: welcome1

* Enable PHP if not already done.

cd C:\product\10.1.3.1\OracleAS_2\Apache\Apache\conf

– Edit httpd.conf

# Comment out
#LoadModule php4_module modules/php4apache.dll
#AddModule mod_php4.c
 
# Add
LoadModule php5_module modules/php5apache.dll
AddModule mod_php5.c
 
# Add .php5
AddType application/x-httpd-php .php .php5

* Edit C:\product\10.1.3.1\OracleAS_2\j2ee\oc4j_soa\config\data-sources.xml
* Change factory-class for “BPELPM_CONNECTION_POOL” from “oracle.jdbc.OracleDriver” to “oracle.jdbc.pool.OracleDataSource”
From:

<connection-pool name="BPELPM_CONNECTION_POOL">
    <connection-factory factory-class="oracle.jdbc.OracleDriver" user="orabpel"/>
</connection-pool>

To:

<connection-pool name="BPELPM_CONNECTION_POOL">
    <connection-factory factory-class="oracle.jdbc.pool.OracleDataSource" user="orabpel"/>
</connection-pool>

* Restart SOA Instances

* Redeploy EJB 3.0 applications.

* Don’t forget to upgrade JDev to 10.1.3.5 as well.

You could get the following error while trying to deploy your bpel application.

An error occurred while attempting to deploy the BPEL suitcase file “C:\product\10.1.3.1\OracleAS_2\bpel\domains\default\tmp\bpel_2516715.tmp”; the exception reported is: archive cannot rename C:\product\10.1.3.1\OracleAS_2\bpel\domains\default\tmp\.bpel_TestProcessor_1.0_f0df3b440d722780bb2c1a088b1d2ba2.tmp

* Manually undeploy your bpel application using the BPEL console,
* Manually remove bpel\domains\default\tmp directory,
* Redeploy.

* Download unlocker.
* Install unlocker.
* Navigate to bpel\domains\default\tmp directory.
* Right click locked .tmp file
* Unlock it.
* Redeploy.

See this post for details and other options.