Andreas Korneliussen wrote:
Glenn Marintes wrote:
You should use execute() or executeUpdate(..) when executing "CREATE
TABLE.."
Yes.. I tried using execute() and executeUpdate(..) but I still have
the exception :(
I have 1GB+ free space on the drive where Derby db is being created :(
What are the other reasons for the XSDF1 sql state?
Other reasons may be that the file exists already. If you have the
stack trace for the exception, we could check the source to see
where it was thrown from.
I have checked it. The .dat file that the exception is printing is
not existing in the directory.
Ok. I looked at the source. It seems you can also get this exception
if there is some SecurityException. Do you run with security manager ?
If so, maybe you need to update the policy file.
Andreas
I got it working!!!
It was not working because some other thread interrupted the thread that
called the executeUpdate().
Actually the interrupt occurred even before the executeUpdate() was
called and hence, was very hard
to track.
Anyway, thanks for all the help.
--
*******************************************
*
* Glenn M. Marintes
* Software Development Section
* JANET
*
