Autoconfig Failed with Error: FsCtxFileException: Start of Root Element Expected

Error :

ERROR: FsCtxFile.XMLParseException

oracle.xml.parser.v2.XMLParseException: Start of root element expected.

at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)

at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:306)

at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)

( or )

ERROR: FsCtxFile.XMLParseException

oracle.xml.parser.v2.XMLParseException: Unexpected EOF

…….....

Or

Caused by: oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsDiscoveryException

Solution :

To implement the solution, please execute the following steps:

1. Backup the fnd_oam_context_files table in the EBS env:

sqlplus applsys/pwd

SQL> create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files;

2. Truncate this table:

SQL> truncate table fnd_oam_context_files;

3. Run autoconfig in the DB tiers to populate fnd_oam_context_files table with the database information;

4. Run autoconfig in each Apps tier to populate fnd_oam_context_files with the application tier information;

5. From the EBS agent home, run:

./emctl upload

This will upload the information from the EBS system to Grid Control.

Note:

By running the following sql query, it will help you identify if there are duplicate node_name entries in the FND_OAM_CONTEXT_FILES table.

  If duplicates are listed, the older entry should be removed only leaving the most current entry.

SQL> select * from FND_OAM_CONTEXT_FILES where status in ('S','F') and name not in

('METADATA','TEMPLATE') and ctx_type='A';

++++++++++++Manjunatha+++++++++++++