RE: Post10gR2Migration:Java:ORA-29532

We found the issue.
The issue was that the whitespaces (including carriage return) were preserved. In which case, we get an Exception. Modifying the Java code (XmlConverter and XmlStartup) to explicitly set the preserveWhiteSpace attribute to false (this is accomplished by invoking the setPreserveSpace(false) method on the parser object) solves this problem. Besides, we also replaced the deprecated method putString() on the CLOB object with the recommended setString() method along with commenting the import of the oracle.jdbc.driver.* (oracle.jdbc.* is already imported) and compiling all the java files with Oracle 10g provided classes12.zip.

Govindan

On Thu, 25 May 2006 14:30:34 -0500, "Jesse, Rich" <Rich.Jesse_at_qg.com> said:
> Stuff like this is the main reason why I still prefer manual DB creation
> and export/import for upgrades.
>
> I had a similar issue, although not after a migration. It was fixed by
> unloading and reloading the JVM manually. I believe it requires the
> instance bounced and usually takes quite awhile. See MetaLink for
> details.
>
> Just in time for the long holiday weekend (in the States)...
>
> GL!
>
> Rich
>

--
http://www.freelists.org/webpage/oracle-l