Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2001
    Posts
    80

    Unanswered: Runstat question

    Can I do runstat on more than 1 table within a database at the same table, any concurrent problem?

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    There might be some concurrency issues when DB2 goes to update the stats in the catalog, but I would think it would just result in a short lock wait at worst, and not any kind of deadlock.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  3. #3
    Join Date
    Dec 2001
    Posts
    80
    Marcus_A,
    Thx.

    Do you mean there is concurrent issue on SYSSTAT table?

  4. #4
    Join Date
    Oct 2005
    Posts
    109
    I suppose the question is:
    Can I do runstat on more than 1 table within a database at the same TIME, any concurrent problem ?

    No problem in the system catalog tables.

    But you might consider: with more than one table in a tablespace - this is not a problem of doing but who gets to read the pages first ... Still should not be a problem either, only for very fragmented data.

    It does not make sense to run runstats twice and in parallel on the same table ...
    Juliane

  5. #5
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by matthewlau
    Marcus_A,
    Thx.

    Do you mean there is concurrent issue on SYSSTAT table?
    Runstats updates many more tables than the SYSSTAT table. My guess is that if any concurrency issue exists against the catalog tables, it would only be a very short lock wait, which you probably would not even notice.
    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
  •