RE: collation SQL_EBCDIC037_CP1_CS_AS
- From: Rich <Rich@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 8 Nov 2006 20:22:01 -0800
Dear Kamil,
Thanks for your help. I solved the problem.
I tried the piece of code and found that Bentaho was not really running
JDK1.5.0_08. It came with its own JRE. I ran the code on the JRD. It
showed:
WARNING: Default charset MS950 not supported, using ISO-8859-1 instead
Exception in thread "main" java.lang.UnsupportedClassVersionError: mytest
(Unsup
ported major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
However, it was ok to run the code by JRE1.5.0_08. Therefore, I replaced
the came-with JRE with JRE1.5.0_08. It works fine now.
By the way, the result I got by using JRE1.5.0_08 was:
Codepage windows-950 supported: true
Codepage x-windows950 supported: false
Codepage CP950 supported: true
Codepage MS950 supported: true
Thanks for your help.
Have a great day.
Best Regards,
Rich
"Kamil Sykora [MSFT]" wrote:
Hello Rich,.
I am unable to reproduce the issue with the 1.0 or 1.1 versions of the SQL
Server 2005 JDBC Driver.
Can you tell me what this code reports for your VM?
import java.nio.charset.*;
...
String codepages[] = {"windows-950", "x-windows950", "CP950",
"MS950" };
boolean supported = false;
for (int i=0; i<codepages.length;i++)
{
supported = Charset.isSupported(codepages[i]);
System.out.println("Codepage " + codepages[i] + "
supported: " + supported);
}
I am getting this output:
Codepage windows-950 supported: true
Codepage x-windows950 supported: false
Codepage CP950 supported: false
Codepage MS950 supported: true
Thanks,
Kamil
Kamil Sykora [MSFT]
Microsoft Developer Support - Webdata
This posting is provided "AS IS", with no warranties, and confers no
rights.
Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.
--------------------
| From: =?Utf-8?B?UmljaA==?= <Rich@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: collation SQL_EBCDIC037_CP1_CS_AS
| Date: Fri, 27 Oct 2006 01:59:02 -0700
|
| Dear all,
|
| My problem is quite similar to AdamG. Here are what I got.
| 1. database MS SQL 2005 with collation "Chinese_Taiwan_Stroke_CI_AS"
| 2. windows 2003 (Database OS)
| 3. Pentaho BI suite running JDK1.5.0_08 (Web server on Windows XP SP2)
| 4. SQL Server 2005 JDBC driver 1.1 (On the web server too for connecting
to
| SQL 2005)
|
| The error message I got is "Codepage 950 is not supported by the Java
| environment."
|
| I had no problem to use JDBC 1.1 with collation
| "SQL_Latin1_General_CP1_CI_AS", but I need to use
| "Chinese_Taiwan_Stroke_CI_AS" somehow though.
|
| Please help!!
|
|
| Rich
|
| "Kamil Sykora [MSFT]" wrote:
|
| > Hello David,
| >
| > The EBCDIC collations bug has been fixed in the 1.1 release of the
driver.
| >
| > Are you using a Java application and the JDBC-ODBC bridge? If that's
the
| > case, you will not benefit from this fix since it's in the SQL Server
2005
| > JDBC driver which is a type 4 driver. I don't think the issue you are
| > describing is related to the fix.
| >
| > Are you able to reproduce this issue with the SQL Servef 2005 JDBC
Driver?
| > If so, can you make a new post with some sample code that describes it?
| >
| > Thanks,
| > Kamil
| >
| > Kamil Sykora [MSFT]
| > Microsoft Developer Support - Webdata
| >
| > This posting is provided "AS IS", with no warranties, and confers no
| > rights.
| >
| > Please do not send email directly to this alias. This alias is for
| > newsgroup
| > purposes only.
| > --------------------
| > | From: =?Utf-8?B?RGF2aWQgU3RhdGVz?= <David
| > States@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: RE: collation SQL_EBCDIC037_CP1_CS_AS
| > | Date: Thu, 31 Aug 2006 14:57:02 -0700
| > |
| > | Has this been fixed. I am trying to connect to a SQL 2005 server
using
| > ODBC
| > | and native client interface, but I get a message saying
| > |
| > | statement execution exception java.sql.SQLException: [Microsoft][SQL
| > Native
| > | Client][SQL Server]Cannot resolve the collation conflict between
| > | "Latin1_General_CS_AS" and "SQL_Latin1_General_CP1_CS_AS" in the
equal to
| > | operation.
| > |
| > | Seems like this is related to the problem you describe.
| > |
| > | David
| > |
| > | "Evan T. Basalik (MSFT)" wrote:
| > |
| > | > After some more internal testing, it looks like our SQL Server 2005
| > JDBC driver is improperly setting the codepage for that collation. We
have
| > filed a bug on
| > | > this issue. If you need further resolution beyond this, feel free
to
| > open a support ticket and we can pursue the possibility of getting a
fix on
| > a specific
| > | > timetable.
| > | >
| > | > Evan
| > | >
| > | > --------------------
| > | > >X-Tomcat-ID: 395515774
| > | > >References: <sWHhg.7613$Z67.1029@xxxxxxxxxxxxxxxxxxxx>
| > | > >MIME-Version: 1.0
| > | > >From: evanba@xxxxxxxxxxxxxxxxxxxx (Evan T. Basalik (MSFT))
| > | > >Organization: Microsoft
| > | > >Date: Tue, 20 Jun 2006 18:16:41 GMT
| > | > >Subject: RE: collation SQL_EBCDIC037_CP1_CS_AS
| > | > >Message-ID: <uXEMzWJlGHA.4928@xxxxxxxxxxxxxxxxxxxxx>
| > | > >Newsgroups: microsoft.public.sqlserver.jdbcdriver
| > | > >--------------------
| > | > >>From: "AdamG" <none@xxxxxxxxxxxxxxxxxx>
| > | > >>Newsgroups: microsoft.public.sqlserver.jdbcdriver
| > | > >>Subject: collation SQL_EBCDIC037_CP1_CS_AS
| > | > >>Lines: 15
| > | > >>X-Priority: 3
| > | > >>X-MSMail-Priority: Normal
| > | > >>X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
| > | > >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
| > | > >>X-RFC2646: Format=Flowed; Original
| > | > >>Message-ID: <sWHhg.7613$Z67.1029@xxxxxxxxxxxxxxxxxxxx>
| > | > >>Date: Wed, 07 Jun 2006 21:54:32 GMT
| > | > >>NNTP-Posting-Host: 204.210.35.61
| > | > >>X-Complaints-To: abuse@xxxxxx
| > | > >>X-Trace: tornado.socal.rr.com 1149717272 204.210.35.61 (Wed, 07
Jun
| > 2006 14:54:32 PDT)
| > | > >>NNTP-Posting-Date: Wed, 07 Jun 2006 14:54:32 PDT
| > | > >>Organization: Road Runner High Speed Online http://www.rr.com
| > | > >>Path:
| >
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS01.phx.gbl!newsfeed00
| > .sul.t-online.de!t-online.de!
| > | >
| >
border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.c| > om!newscon06.news.prodigy.com!prodigy.net!news-east.rr.com!news-
| > | >
| >
feed-01.rdc-kc.rr.com!news.rr.com!cyclone2.kc.rr.com!news2.kc.rr.com!tornad| > o.socal.rr.com.POSTED!53ab2750!not-for-mail
| > | > >>Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.sqlserver.jdbcdriver:7836
| > | > >>X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
| > | > >>
| > | > >>I am running SQL Server 2005 and trying to connect to a DB with
| > collation
| > | > >>set to SQL_EBCDIC037_CP1_CS_AS. On connection
| > | > >>(DriverManager.getConnection(url, userName, password); ) I am
getting
| > | > >>"Codepage 0 is not supported by the Java environment." I am on
JVM
| > build
| > | > >>1.4.2_10-b03.
| > | > >>
| > | > >>1) Has anyone else encountered this?
| > | > >>2) Will a JVM update help? 1.5? a later 1.4?
| > | > >>3) The end thing I am attempting to do is connect from an
iSeries
| > and have
| > | > >>the data sorted as if it was EBCDIC. Am I taking the wrong
approach?
| > | > >>
| > | > >>Thanks
| > | > >>Adam
| > | > >>
| > | > >>
| > | > >>
| > | > >
| > | > >
| > | > >--
| > | > >
| > | > >This posting is provided "AS IS" with no warranties, and confers
no
| > rights. Use of included script samples are subject to the terms
specified
| > at
| > | > >http://www.microsoft.com/info/cpyright.htm
| > | > >
| > | > >Note: For the benefit of the community-at-large, all responses to
| > this message are best directed to the newsgroup/thread from which they
| > originated.
| > | > >
| > | > >
| > | >
| > | >
| > | > --
| > | >
| > | > This posting is provided "AS IS" with no warranties, and confers no
| > rights. Use of included script samples are subject to the terms
specified
| > at
| > | > http://www.microsoft.com/info/cpyright.htm
| > | >
| > | > Note: For the benefit of the community-at-large, all responses to
this
| > message are best directed to the newsgroup/thread from which they
| > originated.
| > | >
| > | >
| > |
| >
| >
|
- References:
- RE: collation SQL_EBCDIC037_CP1_CS_AS
- From: Kamil Sykora [MSFT]
- RE: collation SQL_EBCDIC037_CP1_CS_AS
- Prev by Date: Re: Incoming TDS RPC Protocol Stream Incorrect Error for SQL Server 2005
- Next by Date: RE: No TDS_RET_STATUS was found
- Previous by thread: RE: collation SQL_EBCDIC037_CP1_CS_AS
- Next by thread: Re: Incoming TDS RPC Protocol Stream Incorrect Error for SQL Server 2005
- Index(es):
Relevant Pages
|
Loading