IBM Support

IZ24039: DCS APPLICATION SNAPSHOT REPORTING INACCURATE STATEMENT COUNTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using DCS application snapshots you can see inaccurate
    values for the statement counters.
    The following two examples show variations of this behavior.
    
    Example 1: The overall statement count for a section in the DCS
    application snapshot output is higher than the count in the
    corresponding subsections.
    
    Info for statements taking from 3 to 7 transmissions:
      Number of SQL statements                 = 4
      Number of statements with outbound bytes sent:
    
         Between 1 and 128 bytes               = 0
         Between 129 and 256 bytes             = 0
         Between 257 and 512 bytes             = 2
         Between 513 and 1024 bytes            = 0
         [... all subsequent counters show 0 ...]
    
      Number of statements with outbound bytes received:
         Between 1 and 128 bytes               = 0
         [... all counters in between show 0 ...]
         Between 32000 and 64000 bytes         = 2
         Greater than 64000 bytes              = 0
    
      Number of statements with network time:
         Up to 1 ms                            = 0
         Between 1 and 4 ms                    = 0
         Between 4 and 16 ms                   = 2
         [... all subsequent counters show 0 ...]
    
    
    Example 2: The statement count within a subsection does not
    match the overall statement count for the specific section.
    
    Info for statements taking more than 64 transmissions:
      Number of SQL statements                 = 25
      Number of statements with outbound bytes sent:
         Between 1 and 128 bytes               = 0
         [... all counters in between show 0 ...]
         Between 2049 and 4096 bytes           = 5
         Between 4097 and 8192 bytes           = 5
         Between 8193 and 16384 bytes          = 0
         Between 16385 and 31999 bytes         = 5
         Between 32000 and 64000 bytes         = 10
         Greater than 64000 bytes              = 0
      Number of statements with outbound bytes received:
         Between 1 and 128 bytes               = 0
         [... all counters in between show 0 ...]
         Greater than 64000 bytes              = 25
      Number of statements with network time:
         Up to 1 ms                            = 0
         Between 1 and 4 ms                    = 0
         Between 4 and 16 ms                   = 0
         Between 16 and 100 ms                 = 5
         Between 100 and 500 ms                = 6
         Greater than 500 ms                   = 9
    
    This APAR addresses changes to the monitoring code to allow more
    accurate statement counting.
    

Local fix

  • n/a
    

Problem summary

  • USERS AFFECTED: all using DCS application snapshots
    
    PROBLEM DESCRIPTION:
    When using DCS application snapshots you can see inaccurate
    values for the statement counters.
    
    PROBLEM SUMMARY:
    When using DCS application snapshots you can see inaccurate
    values for the statement counters.
    The following two examples show variations of this behavior.
    
    Example 1: The overall statement count for a section in the DCS
    application snapshot output is higher than the count in the
    corresponding subsections.
    
    Info for statements taking from 3 to 7 transmissions:
      Number of SQL statements                 = 4
      Number of statements with outbound bytes sent:
    
         Between 1 and 128 bytes               = 0
         Between 129 and 256 bytes             = 0
         Between 257 and 512 bytes             = 2
         Between 513 and 1024 bytes            = 0
         [... all subsequent counters show 0 ...]
    
      Number of statements with outbound bytes received:
         Between 1 and 128 bytes               = 0
         [... all counters in between show 0 ...]
         Between 32000 and 64000 bytes         = 2
         Greater than 64000 bytes              = 0
    
      Number of statements with network time:
         Up to 1 ms                            = 0
         Between 1 and 4 ms                    = 0
         Between 4 and 16 ms                   = 2
         [... all subsequent counters show 0 ...]
    
    
    Example 2: The statement count within a subsection does not
    match the overall statement count for the specific section.
    
    Info for statements taking more than 64 transmissions:
      Number of SQL statements                 = 25
      Number of statements with outbound bytes sent:
         Between 1 and 128 bytes               = 0
         [... all counters in between show 0 ...]
         Between 2049 and 4096 bytes           = 5
         Between 4097 and 8192 bytes           = 5
         Between 8193 and 16384 bytes          = 0
         Between 16385 and 31999 bytes         = 5
         Between 32000 and 64000 bytes         = 10
         Greater than 64000 bytes              = 0
      Number of statements with outbound bytes received:
         Between 1 and 128 bytes               = 0
         [... all counters in between show 0 ...]
         Greater than 64000 bytes              = 25
      Number of statements with network time:
         Up to 1 ms                            = 0
         Between 1 and 4 ms                    = 0
         Between 4 and 16 ms                   = 0
         Between 16 and 100 ms                 = 5
         Between 100 and 500 ms                = 6
         Greater than 500 ms                   = 9
    
    This APAR addresses changes to the monitoring code to allow more
    accurate statement counting.
    
    LOCAL FIX:
    n/a
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 7 (s090308)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ24039

  • Reported component name

    DB2 CEE AIX

  • Reported component ID

    5765F3000

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-06-10

  • Closed date

    2009-04-07

  • Last modified date

    2009-04-07

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

    IZ14321

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

Fix information

  • Fixed component name

    DB2 CEE AIX

  • Fixed component ID

    5765F3000

Applicable component levels

  • R810 PSN

       UP

  • R820 PSN

       UP

  • R910 PSN

       UP

  • R950 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"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"}]

Document Information

Modified date:
04 October 2021