Skip to main content
This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

No suitable driver found for jdbc:sybase

SA-44574

Summary



No suitable driver found for jdbc:sybase error is thrown when Test Database connection is clicked on Database record in Pega configured with jdbc URL.

The driver jar is present in the application server classpath.

Error Messages



No suitable driver found for jdbc:sybase:Tds:<your_host>:<your_port>/your_db

Test Database Connection

SQL Code: 0 | SQL State: 08001

Steps to Reproduce



1. Place the jdbc driver jar in server classpath.
2. Bring up the JVM.
3. Configure Database record in Pega and specify jdbc URL and credentials.
4. Click Test connectivity.

Root Cause



A defect in Pegasystems’ code or rules:

JDBC jars have to be explicitly registered to the Driver Manager before they can be used.

Until some process causes this explicit registration, the driver would not be usable, even if it is on the classpath.

However, if a driver’s class name is added to the database/drivers prconfig value, then the engine will explicitly register the driver during start-up, to ensure that it can be used.

Resolution



Perform the following local-change:

Add the jdbc driver class name to database/drivers in the prconfig.

The database/drivers prconfig can contain multiple entries, and the multiple entries should be semicolon separated.

prconfig.xml example:
<env name="database/drivers" value="com.microsoft.sqlserver.jdbc.SQLServerDriver;oracle.jdbc.OracleDriver" />

screenshot:



Suggest Edit

Published November 3, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us