IBM Support

IT13092: TIVOLI STORAGE MANAGER SERVER CAN FAIL TO START WITH ANR9999D_3018691914 TABLE NOT FOUND IN DATABASE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Tivoli Storage manager server can fail to start with the
    following message:
    
    ANR9999D_3018691914 TbGetDatabaseSchema (tbtbl.c:8499)
    Thread<1>: Tab BF_AGGREGATED_BITFILES not found in
    database. Database is not intact schemaCount = 2.
    Restore database or contact IBM Software Service
    for assistance.
    
    The problem occurs because there is more than one
    table schema for the affected table. By default there
    should be only one table schema.
    
    If customer creates alias table schema, this problem
    can occur
    .
    Tivoli Storage Manager server code will be changed
    to allow server startup or restore db to complete
    even if alias table schema exists.
    
    During restore, dsmserv may  crash and create core
    file with the following call stack
    
    (gdb) where
    #0  pkAcquireMutexTracked (mutexP=0x0, file=0x1282a94
        "tbtbl.c", line=2927) at pkmon.c:573
    #1  0x0000000000b65e41 in tbRegisterTableEnhanced
        (tableName=0x13b1b18 "Nodes", abbrevName=0x11071ba
        "ADNR", isBaseTable=True, numCols=106, keyCols=1,
        partKeyCols=0, colInfoP=0x1135f80,
        constraintsInfoP=0x1694ec0, numConstraints=5,
        extDef=0x0) at tbtbl.c:2927
    #2  0x0000000000553b76 in RegisterTables () at adminit.c:7005
    #3  0x00000000004b6d47 in admRestoreDatabase
        (commandString=<value optimized out>) at admstart.c:4144
    #4  0x00000000004a4872 in RestoreDb (argCount=5,
        argVector=0x7ffc99441698) at dsmserv.c:1597
    #5  main (argCount=5, argVector=0x7ffc99441698) at
        dsmserv.c:1425      \
    .
    Trace of failing restore using icrest icvolhst mms
    pvr na session classes may show the following:
    
    ][smexec.c][11926][EndSession]:Session 6 ended.
    [ffdcutil.c][367][FFDCLogThread]:[11-04-2015 10:24:37.653]
    [ FFDC_GENERAL_SERVER_ERROR ]: (rdbicrst.c:1646) dbiInit
    failed with rc 9991.
    [output.c][7644][PutConsoleMsg]:ANR4635I Point-in-time
    database restore complete, restore date 11/01/2015 06:00:22 PM.~
    [admdbbk.c][2332][AdmRestoreDb]:Restore/rollforward
    DB is successful and the volumes used for restore DB has
    been added to vol hist. The fullDevClass used is
    DBBKP_DSK incDevClass used is .
    10:24:37.653 [2][ffdcutil.
    
    You may see the following in db2diag.log when
    restore runs and fails
    
    First you may  see the restore complete:
    .
    2015-11-04-10.23.16.575546-660 E85346E473            LEVEL: Info
    PID     : 27584                TID : 140314291463936 PROC :
    db2sysc 0
    INSTANCE: tsminst1             NODE : 000            DB   :
    TSMDB1
    APPHDL  : 0-10                 APPID:
    *LOCAL.tsminst1.151103212252
    AUTHID  : TSMINST1             HOSTNAME: yourhostname
    EDUID   : 27                   EDUNAME: db2agent (TSMDB1) 0
    FUNCTION: DB2 UDB, database utilities, sqludrsa, probe:889
    MESSAGE : Restore Complete.
    .
    Then this error may occur:
    .
    2015-11-04-10.23.16.799600-660 I88179E645            LEVEL:
    Error
    PID     : 27584                TID : 140314291463936 PROC :
    db2sysc 0
    INSTANCE: tsminst1             NODE : 000            DB   :
    TSMDB1
    APPHDL  : 0-11                 APPID:
    *LOCAL.tsminst1.151103212316
    AUTHID  : TSMINST1             HOSTNAME: yourhostname
    EDUID   : 411                  EDUNAME: db2agent (TSMDB1) 0
    FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:5247
    MESSAGE : ZRC=0xFFFFFBA3=-1117
              SQL1117N  A connection to or activation of database ""
    cannot be made
              because of ROLL-FORWARD PENDING.
    

Local fix

  • Do not create alias table schema until code is
    updated to allow for more than one table schema
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Tivoli Storage Manager server users.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available.This problem is currently  *
    * projected to be fixed in level 7.1.6. Note that this is      *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • This problem was fixed.
    Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT13092

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-13

  • Closed date

    2016-04-08

  • Last modified date

    2016-04-08

  • 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 SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 7.1.3

Reference #: IT13092

Modified date: 08 April 2016