After Upgrading the ADF Libraries the OC4J Instance Startup Fails with the Error: "The plugin OC4J did not have any documents associated with the Document Key" (Doc ID 471838.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version 10.1.2.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Feb-2013***


Symptoms

After upgrading the ADF runtime libraries by using the ADF runtime installer 10.1.3.3.0 the OC4J
home container no longer starts up. The error reported by opmn is:

Error displaying Log Files page. Entity not found.
Resolution:
Entity not found
Base Exception:
The plugin OC4J did not have any documents associated with the Document Key OC4J_INSTANCE_ID:home;
Resolution:
Contact Oracle Support. Exception thrown by plugin "orionp":
The plugin OC4J did not have any documents associated with the Document Key OC4J_INSTANCE_ID:home;
Resolution:
Contact Oracle Support


The installation of the ADF libraries was aborted a few times due to errors before it finally succeeded.

Also the dcm logfile "dcm-daemon~dcm-daemon~dcm~1.log" shows following errors:

...
file:/u01/app/oracle/product/midj2ee/j2ee/home/config/server.xml<Line 3, Column 1>: XML-20108: (Fatal Error) Start of root element expected
...
07/12/21 09:09:14 Error initializing web-site at ./default-web-site.xml: Fatal error at line 3 offset 1 in file:/u01/app/oracle/product/midj2ee/j2ee/home/config/default-web-site.xml:
.<Line 3, Column 1>: XML-20108: (Fatal Error) Start of root element expected.
...


Furthermore the files "server.xml" and/or "default-web-site.xml" are empty or do not contain the contents it should have.

Changes

Updating/Installing ADF runtime libraries.

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