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 21885138: SOA Bundle Patch 12.1.3.0.4(ID:150922.0917.0153)

- Download Patch 21885138 (p21885138_121300_Generic.zip)

Applying Patch 21885138

- Ensure all patch pre-requisites are met as documented in Patch README file.

- Stop all MT services (AdminServer and all Managed server(s)).

- Patch 20163149 is recommended for performance improvement.

- unzip the patch

 $ unzip -d PATCH_TOP p21885138_121300_Generic.zip

- $ cd PATCH_TOP/21885138

- Run OPatch to apply the patch.

   $ opatch apply

Verify patch

$ORACLE_HOME/OPatch/opatch lsinventory|grep 21885138

- Start all MT services

For Bug Fix 18706071 to take effect,  refer to this post.

Patch De-installation

If any issues post patching and rollback is required, please follow below steps:

- Stop MT services

- $ cd PATCH_TOP/21885138

- Run OPatch to deinstall the patch.

- $ opatch rollback -id  21885138

- Start all MT services

Related Posts:

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

Applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

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

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)

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

Checking SOA 12c version

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

OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894

OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894

Redeploying the OAAM Shared Library in Oracle WebLogic is one of the post patching steps after applying Patch 19162894. Refer to this post for more details.

If you have a native integration, redeploy the OAAM shared library by following these steps:

• Start the managed server.

Log in to the WebLogic Administration Console. Open a web browser and enter the URL:

http://hostname:port/console
or

https://hostname:port/console

On the Welcome screen, log in using the user name and password

• In the Domain Structure section of the console, click Deployments. The Summary of Deployments page is displayed.

• In the Summary of Deployments page, select oracle.oaam.libs in the Deployments table and then click Delete.

• In Change Center, click Activate Changes for the changes to take effect.

• Click the Install button.

• In the path field, specify the path to the oaam_native_lib.war file, including the file name.

• Select oaam_native_lib.war and Next.

• On the next screen, select the Install this deployment as a library option and click Next.

• In the Select Deployments targets page, select the managed server from the list of servers to deploy the shared library, oracle.oaam.libs, and click Next and Click Finish.

• In the Change Center, click Activate Changes for the changes to take effect.

Related Posts:

Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC

FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG

Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894

OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894

OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894


Redeploying the OAAM applications is one of the post patching steps after applying Patch 19162894. Refer to this post for more details.


To redeploy the OAAM applications, follow these steps:

• Delete the content from the OAAM Admin server (oaam_admin_server1), OAAM Server server (oaam_server_server1), OAAM Offline server (oaam_offline_server1) temp directories:

MW_HOME/user_projects/domains/domain_home/servers/oaam_admin_server1/tmp
MW_HOME/user_projects/domains/domain_home/servers/oaam_server_server1/tmp
MW_HOME/user_projects/domains/domain_home/servers/oaam_offline_server1/tmp
Start all servers.

• Log in to the WebLogic Administration Console. Open a web browser and enter the URL:

http://hostname:port/console
or

https://hostname:port/console

• Redeploy the oaam_admin application by performing these steps:

1) In the Domain Structure section of the console, click Deployments. The Summary of Deployments page is displayed.

2) Select oaam_admin in the Deployments table and click Update.

3) In the Domain Structure section of the console, click Deployments.

4) In the Summary of Deployments page, select oaam_admin in the Deployments table.

5) Use the Stop drop-down list to select Force Stop Now.

Again select oaam_admin and then click Delete.

6) On the right, under Deployments, click Install.

When locating the deployment to install, provide the location of the oaam_admin.ear file in the Path field. You must include the file name, oaam_admin.ear, when specifying the path.

On the next screen, choose Install this deployment as an application as the targeting style and click Next.

On the next screen, select the OAAM Admin Server as the target for oaam_admin. For example, select the target oaam_admin_server1.

On the next screen for optional settings, make sure you select 'I will make the deployment accessible from the following location' and point to the location where the oaam_admin.ear file will be accessible:

Oracle_IDM/oaam/oaam_admin/ear/oaam_admin.ear
Click Finish to complete the deployment of oaam_admin.

7) Log in to the OAAM Admin Console.

In the Navigation tree, double-click Properties under Environment.

In the Properties page, search for the oaam.taskflow.enum.sessionaddtogroup property.

Select the oaam.taskflow.enum.sessionaddtogroup.name property and click Save.

Saving the property will change it from a file load type property to a database type property. The property is now available in the database.

If the oaam.taskflow.enum.sessionaddtogroup.name property does not exist, create it.

Click the New Property button or Create new Property icon.

In the New Property dialog, type in oaam.taskflow.enum.sessionaddtogroup.name as the property name and SessionAddToGroup as the property value.

Click Save to save the property.

8) Restart the OAAM Admin server.

9) Update and activate changes for OAAM Server.

In the Domain Structure section of the console, click Deployments.

In the Summary of Deployments page, select oaam_server in the deployment table and click Update.

In the Change Center, click Activate Changes for the changes to take effect.

10) Update and activate changes for OAAM Offline.

In the Domain Structure section of the console, click Deployments.

Select the oaam_offline application in the deployment table and click Update.

In the Change Center, click Activate Changes for the changes to take effect.

If you find that oaam_admin, oaam_server, and oaam_offline are not in the Active state, then select the appropriate server and click Start.

When you have applied the OAAM 11.1.2.1.3 patch (19162894), version information is shown when you click the About link on the right side bottom corner. The version information should appear as Version 11.1.2.1.0 (11.1.2.1.0.OAAM_11.1.2.1.0BP_GENERIC_140828.0325).

Related Posts:

Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC

FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG

Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894

Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5


- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)

- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:

- OES 11.1.2.1.1

- OPSS 11.1.1.6.3

- OAM 11.1.2.1.4

- OAAM 11.1.2.1.3

- Copy and unzip p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.

- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)


Pre-requisites

- Stop all servers to which you will apply this bundle patch, and any application that uses this component.

- Backup ORACLE_HOME

- On OAAM Admin and OAAM Server, copy all customized properties, .xml and keystore files to create a backup.

- Set the ORACLE_HOME directory. For example:

$ export ORACLE_HOME=$MW_HOME/Oracle_IDM1


Apply Patch 19162894


- Stop all servers in which you have applied the bundle patch, and any application that uses the component.

- cd /PATCH_TOP/19157616/OAAM/19162894

- Run opatch apply

$ opatch apply


Post Patch Instructions:

i) Redeploying OAAM Applications in Oracle WebLogic

ii) Redeploying the Shared Library in Oracle WebLogic


Rollback Patch 19162894

- Stop all servers in which you have applied the bundle patch, and any application that uses the component.

- cd /PATCH_TOP/19157616/OAAM/19162894

- Run opatch apply

$ opatch rollback -id 19162894

- Start all servers after rolling back the patch

Related Posts:

FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC

FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG

Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894

OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894

Oracle Database - Enterprise Edition - Applying Patch 21800477: QUARTERLY DATABASE PATCH FOR EXADATA (OCT2015 - 11.2.0.4.20)

Oracle Database - Enterprise Edition - Applying Patch 21800477: QUARTERLY DATABASE PATCH FOR EXADATA (OCT2015 - 11.2.0.4.20)

Note steps below are for patching DB Home only. Please review the relevant Patch README file for patching only Grid Infrastructure (GI) home or GI home and DB home together.

- Download Patch 21800477 (p21800477_112040_Linux-x86-64.zip) and copy onto server staging area say PATCH_TOP with appropriate permissions.

Apply latest OPatch Patch

- Check opatch version

$ORACLE_HOME/OPatch/opatch version

- You must use the OPatch utility version 11.2.0.3.6 or later to apply this patch. 

Apply latest OPatch Patch - on all nodes.

cd $ORACLE_HOME
mv OPatch OPatch_<ddmmyy>
unzip /sid/PATCH_TOP/p6880880_112000_Linux-x86-64.zip
export PATH=$ORACLE_HOME/OPatch:$PATH
opatch version

OCM Configuration:

OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file (ocm.rsp) when it is run. Provide ocm.rsp path if it exists or if not create 

it by running following command:

$ORACLE_HOME/OPatch/ocm/bin/emocmrsp

- Unzipped patch location must have read permission for ORA_INSTALL group of user who owns GI Home or group owner of Oracle central inventory.

- cd /sid/PATCH_TOP 

$ unzip p21800477_112040_Linux-x86-64.zip

- cd /sid/PATCH_TOP/21800477

Validate Oracle Inventory on Grid Infrastructure Home and DB Home

$ORACLE_HOME/OPatch/opatch lsinventory -detail -oh $ORACLE_HOME

Save the output of opatch lsinventory to compare the output later in case there are post patching issues and rollback is needed.

OPatch Conflict Check

Determine whether any currently installed one-off patches conflict with the Database Patch For Exadata (OCT2015 - 11.2.0.4.20)   21800477 as follows:

For Grid Infrastructure Home, as home user (skip this step if applying patch on DB home only):

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /sid/PATCH_TOP/21800477/21761335
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /sid/PATCH_TOP/21800477/21352649
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /sid/PATCH_TOP/21800477/21352642

For Database home, as home user:

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /sid/PATCH_TOP/21800477/21761335
$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /sid/PATCH_TOP/21800477/21352649/custom/server/21352649


This report will indicate the patches that conflict with 21800477 and patches for which patch 21800477 is a superset.


Run OPatch SystemSpace Check

Check if enough free space is available on the ORACLE_HOME filesystem for the patches to be applied as given below:

For Grid Infrastructure Home, as home user (skip this step if applying patch on DB home only):

$ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir /sid/PATCH_TOP/21800477/21761335
$ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir /sid/PATCH_TOP/21800477/21352649
$ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir /sid/PATCH_TOP/21800477/21352642

For Database home, as home user:

$ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir /sid/PATCH_TOP/21800477/21761335
$ORACLE_HOME/OPatch/opatch prereq CheckSystemSpace -phBaseDir /sid/PATCH_TOP/21800477/21352649/custom/server/21352649

- Stop DB services - on all nodes

$ORACLE_HOME/bin/srvctl stop home -o $ORACLE_HOME -s /tmp/$ORACLE_SID.txt -n <hostname>

  Stop DB Console

        $ORACLE_HOME/bin/emctl stop dbconsole



Apply following RDBMS patches 

- 21761335: DATABASE PATCH FOR EXADATA (OCT2015 - 11.2.0.4.20)
- 21352649: OCW Patch Set Update : 11.2.0.4.7  

Pre patch step (all DB nodes)

$ /sid/PATCH_TOP/21800477/21352649/custom/server/21352649/custom/scripts/prepatch.sh -dbhome $ORACLE_HOME
 
Apply patch 21761335 (all DB nodes)
 
$ opatch napply -oh $ORACLE_HOME -local /sid/PATCH_TOP/21800477/21761335

Apply patch 21352649 (all DB nodes)

$ opatch napply -oh $ORACLE_HOME -local /sid/PATCH_TOP/21800477/21352649/custom/server/21352649

Patches [   20420937 ] will be rolled back

Post patch step (all DB nodes)
  
/sid/PATCH_TOP/21800477/21352649/custom/server/21352649/custom/scripts/postpatch.sh -dbhome $ORACLE_HOME

- Start DB services

$ORACLE_HOME/bin/srvctl start home -o $ORACLE_HOME -s /tmp/$ORACLE_SID.txt -n <hostname> (all DB nodes)

Patch postinstallation (one node only)

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> connect / as sysdba

SQL> @catbundle.sql exa apply
SQL> @utlrp.sql  
SQL> exit

Verify patch application 

opatch lsinv -oh $ORACLE_HOME |egrep '21761335|21352649'  

Start Mid-Tier services


Rollback patch

- cd $ORACLE_HOME

- Stop DB services - on all nodes

$ORACLE_HOME/bin/srvctl stop home -o $ORACLE_HOME -s /tmp/$ORACLE_SID.txt -n <hostname>

  Stop DB Console

        $ORACLE_HOME/bin/emctl stop dbconsole

- Rollback patch 21761335 - all nodes

- Rollback patch 21352649 - all nodes

- Start DB services - all nodes

Post patch rollback:

- cd $ORACLE_HOME

SQL> connect / as sysdba

SQL> @rdbms/admin/catbundle_EXA_<database SID>_ROLLBACK.sql

- Validate Oracle Inventory on Grid Infrastructure Home and DB Home

$ORACLE_HOME/OPatch/opatch lsinventory -detail -oh $ORACLE_HOME

Re-apply any patches that are missing in the Oracle Inventory after patch roll back.#

- Start Mid-Tier services

Related Posts:

Applying Patch 17747140 - QUARTERLY DATABASE PATCH FOR EXADATA (JAN 2014 - 11.2.0.3.22) and Patch 17992671 - CRS PATCH FOR EXADATA (JAN 2014 - 11.2.0.3.22)

Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OAM 11.1.2.1.4 - Patch 19162892 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5


- Download Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5 (p19157616_111210_Generic.zip)

- Patch 19157616 (p19157616_111210_Generic.zip) includes patches for components:

- OES 11.1.2.1.1

- OPSS 11.1.1.6.3

- OAM 11.1.2.1.4

- OAAM 11.1.2.1.3

- Copy p19157616_111210_Generic.zip onto the server staging area say PATCH_TOP with appropriate permissions.

- Download the latest version of OPatch (11.1.0.9.0 or higher) via Patch 6880880 (p6880880_111000_PLATFORM.zip)


Apply OAM 11.1.2.1.4 - Patch 19162892

- Stop the Admin server and Managed servers (where OAM console and servers have been deployed)

- Unzip the patch zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p19162892_111210_Generic.zip

- cd /PATCH_TOP/19157616/OAM/19162892

- Run OPatch to apply the patch.

   $ opatch apply

- Restart all servers (Admin Server and all Managed Server(s))


Post-Installation Steps for IBM WebSphere (WAS) (Only applicable for OAM installed on the IBM WebSphere Application Server)
-----------------------------------------------

After applying this bundle patch on an instance of OAM installed on the IBM WebSphere Application Server (WAS), you must redeploy the OAM application in WAS for successful patch application. Follow 

steps in Patch README.HTML to manually redeploy the OAM administration application (oam-admin-was.ear) and the OAM server application (oam-server.ear). They should be individually redeployed.

1. "Redeploying oam-admin-was.ear"

2. "Redeploying oam-server.ear"


Patch 19162892 Rollback Instructions:

Post patching, if any issues encountered and rollback is required, follow below steps:

- Stop the Admin server and Managed servers (where OAM console and servers have been deployed)

- Change to the directory where the patch was unzipped.

   $ cd PATCH_TOP/19162892

- Run OPatch to deinstall the patch.

   $ opatch rollback -id 19162892 

- Restart all servers (Admin Server and all Managed Server(s))

Related Posts:

FMW 11.1.1.6.0 - Oracle Platform Security for Java - Applying Patch 15894053: TRACKING BUG FOR OPATCH DELIVERY OF ENTSEC_11.1.1.6.0-IDM11.1.2.1.0_GENERIC

FMW 11.1.1.6.2 JPS for IAM 11.1.2 - Oracle Virtual Directory Patch 14603262: IDS USER/GROUP NAME ATTR NOT MAPPED CORRECTLY TO CONFIGURED VALUES IN OPCONFIG

Applying OPSS 11.1.1.6.3 Patch 18629534 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OES 11.1.2.1.1 - Patch 18629535 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

Applying OAAM 11.1.2.1.3 - Patch 19162894 included in Patch 19157616: ORACLE IDENTITY MANAGEMENT SUITE BUNDLE PATCH 11.1.2.1.5

OAAM 11.1.2.1.3 - Redeploying OAAM applications in Oracle WebLogic Server after applying Patch 19162894

OAAM 11.1.2.1.3 - Redeploying the OAAM Shared Library in Oracle WebLogic after applying Patch 19162894

Applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

Applying Patch 20900599: SOA Bundle Patch 12.1.3.0.3

Note: This post is for applying patch on the SOA MW_HOME and not MW_HOME where JDeveloper is installed.


Patch pre-requisites

- Download the latest version of OPatch 13.2.x via My Oracle Support Patch 6880880. (Choose 13.2.0.0.0 or "OUI NextGen 13.2") p6880880_132000_Generic.zip

- Ensure access to valid OUI Inventory by running $ opatch lsinventory -jre $ORACLE_HOME/jdk/jre

- Validate the executables in system PATH after setting $ORACLE_HOME by running 'which opatch', 'which unzip'

- Download the patch to staging directory eg PATCH_TOP with appropriate permissions


Apply patch 20900599

- Stop all servers (AdminServer and all Managed server(s)).

- Patch 20163149 is recommended for performance improvement.

- Run $ unzip -d PATCH_TOP p20900599_121300_Generic.zip

- Run $ cd PATCH_TOP/20900599

- Apply patch (cold backup recommended)

$ opatch apply

If Patch 19707784 is existing, it will be rolled back.


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

- If any issues after applying the patch and you would like to roll back the patch, kindly run

$ opatch rollback -id 20900599

- While applying the patch, if any conflicts with existing patches detected or a merge patch for conflicting and new patch is required, stop the patch and contact Support.

- Restart all services


Related Posts:

Checking SOA 12c version

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

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 - Applying Patch 21885138: SOA Bundle Patch 12.1.3.0.4(ID:150922.0917.0153)

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)

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

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

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

Patch pre-requisites

- Download the latest version of OPatch 13.2.x via My Oracle Support Patch 6880880. (Choose 13.2.0.0.0 or "OUI NextGen 13.2") p6880880_132000_Generic.zip

- Ensure access to valid OUI Inventory by running $ opatch lsinventory -jre $ORACLE_HOME/jdk/jre

- Validate the executables in system PATH after setting $ORACLE_HOME by running 'which opatch', 'which unzip'

- Download the patch to staging directory eg PATCH_TOP with appropriate permissions

Apply Patch 20163149

- Set ORACLE_HOME to directory where ORACLE XML DEVELOPERS KIT is installed.

- Stop all servers (AdminServer and all Managed server(s)).

- Run $ unzip -d PATCH_TOP p20163149_121300_Generic.zip

- Run $ cd PATCH_TOP/20163149

- Apply the patch (cold backup recommended before applying patch)

$ opatch apply

Patch De-installation

- If any issues after applying the patch and you would like to roll back the patch, kindly run

$ opatch rollback -id 20163149

- While applying the patch, if any conflicts with existing patches detected or a merge patch for conflicting and new patch is required, stop the patch and contact Support.

- Restart all services

Related Posts:

Checking SOA 12c version

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 - 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

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)

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 Patch 20715966: JDEVADF SECURITY PATCH UPDATE 11.1.1.7.0 (CPUJUL2015)

Applying Patch 20715966: JDEVADF SECURITY PATCH UPDATE 11.1.1.7.0 (CPUJUL2015)

Applying Patch 20715966: JDEVADF SECURITY PATCH UPDATE 11.1.1.7.0 (CPUJUL2015)

- Review and download the latest version of OPatch to 

a) For Standalone JDeveloper/Standalone WLS install type: Download the latest version of OPatch(11.1.0.0.0) via BUG 5912518
b) b) For OUI (WebCenter/SOA/Classic/etc) install type: Download the latest version of OPatch (11.1.0.8.3 or higher) via BUG 6880880

- Ensure access to valid OUI Inventory by running opatch lsinventory

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

- Ensure Perl is 5.00503 or higher by sourcing ORACLE_HOME and running 'perl -v'

- For standalone Jdeveloper install or standalone WebLogic install types make sure that WLS server is stopped.


Applying Patch

1. Unzip the patch 20715966 zip file into the PATCH_TOP.

   $ unzip -d PATCH_TOP p20715966_111170_Generic.zip

2. cd PATCH_TOP/20715966/oui

3. Apply patch (Take cold backup as applicable, recommended though not mandatory)

  i) For OUI HOME, run opatch apply

 ii) For standalone JDeveloper Home, run opatch apply -jdk <jdk_path> -jre <jre_path>


4. If Patch is successful, restart MT services - Admin & Managed Servers for OUI Home, Restart Jdeveloper and Integrated WLS for standalone Jdev Home. 

5. Clearing tmp directory recommended post patching and before restarting services.

For standalone JDev Home - 

Default location of tmp => [JDEV_USER_DIR]\DefaultDomain\servers\DefaultServer\tmp\* 

For OUI Home - Default location of tmp =>   

[MW_HOME]/user_projects/domains/[DOMAIN_NAME]/servers/[SERVER NAME]/tmp/*


Patch rollback

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

$ opatch rollback -id 20715966 -jdk <jdk_path> -jre <jre_path>

Clearing tmp directory recommended post rollback before restarting services.

For standalone JDev Home - 

Default location of tmp => [JDEV_USER_DIR]\DefaultDomain\servers\DefaultServer\tmp\* 

For OUI Home - Default location of tmp =>   

[MW_HOME]/user_projects/domains/[DOMAIN_NAME]/servers/[SERVER NAME]/tmp/*



Related Posts:

FMW 11.1.1.7.0 - Applying Patch 18182516: UTF-8 CHARACTERS E3 E80 E81 NOT RECOGNIZED PROPERLY BY B2B

FMW 11.1.1.7.0 - Applying Oracle Jdeveloper Patch 20265562: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 19890682 14047857 16632043

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