IBM Support

LI73734: USING DB2TRC -PERFCOUNT -T FOLLOWED BY OTHER DB2TRC ON / OFF COMMANDS WILL CAUSE THE DB2 INSTANCE TO CRASH

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using db2trc -perfcount -t  followed by other db2trc on / off
    commands(with db2 activity driving trace calls naturally),
    Results in a Trap and Crashes the db2 instance
    

Local fix

  • Avoiding -t wit -perfcount (or just avoiding -perfcount traces
    at the same time as regular db2 trace)
    

Problem summary

  • Users affected: any using the db2trc functionality
    Problem Description: Using db2trc on -perfcount -t and then
    issuing another db2trc on command will trap DB2
    Problem Summary: see above
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 7
    

Temporary fix

  • Avoid doing multiple db2trc commands when using -perfcount -t
    option.
    

Comments

APAR Information

  • APAR number

    LI73734

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-09-01

  • Closed date

    2009-06-04

  • Last modified date

    2009-06-04

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

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

    LI73735

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R910 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 October 2021