IBM Support

JR50357: Q CAPTURE LOG READER THREAD NOT STOPPING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The log reader thread for the Q Capture program in
    Q Replication can continue to read the database recovery
    log after the worker thread assumes it has stopped.
    

Local fix

Problem summary

  • You might see a SIGSEGV error in Q Capture or conflicts at
    the target table for a small window of time. To check for
    conflicts, look for problems that are logged in the
    IBMQREP_EXCEPTIONS table.
    

Problem conclusion

  • The logic to stop the log reader thread is fixed so the
    worker thread correctly waits until the log reader thread
    has stopped completely.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR50357

  • Reported component name

    WS Q-REPLIC LUW

  • Reported component ID

    5724N9801

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-28

  • Closed date

    2014-05-28

  • Last modified date

    2014-05-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

    WS Q-REPLIC LUW

  • Fixed component ID

    5724N9801

Applicable component levels

  • R970 PSY

       UP

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

Document Information

Modified date:
28 May 2014