Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2004
    Posts
    190

    Unanswered: Reorg increased by 2.5 hours

    I have a situation where the runtime to reorg a large table has increase from 2 hours to 4.5 hours in the past 2 weeks. Any ideas what could have caused the sharp rise in runtime ?

    Thanks

    REORG TABLE PROD.GL_ENTRY INDEX PROD.XGLENC02 USE TEMPSPACE1;



    DB21085I Instance "db2inst1" uses "64" 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".

    Solaris 8

  2. #2
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,
    has table grown a bit time? What was table size in pages before and after?
    Grofaty

  3. #3
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Try specifying a temporary tablespace for the reorg. You probably no longer have enough free space inside the tablespace to reorg the table efficiently.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  4. #4
    Join Date
    Apr 2004
    Posts
    190
    The table is reorged on a weekly bases and the number of rows inserted are about the same each week.

    I'm using a temp tablespace to perform the reorg which is ~ 50GB while the table total size is ~ 18GB. See actual reorg command above.

Posting Permissions

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