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

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

- Download Patch 20265562 ( p20265562_111170_Generic.zip )

- Set environment variable ORACLE_HOME to $MW_HOME]/oracle_common

- Stop services

For Standalone JDeveloper install type, shutdown JDeveloper and ensure that Embedded/Integrated WLS Server is also stopped.

For Standalone WLS install type, ensure that WebLogic server is stopped.

Applying Patch 20265562

- Unzip the patch zip file

$ unzip -d PATCH_TOP p20265562_111170_Generic.zip

- $ cd PATCH_TOP/20265562/oui

- Run OPatch apply

- For Standalone JDeveloper install type, start JDeveloper and ensure Embedded/Integrated WLS Server is also started.

- For other install types including standalone WLS, restart Admin Server and Managed Servers.

Patch De-installation

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

- Change to the directory where the patch was unzipped.

   $ cd PATCH_TOP/20265562/oui

- Run OPatch rollback

$ opatch rollback -id 20265562 

- Clean contents of tmp directory from $DOMAIN_HOME\servers\DefaultServer\tmp for standalone Jdeveloper installs and from $DOMAIN_HOME/servers/[servername]/tmp for Admin and Managed Servers of other install types

- Start JDeveloper and ensure Embedded WLS Server is also started

Related Posts:

FMW 11.1.1.7.0 - Applying Patch 20805649: REL9 BP16 CUMULATIVE JDEVADF_11.1.1.7.9ADF-FAREL9-BP_GENERIC_150401.1409.6807

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

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

ODSM 11g - Applying Patch 21665104: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 20715966 17191718 to resolve errors java.lang.Exception: MDSLockedSessionManager already registered. Can't register more than one.

WebCenter Capture 11.1.1.8 Cluster - Workspace created or imported on one node is not visible on the other node and workspace gets deleted on restart of cluster node

WebCenter Capture 11.1.1.8 Cluster - Workspace created or imported on one node is not visible on the other node and workspace gets deleted on restart of cluster node

This issue is seen if the cluster configuration is still based on a file security store. The security information in this case will be stored in a file "system-jazn-data.xml" local to the Weblogic server. 

Example: If you create workspace on Node 1 of cluster, it will save the security information in "system-jazn-data.xml" file on Node 1. "system-jazn-data.xml" on Node2 will not have the updates made to the file on Node 1.


To resolve this issue, use either of the relevant options below:

1) Use OID Based Policy Store (select this if using OID / LDAP)



2) Use Database Based Security Store (OPSS schema)

In either of the options you need to run reassociateSecurityStore and restart the complete domain for workspace created or imported to reflect on both the cluster nodes. 

Related Posts:

WebCenter Capture 11.1.1.8 Cluster - Using Database Based Security Store

WebCenter Capture 11.1.1.8 Cluster - Using OID Based Policy Store

WebCenter Capture 11.1.1.8 Cluster - Creating OPSS schema for using Database Based Security Store

WebCenter Capture 11.1.1.8.0 - reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false") fails with error JPS-00027: There was an internal error: java.sql.BatchUpdateException: ORA-00904: "ATTRKIND": invalid identifier