IBM Support

IC68898: Running runstats immediately after connecting to a database might lead to segmentation faults.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If RUNSTATS is executed immediately after connecting to a
    database, subsequent operations may trap with a segmentation
    fault.  The subsequent operation can be any operation, including
    another RUNSTATS.  For the problem to occur, the RUNSTATS
    operation must be on a table without any indexes.  It does not
    matter if the runstats command specified an INDEX clause or not.
    
    Sample callstacks that can experience the problem:
    
    sqlr_audit
    sqlr_audit_context
    sqlrrcom_dps
    sqlrrcom
    sqlrr_commit
    
    and
    
    sqlr_audit
    sqlr_audit_checking
    sqlrr_check_auth
    sqlrrsta
    sqlrr_runstats_DA
    

Local fix

  • Execute any SQL statement (e.g. "values 1") before running
    RUNSTATS.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 LUW on all supported platforms.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * WITH ACTIVE DATABASE LEVEL AUDIT, PERFORMING RUNSTATS        *
    * RIGHTAFTER DATABASE BECOMES ACTIVE MAY TRAP.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 LUW Version 9.7 Fix Pack 3                    *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Version 9.7 Fix Pack 3
    

Temporary fix

  • The problem will not occur if:
    (1) the table has at least one index,
    
    
    or
    (2) after CONNECT to database, if any SQL statement (e.g.
    
    VALUES(1))
    has been executed before the RUNSTATS command.
    

Comments

APAR Information

  • APAR number

    IC68898

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-27

  • Closed date

    2010-10-12

  • Last modified date

    2010-11-16

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

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

    IC69478

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"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:
16 November 2010