Siebel Database Upgrade Guide for DB2 UDB for z/OS > Planning A Siebel Database Upgrade > About Using the DSNTIAUL Utility >

About DSNTIAUL CCSID Conversion Errors


DSNTIAUL unloads all Siebel CRM application data in an EBCDIC CCSID. If the data to be unloaded is in ASCII format, conversion errors can occur for characters that are supported in ASCII but that are not supported in EBCDIC, for example, the euro and copyright symbols. CCSID conversion errors generate a RC=4 and produce an SQLSTATE=01517.

If the ASCII data contains a character that cannot be converted to EBCDIC, DSNTIAUL stops the unload process at that point. To correct this problem, you can either:

  • Update the source data
  • Specify the DSNTIAUL TOLWARN (YES) parameter

    CAUTION:  It is recommended that you do NOT use the TOLWARN (YES) parameter because it suppresses conversion error messages and can result in data corruption.

    The TOLWARN (YES) parameter forces DSNTIAUL to continue the unload process by inserting substitution characters for characters that cannot be converted; this ensures all records are unloaded even if they contain data that cannot be directly converted from ASCII to EBCDIC.

    However, using the TOLWARN (YES) parameter can also cause corrupted data in your upgraded Siebel application. DSNTIAUL provides the same substitution character for all ASCII characters that cannot be converted to EBCDIC. When the data is converted back to ASCII, the substituted characters are all converted back to the same ASCII character, for example, the euro and copyright symbols will both be represented by the same character. After the upgrade, your Siebel application will contain corrupted data and you will have to review the source data to determine which symbol a corrupted character corresponds to.

Siebel Database Upgrade Guide for DB2 UDB for z/OS Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.