IC95941: "ANS0361I [,,,] ERROR OPENING DATABASE" MESSAGE AT START OF CLIENT BACKUP USING "ENABLEDEDUPCACHE YES"

IBM Tivoli Storage Manager (TSM) Client 7.1.1 Downloads and READMEs

APAR status

• Closed as program error.

Error description

• When using client deduplication with "enablededupcache yes", the
  following errors may appear in the dsmerror.log file when
  starting a backup:
  
  ANS0361I DIAG: openBtDb(): Previous process didn't close the
   database, database may be corrupt.
  ANS0361I DIAG: dbOpen(): Error opening database 'xxx',
   openBtDb(): rc=229 .
  
  Despite these errors, the backup is successful.
  These errors are reported if the previous backup was abruptly
  stopped by a means external to Tivoli Storage Manager's control,
  such as using Task Manager to kill the process, CTRL-C or   UNIX
  kill command to interrupt the backup, stopping the service with
  the Services applet or "net stop" command while backup is
  ongoing. This leaves the dedupcache db locked and possibly
  corrupted, so these messages are reported when the next backup
  starts and the client needs to reinitialize the cache.
  It is preferable to use CANCEL SESSION to stop a running backup
  rather than killing it with any of the methods above.
  That should only be used as a last resort.
  
  
  Tivoli Storage Manager Versions Affected:
    All platforms    6.2 , 6.3 , 6.4
  
  Customer/L2 Diagnostics :
  
  A trace using service traceflag shows the successful restart:
  
  : dedupdb.cpp  (396): DedupDB::Initialize() Opening DedupDB
    Database 'd:\tsm\TSMDEDUPDB_xxx.DB' with exclusive lock ...
  : jbbtreev.cpp (2827): openBtDb(): Previous process didn't close
    the database, database may be corrupt.
  : cacheobj.cpp (600): dbOpen(): Error opening database
    'd:\tsm\TSMDEDUPDB_xxx.DB', openBtDb(): rc=229 .
  : dedupdb.cpp  (412): DedupDB::Initialize():  corrupt cache db
    detected, attempting to restart .
  : dedupdb.cpp  (427): DedupDB::Initialize():  restart
    successful.
  
  Initial Impact: Low
  
  Additional Keywords:
  TSM , cache
  

Local fix

• . If no other problem appears, that means the cache was
    successfully reinitialized, the messages can be ignored.
  . Use CANCEL SESSION to stop (if needed) a running backup.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Windows clients from 6.2 to 6.4              *
  *                 with deduplication enabled.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in level 6.4.2 and 7.1.1.                    *
  *                 Note that this is subject to change at the   *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• The messaging is enhanced to generate a message that the
  deduplication DB is successfully restarted.
  

Temporary fix

Comments

APAR Information

• 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

• R63W PSY

     UP

• R64W PSY

     UP