IBM Support

IV67091: TBSM FAILOVER BACKUP NOT STATRTED CORRECTLY IF STARTED TOO SOON

Direct links to fixes

7.1.0-TIV-NCI-ZLINUX-FP0006
7.1.0-TIV-NCI-WINDOWS-FP0006
7.1.0-TIV-NCI-SOLARIS-FP0006
7.1.0-TIV-NCI-LINUX-FP0006
7.1.0-TIV-NCI-AIX-FP0006
6.1.1-TIV-BSM-FP0004-windows
6.1.1-TIV-BSM-FP0004-zlinux
6.1.1-TIV-BSM-FP0004-solaris
6.1.1-TIV-BSM-FP0004-linux
6.1.1-TIV-BSM-FP0004-aix
6.1.1-TIV-NCI-FP0004-windows
6.1.1-TIV-NCI-FP0004-zlinux
6.1.1-TIV-NCI-FP0004-solaris
6.1.1-TIV-NCI-FP0004-aix
6.1.1-TIV-NCI-FP0004-linux
7.1.0-TIV-NCI-ZLINUX-FP0005
7.1.0-TIV-NCI-LINUX-FP0005
7.1.0-TIV-NCI-WINDOWS-FP0005
7.1.0-TIV-NCI-SOLARIS-FP0005
7.1.0-TIV-NCI-AIX-FP0005
6.1.1-TIV-BSM-FP0003-aix
6.1.1-TIV-NCI-FP0003-zlinux
6.1.1-TIV-NCI-FP0003-windows
6.1.1-TIV-NCI-FP0003-solaris
6.1.1-TIV-NCI-FP0003-linux
6.1.1-TIV-NCI-FP0003-aix
6.1.1-TIV-BSM-FP0003-zlinux
6.1.1-TIV-BSM-FP0003-windows
6.1.1-TIV-BSM-FP0003-solaris
6.1.1-TIV-BSM-FP0003-linux
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 2(7.1.0-TIV-NCI-FP0002)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 3(6.1.1-TIV-BSM-FP0003)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 3 (6.1.1-TIV-NCI-FP0003)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 3(7.1.0-TIV-NCI-FP0003)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 5(7.1.0-TIV-NCI-FP0005)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 4 (6.1.1-TIV-NCI-FP0004)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 4(6.1.1-TIV-BSM-FP0004)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 6(7.1.0-TIV-NCI-FP0006)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 7(7.1.0-TIV-NCI-FP0007)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 8(7.1.0-TIV-NCI-FP0008)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 9(7.1.0-TIV-NCI-FP0009)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 10(7.1.0-TIV-NCI-FP0010)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 11(7.1.0-TIV-NCI-FP0011)
IBM Tivoli Netcool/Impact V6.1.1 Fix Pack 5 (6.1.1-TIV-NCI-FP0005)
IBM Tivoli Business Service Manager V6.1.1 Fix Pack 5(6.1.1-TIV-BSM-FP0005)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 12 (7.1.0-TIV-NCI-FP0012)
IBM Tivoli Netcool/Impact V7.1.0 Fix Pack 13 (7.1.0-TIV-NCI-FP0013)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • TBSM Failover.  When starting both servers, if the backup
    server is started before the primary server is ready, it can
    fail to startup correctly.
    
    This can result in the backup data server trying to resync from
    the primary data server before the primary has fully
    initialised. When trying to retrieve the configuration from the
    primary the secondary will fail with the following errror:
    
     java.net.MalformedURLException: Invalid port number
    :-2147483648
    

Local fix

  • Wait until the primaty server trace.log has displayed the
    message ending:
    
    com.ibm.tbsm.consistency.ConsistencyService
    runConsistencyChecker Entry isRunning=true
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Impact and TBSM users who use failover.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * To start servers in failover mode, the user needs to start   *
    * the primary server and the backup server in that order.      *
    * However if the primary is started before the secondary is    *
    * fully initialised, and has started it's own services, then   *
    * the secondary startup will fail when if it tries to          *
    * resynchronise configuration files from the primary due to a  *
    * malformed port exception. This is more likely to occur in    *
    * TBSM where the main service can take a number of minutes to  *
    * start up.                                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Wait for the primary to fully start before starting          *
    * secondary servers, this can be done by monitoring the        *
    * impactserver.log for the following message on startup -      *
    *                                                              *
    * [ImpactServerManagedBean] Impact instance [<Server_Name>]    *
    * started successfully                                         *
    ****************************************************************
    Secondary server were not checking on initialisation state of
    the primary server before trying to resynchronise files between
    the primary and backup using an incorrect port to try get the
    files from. If this happened both the primary and backup needed
    to be stopped and restarted with an appropriate wait time
    between starting up servers for the failover configuration to
    work.
    

Problem conclusion

  • The fix for this APAR is contained in the following
    maintenance packages:
    Yes
    |Fix Pack | 6.1.1-TIV-BSM-FP0003
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV67091

  • Reported component name

    TIV BUS SERV MG

  • Reported component ID

    5724C5100

  • Reported release

    611

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-11-19

  • Closed date

    2014-12-01

  • Last modified date

    2014-12-01

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

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

Modules/Macros

  • UNKNOWN
    

Fix information

  • Fixed component name

    NETCOOL/IMPACT

  • Fixed component ID

    5724O59IS

Applicable component levels

  • R611 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHYH","label":"Tivoli Netcool\/Impact"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"611"}]

Document Information

Modified date:
03 October 2021