FMW 12.1.3.0.0 - Applying Patch 22364187: OSB Bundle Patch 12.1.3.0.1(ID:151209.1205)

FMW 12.1.3.0.0 - Applying Patch 22364187: OSB Bundle Patch 12.1.3.0.1(ID:151209.1205)

- Download Patch 22364187 (p22364187_121300_Generic.zip)

Applying Patch 22364187

- Unzip the patch

$ unzip -d PATCH_TOP p22364187_121300_Generic.zip 

- Stop all services

- $ cd PATCH_TOP/22364187

- Run opatch apply

$ opatch apply

- Restart all services

Patch De-Installation

If any issues after applying the patch and rollback is required, follow below steps:

- Stop all services

- $ cd PATCH_TOP/22364187

Run OPatch rollback

$ opatch rollback -id 22364187

- Restart all services

Related Posts:

FMW 12.1.3.0.0 - Applying Oracle WebLogic Server Patch 21983457: WLS PATCH SET UPDATE 12.1.3.0.6

Oracle WebLogic Server WLS 10.3.6.0.13 - Applying Patch 21984589: SU Patch [S8C2]: WLS PATCH SET UPDATE 10.3.6.0.13

FMW 11.1.1.9.0 - Applying Patch 22469374: SOA Bundle Patch 11.1.1.9.160119(ID:151224.1926)

FMW 11.1.1.9.0 - Applying Patch 22036578: SOA Bundle Patch 11.1.1.9.6(ID:151015.1650)

Applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

FMW 12.1.3.0.0 - Applying Patch 21885138: SOA Bundle Patch 12.1.3.0.4(ID:150922.0917.0153)

FMW 12.1.3.0.0 - Applying Patch Patch 22524811: SOA Bundle Patch 12.1.3.0.5(ID:160106.0610.0182)

FMW 12.1.3.0.0 Additional steps for Bug 18706071: SUPPORT FOR CREDENTIAL STORE FOR CLOUD CONNECTORS IS MISSING IN OSB after applying Patch 20900599 (SOA Bundle Patch 12.1.3.0.3) or Patch 21885138 (SOA Bundle Patch 12.1.3.0.4)

FMW 12.1.3.0.0 Additional steps for Bug 18706071: SUPPORT FOR CREDENTIAL STORE FOR CLOUD CONNECTORS IS MISSING IN OSB after applying Patch 20900599 (SOA Bundle Patch 12.1.3.0.3) or Patch 21885138 (SOA Bundle Patch 12.1.3.0.4)

After applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3, or Patch 21885138 (SOA Bundle Patch 12.1.3.0.4), follow below steps for Bug Fix 18706071 to take effect,

1. Log in to Fusion Middleware Control Enterprise Manager.

2. Expand "Weblogic Domain" in the left panel

3. Right click on the domain you want to modify and select Security > System Policies to display the page System Policies.

4. In the System Policies page, expand "Search". For "Type" select "Codebase", for "Includes" enter "jca" and click the arrow button.

5. Select "jca-binding-api.jar" in the search returned result and click "Edit".

6. In the "Edit System Grant" page, click on "Add".

7. In the "Add Permission" page, click on "Select here to enter details for a new permission" and enter the following:

Permission Class:oracle.security.jps.service.credstore.CredentialAccessPermission
Resource Name: context=SYSTEM,mapName=SOA,keyName=*
Permission Action: *


8. Click on "OK" to save the new permission.

Related Posts:

FMW 12.1.3.0.0 - Applying Patch 20163149: DATAOBJECT ASSIGNMENT LOST AFTER DEHYDRATION

FMW 12.1.3.0.0 - Applying Patch 21885138: SOA Bundle Patch 12.1.3.0.4(ID:150922.0917.0153)

Applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

Checking SOA 12c version

SOA Bundle Patch 12.1.3.0.1(Patch 19707784) rolled back when applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

FMW 12.1.3.0.3 - Applying SOA Suite Patch 21387680: B21248791 mq adapter error still not fixed

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.