Novell Identity Manager JDBC Driver Upgrading from 3.0.1 to 3.5.1

Driver will not start after upgrading the IDM engine from 3.0.1 to 3.5.1. Trace shows that some xml file is missing. For example: Driver Descriptor file "_default_jdbc.xml" not found.

When upgrading a JDBC driver from 3.0.1 to 3.5.1 it is often best to redo the driver if possible with the new 3.5.1 JDBC pre-configs. The reason for this is that much of the driver configuration parameters are stored in a JAR file called JDBCConfig.jar. This file contains the XML files that are referenced in the trace error.When you upgrade to 3.5.1 the old JDBCConfig.jar file is moved to a backup location and the new JDBCConfig.jar file is placed in the lib directory. Sometimes, but not always, you can fix the problem by moving the JDBCConfig.jar file to a new location (you cannot just rename it, unless you remove JDBC from the name). The new location must be out of any search path. Then you can copy the old IDM 3.0.1 JDBCConfig.jar file from the backup location to the lib directory. You must then restart the server and then try starting the driver. This can sometimes be a temporary workaround but if you add any new JDBC drivers with the IDM 3.5.1 or later preconfig, the new drivers will often not work.

Also, one other possible cause for a driver not starting is if JDBCConfig is not in the classpath.