IC68310: REVISED SPACE REQUIREMENTS FOR ARCHIVE LOGS DURING ONLINE REORG

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • The Capacity Planning section for Archive Logs do not account
    for the log space required during the online reorg.
    
    Because the online reorg is a recoverable operation, all the
    transactions from the reorg are logged.
    During online reorg, each row will have to be moved from one
    location to another.  At this time, DB2 need to write records
    into transaction log showing this information for all rows
    (including the before-move image and after-move image). It will
    also need to include such record for all indexes for each row,
    showing the location of row changed and RID in index record must
    be updated as well.
    Versions Affected: 6.1 and 6.2 on all platforms
    Initial Impact:  medium
    Additional Keywords: zz61 zz62 olr ANR0130E disk full
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    *
    

Problem conclusion

  • A new topic titled "Performing an on-line table reorganization
    requires additional archive log space" has been added to the
    Administrator's Guide and will follow the topic currently
    titled "Archive log space"
    
    Performing an on-line table reorganization requires additional
    archive log space.
    
    The space that is required for an on-line table reorganization
    is determined by the number of rows being reorganized, the
    number of indexes, the size of the index keys, and the current
    organization of the table. It is a good idea to establish a
    typical benchmark for log space consumption associated
    with your tables.
    
    Typically, every row in a table is moved twice during an
    on-line table reorganization. For each index each table row
    must update the index key to reflect the new location. After
    all accesses to the old location have completed, the index key
    is updated again to remove references to the old location.
    When the row is moved back, updates to the index key are
    performed again. All of this activity is
    logged to make on-line table reorganization fully recoverable.
    There is a minimum of two data log records (each including
    the row data) and four index log records (each including the
    key data) for each row (assuming one index). Clustering
    indexes are prone to filling up the index pages, causing
    index splits and merges that must also be logged.  A number of
    the tables implemented by the server have more than one index,
    and a table that has four indices would require sixteen index
    log records for each row being moved for the reorganization.
    
    The server monitors characteristics of the database, the
    active log, and the archive log to determine if a database
    backup is needed.  For example, during on-line table
    reorganization, if the filesystem used for the archive
    log space begins to fill up, the server triggers a
    database backup in order to relieve the situation.
    When a database backup is started, any on-line table
    reorganization in progress is paused so that the database
    backup can operate without contending for resources with
    the reorganization.
    
    
    Affected platforms: AIX, HP-UX, Sun Solaris, Linux, and Windows
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68310

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    61W

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-30

  • Closed date

    2010-06-04

  • Last modified date

    2010-06-09

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

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

Publications Referenced
SC23976901 SC23976902 SC23977001 SC23977002 SC23977101
SC23977102 SC23977201 SC23977202 SC23977901 SC23977902

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

61W

Reference #:

IC68310

Modified date:

2010-06-09

Translate my page

Machine Translation

Content navigation