IBM Support

IT11021: DSMSERV REMOVEDB FAILS AFTER A DATABASE RESTORE TERMINATES UNEXPECTEDLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Description:
    .
    After a database restore is terminated unexpectedly, attempts to
    use the 'dsmserv removedb' command to clean the environment for
    the restore operation to be executed again will fail with the
    following message:
    .
    ANR0238E A database recovery task is prohibiting activation of
    TSMDB1 with sqlcode -1119.
    .
    Running db2 connect to tsmdb1 may fail as follows:
    
    [tsminst1@rhel65 ~]$ db2 connect to tsmdb1
    SQL1119N  A connection to or activation of database "TSMDB1"
    cannot be made
    because a previous restore is incomplete or still in progress.
    SQLSTATE=57019
    .
    
    Initial Impact:  medium
    Additional Keywords: removedb restoredb drop connect prohibit
    activation
    

Local fix

  • Dropping the database as follows will allow Dsmserv restore db
    to complete
    Here are the steps:
    .
    1) Login as the Instance user. If needed CD to your db2 instance
    directory.
    Example:
    /opt/tivoli/tsm/db2/instance/
    do:
    2) db2start
    3) db2 drop db tsmdb1
    4) Try Dsmserv Restore db
    

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.4. Note that this is      *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • This problem was fixed.
    
    Update the DSMSERV REMOVE command topic in the Adminstrator's
    Reference with a new force parameter as follows:
    
    force
       Specifies that the database is removed regardless of
    connections when set to yes. For example, a database named
    tsmdb1 is removed even if it has open connections using the
    following command:
    
    dsmserv removedb tsmdb1 force=yes
    
    Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT11021

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-09-02

  • Closed date

    2015-09-11

  • Last modified date

    2015-09-11

  • 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

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.3"}]

Document Information

Modified date:
26 September 2021