OBIEE Not Starting After Applying CPU Patches (Doc ID 2185761.1)

Last updated on FEBRUARY 07, 2017

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.7.160719 and later
Information in this document applies to any platform.

Symptoms

After applying CPU Bundle Patch and JDK, you can not start up OBIEE application fully. OPMN components could not be started . For instance this is the error in startup log:


08/18/16 14:38:05 Warning: <Aug 18, 2016 2:37:35 PM EDT> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
08/18/16 14:38:05 Warning: <Aug 18, 2016 2:37:43 PM EDT> <Error> <oracle.adf.share.config.ADFMDSConfig> <BEA-000000> <MDSConfigurationException encountered in parseADFConfigurationMDS-01330: unable to load MDS configuration document
08/18/16 14:38:05 Warning: <Aug 18, 2016 2:37:44 PM EDT> <Error> <oracle.adf.share.config.ADFMDSConfig> <BEA-000000> <MDSConfigurationException encountered in parseADFConfigurationMDS-01330: unable to load MDS configuration document
08/18/16 14:38:05 Warning: <Aug 18, 2016 2:37:44 PM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "PolicyManagerValidator" failed to preload on startup in Web application: "/wsm-pm".
08/18/16 14:38:05 Warning: <Aug 18, 2016 2:37:44 PM EDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'wsm-pm'.

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