Unable to Start Second Instance of UCM Cluster when nodes are on Different Patchset Levels (Doc ID 1667518.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle WebCenter Content - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

UCM instance1 is installed on environment A with shared NAS storage, Instance 2 is installed on environment B pointing to the same shared storage.

Instance 1 starts up using cmd, Instance 2 throws the following error and shuts down in cmd.

weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-02592: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: oracle.xml.parser.v2.XMLParseException: Element 'socketOptions' not expected.

Changes

In second instance, noticed WCC and Web Tier versions is different. WCC is 11.1.1.6 and Web Tier is 11.1.1.7. They need to be the same.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms