Skip Headers

# Database Connection Problems

Previous

Next

This section describes common errors and problems you may encounter when communicating with or logging in to the database.

The class [class] was not found.
  Cause: You attempted to log in to the database, but TopLink could not find the JDBC driver for the database.
  Action: Ensure that the `JDBC_CLASSPATH` in the `setenv.cmd` file points to your JDBC driver JAR files. Verify that your PATH includes all files (for example, native `.dll` files) required by the driver. If the path to your JDBC driver JAR files contains spaces, then the path must be enclosed in double-quotes in the `setenv.cmd` file. For example:

      set JDBC_CLASSPATH="C:\Program Files\some directory\driver.jar\"

  For more information, see "Configuring the TopLink Workbench Environment".

Username or password could be invalid.
  Cause: TopLink was unable to log in to the database.
  Action: Ensure that the Username and Password for the database are correct.Verify with your DBA that the database is set up and operating correctly.

You must define a development login.
  Cause: You attempted to log in to the database from TopLink Workbench, but you did not define a development login.
  Action: On the database property sheet, select a Development Login, or create a new Defined Login. See "Configuring Login Information".

No database driver has been specified.
  Cause: You attempted to log in to the database from TopLink Workbench, but you did not complete the login information.
  Action: Complete all the required fields on the database property sheet for the selected development login. See "Configuring Login Information".

Invalid URL specified.
  Cause: You attempted to log in to the database from TopLink Workbench, but the URL is incorrect.
  Action: Complete the URL field on the database property sheet for the selected development login. See "Configuring Login Information".