Can't preview data from DB2 through JDBC

[xihan]

Hi~
I have a DB2(version: 8.2.5) built in AIX OS, and trying to preview data in Table Input Step(PDI version: 3.0) through JDBC in Windows XP OS, but i got error message:
We failed to initialize at least one step. Execution can not begin!.
It seems that PDI 3.0 can connect to DB2, but not support preview data from DB2. How can i solve this problem? anyone can help plz?

Regards,
Jeff

[sboden]

Run it on detailed level and supply us with the actual error messages

Regards,
Sven

[acbonnemaison]

Hi~
I have a DB2(version: 8.2.5) built in AIX OS, and trying to preview data in Table Input Step(PDI version: 3.0) through JDBC in Windows XP OS, but i got error message:
We failed to initialize at least one step. Execution can not begin!.
It seems that PDI 3.0 can connect to DB2, but not support preview data from DB2. How can i solve this problem? anyone can help plz?

Regards,
Jeff

I had the same problem. I solved it by upgrading my JDBC driver to the most recent version.

The most recent version is available for download on the DB2 web site.

[xihan]

Run it on detailed level and supply us with the actual error messages

Regards,
Sven

Hi~ Sven, i got the detailed error messages as fallows:

2009/02/02 13:38:50 - 資料表輸入.0 - ERROR (version 1.0, build 191 from 2008/08/22 15:02:58) : An error occurred, processing will be stopped:
2009/02/02 13:38:50 - 資料表輸入.0 - ERROR (version 1.0, build 191 from 2008/08/22 15:02:58) : Error occured while trying to connect to the database
2009/02/02 13:38:50 - 資料表輸入.0 - ERROR (version 1.0, build 191 from 2008/08/22 15:02:58) :
2009/02/02 13:38:50 - 資料表輸入.0 - ERROR (version 1.0, build 191 from 2008/08/22 15:02:58) : Error connecting to database: (using class com.ibm.db2.jcc.DB2Driver)
2009/02/02 13:38:50 - 資料表輸入.0 - ERROR (version 1.0, build 191 from 2008/08/22 15:02:58) : Unicode string can't convert to Ebcdic string
2009/02/02 13:38:50 - 資料表輸入 - ERROR (version 1.0, build 191 from 2008/08/22 15:02:58) : Error initializing step [資料表輸入]
2009/02/02 13:38:50 - SY_GSS_SMS - ERROR (version 1.0, build 191 from 2008/08/22 15:02:58) : Step [資料表輸入.0] failed to initialize!
2009/02/02 13:38:50 - SY_GSS_SMS - Step [文�*�檔案輸出.0] initialized flawlessly.
2009/02/02 13:38:50 - SY_GSS_SMS - ERROR (version 1.0, build 191 from 2008/08/22 15:02:58) : We failed to initialize at least one step. Execution can not begin!

I have checked my db2 setting, which is that:

Database Configuration for Database b2bprod2

Database configuration release level= 0x0a00
Database release level= 0x0a00
Database territory = TW
Database code page = 1208
Database code set = UTF-8
Database country/region code = 88
Database collating sequence = BINARY
Alternate collating sequence (ALT_COLLATE) =
Database page size = 4096
Dynamic SQL Query management (DYN_QUERY_MGMT) = DISABLE
Discovery support for this database (DISCOVER_DB) = ENABLE
Default query optimization class (DFT_QUERYOPT) = 5
Degree of parallelism (DFT_DEGREE) = 1
Continue upon arithmetic exceptions (DFT_SQLMATHWARN) = NO
Default refresh age (DFT_REFRESH_AGE) = 0
Default maintained table types for opt (DFT_MTTB_TYPES) = SYSTEM

I have no idea how can i probably solve that!
any solutions?
thx for help me again!

Regards,
Jeff

[sboden]

May not be that easy to solve ... Have a look on the internet for the string "Unicode string can't convert to Ebcdic string".

As I see it the DRDA spec is default in EBCDIC (or if you change it, it has to be a single characterset), so it has problems with chinese, korean, ...

Regards,
Sven

[xihan]

May not be that easy to solve ... Have a look on the internet for the string "Unicode string can't convert to Ebcdic string".

As I see it the DRDA spec is default in EBCDIC (or if you change it, it has to be a single characterset), so it has problems with chinese, korean, ...

Regards,
Sven

Hi, Sven:
it sounds the problem is not in PDI itself but in DB2 since its DRDA implementation, right?

but, i try to access in DB2 by writting a JDBC java code with the same jar files(which are db2jcc.jar and db2jcc_license_cu.jar inside Kettle) and query the DB2 data. finally, i can see the data printed in screen succesfully, i guess maybe kettle does some actions when triggering preview event. Can you share your opinions to me plz?

thx for ur help again!

Regards,
Jeff

[sboden]

I'm pretty sure it's something with multi-bytes (korean, chinese, ...), and as such a big part of the people will never hit it. Search on the error string on the internet, I can't read most of the webpages (but maybe you can).

Next up would be trying to replace the jar files of DB2 in PDI with the ones you get with the DB2 client. 1 of the pages I can read partially mentioned that it may be solved in a new version of DB2.

Regards,
Sven

[xihan]

To Sven and acbonnemaison:
thx for ur help and solution,
i will try it through replacing DB2 jar, hope i can finish it!
all the best

Regards,
Jeff