Upgrading ECM From 18.104.22.168 To 22.214.171.124 Fails
Last updated on FEBRUARY 20, 2018
Applies to:Oracle WebCenter Content - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11g]
Information in this document applies to any platform.
During upgrade of ECM from 184.108.40.206 to 220.127.116.11 the pre-check fails at the "Test JDBC Component Schema" with following:
CFGFWK-60850: Test Failed!
CFGFWK-60853: A connection was established to the database but no rows were returned from the test SQL statement.
This error is followed by others during the upgrade and restart process on post upgrade as stated below when starting Admin server and/or Managed server(s).
On Admin Server:
<Aug 3, 2015 3:00:52 PM PDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: weblogic.management.ManagementRuntimeException: weblogic.application.ModuleException: Could not create the JMS descriptor>
<Aug 3, 2015 3:00:52 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 3, 2015 3:00:52 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 3, 2015 3:00:52 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
On Managed Server(s):
<Aug 5, 2015 5:01:59 PM PDT> <Warning> <> <BEA-2156203> <A version attribute was not found in element application in the deployment descriptor in [..]/oracle_common/atgpf/modules/oracle.applcore.model_11.1.1/oracle.applcore.model.stub.ear/META-INF/application.xml. A version attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of the Weblogic Server will reject descriptors that do not specify the JEE version.>
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