Results 1 to 2 of 2

Thread: runstats issue

  1. #1
    Join Date
    Apr 2004

    Unanswered: runstats issue

    I have a table that is replicated to another database, on the same instance. Everything is identical for these tables. The issue is it takes ~ 45 minutes to perform a runstats on the table in one db and it takes ~ 4 hours on the other.

    The only differences between the databases are:

    dft_degree 4 ANY
    primary logs 30 10
    secondary logs 30 20
    softmax 100 80

    Could one of these parameters cause this type of issue? Intra_parallel is NO and max_querydegree is ANY at the DBM level.

    Solaris 8

    DB21085I Instance "db2inst1" uses "32" bits and DB2 code release "SQL08022"
    with level identifier "03030106".
    Informational tokens are "DB2 v8.1.0.89", "special_15295", "U800790_15295", and
    FixPak "9".
    Product is installed at "/opt/IBM/db2/V8.1".

  2. #2
    Join Date
    Sep 2003
    runstats doe a full tablescan; is a heavy I/O process; are the 2 operating systems the same; like, CPU,diskspeed etc; also the tablespaces set up the same way? what is the load on either system when you run runstats?

Posting Permissions

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