Driver not found - JDBC - HELP PLZ!

Question

Hello everyone.
i am trying to access my database and this is the code i made:
public static void connectToDataBase()
Connection connect = null;
try{
String driverName = "oracle.jdbc.driver.OracleDriver";
String serverName = "192.168.5.6";
String portNumber = "1521";
String sid = "deve";
String url = "jdbc:oracle:thin:@" + serverName + ":" + portNumber +
":" + sid;
String usr = "emma";
String pwd = "emma";
//Load the JDBC driver
Class.forName(driverName);
//Connect to the base
connect = DriverManager.getConnection(url,usr,pwd);
catch(ClassNotFoundException e){
System.out.println("Error---No database driver");
catch(SQLException s){
System.out.println("Error---No connection to the database");
However, when i execute this program, a ClassNotFoundException is launched because i get the message "Error---No database driver".
Can anyone help me please??
thank you

Answer 1

However, when i execute this program, a
ClassNotFoundException is launched because i get the
message "Error---No database driver".As mentioned already, you need to add the driver jar in the classpath. Depending on the type of application you are creating, the method for doing that would vary.
For a simple standalone application, it can be achieved by simply including the JAR name (with path) in the classpath. This can be done by editing the CLASSPATH variable, which I mostly do not prefer, or using the command line switch -cp to set the classpath for the specific command.
If you are dealing with web applications, you need not play around with the environment variables simply because it would not have any effect. Almost all application servers AFAIK ignore the environment settings. The best way of doing it is copying the driver jar to the WEB-INF/lib sub-directory under your webapp directory. (You could ignore this advice ATM if you haven't started with web applications yet). However, the preferred method of connection in case of webapps (or J2EE applications I might generalize) is using a datasource.
Finally, a word of advice which I am often tempted to mention early on. Ensure that you are closing all the connections, statements and resultsets in your application once their job is done. Not doing so may lead to further complications in the future, depending on the driver implementations. The safest way is to call the close methods on all the JDBC resources in the finally block of your code to ensure that you always close the resources.
Gluck!