Applications Systems

Different character sets cause DPA connection errors

When attempting to monitor a database that has a different character set than the DPA server and/or DPA Repository database, you may see an error that looks similar to this: An unknown error has occurred. The provided message is "Could not get JDBC Connection; nested exception is java.sql.SQLException: Could not find a Java charset equivalent to DB charset iso_1."

First published date

11/21/2018 10:41 PM

Last published date

5/13/2019 1:41 PM

Overview

SQL Server and Sybase - JTDS

When you attempt to monitor a database that has a different character set than the DPA server and/or DPA Repository database, you may see an error that looks similar to this:
 

An unknown error has occurred. The provided message is "Could not get JDBC Connection; nested exception is java.sql.SQLException: Could not find a Java charset equivalent to DB charset iso_1."
 

Product section

Database Performance Analyzer

Cause

This occurs when the DPA server and Repository are using a different character set than the one used by the monitored database and the JDBC driver java is unable to load the correct character set. For example:

DPA Server: Cp1252
Repository DB: ISO_1
Monitored DB : ISO-8859-9 (Turkish)

Resolution

The ideal solution is to have all three using the same character set. If this isn't possible, you may be able to specify a character set that should be used instead. This is done by specifying a JDBC property in the Advanced Connection Properties of the Register Database Wizard.


For Example:

JTDS = charset=ISO-8859-9