IBM Support

JR40609: Performance issue with Sybase requiring changes to the Sybase ASE write operator to support waves

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Performance issue with Sybase requiring changes to the Sybase
    ASE write
    operator to support waves.
    
    One thing to note is that with Sybase ASE Write Method , bulk
    load API
    is used, which locks the table till the bulk load completes.
    Hence the
    customer will not be able to do any other operation on the table
    like,
    select, delete or update when the job is running. In case of no
    WISD_INPUT, where a new instance is launched, this should not be
    a
    problem, but when WISD_INPUT is used, the stage can potentially
    hold the
    lock for a very long time.
    

Local fix

Problem summary

  • Performance issue with Sybase requiring changes to the Sybase
    ASE write operator to support waves.
    

Problem conclusion

  • Customer would like to use Sybase ASE Write Method to boost
    insert performance across a WAN. As the customer jobs are
    invoked as a web service, asesybasewrite operator needs to be
    made wave aware.
    
    Made asesybasewrite operator wave aware.
    
    Note: As Sybase ASE Write method uses Sybase Bulk Load API, the
    table will be locked during the time the load happens. The
    customer will not be able to execute queries like select,
    update, delete etc on the table. They can however perform load
    to the table through different jobs.
    
    Note: When using Sybase ASE Write Method with WISD_INPUT Stage,
    customer is advised to use batch size option to commit rows
    after certain intervals. By default, Sybase ASE will commit all
    the rows at the end of the Bulk load process. For a job instance
    that does not run to completion, like when using WISD_INPUT, no
    rows will appear in the database if no batch size is specified.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR40609

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-09-09

  • Closed date

    2011-10-03

  • Last modified date

    2012-03-24

  • 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

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R810 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
12 October 2021