you shouldnt ever be directly importing a specific driver. they are runtime bound by the jdbc driver manager. you should be type casting all calls and variables to the primitives and interfaces given in the jdbc api.
they show an example of using the "classForName" but that is a kludge at best. you should be either loading the class name references from a property file and bootstrapping them, or configuring them for the jvm to discover.
also, make sure the driver jar file is on the classpath.
If you are running the code outside the Database, I mean not using the code as Java Stored Procedures or any other way running with the internal OJVM functionality.
You should add the ojdbc5.jar to the running classpath, the class is inside see below: