These days, the CLOB data type is extensively used in many applications. However, our problem was inserting DB2 CLOB data from a Java application into a OS/390 database because the codepage settings are different for both client and server. This tip helps solve the problem of inserting the data into DB2 on OS/390. It has been tested on version 7.2 of the client, version 6.2 of the server, and version 7.2 of DB2 connect.
The meaning of CLOB in Java setCLOB and in OS/390 are different as they are in different codepages. To resolve the problem, we changed the configuration in the db2cli.ini file. The command DISABLEUNICODE was set to 1 and the CLOB columns started receiving the data in OS/390. This is because the Unicode page check was disabled and DB2 for OS/390 accepted CLOB data. Setting this keyword to True will cause all Unicode data to be converted to the application's local codepage first, before the data is sent to the server. Secondly, the codepage can be matched to accept data both ways by setting up the db2cli.ini file as follows:
DISABLEUNICODE = 1 TRANSLATEDLL = X:PATHDB2TRANS.DLL TRANSLATEOPTION = database codepage number
For More Information
- Feedback: E-mail the editor with your thoughts about this tip.
- More tips: Hundreds of free DB2 tips and scripts.
- Tip contest: Have a DB2 tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize -- submit your tip today!
- Ask the Experts: Our SQL, database design, Oracle, SQL Server, DB2, metadata, and data warehousing gurus are waiting to answer your toughest questions.
- Forums: Ask your technical DB2 questions--or help out your peers by answering them--in our active forums.
- Best Web Links: DB2 tips, tutorials, and scripts from around the Web.