IBM Support

JR62250: APPLY TO ORACLE CAN FAIL WITH AN INVALID NUMBER EXCEPTION

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

  • Apply to Oracle can fail with an Oracle "Invalid Number"
    exception when the source is Classic Replication and the source
    column is mapped to a target column with the NUMBER datatype
    with no precision and no scale, and the Classic database
    character set is not UTF-8. The problem will always occur
    during mirroring, but will only occur during refresh if JDBC
    refresh is used instead of Oracle fast load refresh. The
    problem exists staring with CDC release 11.3.3.
    

Local fix

  • Workaround: For refresh, use Oracle fast apply if possible. Or
    for both refresh and mirror, change target data type from
    NUMBER to
    NUMBER(precision,scale),
    NUMBER(precision),
    or
    NUMBER(*,scale).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue may affect you if you are using CDC 11.3.3 and    *
    * later when the source column is mapped to a target column    *
    * with the NUMBER datatype with no precision and no scale.     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The problem occurs when the source, such as some CDC Classic *
    * sources, does not support MBCS and the negotiated data       *
    * character set encoding is not UTF8.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Upgrading to IDR 11.4.0.2-5548 or newer for Oracle resolves the
    issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62250

  • Reported component name

    IS CDC ORACLE

  • Reported component ID

    5725E30OR

  • Reported release

    B40

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-20

  • Closed date

    2020-04-23

  • Last modified date

    2020-04-23

  • 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

    IS CDC ORACLE

  • Fixed component ID

    5725E30OR

Applicable component levels

  • RB40 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.4","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
25 August 2020