FMW 11.1.1.8.0 Applying Patch 22060958: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.15

FMW 11.1.1.8.0 Applying Patch 22060958: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.15

Patch 22060958 is an interim Oracle WebCenter Content 11.1.1.8.0 patch for Bug: 22060958 (MLR 15)

Please note if Patch 21617568: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.14 has been applied on this instance, it will be rolled back during patching

- Ensure all the patch pre-requisites are met as in the README file

- Set ORACLE_HOME to WCC Home say $MW_HOME/WCC

- Stop MT services (Admin & Managed Servers)

- If using EBS or PSFT, modify below file:

For EBS - $ORACLE_HOME/ucm/idc/components/AppAdapterEBS/AppAdapterEBS.hda
For PSFT- $ORACLE_HOME/ucm/idc/components/AppAdapterPSFT/AppAdapterPSFT.hda
to change the "build=1" value to "build=2" or higher value

- Download and unzip the Patch 22060958 (p22060958_111180_Generic.zip)

$ unzip -d PATCH_TOP p22060958_111180_Generic.zip

- cd PATCH_DIR/22060958

- Apply the patch

$ opatch apply

- Verify the patch applied

opatch lsinventory |grep 22060958

- Clear browser cache & start MT services (Admin and Managed Servers)

Patch rollback

If any issues after applying the patch and if rollback is needed,

- Stop MT services

- cd PATCH_DIR/22060958

$ opatch rollback -id 22060958


- Clear browser cache & start MT services (Admin and Managed Servers)

Related Posts:

Applying Patch 21617568: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.14

Applying Patch 22449847: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.9.160119

Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

FMW 11.1.1.8.0 Applying Patch 21617568: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.14

FMW 11.1.1.8.0 Applying Patch 21617568: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.14

Patch 21617568 is an interim Oracle WebCenter Content 11.1.1.8.0 patch for Bug: 21617568 (MLR 14)

Pls note any previously applied MLR patches may be rolled back when applying this patch.

- Ensure all the patch pre-requisites are met as in the README file

- Set ORACLE_HOME to WCC Home say $MW_HOME/WCC

- Stop MT services (Admin & Managed Servers)

- If using EBS or PSFT, modify below file:

For EBS - $ORACLE_HOME/ucm/idc/components/AppAdapterEBS/AppAdapterEBS.hda
For PSFT- $ORACLE_HOME/ucm/idc/components/AppAdapterPSFT/AppAdapterPSFT.hda
to change the "build=1" value to "build=2" or higher value

- Download and unzip the Patch 21617568 (p21617568_111180_Generic.zip)

$ unzip -d PATCH_TOP p21617568_111180_Generic.zip

- cd PATCH_DIR/21617568

- Apply the patch

$ opatch apply

- Verify the patch applied

opatch lsinventory |grep 21617568

- Clear browser cache & start MT services (Admin and Managed Servers)

Patch rollback:

If any issues after applying the patch and if rollback is needed,

- Stop MT services

- cd PATCH_DIR/21617568

$ opatch rollback -id 21617568


- Clear browser cache & start MT services (Admin and Managed Servers)

Related Posts:

Applying Patch 22060958: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.15

Applying Patch 22449847: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.9.160119

Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

FMW 11.1.1.9.0 - Applying Patch 22511786: WebCenter Portal Bundle Patch 11.1.1.9.160119(ID:160107.0701)

FMW 11.1.1.9.0 - Applying Patch 22511786: WebCenter Portal Bundle Patch 11.1.1.9.160119(ID:160107.0701)

- Download Patch 22511786 (p22511786_111190_Generic.zip)

Applying Patch 22511786

- Apply this bundle patch on both ORACLE_HOMEs:

      * [MW_HOME]/oracle_common  (JRF Home)
      * [MW_HOME]/Oracle_WCP1    (Webcenter Portal Home)

- Stop all servers (Admin Server and all Managed Servers

- Unzip the patch

$ unzip -d PATCH_TOP p22511786_111190_Generic.zip

- $ cd PATCH_TOP/22511786

- Run opatch apply on both ORACLE_HOMEs (JRF Home and WCP Home)

$ opatch apply

- Start all servers (Admin Server and all Managed Servers)

Post-Patch Instructions

- Update the WebCenter Portal Extension Bundle for JDeveloper

The extensions named "WebCenter Portal - Framework" and "WebCenter Portal Task Flow Customization Framework" should have a version 11.1.1.9.0.160107.0701

- Fix for Bug 20132344 and Bug 20132372

i) Stop Spaces managed server

ii) Clean old classfiles of scripts and scripthandlers.

rm -f $ORACLE_HOME/common/wlst/*.class
rm -f $ORACLE_HOME/common/script_handlers/*.class

touch $ORACLE_HOME/common/wlst/11.1.1.9.0

iii) Start Spaces managed server

iv) To rename users, use command synchronizeUserInformation and operationType - RENAME_USERS_FROM_MAPPING_FILE.

Patch De-Installation

- Stop all servers (Admin Server and all Managed Servers

- $ cd PATCH_TOP/22511786

- Run opatch rollback from both ORACLE_HOMEs (WCP_Home and oracle_common Home)

$ opatch rollback -id 22511786

- Remove WebCenter Portal Extension Bundle for JDeveloper updated after patching

- For Bug 20132344 and Bug 20132372

i) Stop Spaces managed server if running

ii) Clean old classfiles of scripts and scripthandlers.

rm -f $ORACLE_HOME/common/wlst/*.class
rm -f $ORACLE_HOME/common/script_handlers/*.class

touch $ORACLE_HOME/common/wlst/11.1.1.9.0

iii) Start Spaces managed server

- Start all servers (Admin Server and all Managed Servers)

Related Posts:

FMW 11.1.1.9.0 - Applying Patch 22449847: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.9.160119

FMW 11.1.1.8.0 - Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

FMW 11.1.1.9.0 - Applying Patch 22449847: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.9.160119

FMW 11.1.1.9.0 - Applying Patch 22449847: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.9.160119

- Download Patch 22449847 (p22449847_111190_Generic.zip)

Applying Patch 22449847

- Set ORACLE_HOME to WebCenter Content Home, $MW_HOME/Oracle_WCC1

- Stop all servers (Admin Server and all Managed Servers)

- Unzip the patch

$ unzip -d PATCH_TOP p22449847_111190_Generic.zip
   
- $ cd PATCH_TOP/22449847

- Run opatch apply

$ opatch apply

- Start all servers (Admin Server and all Managed Servers)
       
Patch De-Installation

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

- Stop all servers (Admin Server and all Managed Servers)

- $ cd PATCH_TOP/22449847

- Run opatch rollback

$ opatch rollback -id 22449847

- Start all servers (Admin Server and all Managed Servers)

Related Posts:

Applying Patch 22060958: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.15

FMW 11.1.1.8.0 Applying Patch 21617568: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.14

FMW 11.1.1.9.0 - Applying Patch 22511786: WebCenter Portal Bundle Patch 11.1.1.9.160119(ID:160107.0701)

FMW 11.1.1.8.0 - Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

FMW 11.1.1.7.0 - Applying Oracle WebCenter Portal Patch 18334433: COMPOSER COMPONENT PROPERTIES DIALOG FAILS TO SAVE METHOD-VALUED ELS

FMW 11.1.1.7.0 - Applying Oracle WebCenter Portal Patch 18334433: COMPOSER COMPONENT PROPERTIES DIALOG FAILS TO SAVE METHOD-VALUED ELS

- Download Patch 18334433 ( p18334433_111170_Generic.zip )

- Please note this patch is applicable to two ORACLE_HOMEs:

       -> $MW_HOME/oracle_common (JRF Home)
       -> $MW_HOME/Oracle_WC1 (Webcenter Home)
   

Applying Patch 18334433

- Stop all servers (Admin Server and all Managed Servers)

- Unzip the patch zip file

$ unzip -d PATCH_TOP p18334433_111170_Generic.zip

- $ cd PATCH_TOP/18334433/oui

- Run opatch apply on JRF Home and WebCenter Home

i) Set ORACLE_HOME environment variable to $MW_HOME/oracle_common

$ opatch apply

ii)Set ORACLE_HOME environment variable to $MW_HOME/oracle_WC1

$ opatch apply

- Verify the patch

$ opatch lsinventory (on both JRF Home and WebCenter Home)

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

Patch De-Installation

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

$ cd PATCH_TOP/18334433/oui

3. Run OPatch rollback (on both JRF Home and WebCenter Home)

- Stop all servers (Admin Server and all Managed Servers)

i) Set ORACLE_HOME environment variable to $MW_HOME/oracle_common

- opatch rollback -id 18334433

ii) Set ORACLE_HOME environment variable to $MW_HOME/oracle_WC1

- opatch rollback -id 18334433        

- Restart all servers (Admin Server and all Managed Servers


Related Posts:

FMW 11.1.1.7.0 MDS Patch 17693339 removed after applying ADF Patch for WebCenter Portal - Patch 21880254: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 20224749 21789440

WebCenter Content 11.1.1.8.9 Stuck Threads Issue - Applying Patch 20319643: STUCK THREADS DUE TO UNSAFE RIDC CODE - HASHMAP

FMW 11.1.1.8.0 - Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

FMW 11.1.1.7.0 MDS Patch 17693339 removed after applying ADF Patch for WebCenter Portal - Patch 21880254: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 20224749 21789440

FMW 11.1.1.7.0 MDS Patch 17693339 removed after applying ADF Patch for WebCenter Portal - Patch 21880254: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 20224749 21789440

- Download patch 21880254 (p21880254_111170_Generic.zip)

Pre-Patch Conflict Checks

cd $MW_HOME/patches/21880254/oui

export ORACLE_HOME=$MW_HOME/product/111/oracle_common/

$ opatch apply -report

OPatch detects the Middleware Home as "$MW_HOME/product/111"


Applying interim patch '21880254' to OH '$MW_HOME/product/111/oracle_common'

Verifying environment and performing prerequisite checks...

Interim patch 21880254 is a superset of the patch(es) [  19832590 ] in the Oracle Home


Patch(es) [  19832590 ] are subset patch(es) of the Patch currently being installed [ 21880254 ].

Patch(es) [  17693339 ] conflict with the Patch currently being installed [ 21880254 ].


To resolve patch conflicts, please contact Oracle Support Services.

If you continue, all conflicting patch(es) will be rolled back and the new Patch [ 21880254 ] will 
be installed.

Do you want to proceed? [y|n]
Y
User Responded with: Y

OPatch will roll back the subset patches and apply the given patch
All checks passed.


Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '$MW_HOME/product/111/oracle_common')



Is the local system ready for patching? [y|n]
Y
User Responded with: Y
Backing up files...


[Report] The following patches will be rolled back:  19832590 17693339


Skip patching component oracle.jrf.adfrt, 11.1.1.7.0 and its actions.

The actions are reported here, but are not performed.

ApplySession skipping inventory update.


Verifying the update...
Inventory and System verification is performed here.

Patch 21880254 successfully applied

OPatch succeeded.


Applying Patch 21880254

- Shutdown MT services

- Set Environment variables

export ORACLE_HOME=$MW_HOME/product/111/oracle_common/


export PATH=$PATH:$MW_HOME/product/111/oracle_common/OPatch/

- Apply patch on the MT nodes

cd $MW_HOME/patches/21880254/oui
opatch apply

- Verify Patch

opatch lsinventory | grep 21880254

- Start MT services

Related Posts:

FMW 11.1.1.7.0 - Patch 21880254 removed after applying Patch 22048340: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 17693339 21880254

FMW 11.1.1.7.0 (Dynamic Monitoring Service) - Applying Patch 18748961: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 16541855 18232869

FMW 11.1.1.8.0 - Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

WebCenter Content 11.1.1.8.9 Stuck Threads Issue - Applying Patch 20319643: STUCK THREADS DUE TO UNSAFE RIDC CODE - HASHMAP

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

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

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

If you are trying to execute reassociateSecurityStore command on one of the cluster nodes of WebCenter Capture 11.1.1.8.0 to resolve the issue detailed in this post, you may run into errors as below.

JPS-00027: There was an internal error: java.sql.BatchUpdateException: ORA-00904: "ATTRKIND": invalid identifier

wls:/your_domain/serverConfig> reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false")


Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)

Command FAILED, Reason: JPS-00027: There was an internal error: java.sql.BatchUpdateException: ORA-00904: "ATTRKIND": invalid identifier


Traceback (innermost last):
 File "<console>", line 1, in ?
 File "MW_HOME\fmw\product\111\ORACLE~1\common\wlst\jpsWlstCmd.py", line 1343, in reassociateSecurityStore
 File "MW_HOME\fmw\product\111\ORACLE~1\common\wlst\jpsWlstCmd.py", line 1314, in reassociateSecurityStoreImpl

       at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
       at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
       at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source)
       at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:960)
       at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
       at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
       at weblogic.security.Security.runAs(Security.java:61)
       at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:958)
       at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1029)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:606)


javax.management.MBeanException: javax.management.MBeanException: JPS-00027: There was an internal error: java.sql.BatchUpdateException: ORA-00904: "ATTRKIND": invalid identifier



You may hit these errors because OPSS schema may not have been upgraded and hence is not at version 11.1.1.8.0.

Verify OPSS schema version by running below SELECT query.

SQL> SELECT OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY;

If OPSS schema version is not 11.1.1.8.0 (let's say eg: OPSS version is 11.1.1.7.0 with U flat set to N), then run ./psa and upgrade OPSS schema to 11.1.1.8.0

Once OPSS is upgraded to 11.1.1.8.0, run reassociateSecurityStore again.

reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false") 

This time it should execute without errors as below:

Re-associate to OPSS Security Store

cd ORACLE_COMMON_HOME\common\bin
./wlst.sh
connect("Admin_User","Admin_User_Password","t3://hostname:port")

wls:/your_domain/serverConfig> reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false")
Already in Domain Runtime Tree

Starting policy store reassociation.
The store and ServiceConfigurator setup done.
Schema is seeded into the store
Data is migrated to the store. Check logs for any failures or warnings during migration.
Data in the store after migration has been tested to be available
Update of in-memory jps configuration is done
Policy store reassociation done.
Starting credential store reassociation
The store and ServiceConfigurator setup done.
Schema is seeded into the store
Data is migrated to the store. Check logs for any failures or warnings during migration.
Data in the store after migration has been tested to be available
Update of in-memory jps configuration is done
Credential store reassociation done
Starting Keystore reassociation
The store and ServiceConfigurator setup done.
Schema is seeded into the store
Data is migrated to the store. Check logs for any failures or warnings during migration.
Data in the store after migration has been tested to be available
Update of in-memory jps configuration is done
Keystore reassociation done
Starting audit store reassociation
The store and ServiceConfigurator setup done.
Schema is seeded into the store
Data is migrated to the store. Check logs for any failures or warnings during migration.
Data in the store after migration has been tested to be available
Update of in-memory jps configuration is done
Audit store reassociation done
Jps Configuration has been changed. Please restart the application server.

wls:/your_domain/serverConfig>

Related Posts:

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 - 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 Cluster - Creating OPSS schema for using Database Based Security Store

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

When using Database Based Security Store, follow steps below for OPSS schema creation.

- Download 11.1.1.8 RCU Patch 17068284
- Invoke RCU from /SID/fmw/product/111/oracle_common/bin ) and create OPSS schema

OPSS schema creation

i) Select Create

ii) DB connection Details:
- Host:
- Port:
- Service type:
- Username: system
- PASS: system_password
- Role: SYSDBA.

iii) On Select Components:


- Select "Select an existing Prefix" and verify SID is selected.
- Components:
Open "As Common Schemas" and select "Oracle Platform Security Services"


iv) On Schema Password, select "Use same passwords for all schemas" and enter password of "SID_MDS" schema

v)  Proceed further till OPSS schema gets created.

Related Posts:

WebCenter Capture 11.1.1.8 Cluster - Using Database Based Security Store

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 - Using OID Based Policy 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

WebCenter Capture 11.1.1.8 Cluster - Using Database Based Security Store

WebCenter Capture 11.1.1.8 Cluster - Using Database Based Security Store


If facing an issue in WebCenter Capture 11.1.1.8 cluster with workspace imported / created on one node not being available on the other node of cluster as detailed in this post, one of the ways to resolve the issue is using Database Based Security Store.

Using Database Based Security Store

1) Create OPSS schema

2) Create Data Source

- Create a non-XA data source with support for global transactions disabled / unchecked (Configuration -> Transactions) in WebLogic console (JNDI name should be of format "jdbc/opss-ds" or "jdbc/cap-opss-ds") 

- Target this data source to the cluster & admin server. If other managed servers are to use the data source, the OPSS source must also target those managed servers / clusters.

- Restart MT services

3) Re-associate to OPSS Security Store

cd ORACLE_COMMON_HOME\common\bin
./wlst.sh
connect("Admin_User","Admin_User_Password","t3://hostname:port")

reassociateSecurityStore(domain="your_domain", servertype="DB_ORACLE",datasourcename="jdbc/opss-ds", jpsroot="cn=jpsTestNode", join="false") 

4) Restart the complete domain.

Now from the other cluster node (say Node 2) try accessing workspace that was created / imported on one of the WebCenter Capturecluster nodes (say Node 1). Workspace should now be visible from both the cluster nodes.

Related Posts:

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

WebCenter Capture 11.1.1.8 Cluster - Using OID Based Policy Store

WebCenter Capture 11.1.1.8 Cluster - Using OID Based Policy Store

If facing an issue in WebCenter Capture 11.1.1.8 cluster with workspace imported / created on one node not being available on the other node of cluster as detailed in this post, one of the ways to resolve the issue is using an OID Based Policy Store.


- On MT Host 1, invoke WLST

cd ORACLE_COMMON_HOME/common/bin
./wlst.sh

- Run connect() as below

connect("Admin_User","Admin_User_Password","t3://hostname:port")

- Execute   reassociateSecurityStore command as below using correct domain name and LDAP details 

reassociateSecurityStore(domain="your_domain",admin="cn=orcladmin",password="orclPassword",ldapurl="ldap://LDAP_HOST:LDAP_PORT",servertype="OID",jpsroot="cn=jpsroot_ecm")


- Restart the complete domain once reassociateSecurityStore is executed without any errors.

- Now from the other cluster node (say Node 2) try accessing workspace that was created / imported on one of the WebCenter Capturecluster nodes (say Node 1). Workspace should now be visible from both the cluster nodes.

Related Posts:

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 - Using Database Based Security 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

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

FMW 11.1.1.8.0 - Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

FMW 11.1.1.8.0 - Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

1. Download the patch 20022599 to staging area PATCH_TOP and unzip it

$ unzip -d PATCH_TOP p20022599_111180_Generic.zip
   

2. Set environment variables and stop MT services

a. Set ORACLE_HOME - eg: $MW_HOME/wcc_111
   
b. Stop MT services (Admin Server and all Managed Server(s)).

c. Depending on whether you use EBS or PSFT, modify the AppAdapterEBS.hda file under $Oracle_Home/ucm/idc/components/AppAdapterEBS 
   OR AppAdapterPSFT.hda under $Oracle_Home/ucm/idc/components/AppAdapterPSFT to change the "build=1" value to "build=2" (or any higher value).  


3. Apply the patch

$ cd PATCH_TOP/20022599

$ opatch apply
       

4. Post-Patching Steps

- Clear browser cache

- Start MT services

5. For instructions on the setup and configuration of the Content UI, pls review below document links

- Chapter 12 Configuring Content Server with the WebCenter Content User Interface

- Review the exact details of the following Document out on the Oracle Support Portal:
How to Install and Configure the Webcenter Content 11.1.1.8.0 Content UI (Doc ID 1617477.1)


6. Patch Rollback

If any issues post patching and roll back is required,

- Stop services

- Rollback the patch

$ opatch rollback -id 20022599
                          
- Clear browser cache


- Start all services

Related Posts:

FMW 11.1.1.9.0 - Applying Patch 22449847: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.9.160119

Applying Patch 22060958: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.15

FMW 11.1.1.8.0 Applying Patch 21617568: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.14

FMW 11.1.1.7.0 MDS Patch 17693339 removed after applying ADF Patch for WebCenter Portal - Patch 21880254: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 20224749 21789440

WebCenter Content 11.1.1.8.9 Stuck Threads Issue - Applying Patch 20319643: STUCK THREADS DUE TO UNSAFE RIDC CODE - HASHMAP

FMW 11.1.1.7.0 - Applying Oracle WebCenter Portal Patch 18334433: COMPOSER COMPONENT PROPERTIES DIALOG FAILS TO SAVE METHOD-VALUED ELS

WebCenter Content 11.1.1.8.9 Stuck Threads Issue - Applying Patch 20319643: STUCK THREADS DUE TO UNSAFE RIDC CODE - HASHMAP

WebCenter Content 11.1.1.8.9 Stuck Threads Issue - Applying Patch 20319643: STUCK THREADS DUE TO UNSAFE RIDC CODE - HASHMAP

In WebCenter Content 11.1.1.8.x instance, if Admin or Managed Servers are showing stuck threads and if errors as below are seen, restarting the server may not always be a good workaround if the stuck threads are encountered frequently especially in Pre-Production and Production environments.

You should consider applying Patch 20319643: STUCK THREADS DUE TO UNSAFE RIDC CODE - HASHMAP

Stuck Thread Errors
.
.
.

which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.util.AbstractCollection.toArray(AbstractCollection.java:195)
java.lang.String.split(String.java:2311)
java.lang.String.split(String.java:2355)
oracle.stellent.ridc.convenience.usersecurity.impl.AclListInfo.getRoleList(AclListInfo.java:125)
oracle.stellent.ridc.convenience.usersecurity.impl.AclListInfo.getRoleListAccess(AclListInfo.java:88)
oracle.stellent.ridc.convenience.usersecurity.impl.AccessResolverAcl.resolveAccessLevel(AccessResolverAcl.java:137)
oracle.stellent.ridc.convenience.usersecurity.impl.UserSecurityGroupsCache.getAccessLevelForDocument(UserSecurityGroupsCache.java:325)
oracle.webcenter.content.integration.spi.ucm.UCMBridge.getAccessLevel(UCMBridge.java:882)
oracle.webcenter.content.integration.spi.ucm.UCMBridge.getAccessLevel(UCMBridge.java:865)
oracle.webcenter.content.integration.spi.ucm.UCMBridge.getUCMAccessLevel(UCMBridge.java:2728)
oracle.webcenter.content.integration.spi.ucm.UCMBridge.checkSecurityLevelForNode(UCMBridge.java:2691)
oracle.webcenter.content.integration.spi.ucm.UCMBridge.canAccessNode(UCMBridge.java:2648)
oracle.webcenter.content.integration.spi.ucm.NodeOps.getNodeFromCache(NodeOps.java:741)
oracle.webcenter.content.integration.spi.ucm.NodeOps.getUCMNodeWithId(NodeOps.java:1521)
oracle.webcenter.content.integration.spi.ucm.UCMWebLink.findUrlProperty(UCMWebLink.java:88)
oracle.webcenter.content.integration.spi.ucm.HtmlLinkRewriter.getLinkText(HtmlLinkRewriter.java:300)
oracle.webcenter.content.integration.spi.ucm.HtmlLinkRewriter.rewriteWcmResourceUrl(HtmlLinkRewriter.java:277)
oracle.webcenter.content.integration.spi.ucm.HtmlLinkRewriter.rewriteWcmUrl(HtmlLinkRewriter.java:464)
oracle.webcenter.content.integration.spi.ucm.HtmlLinkRewriter.rewriteLinks(HtmlLinkRewriter.java:218)


Pre-requisite Patch 

20022599

WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

- Download and copy the patch p20319643_111189_Generic.zip (password protected) to the staging area

- Stop MT services

- Take backup of jar file /sid/fmw/product/111/wcc_111/ucm/Distribution/RIDC/oracle.ucm.ridc-11.1.1.jar

- Apply the patch

cd /sid/fmw/patches/20319643
export ORACLE_HOME=/sid/fmw/product/111/wcc_111

$ORACLE_HOME/OPatch/opatch apply

bash-3.2$ $ORACLE_HOME/OPatch/opatch apply
Oracle Interim Patch Installer version 11.1.0.9.9


Oracle Home       : /sid/fmw/product/111/wcc_111
Central Inventory : /sid/fmw/oraInventory

   from           : /sid/fmw/product/111/wcc_111/oraInst.loc
OPatch version    : 11.1.0.9.9

OUI version       : 11.1.0.9.0

Log file location : 
/sid/fmw/product/111/wcc_111/cfgtoollogs/opatch/20319643_date-time/apply2015_date-time.log


OPatch detects the Middleware Home as "/sid/fmw/product/111"


Applying interim patch '20319643' to OH '/sid/fmw/product/111/wcc_111'

Verifying environment and performing prerequisite checks...
All checks passed.


Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/sid/fmw/product/111/wcc_111')


Is the local system ready for patching? [y|n]

y
User Responded with: Y
Backing up files...


Patching component oracle.contentserver11.ridc, 11.1.1.8.0...


Patching component oracle.contentserver11.dist, 11.1.1.8.0...

Verifying the update...

Patch 20319643 successfully applied

Log file location: 
/sid/fmw/product/111/wcc_111/cfgtoollogs/opatch/20319643_date-time/apply_date-time.log

OPatch succeeded.

- Verify the patch applied

$ORACLE_HOME/OPatch/opatch lsinventory |grep 20319643


- Start MT services 

Related Posts:

FMW 11.1.1.8.0 - Applying Patch 20022599: WEBCENTER CONTENT BUNDLE PATCH 11.1.1.8.9

FMW 11.1.1.7.0 - Applying Patch 16810628: BOTTLENECK IN WEBLOGIC EXHAUSTING WEBLOGIC THREADS

WLS 10.3.6 - Applying Patch 14463779: SU Patch [UJIZ]: STRESS:REGRESSION; STUCK THREADS AND FAILURES DURING STOCK TRADER CONV WEB-SVCS

FMW 11.1.1.7.0 MDS Patch 17693339 removed after applying ADF Patch for WebCenter Portal - Patch 21880254: MERGE REQUEST ON TOP OF 11.1.1.7.0 FOR BUGS 20224749 21789440

FMW 11.1.1.7.0 - Applying Oracle WebCenter Portal Patch 18334433: COMPOSER COMPONENT PROPERTIES DIALOG FAILS TO SAVE METHOD-VALUED ELS