Oracle DataSource Driver

[Hun]

Hi,

I am running Wesphere Advance Single Server Edition 4.0. I am trying to connect to my database using datasource. My datasource returns a null value.

I tried using classes12.zip in my application /lib directory, but still receiving errors. I also put the classes12.zip outside into the application server directory, and it is still incorrect. I have my datasource point to both directory.

Do I need to install the Oracle 8i client to communicate with my remote Oracle Database.

Please help!

 

[fearo]

Do I need to install the Oracle 8i client to communicate with my remote Oracle Database?

Yes

Refer to page 365 of the WebSphere v4.0 Handbook.

Regards,

Eddie

 

[Hun]

Thank you for your assistance.

The reason for the null pointer exception was that we had several jars that conflicted with the class loaders and the application server's classes.

the classes12.zip contains all the java classes that is needed to communicate with the database even without the Oracle 8 client. You need the client only when you are running a thick or oci drivers.

Hope this helps others who ran into the same situation as we did.

 

[Imharil]

Hello,

I have the same problem when I try to run Wesphere Advance Single Server Edition 4.0 and to connect it to my database using datasource; my datasource returns a null value.
I also have the classes12.zip, but I don`t know jars that conflicted with the class loaders and the application server's classes.

I waiting for your help because I am in a very complicated situation. Thanks

 

[Hun]

To resolve this issue, I have to put my classes12.zip in my WebSphere/AppServer/classes directory.

Remember to make sure your server is set to application visibility.

Hope this help.

 

[thietkn]

/lib only to put .jar file not for .zip file. So you havo to set classes12.zip in your JVM classpath

 

[jobmiller]

If anyone could post the steps needed to get oci drivers to work in websphere, I would be very appreciative.

I have been trying for 5 days to get it to work.

it works for oc4j deployment, but i am not familiar enough with websphere admin to get all the paths set right everywhere for a driver.

currently it tells me "Thin is only supported protocol"

so it is finding the driver, just not the client libraries I assume on NT.

Job