IC68323: JOURNAL DATABASES MAY BECOME CORRUPTED WHEN THE PRESERVEDBONEXIT SETTING IS USED AND CAUSE THE JOURNAL DAEMON TO ABEND.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Corrupt journal database can cause Journal daemoncrash on
    tsmjbbd!bTree::purgeCache when using PreserveDbOnExit option.
    Stack trace is as follows:
    tsmjbbd!bTree::purgeCache+0x6d
    tsmjbbd!bTree::fetchPage+0x3ee
    tsmjbbd!bTree::Search+0x146
    tsmjbbd!bTree::Search+0x166
    tsmjbbd!bTree::Search+0x166
    tsmjbbd!bTree::Search+0x78
    tsmjbbd!dbObject::dbGetExplicit+0xf1
    tsmjbbd!jnlDBCntrl+0x1202
    tsmjbbd!DbAccessThread+0xd4
    msvcr90!_callthreadstartex+0x17
    msvcr90!_threadstartex+0x84
    kernel32!BaseThreadInitThunk+0xd
    ntdll!RtlUserThreadStart+0x1d
    
    The problem can manifest itself in Client Deduplication
    with the 6.2.0 client also. Error messages similar to the
    following are logged in the error log:
    
    ANS0361I DIAG: jbbtreev.cpp (4553): purgeCache(): db
    corruption detected, actlist points to a disk node
    not in memory
    cur->nodeIX: 6
    indexArray count: 106 entries
    
    ANS0361I DIAG: cacheobj.cpp (987) dbUpdEntry():
    Insert(): errno = 228, "Unknown error 228"
    
    Initial Impact: Medium
    TSM Versions Affected: 6.1 and 6.2 windows clients.
    Additional Keywords: zz61 zz62
    

Local fix

  • refrain from using PreserveDbOnExit option until a fix is
    available. Journal databases should be deleted before the fix is
    applied to avoid the problem (if the fix is applied and journal
    databases aren't deleted the problem may occur once and cause
    the abend, the next time the journal daemon is started affected
    journal databases will be deleted and the problem won't happen
    again).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All 5.5, 6.1, and 6.2 TSM Client users       *
    ****************************************************************
    * PROBLEM DESCRIPTION: See Error Description                   *
    ****************************************************************
    * RECOMMENDATION: Apply the csd when available.                *
    *                 Target relleases: 5.5.3, 6.1.4, 6.2.1        *
    *                 Note: these targets may change at IBM's      *
    *                       discretion.                            *
    ****************************************************************
    

Problem conclusion

  • The problem was corrected so that it no longer occurs.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC68323

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    61F

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-30

  • Closed date

    2010-05-06

  • Last modified date

    2010-05-06

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

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

Modules/Macros

  • DSMC
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R62A PSY

       UP

  • R62H PSY

       UP

  • R62L PSY

       UP

  • R62S PSY

       UP

  • R62M PSY

       UP

  • R62W PSY

       UP

  • R61A PSY

       UP

  • R61I PSY

       UP

  • R61L PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

61F

Reference #:

IC68323

Modified date:

2010-05-06

Translate my page

Machine Translation

Content navigation