Applying Patch 20900797: SOA Bundle Patch 11.1.1.7.8

Applying Patch 20900797: SOA Bundle Patch 11.1.1.7.8

Pre-Patch Instructions

- Review and download the latest version of OPatch 11.1.x via Bug 6880880

- Ensure access to valid OUI Inventory by running opatch lsinventory

- Validate the executables in system PATH like 'which opatch', 'which unzip'

- You MUST apply this patch to both SOA Home $MW_HOME/Oracle_SOA1 and Oracle Common Home $MW_HOME/oracle_common without fail.


Applying Patch

1. Download and unzip the patch zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p20900797_111170_Generic.zip

2. cd PATCH_TOP/20900797

3. Run opatch apply (Ensure MT services are already stopped, cold backup is recommended before patch)

4. If Patch is successful, restart MT services. Verify the patch by running 

$ opatch lsinventory | grep 20900797

Additionally you may also apply the SOA and BPM JDev extensions directly from JDeveloper via the “check for updates” feature

Rollback Patch

If patch fails for some reason, rollback the patch and restart MT services.

$ opatch rollback -id 20900797


Related Posts:

Applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

Applying Patch 20423535: SOA Bundle Patch 11.1.1.7.7

Applying Patch 19953598: SOA Bundle Patch 11.1.1.7.6

Applying Patch 19190139 SOA BUNDLE PATCH 11.1.1.7.5

Applying Patch 18609527 SOA BUNDLE PATCH 11.1.1.7.4

Applying Patch 18072286 SOA BUNDLE PATCH 11.1.1.7.3

Applying Patch 17584181 SOA BUNDLE PATCH 11.1.1.7.2

FMW 11.1.1.6.0 - Applying Patch 16702086: SOA BUNDLE PATCH 11.1.1.6.7

Applying Patch 20423535: SOA Bundle Patch 11.1.1.7.7

Applying Patch 20423535: SOA Bundle Patch 11.1.1.7.7

Pre-Patch Instructions

- Review and download the latest version of OPatch 11.1.x via Bug 6880880

- Ensure access to valid OUI Inventory by running opatch lsinventory

- Validate the executables in system PATH like 'which opatch', 'which unzip'

- You MUST apply this patch to both SOA Home $MW_HOME/Oracle_SOA1 and Oracle Common Home $MW_HOME/oracle_common without fail.

Applying Patch 20423535

1. Download and unzip the patch 20423535 zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p20423535_111170_Generic.zip

2. cd PATCH_TOP/20423535

3. Run opatch apply (Ensure MT services are already stopped, cold backup is recommended before patch)

4. If Patch is successful, restart MT services. Verify the patch by running 

$ opatch lsinventory | grep 20423535

Additionally you may also apply the SOA and BPM JDev extensions directly from JDeveloper via the “check for updates” feature

5. If patch fails for some reason, rollback the patch and restart MT services.

$ opatch rollback -id 20423535

Related Posts:

Applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

Applying Patch 20900797: SOA Bundle Patch 11.1.1.7.8

Applying Patch 19953598: SOA Bundle Patch 11.1.1.7.6

Applying Patch 19190139 SOA BUNDLE PATCH 11.1.1.7.5

Applying Patch 18609527 SOA BUNDLE PATCH 11.1.1.7.4

Applying Patch 18072286 SOA BUNDLE PATCH 11.1.1.7.3

Applying Patch 17584181 SOA BUNDLE PATCH 11.1.1.7.2

FMW 11.1.1.6.0 - Applying Patch 16702086: SOA BUNDLE PATCH 11.1.1.6.7

BEA-149231 Unable to set the activation state to true for the application 'soa-infra'.SOA-Infra fails to start if a composite fails on startup of SOA server 11.1.1.7.6 / 11.1.1.7.7

BEA-149231 Unable to set the activation state to true for the application 'soa-infra'.SOA-Infra fails to start if a composite fails on startup of SOA server 11.1.1.7.6 / 11.1.1.7.7

SOA-Infra fails to start if a composite fails on startup of the SOA server 11.1.1.7.6 / 11.1.1.7.7

Error messages as below can be seen in the stdout 

Deployer BEA-149231 Unable to set the activation state to true for the application 'soa-infra'. weblogic.application.ModuleException: [HTTP:101216]Servlet: failed to preload on startup in Web application: "/soa-infra". oracle.fabric.common.FabricException: Error in getting XML input stream: oramds:/deployed-composites/test1/composite.xml: oracle.mds.exception.MDSException: MDS-00054: The file to be loaded oramds:/deployed-composites/test1/composite.xml does not exist.

1) For SOA 11.1.1.7.6


Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS


Pre-requisite Patches ( Mandatory)
-----------------------------------------------

19953598 SOA Bundle Patch 11.1.1.7.6


2) For SOA 11.1.1.7.7

Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS
 

Pre-requisite Patches ( Mandatory)
-----------------------------------------------


20423535 SOA Bundle Patch 11.1.1.7.7

Applying Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS on SOA 11.1.1.7.7

Applying Patch 16574779: SOA-INFRA SHOULD START UP INSPITE OF ERRORS ENCOUNTERED IN SOA APPS on SOA 11.1.1.7.7

If soa-infra fails to start on SOA 11.1.1.7.7 start due to failure in starting a composite, you will see errors in stdout as in this post. 

If the errors are similar then you should consider applying Patch 16574779.


Pre-requisite Patches
-----------------------------

20423535 SOA Bundle Patch 11.1.1.7.7


Pre-Installation Instructions:
------------------------------

- Ensure Patch 20423535 SOA Bundle Patch 11.1.1.7.7 already applied. 

- Review and download the latest version of OPatch 11.1.x via Bug 6880880

- Ensure access to valid OUI Inventory by running opatch lsinventory

- Validate the executables in system PATH like 'which opatch', 'which unzip'


Installation Instructions
---------------------------

1. Unzip the patch zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p16574779_111177_Generic.zip

2. $ cd PATCH_TOP/16574779/oui

3. Stop MT services and run opatch apply (Conflict checks & cold backup recommended before applying patch)

4. If patch is successful, restart the services and verify the patch by running opatch lsinventory | grep 16574779


5. If patch fails for some reason, roll back the patch by running opatch rollback -id 16574779 and restart the services. 

Related posts:

BEA-149231 Unable to set the activation state to true for the application 'soa-infra'.SOA-Infra fails to start if a composite fails on startup of SOA server 11.1.1.7.6 / 11.1.1.7.7

Applying SOA Bundle Patch 20423535: PS6 Bundle Patch 7 (11.1.1.7.7) and OSB Bundle Patch 20423630: PS6 Bundle Patch 4 (11.1.1.7.4)

Applying SOA Bundle Patch 20423535: PS6 Bundle Patch 7 (11.1.1.7.7) and OSB Bundle Patch 20423630: PS6 Bundle Patch 4 (11.1.1.7.4)

I) Applying SOA Bundle Patch 20423535:  PS6 Bundle Patch 7 (11.1.1.7.7)
----------------------------------------------------------------------------------------------------


- Before applying patch, run below on soa_111 & oracle_common home to ensure that the patch is not already applied. You may also check for conflicts with existing patches.

opatch apply -report


- Stop services & take cold backup


Download the patch & copy to staging area.

cd /stage/20423535


i) Apply Patch 20423535 on soa_111 home
----------------------------------------------------------

export ORACLE_HOME=/instance_name/fmw/product/111/soa_111
export PATH=$ORACLE_HOME/OPatch:$PATH  


opatch apply

Verify patch applied
---------------------
opatch lsinventory|grep 20423535



ii) Apply Patch 20423535 on oracle_common home
--------------------------------------------------------------------

export ORACLE_HOME=/instance_name/fmw/product/111/oracle_common

export PATH=$ORACLE_HOME/OPatch:$PATH
  
opatch apply
  
Verify patch applied
---------------------------

opatch lsinventory|grep 20423535




II) Applying OSB Bundle Patch 20423630:  PS6 Bundle Patch 4 (11.1.1.7.4)
-----------------------------------------------------------------------------------------------------

- Before applying patch, run below on osb_111 home to ensure that the patch is not already applied
- Stop services & take cold backup


Download the patch & copy to staging area.

cd /stage/20423630

opatch apply -report

export ORACLE_HOME=/instance_name/fmw/product/111/osb_111
export PATH=$ORACLE_HOME/OPatch:$PATH
  

opatch apply

Verify patch applied
--------------------

opatch lsinventory|grep 20423630  


III) Post Patching
-------------------


Move tmp and cache for Admin and each managed server
-----------------------------------------------------


cd /instance_name/admin/user_projects/soa_domain/servers/

mv tmp tmp_<date>

mv cache cache_<date>


Move the application staging area for each managed server
---------------------------------------------------------

Location of staging area: domain_home/servers/osb_server1/stage. 


PLEASE NOTE: If staging directory for each managed server is not deleted, then the patch will not take effect & the server may not even start successfully.


Once server started, verify if the stage directory has got recreated.


cd /instance_name/admin/user_projects/soa_domain/bin


Configure setDomainEnv.sh
-------------------------

Take a backup of setDomainEnv.sh and add the below line appropriately


EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} 

-Dcom.bea.wli.sb.pipeline.RouterRuntimeCache.preload=true"
export EXTRA_JAVA_PROPERTIES



Start the services & ensure all urls work fine & no post patch errors seen in the logs.