IBM Support

JR32258: THE BIGINT DATATYPE IS NOT SUPPORT ON UNIX FOR MSSQL ODBC DRIVERFROM DATADIRECT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Vendor Solution.

Error description

  • The server job gave warning      Type: Warning
    User Name: dsadm
       Message::
    LoadIncMADTBISalesHash..madt_bi_sales_lkp.madt_bi_sales_out:
    DSD.BCIOpenR results of SQLColAttributes(madt_bi_sales_key) gave
    MetaData mismatch
    COLUMN.TYPE Expected = BigInt Actual = Numeric
    Customer would like to change to INFO message because their job
    cannot have any warning.
    
    this is server job- changed to numeric fixed the issue, but
    customer cannot change. there are hundred jobs to be changed.
    PX jobs can use message handler to surpress the message.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Jobs with server ODBC stage gave MetaData mismatch warnings on
    COLUMN.TYPE BigInt.
    ****************************************************************
    PROBLEM DESCRIPTION:
    Jobs with server ODBC stage gave following MetaData mismatch
    warnings:
    s of
    SQLColAttributes(madt_pre_acq_sales_key) gave MetaData mismatch
    d = BigInt Actual = Numeric
       The issue is version 5.3 DataDirect SQL Server
    Wire Protocol  Driver does not support bgint data type on UNIX
    platforms. There are two DataDirect defects for this issue:
            ct to correct the users guide.   t to
    add support for bigint on unix/linux platforms (DD00028868)
            The documentation defect has
    been fixed in version 6.0 User's   Guide with following
    footnote:        1. Bigint supported
    on Windows driver only.
    ****************************************************************
    RECOMMENDATION:
    Apply patch JR32258.
    This change is included in 8.1 Fix Pack 1.
    ****************************************************************
    

Problem conclusion

  • Resolution was to add an environment variable
    DSODBC_NO_BIGINT_WARNINGS for the server ODBC stage to allow
    MetaData mismatch warnings to be
    
    a) suppressed when DSODBC_NO_BIGINT_WARNINGS is set to value
    1, or
      b) demoted to informational when DSODBC_NO_BIGINT_WARNINGS is
    set to value 2
    for DataDirect SQL Server Wire Protocol Driver on UNIX
    platforms.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR32258

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    801

  • Status

    CLOSED ISV

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-05

  • Closed date

    2009-03-23

  • Last modified date

    2009-12-15

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

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

Modules/Macros

  • SERVER
    

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 December 2009