IBM Support

JR38237: TERADATA MULTILOAD JOB HANG WHICH CAUSE 32,000 + LOCKS ON THE SYS.MESSAGE FILE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Teradata job hang which cause 32,000 + locks on the SYS.MESSAGE
    file
    

Local fix

Problem summary

  • When user access the project thru DS client, it hangs.  Found
    out there are about 32,000 + locks on the SYS.MESSAGE file.
    If thejob was killed and the project was running thereafter
    smoothly.
    

Problem conclusion

  • When there is no data to write to a pipe using load methods
    tpump or mload in opening and closing the FIFO's.
    i.e When there is no data FIFO which has got opened need to
    close the connection because of no data,
    which is causing some synchronisation issues on the pipe and
    resulting in hang.
    

Temporary fix

  • Providing the latest patch JR38237.The job should now run with
    out any hang.
    

Comments

APAR Information

  • APAR number

    JR38237

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    752

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-11

  • Closed date

    2011-01-11

  • Last modified date

    2011-11-23

  • 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

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R753 PSY

       UP

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

Document Information

Modified date:
06 October 2021