ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Surette <>
Subject Re: Oracle OCI JDBC usage
Date Wed, 31 Oct 2001 18:49:27 GMT
I use sql tasks with the oci driver.

As for your first problem, I experienced it as well.
My workaround is to only include one <sql> task per
target, then create multiple targets with dependencies
between them. 

I don't understand your second problem. Everyone in 
my group has the OCI dlls in their $PATH and it
works. I don't think we have $LD_LIBRARY_PATH set
but I'm not at work right now so I can't verify this.
But I don't think you'll be able to set these effectively
within the ant build file since the VM is already
started up. If you really want to to be able to set
these in the ant script, I think you'll need to use
the 'java' task to restart ant with the necessary env
variables set.

One nice addition to the Sql task (and the Ant task)
would be to add a 'fork' attribute. 

Alban Peignier wrote:
> Hi,
> We are trying to use the sqlexec Ant task with the Oracle OCI JDBC
> Driver. We have two problems :
> - two consecutive sqlexec calls are executed into two separate
> ClassLoaders. The OCI JDBC Driver is loaded twice ... and the native
> library too :( Resulting in a exception at the second call since the
> native library can't be reloaded .
> - We can set the java.library.path into a Ant build file and thus we
> have to set it the LD_LIBRARY_PATH before executing Ant ...
> Did anybody resolve these problems ? (without using the Thin JDBC Driver :)
> Banban & FX
> --
> To unsubscribe, e-mail:   <>
> For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message