DB2-Errors and fixing ways _sql0332n character conversion from the source code-CSDN博客

本文链接：https://blog.csdn.net/dgenerationx/article/details/4044225

本文介绍了两种常见的DB2连接异常及其解决方法。一是字符集不匹配导致的SQL0332N错误，通过更改客户端字符集为Unicode (UTF-8) 解决；二是未绑定数据库导致的SQL0805N错误，通过配置助手完成绑定操作解决。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Exception when connect to the remote DB2 Server

1. exception

SQL0332N Character conversion from the source code page "819" to the target code page "1386" is not supported. SQLSTATE=57017

a. analysis

                   Looks like on database code page is 819 and on v9 client code page is 1386.

                   Code page 819 is Albania, territory.                -- the remote server
                   Code page 1386 is China (PRC), territory .      -- my local

b. Fixing way

There is no conversion available between these two code pages.
So you can change the code page on client to 819 or Unicode(UTF-8) 1208.

yup, I like Unicode, so the steps I ran as followings:/Program Files/IBM/SQLLIB/BIN>db2set db2codepage=1208 C:/Program Files/IBM/SQLLIB/BIN>db2set db2country=86 C:/Program Files/IBM/SQLLIB/BIN>db2 terminate DB20000I The TERMINATE command completed successfully. C:/Program Files/IBM/SQLLIB/BIN>db2stop force SQL1064N DB2STOP processing was successful. C:/Program Files/IBM/SQLLIB/BIN>db2start SQL1063N DB2START processing was successful.

Then everything turns to be Ok. remote serverd was connected successful

2. exception

SQL0805N Package NULLID.******** was not found

a. analysis,

it caused by the client didn't bind the DB2 database v7 or v8

b Fixing way,

we need to bind on that.

The best way is to use Configurate Assistant

1. Launch Configurate Assistant

2. Right click on your database

3. Then select Bind

4. Choose CLI to be bind.