Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Database Performance Analyzer (DPA) > Different character sets cause connection errors

Different character sets cause connection errors

Table of contents


SQL Server and Sybase - JTDS

When attempting to monitor a database that has a different character set than the Ignite server and/or Ignite 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."


This occurs when the Ignite 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:

Ignite Server: Cp1252

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


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


Updates to the SQL Server JTDS Driver

There was a change in DPA version 10.0 to the jTDS drive for this issue. (The release notes are here.


DPA 10.0 updates the JTDS driver from 1.2.2 to 1.3.1. Improvements include:

  • SSL with BEAST detection
  • Java 1.8
  • Alternative data conversions for issues such as Turkish character recognition
  • Multi-subnet failover
  • ApplicationIntent=ReadOnly for read-only instances


Last modified
19:08, 22 Jun 2016