DocumentBuilder.parse() fails after CLOB is updated

Question

I have written a java application that reads XML content stores in a CLOB column in a 9.2.0.5 database. The application works just fine until the contents of the CLOB is modified, then I get the fatal error shown below.
I am using classes from the javax.xml.parsers.* package to process the XML content. Using an OracleStatement and OracleResultSet I read the CLOB column into a CLOB variable (named clob) using the getCLOB() method. I then create an InputSource using the following statement:
InputSource source = new InputSource(clob.getAsciiStream());
and then create a Document using the following the statements:
builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
outDoc = builder.parse(source);     
The parse method works fine until the CLOB is updated (using TOAD) and then it fails. I have modified the program to print the contents of the CLOB using the methods described in the Oracle JDBC guide; using a while loop, CLOB.read() and StringBuffer. I have noticed that the output before and after the CLOB is updated is definitely different; there is extraneous information following the XML document - I just don't understand why this happens.
[Fatal Error] :23:10: Content is not allowed in trailing section.
org.xml.sax.SAXParseException: Content is not allowed in trailing section.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at com.embMessageProcessor.processMsgList(embMessageProcessor.java:91)
at com.embMessageProcessor.main(embMessageProcessor.java:28)
Press any key to continue...

Answer 1

rangelot,
Could be a bug in the JDBC driver you are using. Sorry, I couldn't find any details, in your post, of which one you are using.
JDBC drivers also need to be compatible with JDK versions. Have you verified that yours is compatible?
JDBC drivers are supposed to be backward compatible, so maybe using the latest Oracle JDBC driver may resolve this problem.
Have you checked the MetaLink Web site? This may be a known issue. If not, then you can always report it as a bug (also on MetaLink).
Good Luck,
Avi.