Generally you get the reason 0x3
from error -4499
out of the IBM JDBC driver when you are connecting to a SSL port, but you have not specified sslConnection=true
on your JDBC connection string. You can also get the error if your database name is incorrect (i.e. does not exist on the server), or your JDBC dirver is too old (DB2 JDBC Driver Versions and Downloads Download Fix Packs by version for IBM Data Server Client Packages)
If connecting to Db2 on Cloud, Db2 Warehouse or Db2 Warehouse on Cloud, all you should need is the sslConnection=true
as the CA certificate used in these products is part of the Db2 driver package (for recent drivers anyway)
If connecting to Db2 on premise, you can specify your certificate location via the JDBC properties sslCertLocation
or sslTrustStoreLocation
and sslTrustStorePassword
Common IBM Data Server Driver for JDBC and SQLJ properties for all supported database products
sslCertLocation
Specifies that an application can configure the location of a trusted certificate file. For applications that have the database server certificate, sslCertLocation is the only property that is needed to be configured to instruct IBM Data Server Driver for JDBC and SQLJ to trust the certificate for SSL connections.
This property removes the need to import the certificate into a Java truststore database and related driver configurations.
Error codes issued by the IBM Data Server Driver for JDBC and SQLJ
error codes in the ranges -4200 to -4299, and -4450 to -4499 are reserved for the IBM® Data Server Driver for JDBC and SQLJ.