Ok..So background is ..I was doing upgrade of Hyperion 11.1.2.1 to 11.1.2.3. We have upgraded all the components with some minimal issues. As we are freak of this lazy world. We started all services directly without starting Weblogic.
And, As all the deployment gone fine..We never got any requirement to peep in Weblogic console and check the status of the deployed clusters by simply following "If it ain't broke, don't fix it".
But Then We got requirement to deploy DRM (DATA RELATIONSHIP MANAGEMENT) API, as customer was using this function in 11.1.2.1.
Now to delete the old deployment we need weblogic and delete the old jar file ..As a traditional manner, we tried to start the Weblogic console.
Now the whole issue arises..When we try to start weblogic, it gets failed..We even tried with Nodemanger to start just Admin Console ..But that too didn't work.
The error from the logs is as below...
<Nov 26, 2014 6:51:20 PM CST> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /Oracle/Middleware/user_projects/domains/EPMSystems/config/config.xml - Expected elements 'staging-mode@http://xmlns.oracle.com/weblogic/domain alt-descriptor-path@http://xmlns.oracle.com/weblogic/domain alt-wls-descriptor-path@http://xmlns.oracle.com/weblogic/domain application-identifier@http://xmlns.oracle.com/weblogic/domain application-name@http://xmlns.oracle.com/weblogic/domain' instead of 'cache-in-app-directory@http://xmlns.oracle.com/weblogic/domain' here in element app-deployment@http://xmlns.oracle.com/weblogic/domain>
<Nov 26, 2014 6:51:20 PM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141245]Schema Validation Error in /Oracle/Middleware/user_projects/domains/EPMSystems/config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false>
<Nov 26, 2014 6:51:20 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Nov 26, 2014 6:51:20 PM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Nov 26, 2014 6:51:20 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
We did some goggling and checked various blogs but those didn't help us in my case.Some are here for you to refer(may be they work for you :))
This remember me of quote “The fundamental cause of the trouble is that in the modern world the stupid are cocksure while the intelligent are full of doubt.” ― Bertrand Russell
After digging further as pointed in error..Here is the resolution.
Config File has below tag:
<app-deployment>
<name>oracle-epm-drm-webservices</name>
<target>FoundationServices</target>
<module-type>ear</module-type>
<source-path>/Oracle/Middleware/EPMSystem11R1/products/DataRelationshipManagement/api/oracle-epm-drm-webservices.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<cache-in-app-directory>false</cache-in-app-directory>
</app-deployment>
Remove below tag from the config.xml file. This resolve the issue and to avoid i just removed that deployment App.
<cache-in-app-directory>false</cache-in-app-directory>
I just want to highlight one more point that this issue we faced in 10. 3.6 and a security patch is applied to avoid vulnerable security issues as suggested by oracle.
