OIC GEN 3 ISSUES - Fixing NXSD Schema "No Data Found" or "No File to Process" Errors

🧠 Oracle Integration Cloud – Fixing NXSD Schema "No Data Found" or "No File to Process" Errors

📅 Updated: July 26, 2025
🔧 Category: Oracle Integration / File-Based Integrations
✍️ Author: Aks

---

⚠️ Problem Statement

You’ve built a file-based integration in OIC or SOA Suite using the NXSD schema (Native Format Builder). But during testing or runtime, you get errors like:

• “No data found or file is empty”

• “No file to process”

• “NXSD parser error – Data is not present in expected format”

---

🧪 Common Symptoms

• The integration completes with warning or faulted status.

• Logs or activity stream shows:

  JCA-11611: Failed to parse file.
  Reason: Data not present in expected format.
  

• No records are inserted or mapped.

• You receive a blank payload or <null> in the target node.

---

🔍 Root Cause

These issues almost always boil down to mismatch between your NXSD schema definition and the actual data in the file.

💡 NXSD (Native eXternal Schema Definition) is used in OIC/SOA to parse flat files (CSV, TXT, fixed-length, etc.). It acts like an XSD for non-XML data.

---

🛠️ Step-by-Step Fix Guide

✅ 1. Check File Format vs Schema

• Open your file and compare:

  • Delimiter used (comma, pipe, tab)

  • Number of fields per line

  • Presence of header rows

• Match these against the NXSD schema (.xsd with NXSD annotations).

📎 Example: If your NXSD expects 5 fields but the file contains 6, parsing will fail.

---

✅ 2. Validate NXSD Schema in JDeveloper or OIC

• If using JDeveloper:

  • Right-click NXSD file → Run Native Format Tester

  • Load sample data → See if parsing works

• In OIC, download and test file locally or review logs from the Activity Stream.

---

✅ 3. Set Correct Record Delimiter and Field Count

In NXSD definition:

• Check recordSeparator, e.g., \n, \r\n

• Ensure each <element> tag matches a field in the row

• If the file has blank lines or extra separators, parsing may break

<nsxsd:element name="Employee">
  <nsxsd:field name="EmpId"/>
  <nsxsd:field name="Name"/>
  <nsxsd:field name="Salary"/>
</nsxsd:element>

---

✅ 4. Use IgnoreEmptyLines="true" (Optional)

Add this attribute to <nxsd:format> if your file has blank lines:

<nxsd:format name="MyFormat" type="delimited" delimiter="|" ignoreEmptyLines="true" />

---

✅ 5. Watch for Header Rows

If your file contains headers, you must skip them:

<nxsd:format name="Header" skipLines="1" ... />

Alternatively, handle this in OIC using the file adapter configuration (uncheck “First row as header”).

---

✅ 6. Validate File Encoding

• Ensure your file is UTF-8 encoded (especially if created in Excel or external systems)

• Use Notepad++ or VS Code to confirm encoding

---

✅ 7. Use File Test Flow

If you're unsure, create a dummy integration that reads the file and logs its content. This helps isolate whether the error is with:

• File reading

• NXSD parsing

• Mapping logic

---

🔄 Example: Fix for a 3-Column CSV with Pipe Delimiter

✅ Input File

101|John Smith|65000
102|Lisa Wong|72000

❌ Common Mistake in NXSD

Using comma , instead of pipe |:

<nxsd:format delimiter="," />

✅ Corrected NXSD Snippet

<nxsd:format delimiter="|" recordSeparator="\n" />
<nxsd:element name="Employee">
  <nxsd:field name="EmpId"/>
  <nxsd:field name="Name"/>
  <nxsd:field name="Salary"/>
</nxsd:element>

---

📋 Summary Table

Issue	Possible Fix
File is blank	Check if file is being dropped correctly
File delimiter mismatch	Update NXSD with correct `delimiter="
Unexpected number of fields	Match schema elements with actual columns
Blank lines in file	Use ignoreEmptyLines="true"
File includes headers	Use skipLines="1" or handle via File Adapter UI
Encoding issues	Convert file to UTF-8

---

🎯 Conclusion

NXSD schema parsing issues can be frustrating but are often caused by small misconfigurations. By validating your file structure, NXSD definitions, and adapter settings, you can quickly isolate and fix the issue.

✅ Always test your schema with sample data and use logging and tracing to confirm what’s being parsed.