Configuring the ObjectServer to support intra-device correlations
You must perform this task as an IBM Tivoli Netcool/OMNIbus user with ISQLWrite permissions.
From a command prompt, run the extracted advcorr.sql script using one of the following platform-dependent, case-sensitive commands:
On UNIX and Linux operating systems:
$OMNIHOME/bin/nco_sql -server objectserver_name -user username -password password < path_to_file/advcorr.sql
Where:
$OMNIHOME represents your installation location of IBM Tivoli Netcool/OMNIbus
objectserver_name represents the name assigned to your ObjectServer
username and password are your ObjectServer login details
path_to_file is the directory path to the files extracted in the previous section
On Windows operating systems:
%NCHOME%\bin\redist\isql.exe -S objectserver_name -U username -P password -i path_to_file\advcorr.sql
Where:
%NCHOME% represents your installation location of IBM Tivoli Netcool/OMNIbus
objectserver_name represents the name assigned to your ObjectServer
username and password are your ObjectServer login details
path_to_file is the directory path to the files extracted in the previous section
As part of the configuration, the script attempts to drop intra-device correlation tables (and associated triggers) which might have been created during a previous installation. As this is a first-time installation, no such tables or triggers exist, and an error listing is generated on completion. These messages are harmless and can be ignored. A sample output is shown below:
ERROR=Object not found on line 102 of statement
'--#######################################################################
######...', at or near 'AdvCorr_SetCauseType'
ERROR=Object not found on line 1 of statement 'drop trigger
AdvCorr_LPC_RC;...',
at or near 'AdvCorr_LPC_RC'
ERROR=Object not found on line 1 of statement 'drop trigger
AdvCorr_LPC_Sym;...', at or near 'AdvCorr_LPC_Sym'
ERROR=Object not found on line 4 of statement '-- Drop tables in case they
already exist from a previous installation...', at or near
'AdvCorrLpcSymCand'
ERROR=Object not found on line 1 of statement 'drop table
alerts.AdvCorrLpcRcCand;...', at or near 'AdvCorrLpcRcCand'
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
(0 rows affected)
The advcorr.sql script creates the following objects in the ObjectServer, to aid in determining the causal relevance of events:
- Intra-device correlation (AdvCorr) tables within the
alerts
database - Supplementary automations implemented as an AdvCorr trigger group and three related triggers
- Additional columns in the
alerts.status
table
Improving OMNIbus performance in failover architecture
The advcorr.sql file
has been updated to include a WHEN
condition for
all Advanced Correlation (AdvCorr) triggers so that they will only
run on the primary ObjectServer to improve performance in a failover
architecture. For example: when get_prop_value('ActingPrimary')%='TRUE'