Question

我正在办理一项 Java诉申请,将我需要进口的档案移交给第二行的服务器。之后,Java Application创建了一个JDBC与数据库的联系,并运行:

 CALL SYSPROC.ADMIN_CMD( import from <filename> of del modified by decpt, coldel; messages on server inert into <view> )

The problem I have seems somehow conencted to the charset of either the database of the user the database uses to import the files (using the admin_cmd stored procedure). That problem is: "Umlaute", like ä,ö,ü get messed up by this import. I had this sort of problem in the past and solution always was to set the LC_CTYPE of the user importing the data to de_DE.iso88591

What I already ruled out as the source of the problem: - The file transfer to the database server. (Umlaute are still ok after that) - The JDBC Connection (I simply inserted a line through the sql command instead of reading from a file)

现在我并没有说,亚银2使用什么来通过杀伤人员地雷进口档案。我还认为,它可能在某种程度上与非行2环境相关联,因为与所有其他方式一样,插入、将......数据输入其中,将工作罚款。

是的,我需要使用杀伤人员地雷。亚洲开发银行2指挥线工具是一种表演夜总会。

Answer 1

最佳办法(针对动物):

Create all databases as UTF-8
Make sure all operating system locales are UTF-8
Get rid of all applications that don t handle their data as UTF-8
Slaughter every developer and vendor not adhering to UTF-8. Repeat and rinse until 100% completed.

DB2 确实是,并将你的输入数据转换为你的(进口指挥部基本上将数据管入插入条款——这些条款总是得到处理)。我提供的联系将概述基本原则,并给予你几个尝试。另外,还有。根据你的说法,你可以尝试确定环境变量db2codepage,以便与你的有限数据文档相对应,这应当有所帮助。而且,自律式出口可能更好,因为它们在每卷中都附有相关信息。

Answer 2

感谢您的答复。

最后,我通过增加一个席位来确定这个问题。

MODIFIED BY CODEPAGE=1252

致我的亚行进口指挥部。这似乎凌驾于以前使用过制版环境之上。数据库的缺省代码也看上去,因为定在1252处。我现在能够认为的唯一事情,是所有这一切的原因,可能是在通过杀伤人员地雷进口时使用亚银2。

友情链接