Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
IBM jdbc driver bug results in exception: "java.lang.NoClassDefFoundError: sun/io/ByteToCharConverter" - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • IBM jdbc driver bug results in exception: "java.lang.NoClassDefFoundError: sun/io/ByteToCharConverter"
KB0550816

IBM jdbc driver bug results in exception: "java.lang.NoClassDefFoundError: sun/io/ByteToCharConverter"


14950 Views Last updated : Oct 16, 2023 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Description

JDBC probes can result in an exception, "java.lang.NoClassDefFoundError: sun/io/ByteToCharConverter". This is believed to be the result of a bug in the DB2 JDBC driver as documented here: http://www-01.ibm.com/support/docview.wss?uid=swg1IC74895.

The IBM driver is calling an internal class in the Sun JRE, and Oracle / Sun removes the class. There is an update for the driver that addresses the issue but also requires adjusting a parameter.

Steps to Reproduce

 

Insert a non-UTF-8 character in a DB2 record and query by JDBC probe.

Workaround

Workaround #1:

  1. Review the description of the problem from IBM.
  2. Download and install the updated DB2 package and associated driver, db2jcc.jar, following the steps in KB0551236.
  3. In the agent/conf/wrapper-override.conf, add a line as follows:

    wrapper.java.additional.1=-Ddb2.jcc.charsetDecoderEncoder=3

Workaround #2:

Eliminate all invalid characters from the tables accessed.

These are subject to test pending access to a DB2 test environment.

 


Related Problem: PRB635705

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.