IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Set up event forwarding to Netcool/OMNIbus > Upgrade from a previous installation of IBM Tivoli Monitoring and Netcool/OMNIbus integration

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

---

Replace the default deduplication trigger

With previous versions of the triggers provided by the IBM Tivoli Monitoring event synchronization component, the default deduplication trigger was overwritten in the Netcool/OMNIbus ObjectServer. The overwriting causes you to lose any customizations you made to the trigger. The latest version of the event synchronization component provides a deduplication trigger specific to Tivoli Monitoring called itm_deduplication.

If your default deduplication trigger has IBM Tivoli Monitoring logic, follow these steps to apply the default deduplication trigger to the Netcool/OMNIbus ObjectServer. The tasks in this section should be completed by the Netcool/OMNIbus Administrator.

1. Open the automation.sql file located at %OMNIHOME%\etc\automation.sql (Windows) or $OMNIHOME/etc/automation.sql (UNIX).

2. Locate the command that creates the deduplication trigger. For example:

   create or replace trigger deduplication 
   group default_triggers
   priority 1
   comment 'Deduplication processing for ALERTS.STATUS'
   before reinsert on alerts.status 
   for each row 
   begin
         set old.Tally = old.Tally + 1;
         set old.LastOccurrence = new.LastOccurrence;
         set old.StateChange = getdate();
         set old.InternalLast = getdate();
         set old.Summary = new.Summary;
         set old.AlertKey = new.AlertKey;
         if (( old.Severity = 0), and (new.Severity > 0))
         then           set old.Severity = new.Severity;
         end if;
   end;
   go

3. Copy this command to a temporary file. For this example, the temporary file is /tmp/dedup.sql.

4. Edit the command in the temporary file to add the line in bold type so that the deduplication trigger ignores IBM Tivoli Monitoring events and does not change the summary and severity of those events:

   for each row
   when (new.Type != 20), and (new.Type != 21)
   begin

5. Run the command to replace the deduplication trigger.

   • %OMNIHOME%\..\bin\redist\isql -U username -P password -S server_name < C:\tmp\dedup.sql

   • $OMNIHOME/bin/nco_sql -user username -password password -server server_name < /tmp/dedup.sql

   where:

   OMNIHOME

   Is the system-defined variable defining the installation location of OMNIbus

   username

   Is the OMNIbus Object Server user name

   password

   Is the OMNIbus Object Server password

   server_name

   Is the OMNIbus Object Server name defined for process control.

Parent topic:

Upgrade from a previous installation of IBM Tivoli Monitoring and Netcool/OMNIbus integration

---

+

Search Tips   |   Advanced Search