Welcome Guest! Log in
The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Reversing CCSID in DB2/400 database

    DB2/400 databases use a specific term “CCSID” to describe the encoding used for the data stored in the database. CCSID can be defined in DB2/400 for each column separately.

    It is worth noting that during the reverse of DB2/400 in Stambia, CCSIDs are not automatically reversed. Therefore, all intermediary tables will be created with the default CCSID of the database.

    In most cases this won’t cause any problems, but sometimes it might lead to conversion problems like this:

    java.sql.SQLException: [SQL0332] Character conversion between CCSID 1200 and CCSID 65535 invalid.

    In case you ever experience any problems related to CCSID, it is worth trying to use the option “Reverse CCSID” to get the CCSIDs into your metadata.

    This information will be then used by Stambia druing the creation of the intermediary tables and may ultimately solve your problem.


    To use the option, you need to go to your metadata and click on the schema. In the "Advanced" tab you will need to check the option “Reverse CCSID” and then reverse your metadata once again and save it:

     505 reverse ccsid option


    You can consult the reversed CCSIDs in the “Advanced” tab when you click on the specific column that has a defined CCSID in your database.

    505 reversed ccsid

    Stambia DI for IBM DB2/400

      Stambia Data Integration allows to work with IBM DB2/400 databases to produce fully customized Integration Processes.

      The database structure can be entirely reversed in Metadata and then used in Mappings and Processes to design and adapt the business rules to meet the user's requirements.

      Read more: Stambia DI for IBM DB2/400


      Suggest a new Article!