Home > ERP, Support, Technology, Work Life > Fixed: Oracle iSetup XML Uploading Error

Fixed: Oracle iSetup XML Uploading Error

For the past month at work we have been experimenting with Oracle iSetup as a way to migrate Oracle R12 configurations from instance to instance.  We had been using Rapid Solutions (Rapid e-Suite) in Oracle 11i in the past, but wanted to try something quicker, more robust, and seeded with Oracle.

The iSetup module worked pretty well in our proof of concept testing.  But we ran into a problem when we started migrating our multi organization/business unit configurations. We have multiple business units because we are sharing the instance with another division at our company. Migrating configurations with iSetup brings all the ORGs and sites along with each configuration, however we only wanted our division’s configurations migrated.  To solve the problem, we started editing the exported XML before loading it into the new instance.

Editing XML is relatively time consuming and prone to error when editing in a text editor compared to a program designed to edit XML.  We tried to use the free Microsoft XML Notepad 2007, however, loading the exported files was causing iSetup to fail on upload.  I found the problem and solved it as described below.


  • Oracle iSetup module in Oracle E-Business suite R12
  • XML Documents edited by Microsoft XML Notepad 2007


  • iSetup reports error when uploading edited XML files
  • Log file as seen here:
oracle.xml.parser.v2.XMLParseException: Start of root element expected.
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:341)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:205)
at oracle.apps.az.r12.api.BC4JAPI.createAPIEntityItems(BC4JAPI.java:330)
at oracle.apps.az.r12.extractor.cpserver.UploaderContextImpl.validateExtract(UploaderContextImpl.java:170)
at oracle.apps.az.r12.extractor.cpserver.UploaderContextImpl.upload(UploaderContextImpl.java:105)
at oracle.apps.az.r12.extractor.cpserver.UploaderCp.runProgram(UploaderCp.java:74)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)


  • Oracle XML files are saved in ASNI text encoding even though the XML header specifies UTF-8
  • Oracle iSetup expects ASNI encoded XML files contained within uploaded ZIP file
  • Microsoft XML Notepad 2007 saves XML files in UTF-8 encoding


  1. Download extraction ZIP file generated by Oracle iSetup
  2. Extract ZIP file to your computer
  3. Edit and save extracted XML file in Microsoft XML Notepad
  4. Open saved file in Notepad (Text Editor)
  5. Save As ASNI encoding
  6. Replace existing file within original ZIP file
    1. ZIP file compression levels and algorithms must reamin intact
    2. 7-ZIP supports replacing files within an existing file using drag and drop functionality
  7. Upload updated ZIP file to Oracle iSetup as a new extraction.
  8. Load extraction into source instance


It may seem like this is backwards, but from few hours of troubleshooting, this is what I concluded, and this is working for us. I may open a TAR with Oracle to get this bug fixed.  Before it is, however, this is how we are proceeding with our iSetup configurations.
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: