Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

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

Different character sets cause connection errors

Table of contents

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."

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

 

Last modified

Tags

Classifications

Public