IBM Support

JR61901: INVALID SUBTYPE FOR CHARACTER DATA: UNKNOWN ON TABLE ORGINALLY CREATED IN DB2 6 WITH SYSIBM.SYSCOLUMNS.FOREIGNKEY BLANK

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • "Invalid subType for character data: UNKNOWN" error from
    Db2zCcsidTypeClassifier.
    Table was originally created in Db2 6
    and so the SYSIBM.SYSCOLUMNS.FOREIGNKEY column, which normally
    contains 'S' for SBCS or 'M' for MIXED, contains a blank
    (UNKNOWN).
    

Local fix

  • Workaround: Create a new table in the latest database instead
    of migrating the tables.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue affects clients who are using IBM Data            *
    * Replication CDC Db2 for z/OS remote source, and are mapping  *
    * tables that were created in Db2 version 6.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Mapping a table ends on error. The error reports "Invalid    *
    * subType for character data: UNKNOWN". This was due to a      *
    * table created in an earlier version of Db2, such as Db2 v6,  *
    * not having a FOREIGNKEY type set.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDR LUW 11.4.0.2-5528 for Db2 for z/OS remote     *
    * source.                                                      *
    ****************************************************************
    

Problem conclusion

  • Upgrading to IDR LUW 11.4.0.2-5528 for Db2 for z/OS remote
    source resolves the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR61901

  • Reported component name

    IDR DB2ZOS REMS

  • Reported component ID

    5737C30DR

  • Reported release

    B40

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-01-17

  • Closed date

    2020-02-28

  • Last modified date

    2020-02-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    IDR DB2ZOS REMS

  • Fixed component ID

    5737C30DR

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCMT2Q","label":"InfoSphere Data Replication"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 April 2020