Site Overlay


From the server standpoint there is not difference between the two. Now my questions are: If this is the case, and for example if all database connections were handled through a configuration file with the above OCI connection string, then theoretically the thick driver should work. So, I a use sqlplus to flush the shared pool. Generally the Thin driver is the best choice. Shouldn’t it be closer or the same as the PreparedStatement?

Uploader: Migul
Date Added: 13 May 2017
File Size: 70.11 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 38089
Price: Free* [*Free Regsitration Required]

The reason is mostly performance.

Differences between Oracle JDBC thin and thick drivers

The goal here is have N users doing M iterations concurrently — you know, like you might have doing in the tjick world for example.

Thus, it is only an option on platforms that have native Oracle drivers available and it is not a “pure” Java implementation. Elliott Frisch k 13 89 This driver gives the maximum performance for an Oracle client application.

Post as a guest Name. That prepared statement is looking pretty good now. We are getting an error. So can thicm safely use oci thick driver URL for thin driver “ojdbc.

Regarding Oracle thin and thick drivers (JDBC and Relational Databases forum at Coderanch)

When deploying on a server machine, I prefer to use the OCI drivers. Your input on this is highly appreciated. We had thin driver with 9i and had perfomance problems during high load on system, then we switched to oci – and everything was fine.


Our web application uses Servlets and JSPs we do not use appletswhich are housed in a Tomcat engine. Thank you Dennis, I bring it on-list again.

What is thin driver and thick driver. Why it is called so?

Sep 15, ’04 at 7: The difference lies in how they connect to the database and how they transfer jdgc. We presently use the thin driver to connect to an Oracle8i 8. There aren’t settings to configure on the application side or the server side besides username, password, address, port and name usually in tnsnames. Dev Gym Classes, workouts and quizzes on Oracle Database technologies.

What is thin driver and thick driver. Why it is called so?

It is Oracle platform-specific and requires an Oracle client installation. Showing Answers 1 – 8 of 8 Answers. It will require the installation of the Oracle8 client on the machine with the tomcat engine. I would figure my “Parse” and “Execute” counts to be the same as the PreparedStatement version. The copy here in our group seems to have taken legs, so recalling from memory, I recall that under some circumstances the thin is faster and other times the thick is faster.


In all our OOW presentations we recommend to use the thin driver.

If you think the above answer is not correct, Please select a reason and add your answer below. Oracle’s connection pooling software October 11, – 1: A couple of things to add I can’t seem to find any mention of this in the Oracle docs or on Google.

Which driver should I use? We have to wait for a reply from the Patent Office before getting final approval, so please be patient. What other impact can it have wrt to deployment, performance, maintenance etc. I am using a Oracle “ojdbc I have a regarding which JDBC client side driver to use: But, then we have to query the database each time.

© 2020 All rights reserved