problem with iso-8859-2 chars, oracle rdb, jdbc

From: Krzysztof Sobczuk (krzysztof.sobczuk_at_pentacomp.com.pl)
Date: 07/28/04

  • Next message: Lothar Kimmeringer: "Re: problem with iso-8859-2 chars, oracle rdb, jdbc" 
    Date: Wed, 28 Jul 2004 18:48:15 +0200

    Hello,

    I am dealing with a problem connected with special polish iso-8859-2
    characters between Oracle Rdb, Oracle SQL/Services on server side and jdbc
    on client side.

    Oracle Rdb OCI Server Release 7.1.5.9.1 - Production, Level 1.7;
    Oracle Rdb SQL Release 7.0.7.3.0 - Production;
    CORE Version 4.0.5.0.0 - Production;
    TNS for VMS: Version 8.0.5.0.2 - Production;
    NLSRTL Version 3.3.2.0.0 - Production;
    Metadata Views Version 7.1.5.9.0 - Production;
    Oracle Compatible Release 8.0.5.1.0;

    Database is in WE8DEC charset and NLS_LANG on server side is set to WE8DEC.
    Specific polish characters in database have ISO-8859-2 codes:
    a1 c6 ca a3 d1 d3 a6 ac af (9 big chars)
    b1 e6 ea b3 f1 f3 b6 bc bf (9 small chars)

    1. When I use jdbc oci driver polish iso-8859-2 characters are transferred
    to client as:
    a1 c6 ca a3 d1 d3 a6 ac af b1 e6 ea b3 f1 f3 b6 bc bf
    So it is ok so far.

    After conversion in jdbc driver I get something like this:

    C2 A1 C3 86 C3 8A C2 A3 C3 91 C3 93 EF BF BD EF
    BF BD EF BF BD C2 B1 C3 A6 C3 AA C2 B3 C3 B1 C3
    B3 C2 B6 C2 BC C2 BF

    or depending on method of retrieving from resultset
    A1 C6 CA A3 D1 D3 FD FD FD B1 E6 EA B3 F1 F3 B6
    BC BF

    Three last big polish chars have incorrect codes "FD".

    2. When I use jdbc thin driver polish iso-8859-2 characters are transferred
    to client as:
    C2 A1 C3 86 C3 8A C2 A3 C3 91 C3 93 EF BF BD EF
    BF BD EF BF BD 20 C2 B1 C3 A6 C3 AA C2 B3 C3 B1
    C3 B3 C2 B6 C2 BC C2 BF

    Here three last big polish chars have incorrect codes "EF BF BD" even before
    they reach jdbc driver.

    I suppose the problem is in jdbc driver classes and native sql procedures on
    server side which convert oracle
    chars to unicode and vice versa. There not exists proper mapping of
    charaters?
    What do I have to do to get proper iso-8859-2 chars from jdbc driver?

    Thanks for any suggestions,
    Krzysiek Sobczuk

  • Next message: Lothar Kimmeringer: "Re: problem with iso-8859-2 chars, oracle rdb, jdbc"

    Relevant Pages

    • Re: Access Oracle Objects via PLSQL from JDBC
      ... In oracle demos I couldn't find a such examples.... ... This example uses a JDBC thin client to call a PLSQL stored ... test.java - this calls the plsql and displays the resultset ... // JDBC Implementation specific connect string ...
      (comp.lang.java.programmer)
    • Re: Database wars
      ... > Queries with Prevayler are more than 9000 times faster than querying ... > Oracle through JDBC. ...
      (borland.public.delphi.non-technical)
    • Re: ORA-01483: invalid length for DATE or NUMBER bind variable :(
      ... Oracle, ODBC and DB2/CLI Template Library, Version 4.0.101, by Sergei Kuchin ... NLS_DATE_LANGUAGE POLISH ... Log onto each Oracle database using the ID that the task ... PS - Can you set up an SQL trace for the failing task? ...
      (comp.databases.oracle.server)
    • Re: Wrong Return Value from statement.executeUpdate(query)
      ... On 20.04.2007 17:50, Joe Weinstein wrote: ... Oracle would need a "BEGIN delete ...; delete ...; END;". ... since JDBC 1.0. ... For example accessing meta data - although there is a clear defined interface drivers still choose to interpret arguments differently. ...
      (microsoft.public.sqlserver.jdbcdriver)
    • Help with Java Applet please...
      ... running on an old Sun box with Oracle on the same box. ... I'm stuck because of this Java Applet. ... I did some reading on JDBC, ... can't tell how it was connecting because I don't see any reference to ...
      (comp.lang.java.programmer)