File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes JDBC and Relational Databases and the fly likes thin? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "thin?" Watch "thin?" New topic


kedar parundekar
Ranch Hand

Joined: May 10, 2006
Posts: 40
In case of type4 driver , I require following URL

Connection con = DriverManager.getConnection("jdbcracle:thin:@dbs:1521rcl","scott","tiger");

Q.> What is thin?
Scott Selikoff
Saloon Keeper

Joined: Oct 23, 2005
Posts: 3753

The opposite of a fat driver!

But seriously... Oracle provides two versions of its driver: thin and OCI (thick). Thin is based purely in java and is generally very stable whereas OCI is written in more Oracle native code and is considered more powerful.

I've found most people use thin drivers although there are some excellent reasons for using OCI. Here's a short post listing some reasons:

[OCA 8 Book] [Blog]
stu derby
Ranch Hand

Joined: Dec 15, 2005
Posts: 333
What Scott said...

The "thin" driver merely requires the right jar file(s), usually just one, while the "thick" driver requires an Oracle Client installation, which includes some native code components (DLLs or shared libraries) and the environmental settings to find them.

In other words, the "thin" driver will run any place Java runs, but the "thick" driver is available only for a handful of operating systems (most of the major ones).
I agree. Here's the link:
subject: thin?
It's not a secret anymore!