Results 1 to 2 of 2
  1. #1
    Join Date
    Jun 2003
    Location
    Canada
    Posts
    37

    Unanswered: Why does my application query end up in syscat?

    The following is extracted from TMON for DB2's Collection Analysis
    We are a DB2 for OS/390 shop, v7.2 FP8

    I have a number of dynamic statements that occasionally find themselves waiting for very long time for the DB2 system catalog. I assume we are waiting for authorization and stats (?).

    But this long? Any ideas?


    Thread Resource Summary
    DB2 Collection Analysis
    +- Total Suspend -+ +--- Total I/O ---+
    Resource Type Count Elapsed Time Count Elapsed Time
    DSNDB06.DSNATX02 IX 0 0.0000 3 0.1074
    DSNDB06.DSNDSX01 IX 0 0.0000 3 1.3307
    DSNDB06.DSNDTX01 IX 0 0.0000 1 8.6930
    DSNDB06.DSNTNX01 IX 0 0.0000 2 0.0469
    DSNDB06.SYSDBASE TS 0 0.0000 10 13.7603
    DSNDB06.SYSSTATS TS 0 0.0000 5 0.0949
    someapdb.appindex1 IX 0 0.0000 3 0.0501
    someapdb.appindex2 IX 0 0.0000 2 0.0523

    Thanks,

    Julius

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Running DDL during queries with dynamic has been kown to cause conteintion on the catalog that the queries need for access path selection and authorization. Some mainframe shops have shaddow catalogs because of this.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •