Configuring extra failover capabilities in the Netcool/Impact environment

Edit online

Configure extra failover capabilities in the Netcool®/Impact environment by adding a cluster to the Netcool/Impact environment. To do this you must update the data sources in IBM® Tivoli® Netcool/Impact.

About this task

Update the following data sources when you add a cluster to the Netcool/Impact environment.
  • seasonalReportDataSource
  • RelatedEventsDatasource
  • NOIReportDatasource
Complete the following steps to update the data sources.

Procedure

  1. In Netcool/Impact, go to the Database Failure Policy.
  2. Select Fail over or Fail back depending on the high availability type you want. For more information, see the failover and failback descriptions.
  3. Go to Backup Source.
  4. Enter the secondary Impact Server's Derby Host Name, Port, and Database information.
    Standard failover
    Standard failover is a configuration in which an SQL database DSA switches to a secondary database server when the primary server becomes unavailable and then continues by using the secondary until Netcool/Impact is restarted.
    Failback
    Failback is a configuration in which an SQL database DSA switches to a secondary database server when the primary server becomes unavailable and then tries to reconnect to the primary at intervals to determine whether it returned to availability.

What to do next

If you encounter error ATKRST132E, see details in Troubleshooting Event Analytics

If you want your Netcool/Impact cluster that is processing events to contain the same cache and update the cache, at or around the same time, you must run the file relatedevents_objectserver.sql with nco_sql. The relatedevents_objectserver.sql file contains the following commands.
create database relatedevents;
create table relatedevents.cacheupdates persistent (name varchar (20) primary key, 
updates integer);
insert into relatedevents.cacheupdates (name, updates) values ('RE_CACHE', 0);