This one time, at band camp, David Duarte said: DD >Hi, DD > DD >Why don't you use thin driver? It doesn't depends on os (it's full java and DD >doesn't use native methods !). DD >You can download it for free in oracle web site. DD >I hope this tip will help you. DD >
If Venkatesh wants to do any streaming of BLOBS/CLOBS, he must use the OCI driver. However, all other operations (AFAIK) can be accomplished using the thin driver. DD > DD >When i tried to connect to the database using oci driver, DD > DD >i am using the following, DD > DD >driver---------------------jdbc817jdk12-nt,classes12.zip&ocijdbc8.dll DD >java-----------------------jdk1.3 DD >oracle server-----------8.1.7 DD >oracle client------------8.1.7 DD > DD >anybody who has come across this,please let me know the process of jdbc DD >connectivity using oci driver,or send me the details of how to debug this. DD > First of all, see http://castor.exolab.org/database-conf.html, specifically: 'The means to acquire a database connection is specified in one of three ways: as a JDBC 2.0 driver URL, as a JDBC 2.0 DataSource, or as a DataSource to lookup through JNDI.' and the example database.xml for the Oracle thin driver. If your database.xml actually contains 'jdbc817jdk12-nt,classes12.zip&ocijdbc8.dll' I believe that this is your problem. Post your database.xml and your actual CLASSPATH for further analysis. The exception looks to me like it's not even making a connection to the database. -- perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");' ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
