今天运行datastage 报这个错误,就是连不上db2 数据库

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

查询资料处理如下

db2set db2codepage=1208

db2set db2country=86

db2 terminate

数据成功连上

 

以下转载:

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

[c-sharp] view plain copy print ?
  1. :/Program Files/IBM/SQLLIB/BIN>db2set db2codepage=1208
  2. C:/Program Files/IBM/SQLLIB/BIN>db2set db2country=86
  3. C:/Program Files/IBM/SQLLIB/BIN>db2 terminate
  4. DB20000I The TERMINATE command completed successfully.
  5. C:/Program Files/IBM/SQLLIB/BIN>db2stop force
  6. SQL1064N DB2STOP processing was successful.
  7. C:/Program Files/IBM/SQLLIB/BIN>db2start
  8. SQL1063N DB2START processing was successful.

:/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.