Product Documentation
Abstract
OMNIbus provides periodic fixes for release 8.1. The following is a complete listing of GA and scheduled fixes for OMNIbus Core Version 8.1 with the most recent fix at the top.
8.1.0.10
| Status | |
|---|---|
|
Fix release date: 12/16/2016 Last modified: 12/16/2016 Status: Recommended Download information |
| APAR | Description |
| IV89106 | If probe-specific environment files exist, the nco_probe wrapper script did not check and source the probe-specific environment files. This problem is now fixed. |
| IV89509 | Gateways perform many SQL select statements with lists of ServerSerials in the where clause. To improve the performance of these queries, an index is now added to the default ObjectServer sql. Existing ObjectServers must be updated manually to benefit from this added index, see the update sql file in the $OMNIHOME/etc/default directory. |
| IV90524 | An installation that is performed as root by using the install_gui.sh script included with Core OMNIbus incorrectly calls the Installation Manager userinst script for a non-administrator installation, instead of the 'install' script for an administrator installation. This incorrect call places various files in an unexpected location, for example the Installation Manager registry file is in $HOME/etc/.ibm/registry/InstallationManager.dat, instead of /etc/.ibm/registry/InstallationManager.dat. The update scripts that are supplied with a fix pack check only the expected location and fail to find the Installation Manager installation location for these types of installations. This issue is now fixed. The update scripts are now modified to check both the expected and erroneous locations so that they can be used for fix pack installations. You do not need to move existing installations. |
| IV91125 | To address possible security issues, the JRE for Tivoli Netcool/OMNIbus V8.1.0 is updated to IBM JRE 7.0 SR9 FP60. |
| IV91244 | Array, table & registertarget definitions are no longer restricted to the beginning of a probe rules file. Now, you can add these definitions anywhere it is appropriate to do so. For example, an array can be defined in the middle of a block of rule processing statements, immediately before use. Also, it is now possible for a file that contains a definition to be included multiple times in the set of rules that are read by a probe. For more information about probe rules files, see the 'Probe and Gateway' documentation. |
8.1.0.9
| Status | |
|---|---|
|
Fix release date: 09/22/2016 Last modified: 09/22/2016 Status: Superceded Download information |
| APAR | Description |
| IV75048 | The Netcool/OMNIbus Administrator can make up to six attempts to authenticate with a process agent when using invalid user credentials. This issue has been fixed so that the Netcool/OMNIbus Administrator only makes a maximum of two attempts to connect to a Process Agent when using invalid user credentials. |
| IV84967 | The MIB manager function to generate test traps sends the OID as the first varbind and the system up time as the second varbind when generating SNMPv2 traps. This does not conform to the RFC 1448 specification which states that system up time should be the first varbind and OID the second for SNMPv2 traps. This APAR modifies the MIB Manager Trap Generator code so it sends up time before OID and conforms to the RFC 1448 specification. |
| IV85380 | A code path has been identified where the ObjectServer can core dump if a SELECT query returns a data set with a large number of rows. This code path is now resolved so the core dump no longer occurs. |
| IV86599 | The intermittent corruption of external procedure arguments, by the Process Agent, is now fixed. |
| IV86613 | A Certificate Validation dialog no longer displays when the Netcool Administrator client connects to an ObjectServer that is configured with SSL communications and where the server certificate contains a subject name that does not begin with the Common Name (CN) attribute. |
| IV87122 | The memory footprint of the uni-directional and bi-directional ObjectServer gateways could unexpectedly grow if event fast track was enabled in a source ObjectServer. The unexpected memory growth is now fixed. |
| IV87274 | The values of the LC_ALL/LC_CTYPE/LANG environment variables are now logged at the top of the log header on UNIX. |
8.1.0.8
| Status | |
|---|---|
|
Fix release date: 07/12/2016 Last modified: 07/12/2016 Status: Recommended Download information |
| APAR | Description |
| IV70937 | The nco_config command will remove the newline character on triggers that contain comments after the "When" clause. This causes the trigger to fail the syntax check. This problem has been resolved. |
| IV72912 | A "ping host" command from a Netcool Administrator on Windows will hang the Administrator process. The problem has been resolved in this fix pack. |
| IV79347 | Probes intermittently failed to connect to the ObjectServer with the following error message in the probe logfile: 'Error: E-UNK-000-000: Server verification failure. Failure Code=1013.' This has now been fixed. |
| IV82539 | The SQL generated by nco_osreport for use by nco_dbinit specifies 'persistent' as the memstore type for all memstores to be created. This problem has been fixed so that memstore type in the generated SQL will be persistent, virtual, or temporary, to match the memstore type in the ObjectServer. |
| IV83155 | A SELECT query can return incorrect results when it contains a clause which compares 2 aggregate functions. The following is an example of a query which can return incorrect results: "select count(*) as CNT,Node, max(Severity) as MAX_SEV, max(Tally) as MAX_TAL from alerts.status group by Node having max(Tally) < max(Severity)" The code has been modified to fix this issue. |
| IV83627 | This fix-pack adds four new features to scope-based event grouping automation. 1. The scope-based event grouping automation is now extended to also clear childless synthetic parents created by the analytics-based event grouping. 2. The scope-based event grouping is now updated to allow a user to modify the ScopeIDParent Summary text in relation to the number of affected subgroups present. Previously it was hardcoded to say "X sites affected". Customers use different things to subgroup by, which are not necessarily sites. This additional property allows users to specify the label, other than "site". The new property is called SEGScopeIDSitesAffectedLabel and has a default value of "site". 3. The scope-based event grouping automation creates journal entries with the underlying children events' details in them. Previously it did this function only for synthetic parent events created for scope-based event grouping. This function is now extended to also perform the same journaling function for the synthetic parent events created by the analytics-based event grouping. 4. The following two properties control whether OwnerUID and OwnerGID propagate from parent events to child events, or not. SEGPropagateOwnerUID SEGPropagateOwnerGID A 0 means it does not, and a 1 means it does. This enhancement adds a third value. A value of 2 for SEGPropagateOwnerUID means that it propagates only OwnerUID if the child event is not owned by anyone i.e. the child has an OwnerUID of 65534 (Nobody). Similarly, a value of 2 for SEGPropagateOwnerGID means that it propagates only OwnerGID if the child event is not owned by any group i.e. the child has an OwnerGID of 0 (Public). This feature also applies to any groups created by the Event Analytics based event grouping. |
| IV84051 | The following two triggers, which are part of the self-monitoring solution, are now modified to drop the insertion of housekeeping synthetic events from the collection layer into the aggregation layer: sm_top_nodes_insert sm_top_nodes_reinsert Housekeeping synthetic events were previously allowed to be inserted into the aggregation layer and might result in large numbers of warning level alerts in the ObjectServer. The $OMNIHOME/etc/update81fp7to81fp8.sql file contains new versions of these triggers. |
| IV84144 | The MIB Manager code is now updated to stop the MIBManager utility from going into a hard loop. Before this update, the MIBManager utility might go into a hard loop when it processed a MIB file that contained the following definition. Unsigned32 ::= Unsigned32 (0..4294967295) The hard loop behavior no longer occurs. |
| IV84416 | The table 'master.correlation_scopealias' table became obsolete in the event grouping extension shipped with OMNIbus 8.1 FP 7. The FP4 to FP 7 update script attempted to drop the table but after the update script ran, the table still existed in the ObjectServer. The 'SEGUseSiteNamePrefix' and 'SEGUseSiteNameCustomText' properties that were added in FP 7 were turned OFF by default in the original FP4 to FP 7 update script. The default for both these properties is that they should be turned ON. The script is now fixed: '$NCHOME/omnibus/extensions/eventgrouping/update/update81fp4to81fp7/update81fp4to81fp7_aggregation.sql'. |
| IV84442 | The ObjectServer is now modified to prevent high profiling times that were previously caused by IDUC v1 clients not retrieving change sets in a timely fashion. Now the IDUC v1 IBM Tivoli Network Manager gateways and native event lists are no longer automatically registered for notification of changes within the alerts.journal table. |
| IV84621 | Issuing the command 'flush iduc' from a SQL trigger can cause the ObjectServer to terminate. Clients which issue 'flush iduc' directly are not impacted. |
| IV84632 | In response to RFE 18860, it is now possible for a probe to failover/failback between an ObjectServer pair where the primary server and backup server have schemas that differ from each other. Previously the probe had to be stopped/restarted in order to adapt to a new schema. This implementation extended the work that was done for APAR IV75451 which was delivered in Tivoli Netcool/OMNIbus 8.1.0 Fix Pack 4, 8.1.0-TIV-NCOMNIbus-FP0004. Similarly as for APAR IV75451, the following schema differences can be successfully handled: * The addition of new fields added to any position in the schema. * The complete removal of fields from the schema. * Fields in the schema that have changed their order. * Fields whose data types have changed. Existing values will be converted if possible, otherwise a default value will be populated. * Fields that have been renamed will be treated as a new column. The previous name will be treated as a field that has been removed. |
8.1.0.7
| Status | |
|---|---|
|
Fix release date: 03/25/2016 Last modified: 03/25/2016 Status: Superseded Download information |
| APAR | Description |
| IV78818 | The de-duplication trigger in the configuration for the default multi-tier aggregation layer type ObjectServer has been modified so that it will not alter the Severity of events that have been suppressed by the ITNM root cause analysis (RCA) mechanism. |
| IV80092 | An issue introduced in Tivoli Netcool/OMNIbus Fix Pack 4 meant indexes were not used by triggers and procedures at all times. This issue has now been fixed. |
| IV80567 | In response to RFE request 81245, additional password checking
functionality has been added to the ObjectServer.
The additional checks allow an administrator to specify that
ObjectServer user passwords cannot contain the user name.
The checks are configured using the PasswordFormat property,
which now includes an additional |
| IV80895 | The JRE for Tivoli Netcool/OMNIbus V8.1.0 was updated to IBM JRE 7.0 SR9 FP30 to address possible security issues. |
| IV81216 | The Aggregation layer self-monitoring log file includes entries for all alerts that it generates as well as those it receives from both AGG_B and any Collection layer ObjectServers. Previously it was ambiguous as to which ObjectServer the alerts were coming from, with respect to the log messages. This fix prepends the ServerName the alert was generated on to the log file message to clarify this. Users who have V8.1 fix pack 6 or older should apply the following file to address this APAR: $OMNIHOME/etc/update81fp5to81fp7.sql The Netcool administrator should review the contents of this file before it is applied. |
| IV81225 | The scope-based event grouping code in OMNIbus/extensions has been extended with configurable properties that can be used to set up the behavior as well as the look and feel of the resulting event groups. The properties provide flexibility and also enable the "one incident = one ticket" scenario. The properties are stored in the master.properties table and can be modified dynamically. The properties include the following features: - Propagate Acknowledged status, ticket number, owner UID and GID to children - Simplify the grouping to a single level for the more simple use-cases - Customize the look and feel of synthetic parent events - Option to populate parent event Node field with Node of first child received - Propagate attributes of synthetic parent events down to their children - Propagate detail of priority child events up to the parent event - Roll up child event details into journal entries in the synthetic parent - Dismantle any groups that do not have the minimum number of events To upgrade scope-based event grouping to use the new properties, see the instructions in the IBM Knowledge Center at http://ibm.biz/seg_docs |
8.1.0.6
| Status | |
|---|---|
|
Fix release date: 01/29/2016 Last modified: 01/29/2016 Status: Superseded Download information |
| APAR | Description |
| IV78816 | The JRE for Tivoli Netcool/OMNIbus V8.1.0 was updated to IBM JRE 7.0 SR9 FP20 to address possible security issues. |
| IV79413 | A password may show up in plain text in a 'create user' error message. This problem has been resolved. |
| IV79952 | The GSKit version has been upgraded to 8.0.50.57 on OMNIbus 7.3.1, 7.4.0, and 8.1.0 to include a fix for a potential security problem. |
8.1.0.5
| Status | |
|---|---|
|
Fix release date: 12/18/2015 Last modified: 12/1/2015 Status: Superseded Download information |
| APAR | Description |
| IV69160 | When a LOOKUP table is empty, the cache file has an incorrect checksum because of a syntax error. This problem has been resolved. |
| IV75714 | If the ProbewatchHeartbeatInterval property is set to a non-zero value, and a probe fails to read its rules file, the probe will deadlock while trying to shutdown if CacheRules is set to 0. If CacheRules is set to 1, the probe will deadlock while trying to read the cached rules file. These deadlocks have been resolved. |
| IV77594 | The probe rules might not retrieve time fields correctly for probes running in 64-bit mode. This problem has been fixed. |
| IV77881 | Probes could fail to shutdown cleanly when not in peer-to-peer failover mode. This has been resolved. |
| IV78263 | The maximum size of the trigger action code block has been updated to 32 KB from 8 KB. The new maximum size is applied automatically when upgrading to the latest fix pack. The fix implemented in APAR IV73963 has been reversed and you can use the full 32 KB available in the SQL procedure's body statement. |
| IV78277 | Faster response time to HTTP POST requests made to the ObjectServer HTTP/OSLC Interface by HTTP clients. This is due to reduced contention between the threads in the request thread pool. |
| IV78667 | The GSKit version has been upgraded to 8.0.50.55 on OMNIbus 7.3.1, 7.4.0, and 8.1.0 to include a fix for a potential security problem. |
| IV78761 | This enhancement automates 3 housekeeping tasks. The first automatically sets ExpireTime for events where it is not set. The second monitors row counts and takes action if thresholds are exceeded. The third de-escalates the Severity of events as they age so that they eventually are removed from the system. All three store relevant thresholds in the master.properties table so that users can modify the behavior of the automated tasks without having to modify any trigger code. The trigger group to which these triggers belong to is initially disabled, as are the triggers themselves. This is a safeguard against unintentional execution of the triggers in a live environment. These triggers should only be enabled in a live environment after full load and functional testing have been carried out in a representative development or test environment. |
| IV79182 | This enhancement modifies the SCALA triggers which are used to send events to the Message Bus Gateway via AEN and affect users of IBM Smart Cloud Log Analysis (LA) with the OMNIbusInsightPack version 1.3.0.2 only. Changes need to be applied to the ObjectServer that the Message Bus Gateway connects to when it is configured to send event data to LA. If the ObjectServer instance was created prior to fix pack 5 being applied, you must run the following SQL file to upgrade the SCALA AEN triggers. If you don't do this, updates will not be forwarded LA: $OMNIHOME/etc/update81to81fp5.sql The systems administrator should review the contents of this file before it is applied If you are using the SCALA ITNM triggers in the $OMNIBUS/extensions/scala directory, you must apply the 'scala_itnm_configuration.sql' file which ships with ObjectServer fixpack 5. Errors due to duplicate entries can be ignored when applying these triggers. |
8.1.0.4
| Status | |
|---|---|
|
Fix release date: 09/14/2015 Last modified: 09/14/2015 Status: Superseded Download information |
| APAR | Description |
| IV61840 | The LDAPTimeout parameter might not time out LDAP authentication requests under the following conditions: - An SSL protocol is being used - A TCP/IP socket level call is delayed - An LDAP search is delayed This can delay the ObjectServer failing over to a backup if it is configured to use multiple LDAP servers and the first one is unresponsive or unavailable. This problem has been resolved. |
| IV67946 | Log file pooling/rolling does not release file handles. This problem has been resolved. |
| IV68107 | The MIB manager garbles the generated rules file when exporting MIBs causing any events processed by these rules to have an unusable OS_EventId. This problem has been resolved. |
| IV68942 | A malloc error was issued when using invalid data in probe rules for the nvp_add function. That message was incorrect and was replaced with the correct error message that hilights the invalid data. |
| IV72682 | When the 'KeepLastBrokenSAF' property is set to '1' and any corrupt records are found during the forwarding of store-and-forward cached alerts, the original SAF file should be retained and renamed to a file with the suffix '.broken'. Due to regression introduced in fixpacks 7.3.0.6 and 7.3.1.2, this was not happening. The regression is also present in fixpacks 7.4.0.5 and 8.1.0.2 and earlier fixpacks of the 7.4 and 8.1 releases. This has now been fixed. |
| IV73109 | The ICU component used by Tivoli Netcool/OMNIbus has been upgraded to version 55.1 to address a potential security problem that is fixed in this version of ICU. |
| IV73123 | The LDAP libraries used by Tivoli Netcool/OMNIbus were updated to TDS version 6.3.1.10 to address potential security issues. Note: Not available for platform HPUXIA. |
| IV73221 | New function to allow redirecting ObjectServer connections to a different ObjectServer (or a different virtual pair). There is a new signal trigger, named pre_connect, which is always called when a client connects, before authentication. There is new sql " alter system redirect connection 'SERVERNAME' " which can only be issued from this new signal trigger. It causes the client to be redirected to that SERVERNAME. Note that the new SERVERNAME must exist in the omni.dat where the ObjectServer resides. |
| IV73279 | The JRE for Tivoli Netcool/OMNIbus V8.1.0 was updated to IBM JRE 7.0 SR9 FP10 to address possible security issues. |
| IV73670 | The version of the IBM Eclipse Help System (IEHS) included in
Tivoli Netcool/OMNIbus has been updated to the latest supported
version (V3.6.2.1). Note that the update means users need to use
the full context root in the URL to access the IEHS help in
Information Center mode ( |
| IV73963 | There is an internal limit of 16K on a 'create procedure' SQL statement. Previously, the system issued an error message for statements that exceeded 32K but would core dump on statements that were between 16K and 32K in size. The code has been fixed to reject a 'create procedure' statement that exceeds 16K and log an error message. |
| IV74587 | Users are not able to run nco_confpack on a machine running Windows 20128 R2. This problem has been resolved. |
| IV74679 | When using the update_silent.sh script as root user to install a Netcool/OMNIbus core fix pack, users were asked to accept the license despite specifying their acceptance of the license on the command line. This issue has now been resolved. |
| IV74891 | If an event is deleted in the Aggregation layer and then deduplicates in the Collection layer, this causes a new event insert in Aggregation with the same ServerName/ServerSerial values. As a result, when the historical gateway sends the new insert to the historical database, the insert fails due to a Unique Constraint or Primary Key error, since the same primary key ServerName/ServerSerial already exists in the database. This problem has been resolved. |
| IV75451 | On reconnection to an ObjectServer, a probe is able to handle certain changes in that server's schema and data stored in its Store-And-Forward (SAF). The following schema differences can be successfully handled: * The addition of new fields added to any position in the schema. * The complete removal of fields from the schema. * Fields in the schema that have changed their order. * Fields whose data types have changed. Existing values will be converted if possible, otherwise a default value will be populated. * Fields that have been renamed will be treated as a new column. The previous name will be treated as a field that has been removed. |
| IV75452 | String expressions can now be used for regular expressions in rules files, rather than just hard coded regular expression strings. See the updated documentation for more details of this and the new -maxtransientregexp property. |
| IV75473 | An extraordinarily large query caused a stack overflow on AIX. Stack usage has reduced to prevent this from happening. |
| IV75482 | An exception is thrown when installing an iFix for a component sharing the same Installation Manager profile as Netcool/OMNIbus core. This issue has now been resolved. |
| IV75484 | Metadata related to HPUX was incorrectly included in the Netcool/OMNIbus core Installation Manager packaging. This issue has now been resolved. |
| IV75494 | The device counter extension in Tivoli Netcool/OMNIbus keeps tracks of the number of nodes it receives events from, and logs a daily count to a log file. If no events are received from a node for 365 days, the node is automatically removed from the count. |
| IV75501 | The Package Group Name label used by the Netcool/OMNIbus core component in Installation Manager has changed from "IBM Tivoli Netcool OMNIbus" to "IBM Netcool Core Components". This is purely a cosmetic change to reflect that there might be more components installed into the profile than Netcool/OMNIbus core alone. This change will only be visible to people performing a fresh installation of Netcool/OMNIbus core fix pack 4 or later. |
| IV75502 | Events breaching the XinY threshold were not getting escalated on deduplication unless SuppressEscl was set to zero. This issue has been corrected and all events that breach the threshold are escalated after you re-import the updated SQL file into the ObjectServer using nco_sql. |
| IV75555 | In response to RFE request 14818, the following new SNMP datatype conversion functions have been added to the Netcool/OMNIbus Probes library: hextimetostring - Converts a space-delimited hexadecimal date and time value into a time stamp string that conforms to the ISO8601 format. hextoascii - Converts a space-delimited hexadecimal string into an ASCII string. decimaltoascii - Converts a space-delimited decimal string into an ASCII string. hextodecimal - Converts a hexadecimal string into a decimal string. You can use it for straightforward conversions with or without optional delimiter arguments. You can also use replacement delimiter arguments for more complicated conversions, for example, to convert a space-delimited hexadecimal IPv4 network address into a dotted decimal address. decimaltohex - Converts a decimal string into a hexadecimal string. You can use it for straightforward conversions with or without optional delimiter arguments. You can also use replacement delimiter arguments for more complicated conversions, for example, to convert a dotted decimal MAC address into standard human-readable IEE802 format. More details on these new functions can be found in the IBM Netcool/OMNIbus Knowledge Center. |
| IV75641 | This update includes fixes for the ScopeAlias grouping logic, SiteNameParent event creation, and ticket number propagation. The following enhancements are also included: support for multitiered environments; being able to specify the quiet period for different types of event (and not simply use the global default value); an option to specify whether or not to automatically propagate Acknowledged status to child events; an option to specify whether or not to automatically propagate the ticket number to unticketed, unsuppressed child events; and a template Probe rules and Impact policy to help users implement custom scope-based event grouping. An SQL file and README are provided for updating an existing implementation of scope-based event grouping from the first GA release (8.1 Fix Pack 3) to this version released in 8.1 Fix Pack 4. |
| IV75687 | On AIX, the ObjectServer process size increased every time gateway synchronization occurred. This issue has now been resolved. |
| IV75900 | Upgrade to GSKit version 8.0.50.47 on OMNIbus 7.3.1, 7.4.0, and 8.1.0. This is due to a potential security problem that was fixed in this version of GSKit. |
| IV76107 | Events breaching the XinY threshold are not escalated on deduplication unless SuppressEscl is set to zero. The 'xiny_on_reinsert' trigger has been modified so that escalation only happens on either normal (0) or suppressed (4) events. |
8.1.0.3
| Status | |
|---|---|
|
Fix release date: 04/10/2015 Last modified: 04/10/2015 Status: Superseded Download information |
| APAR | Description |
| IV69143 | The LDAP libraries used by Tivoli Netcool/OMNIbus were updated to SDS version 6.3.1.9 to address potential security issues. |
| IV70540 | The GSKit component used by Tivoli Netcool/OMNIbus is upgraded to version 8.0.50.41. This is done to address a potential security problem that is fixed in this version of GSKit. |
| IV71122 | The JRE for Tivoli Netcool/OMNIbus V8.1.0 was updated to IBM JRE 7.0 SR8 FP10+IV70681 to address possible security issues. |
8.1.0.2
| Status | |
|---|---|
|
Fix release date: 03/10/2015 Last modified: 03/10/2015 Status: Superseded Download information |
| APAR | Description |
| IV51280 | The indexes implemented in OMNIbus prevent some post-database action based triggers from functioning correctly. The problem is that indexes are updated after the post insert action has been fired. For example, it is not possible to find the new row using the Serial field in an after insert trigger because the index on the Serial field has not been updated. Note, the new row variable holds a reference to the row which can be used instead. This problem has been corrected. |
| IV62328 | Problems occurred after changing an SQL parameter from IN to Out within procedure calls. The problem caused the Object Server to crash. This problem is resolved. |
| IV64024 | The client profiling code was taking locks unnecessarily. This issue potentially limited performance. The resolution of this issue required no functional change but performance could improve. |
| IV64030 | If an integer value in a property file starts with a zero, the value was treated as octal-based rather than base 10. This problem has been resolved. |
| IV64823 | When using registertarget/settarget, the server name value from the registertarget/settarget directives should be on the insert statement in the log file. This problem has been resolved. |
| IV64841 | When the CREATE INDEX command was used to create an index, the index was not used by existing triggers and procedures. Also, the debug log for each table scan was no longer created. This issue has been fixed. |
| IV65579 | The shared library version information will now be included when a probe is run with the -version option. It will also be added to the log header that is written out with each new log file. |
| IV68196 | This APAR contains changes to the triggers that configure the integration with the IBM Operations Analytics - Log Analysis product. The changes are for use with the Network Manager Insight Pack. After you apply this file, the triggers prevent events from being forwarded to IBM Operations Analytics - Log Analysis until the events are enriched by data from the Network Manager product. (To enrich events, Network Manager populates the NmosObjInst column of the ObjectServer alerts.status table during event processing; the Insight Pack requires that the NmosObjInst column be populated.) The trigger runs every 5 seconds. If the events are not enriched 20 seconds after the trigger has run, the events are forwarded to IBM Operations Analytics - Log Analysis without NmosObjInst data. |
| IV68690 | The syntax probe was unable to validate probe-specific rules functions. This problem has been fixed. A corresponding fix to any probe which uses probe-specific functions is required. |
| IV68940 | When the CacheRules property was set to 1, the lookup table was not written properly after a -HUP command was issued. This problem has been resolved. |
| IV69161 | If events occur at the same time within the same scope of influence, those events are probably related to the same incident or outage. Out-of-the-box event grouping helps you to organize and group your event data by incident, based on the setting of a scope. You can set ScopeID in the Probe rules or through enrichment after insert, which will cause your events to automatically group together based on this scope in the Event Viewer. |
| IV69293 | The JRE for Tivoli Netcool/OMNIbus V8.1.0 was updated to IBM JRE 7.0 SR8 FP10 to address possible security issues. |
| IV69933 | Environment variables can now be specified in properties that expect a path string. This change affects the following properties: ConfigFile, PropsFile, RedirectFile and TicketDir. |
| IV69934 | The probe HTTP REST interface has a new URL that you can use to reload rules files. Success or failure messages are returned in the HTTP response, rather than an event being generated. The URL is as follows: hostname:port/probe/common/reloadrules method: put payload: {"reloadruleflag": 1} Any syntax error in the rules file is returned in the HTTP response. |
8.1.0.1
| Status | |
|---|---|
|
Fix release date: 09/22/2014 Last modified: 11/10/2014 Status: Superseded Download information |
| APAR | Description |
| IV55784 | If a pre-insert trigger also does an insert into the same table, the two events can end up with the same Serial value if the Serial number wraps during the insert. This problem is resolved. |
| IV56455 | The failover thread of a probe running in slave mode in a peer-to-peer failover setup might hang. This could result in the probe failing to send events on if it loses contact with the master probe of the peer-to-peer pair. It could also result in unbounded memory growth of the slave probe as it buffers all events without flushing the buffers. This issue has been fixed. |
| IV56609 | The primary and backup ObjectServers might not resynchronize properly if the primary ObjectServer fails again before a resynchronization is complete. This problem has been resolved. |
| IV59634 | A timeout can occur between AEN clients and the ObjectServer when using a firewall bridge. A new trigger, aen_heartbeat, is added to automation.sql. To resolve the problem, enable this trigger. |
| IV59959 | The GSKit component used by Tivoli Netcool/OMNIbus is upgraded to version 8.0.50.20. This is done to address a potential security problem that is fixed in this version of GSKit. |
| IV60193 | The ObjectServer HTTP/OSLC Interface now uses chunked transfer encoding to stream large result payloads to HTTP/1.1 clients. This reduces the amount of memory consumed for these large responses and improves overall interface performance. Certain chunking-related features, such as the optimal chunk size, can be changed if required in the "chunking" section of the server interface configuration file, $OMNIHOME/etc/restos/servercfg.json. |
| IV61491 | MIB Manager might fail to import an MIB if the MIB contains non-ASCII characters and MIB Manager is not running in a UTF-8 locale. The import completes without errors or warnings but the MIB is not displayed in the 'MIB Modules' tab on MIB Manager. This problem has been resolved. |
| IV61642 | On shutdown, there was a small chance that the ObjectServer would dump core. The dump happened after the database files were written, so there was no risk to data. This problem is fixed. |
| IV62192 | MIBs containing extra spaces failed to import properly resulting in orphans. This problem has been resolved. |
| IV62891 | The nco_config updates a Boolean column when selected. This problem has been resolved. |
| IV63168 | Assigning an integer value to a string column in a JSON row set payload for an ObjectServer table that was sent as part of an HTTP POST to the servers HTTP interface, caused the server to crash. This issue is now fixed. The type mismatch is now correctly handled and a HTTP 400 (Bad Request) is returned with a JSON error payload to indicate a type mismatch. |
| IV63169 | The JRE installed for use by Netcool/OMNIbus has been upgraded to 7.0 SR7 FP1 (7.0 SR6 FP1 on HP-UX). The security related files java.security, US_export_policy.jar, and local_policy.jar have been marked as configuration files so that future updates to the JRE will retain any changes made to these files. When upgrading from 8.1.0.0 any changes made to java.security, US_export_policy.jar, and local_policy.jar will be overwritten. These changes will need to be reapplied after the installation of 8.1.0.1. If you are upgrading from 8.1.0.0 and have made changes to java.security, note that the new JRE contains some extra values for the package.access and package.definition properties. Take care when reapplying changes to this file. If you need to roll back to 8.1.0.0 and have made changes to java.security, US_export_policy.jar, or local_policy.jar you must delete or rename these files before attempting to roll back. |
| IV63203 | In order to improve consistency between Netcool applications, the Process Agent (nco_pad) now supports -messagelog, -messagelevel, and -maxlogfilesize arguments. The additional arguments replace -logfile, -debug and -logsize arguments which have been deprecated and will no longer show in the default help text. Furthermore, support for a properties file has also been added to nco_pad and a default properties file is supplied ($OMNIHOME/etc/nco_pa.props). All properties in the file are disabled by default. A -propsfile argument has been added to nco_pad to enable a properties file path to be specified via the command line. During startup nco_pad will output server settings to the message log at information message level. More details on the new nco_pad properties and arguments can be found in the IBM Knowledge Centre at: http://www-01.ibm.com/support/knowledgecenter/SSSHTQ_8.1.0/com.ibm.netc… |
| IV63212 | RFE 4780: The default Resync.LockType property of Uni-Directional and Bi-Directional ObjectServer Gateways (nco_g_objserv_uni, nco_g_objserv_bi) has changed from 'FULL' to 'PARTIAL'. |
| IV63220 | The use of HTTPS communication between the ObjectServer and a JazzSM registry no longer experiences failures when chunked encoding is in use. The problem was caused by short reads of data from the underlying SSL library that was not correctly identified in the HTTP library. These short reads are now identified and processed correctly. |
| IV63222 | RFE 19562: Property to disable probe details. A new common property called DisableDetails and command-line options called -disabledetails and -enabledetails have been added to Netcool/OMNIbus probes. You can use these to disable the generation of alerts details instead of editing rules files manually. |
| IV63225 | The nco command fails to start on some operating systems. This problem has been resolved. |
| IV63228 | nco_pad currently uses an older ctime() based timestamp for messagelog entries and this is inconsistent with the timestamps generated by applications that use NLog() which have an ISO8601 format. This enhancement updates nco_pad message log to use ISO8601 and provides an OldTimeStamp property and -oldtimestamp argument to enable legacy timestamp should they be required. |
| IV63229 | Administrator did not show options for manipulating indexes when connecting to a V8.1 ObjectServer. This issue has been fixed. |
| IV63230 | During migrations from previous versions to Netcool/OMNIbus V8.1 on UNIX and Linux operating systems, the desktop configuration files were incorrectly copied to $NCHOME/omnibus/etc instead of $NCHOME/omnibus/desktop. This issue has been fixed. The desktop files are now copied to the correct directory. |
| IV63230 | UPGRADE.SH did not migrate over configuration files in $OMNIHOME/etc/restos or migrate the docroot and uipreview subdirectories in $OMNIHOME/etc/restos. This is resolved. |
| IV63234 | If a iduc evft command was issued from a temporal trigger, there was a small chance that a core dump might occur. This issue has been fixed. |
| IV63236 | If a value outside the range 0 to 65535 is entered in to a port field in the Initial Configuration Wizard the value is silently altered to be within the range. The user is now shown an error message. If a long installation path is entered into the Initial Configuration Wizard, the ObjectServer pages might not display correctly. This issue has been fixed. When run in text mode the Initial Configuration Wizard did not limit the length of server names. This has been fixed. The Initial Configuration Wizard's list of configuration actions has been reformatted to increase the separation between the component name and the action. The Initial Configuration Wizard error messages for 'port in use' and 'zero port not allowed for the PA' were not displayed correctly. This has been fixed. When run in GUI mode the Initial Configuration Wizard would error when the contents of a required integer port field were deleted. This has been fixed. Fixed a minor typo "Netcoo" -> "Netcool" in the Process Agent edit page. |
| IV63237 | Within MIB Manager, if help content is selected from the menu items, the expected help files are not displayed. Instead, a "Topic not found" message is displayed. This issue has been fixed. |
| IV63248 | If a non-zero IDUC port was specified for an ObjectServer, it was not set as a command-line argument in the Process Agent configuration file (nco_pa.conf). This issue has been fixed. |
| IV63249 | The properties dialogue Web GUI Version selection control of the AEN client, nco_aen, contained only out of support versions of the Web GUI. This has been updated to contain currently supported versions. |
| IV63757 | The following Log File Pool properties were added to the default NCOMS.props file: LogFileUsePool, LogFilePoolSize, LogFileUseStdErr. |
| IV63758 | Some fields of the Restrict Rows section of the desktop View Builder did not work correctly. These fields restrict the number of rows on display in the event list. Minimum Maximum Default After you entered values in these fields, they defaulted back to 1. The same occurred after you used the arrows to change the values. This problem has been fixed. |
| IV63759 | After you changed the value of the event_flash_time property in the ~/.omnibus/prefs file, then event list freezes. This problem has been fixed. |
[{"Product":{"code":"SSSHTQ","label":"Tivoli Netcool\/OMNIbus"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Netcool\/OMNIbus","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27042312