IBM DB2 CODEPAGE

[kschwab]

I upgraded to DB2 v7.1 on a test WinNT Server.Get this error when

testing newly created connection to database in Client

Configuration Assistant."The connection test

failed.[IBM][CLI Driver] SQL0332N There is no available

conversion for the source code page "1208" to the target

code page "UNKNOWN". Reason Code "3". SQLSTATE=57017"
Any ideas what I can do to fix this?

 

[vleroux]

Not sure if this will help in your case.... but I've seen this very thing happen to a few other folks in my office and here's what they did to correct this error ...

I believe a codepage of "1208" is a Multi-language Supported (MLS) code page (or UNICODE) and not supported under DB2 UDB when using the CONNECT feature to a host DB2 (OS/390 for example). You may have to change the DB2CODEPAGE setting to a value that is supported on the host. Say 1252 (English) ....

You may have to do one or all of the following to accomplish this ....

1. Check/verify/remove the DB2CODEPAGE environment setting on your WIN/NT machine if it's set to 1208. (START/SETTINGS/CONTROL PANEL/SYSTEM/ADVANCED/Environment variables/system variables)

2. Issue 'DB2SET DB2CODEPAGE=1252' from DOS prompt and STOP/START DB2 via
DB2STOP/DB2START commands within the command line processor (CLP).

You may also have to redo your database instance if you're still getting the error after doing the above steps.

 

[joeting]

Is it possible to programmatically change the DB2CODEPAGE environment setting? I'm writing a C++ CLI program whih has its own character translation routines. I'm trying to bypass the automatic translation that DB2 does by setting the application code page to the database code page.