Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 15, 8.1.0-TIV-NCOMNIbus-FP0015

Notice: IBM will withdraw support for the selected Netcool product versions licensed under the IBM International Program License Agreement.

The following defect solutions are included in this release:

8.1.0-TIV-NCOMNIbus-FP0015
--------------------------

IJ00055
Deprecated properties are written to the ObjectServer props file following runtime property modification. When the ObjectServer restarts, deprecated property warning messages are output to the screen. This issue is now resolved. The following ObjectServer properties and arguments are obsolete and will not appear in product '-help' text or '-dumpprops' property output:

NHttpd.SSLCertificatePwd -nhttpd_sslcertpwd
RestrictionEnforceDeleteCheck -norestrictionenforcedeletecheck
RestrictionEnforceInsertCheck -norestrictionenforceinsertcheck
RestrictionEnforceUpdateCheck -norestrictionenforceupdatecheck

The affected properties and arguments may continue to exist in the properties file and command line, but they are ignored.


IJ00111
Users are not able to run nco_confpack on a machine running Windows Server 2016. This problem is now fixed.


IJ00198
PAM authentication fails when connecting to the Process Agent in 8.1.0.13, when the PAM configuration does not have pam_unix.so. This problem is now fixed.


IJ00362
Use of the genevent() function to insert into a target that did not contain an Identifier field could cause invalid SQL to be executed if the current invocation of the rules file had some
details() entries active. On versions of OMNIbus from v8.1.0.9 to v8.1.0.14 this caused the probe to exit. This problem is now fixed.


IV76852
The ObjectServer can core dump when processing an 'ALTER TABLE' SQL statement. This core dump can occur if multiple varchar columns are added or dropped and a trigger exists with an action containing a 'FOR EACH ROW' loop that iterates over the altered table. This issue is now resolved.


IV77452
When connecting multiple co-located gateways to an ObjectServer, only a single row is displayed in table iduc_system.iduc_stats. This problem is now fixed. The fix creates a row in the table for each gateway instance that connects to the ObjectServer and registers for IDUC notifications.


IV89867
Accelerated Event Notification: When the best practice multitier accelerated_inserts trigger is enabled and there is a large insert rate, an ObjectServer gateway can grow in memory because it is unable to keep up with the event fast track load. The problem is caused by the gateway reader generating an SQL SELECT statement for each fast track row. In this fix pack, ObjectServer gateways have been modified to enable multiple fast track rows to be read by the gateway at one time. This modification improves the performance of fast track  notification under high load conditions.


IV90338
A new ProbeWatch alert is automatically generated whenever a probe fails over from secondary to primary mode and vice versa in a peer-to-peer setup. ProbeWatch alerts from probes running in secondary mode are no longer cached and discarded but are forwarded on to the ObjectServer.  An example about how to process the new ProbeWatch failover alerts is available in OMNIHOME/extensions/probewatch/probefailover.include.


IV96571
The nco_osreport tool fails to copy the table data for an ObjectServer when the alerts status table has a column marked as hidden. This problem is now fixed.


IV97315
It is now possible to disable specific SSL/TLS ciphers per protocol for servers. For more information about configuration details, see
https://www.ibm.com/support/knowledgecenter/en/SSSHTQ_8.1.0/com.ibm.netcool_OMNIbus.doc_8.1.0/omnibus/wip/admin/task/omn_adm_disableSSLTLScipers.html


IV97909
The isql.bat command fails to run and reports an error when run on a Windows machine running in the German language. This issue is now resolved.


IV98647
The device counter extension was unable to handle a large number of master.device entries (>200). The Aggregation ObjectServer would report errors concerning corrupted name value pair strings.  The device_counter_process_table trigger on the Collection ObjectServers was corrected. These triggers require a manual update that uses the files in the
extensions/devicecounter/update/update81fp4to81fp15 directory.


IV98969
Scope-based grouping is now updated to remember the highest priority child event seen in the group, for the purposes of propagating priority child event information. Previously the
propagation of child event information was done dynamically but got lost when that priority event cleared, because propagation was done solely on what events were present at the time. This meant that historical reporting could end up with blank values in the synthetic parent Summary field, if the CustomText was being included from the priority child event.

The four different priorities are as before:
first FirstOccurrence
last LastOccurrence
highest CauseWeight
highest ImpactWeight

With the fix in FP15, the following examples show what will happen now:

- If the highest CauseWeight is selected as the highest priority (SEGPropagateTextToScopeIDParentCause: 1), the details from the child event with the highest CauseWeight ever seen in the group is retained and used for populating the CustomText for the synthetic event, even if that child event clears. This information will update only if a child event is seen with a higher CauseWeight.

- If the first FirstOccurrence is selected as the highest priority (SEGPropagateTextToScopeIDParentFirst: 1), the details from the child event with the first FirstOccurrence ever seen in the group is retained and used for populating the CustomText for the synthetic event, even if that child event clears. This information will update only if a child event is seen with an earlier FirstOccurrence. This essentially means the priority child event is the very first child event to enter the group. Customers have specifically asked for this feature.

This is important so that the most relevant information is retained in the synthetic parent event - both for ticketing purposes, as well as for reporting purposes in the historic event
archive.


A variety of other small fixes and enhancements have also been made in this fix pack including:
- A new property to show the number of active alarms at the front of the synthetic parent Summary, rather than at the end.
- A fix to the dismantling of small groups function so that it's based on a historic count, rather than the number of events present at the time.
- A new function to fix the time window to a static value - by prepending the string FX: to the beginning of the ScopeID.


IV99760
To mitigate against CVE-2017-1000100., HTTP GET operations that were performed by libcurl are now performed by libnhttpd.