Enabling on-premises scope-based event grouping

Edit online

The cloud native analytics component in your hybrid deployment disables any existing on-premises scope-based event grouping triggers during installation. However, the triggers that are related to enriching the ScopeID column and needed for scope grouping are not disabled. A specific set of triggers is added for cloud native analytics. Cloud native analytics creates scope-based groups, based on scope enrichment, and augments those groups with other groups from other analytics. The original on-premises scope-based event grouping triggers must remain disabled while cloud native analytics is actively preforming the task of scope-based grouping. To re-enable the on-premises scope-based grouping, you must first set the scope-based policy in the cloud native analytics policy UI to Disabled. Then, complete the following steps to re-enable the on-premises scope-based grouping.

Procedure

Check whether you already have scoping enabled on your on-premises ObjectServer. Run the following command.
```
$OMNIHOME/bin/nco_sql -user username -password password -server server_name
```
Where
- username is the administrative user for the ObjectServer, usually root.
- password is the password for the administrative user.
- server_name is the name of your ObjectServer.
Verify that:
- A row is returned by the following query: select TriggerName from catalog.triggers where TriggerName='correlation_new_row';
- The ScopeID field is present in the alerts.status table.
If the trigger is missing, complete the steps in the Installing scope-based event grouping topic in the IBM® Tivoli® Netcool®/OMNIbus documentation.
To enable scope-based grouping, use the following steps:
1. Download the file legacy_scoping_procedures.sql from here.
2. Run the downloaded SQL file on your primary ObjectServer to update the triggers.
```
$OMNIHOME/bin/nco_sql -server servername -user username -password password < legacy_scoping_procedures.sql
```
  Where
  - username is the administrative user for the ObjectServer, usually root.
  - password is the password for the administrative user.
  - server_name is the name of your primary ObjectServer.
3. Run the downloaded SQL file on your backup ObjectServer to update the triggers.
```
$OMNIHOME/bin/nco_sql -server servername -username username -password password < legacy_scoping_procedures.sql
```
  Where
  - username is the administrative user for the ObjectServer, usually root.
  - password is the password for the administrative user.
  - server_name is the name of your backup ObjectServer.
4. Run the following commands on both your primary and backup ObjectServer, to enable the legacy on-premises scope-based triggers.
```
$OMNIHOME/bin/nco_sql -server servername -username username -password password
1> execute procedure cea_enable_legacy_scope_triggers;
2> go
```