IC62254: TSM JOURNAL DATABASE GOES OFFLINE AFTER RECEIVING DBGETEXPLICT()SEARCH(): ERRNO = 22 "INVALID ARGUMENT" ON WINDOWS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • It has been observed that the TSM Journal will go offline when
    the following errors are reported in the jbberror.log
    06/02/2009 20:07:48 dbGetExplict(): Search(): errno = 22,
       "Invalid argument"
    06/02/2009 20:07:48 handleDbResultCode(): db access error 22
       returned from db method 'dbGetExplicit'.
    06/02/2009 20:07:48 handleDbResultCode(): Database error on
       journal db file 'C:\Program Files\Tivoli\TSM\baclient-
       \tsmC__.jdb', journal will be restarted.
    
    Even if the last message says the journal will be restarted,
    it is instead put offline.  All subsequent backups are
    traditional incremental backups.
    
    Another symptom is that during a Tivoli Storage Manager journal
    based backup, the journal service tsmjbbd.exe may crash with a
    crash entry similar to the following in dsmcrash.log:
    
    tsmjbbd.exe caused exception C0000005
    (EXCEPTION_ACCESS_VIOLATION) at 001B:004047CC
    
    Register dump:
    EAX=01920038  EBX=7813434C  ECX=012F013B  EDX=014A9B12
    ESI=0090EE24
    EDI=00000001  EBP=00000000  ESP=00CC27E8  EIP=004047CC
    FLG=00010246
    CS=001B   DS=0023  SS=0023  ES=0023   FS=003B  GS=0000
    
    Crash dump successfully written to file 'C:\Program
    Files\Tivoli\TSM\baclient\dsmcrash.dmp'
    
    Stack Trace:
    
    The call stack entry in dsmcrash.log is empty, but the call
    stack from the resulting client crash dump file dsmcrash.dmp
    (here from aTivoli Storage Manager 5.5.2.2 client) looks as
    follows:
    tsmjbbd!bTree::openBtDb+0x4ac
    tsmjbbd!dbObject::dbOpen+0xf9
    tsmjbbd!addDB+0x2d9
    tsmjbbd!jnlDBCntrl+0x184
    tsmjbbd!DbAccessThread+0xc4
    msvcr80!_callthreadstartex+0x1b
    msvcr80!_threadstartex+0x66
    kernel32!BaseThreadStart+0x34
    
    
    Versions Affected:  TSM Client 5.5 and 6.1 for Windows
    Initial Impact:  medium
    Additional Keywords: tsmjbbd io win2k3 win2k8 zz61
    

Local fix

  • To get the journal online again, there are two options:
    1 - restart the TSM Journal Service
    2 - Remove and add the file system from TSMJBBD.INI.  For
    example, in the above error, the problem was with the journal
    for C:.  If the entry for filesystems is:
       JournaledFileSystems=C: D:
    Change it to:
       JournaledFileSystems=D:
    Then save tsmjbbd.ini.  Wait a few seconds and edit tsmjbbd.ini
    again and change it back to:
       JournaledFileSystems=C: D:
    After it is saved, you should see an entry in the Event Viewer
    Application Log saying the journal for C: is now online.  The
    next backup will be incremental to validate the journal db,and
    subsequent backups will be journal based.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of journal-based backup on IBM     *
    *                 AIX and Microsoft Windows platforms          *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 5.5.3, 6.1.2, and 6.1.3. Note this *
    *                 is subject to change at the discretion of    *
    *                 IBM.                                         *
    ****************************************************************
    *
    

Problem conclusion

  • The journal daemon has been fixed so that when a database error
    occurs, the journal will be reset and used after the next full
    incremental backup operation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC62254

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-28

  • Closed date

    2009-09-28

  • Last modified date

    2009-11-17

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

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

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R55A PSY

       UP

  • R55F PSY

       UP

  • R55W PSY

       UP

  • R61A PSY

       UP

  • R61F PSY

       UP

  • R61W PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

61W

Reference #:

IC62254

Modified date:

2009-11-17

Translate my page

Machine Translation

Content navigation