Name: 7.2.0.1-TIV-NCOMNIbus-FP0001
Enter the following command to install this fix interactively, replacing the arch placeholder with the string identifying your platform:
$NCHOME/install/ncisetup -install 7.2.0.1-TIV-NCOMNIbus-arch-FP0001.jar
Enter the following command to install this fix non-interactively, replacing the arch placeholder with the string identifying your platform:
$NCHOME/install/ncisetup -install 7.2.0.1-TIV-NCOMNIbus-arch-FP0001.jar -silent
Extract the contents of 7.2.0.1-TIV-NCOMNIbus-win32-FP0001.zip into a temporary location, and double-click setup.exe to install this fix.
The following defect solutions are included in this release:
The ObjectServer's memory usage previously increased when processing commands containing a WHERE condition that compared the string returned by a SQL function with a list comparison operator. The following command is an example of the type of SQL that caused the problem:
SELECT Identifier FROM alerts.status WHERE substr( Node, 1, 2 ) IN ( 'aaaa', 'bbbb');
When using the nco_confpack -import command to import classes, if there are classes with identical class IDs but different class names on the source and target ObjectServer, an ID mismatch error will be raised. To overwrite the class name on the target ObjectServer, use the -force command-line option to suppress the error message.
The ObjectServer no longer core dumps when combining the results of a string function with the NOT LIKE comparison operator.
It is now possible to define a cache filter condition that should be used by an ObjectServer writer when it attempts to refresh its destination table cache at the start of processing a batch of IDUC updates. This filtering is useful in silo-oriented deployemnts where the uni-directional ObjectServer gateway runs locally to the source server. The destination server is a consolidation of events from multiple locations and pulling the cache details for all rows is not really necessary.
The cache filter is set for an ObjectServer gateway by using the table replication definition file, as shown in the following example:
REPLICATE ALL FROM TABLE 'alerts.status'
USING MAP 'StatusMap'
CACHE FILTER 'ServerName IN (\'NCOMS_P\',\'NCOMS_B\')' ;
Both the uni-directional and bi-directional ObjectServer gateways will raise two new signals within the connected ObjectServers to indicate the start and finish of a resynchronisation operation. The two new ObjectServer signals are "gw_resync_start" and "gw_resync_stop", and they provide additional information to an automation about the nature of the ObjectServer's role in the resynchronisation, such as whether it is the master or slave of the operation. Both of the signals have the following signal arguments available within an attached automation:
gateway_name: The name of the gateway that is starting or finishing the resynchronisation; for example, NCO_GATE.
node: The host name of the machine that the gateway is running on.
at: The time at which the resynchronisation was started and finished.
is_master: A boolean that indicates whether the local ObjectServer is the master or slave of the resynchronisation.
The "install-patch-1", "install-patch-2" and "install-patch-3" patches are obsolete and can no longer be installed. This prevents potential issues when installing other patches.
Previously, the use of the following statement in a deduplication trigger caused the internal value of the Serial to be corrupted:
set row old = new;
This has been fixed.
Previously, if a realtime client could not read the IDUC messages sent by the ObjectServer in a timely manner, the send buffer on the ObjectServer would fill up and the send operation would block until the client either resumed reading or was disconnected from the ObjectServer. This has been resolved.
Previously, during an nco_confpack export on Windows, a case sensitive match was performed on the file and directory names specified in exclusions.xml file. However, file and directory names on Windows are not case sensitive.
This has been fixed. The match performed for exclusions.xml on Windows platforms is no longer case sensitive.
The ObjectServer migration from 3.6 to 7.2 using UPGRADE.sh was not migrating the Tools database properly. This is now fixed
.Now the migration of the Tools database is done as follows
: -All 7.2 Tools.* tables entries are copied to the migrated ObjectServer
-Only those Tools.* tables entries from 3.6 will be copied to the migrated objectserver
which are not present in 7.2 Tools.* tables.
-If any Tool entry has exactly the same entry in 3.6 and 7.2, only one entry is retained
from 7.2.
-If any Tools.* tables entry in 3.6 has the same primary key as the 7.2 entry, but has a
different actual entry, then that value will be copied into migrated ObjectServer by
changing primary key value. Changes to the primary key will be logged in the
nco_os_migrate.log file and related Tools tables will be changed accordingly during
migration.
Before this fix, for some classes with duplicated class names, nco_confpack could only list, export and import one class entry for them. Now all classes on the source ObjectServer can be exported and then imported to the target ObjectServer, regardless of whether their names are duplicated. The list file generated by nco_confpack using the -list option has both Class Id and Class Name for Classes to identify individual classes.
The "When" condition clause of a temporal trigger was being stripped out when importing this trigger to a target ObjectServer. This problem has now been fixed. The condition clause is now imported properly.
Probes were logging their encrypted properties in plain text when debug logging was switched on and the log file rolled over. They now log their encrypted properties as "*********".
Encrypted properties and the keyfile property entry could not contain any envronment variables (for example, OMNIHOME) as part of their path. They are now expanded correctly.
Previously, the linux2x86install script would not install the startup service in the correct format for SuSE Linux. This was partly due to specific Red Hat functions being used in the "nco" service script
.The service script has now been modified to use SuSE specific functions as well as Red Hat ones. The install script now distinguishes between different types of Linux and either includes or discards sections of the "nco" service script based on the type of Linux being used
.Any lines that are specific to either Red Hat or to SuSE Linux are now enclosed in comment lines as follows
: ### REDHAT ONLY
<Red Hat specific lines>
...
### END REDHAT ONLY
### SUSE ONLY
<SuSE specific lines>
...
### END SUSE ONLY
Do not nest the "REDHAT ONLY" and "SUSE ONLY" lines.
Transient views and filters (created with NCOELCT.EXE) are no longer added to view/filter drop down boxes unless "Keep Window" menu option selected.
The transient event list (nco_elct) now runs on a slow network without issues when other event lists (nco_event) are running.
If a probe connected to an ObjectServer just as the server was starting up or shutting down, the probe could enter SAF mode and not leave it. This has been fixed.
Previously there was a problem with menu options selected from a transient view window that had been launched by NCOElct on Windows. If, for example, the freeze option was selected from the pull down menu, the Event List would crash and need restarting. All pull down menu options now work correctly from the transient view.
The nco_g_tivoli_eif gateway was failing to start due to a race condition. This has been fixed. Also fixed was an issue whereby gateway watch messages occasionally caused the gateway to fail.
The UNIX Filter Builder has been extended to allow more advanced conditions to be created. The Filter Builder allows the construction of predicates of different levels of complexity. The existing 'Simple' and 'Complex' types are restricted to predicates of the form 'ColumnName operator expression'. The new 'Freeform' type permits you to enter an arbitary predicate. This allows the advanced features of the v7 ObjectServer SQL to be used. As each predicate is edited, it is validated by the ObjectServer. Individual predicates are built into a complete condition as before.
When running most components on AIX 6.1, the following error was generated
."Error: Unknown target platform : AIX
Using the default program setting."
This has now been fixed.
In the Unix Event List, when the user attempted to perform a significantly large command, such as deleting 30,000 events, the Event List would disconnect and the tool would not run
.This was due to the use of a fixed-size memory pool for Sybase connections in the Event List. When a tool is used that is too large to fit into the memory pool, a memory error occurs
.The use of a memory pool has been disabled by default. The system now supplies the Event List's memory requirements. If necessary, the memory pool can be reactivated by setting the NCO_MEM_POOL_SIZE environment variable to a minimum of 1048576 (1 megabyte).
The UNIX Filter Builder has been extended to allow more advanced conditions to be created. The Filter Builder allows the construction of predicates of different levels of complexity. The existing 'Simple' and 'Complex' types are restricted to predicates of the form 'ColumnName operator expression'. The new 'Freeform' type permits you to enter an arbitary predicate. This allows the advanced features of the v7 ObjectServer SQL to be used. As each predicate is edited, it is validated by the ObjectServer. Individual predicates are built into a complete condition as before.
nco_igen did not run on AIX 6 unless the '-arch' option was specified. nco_igen will now run without this option, and will create $NCHOME/etc/interface.aix5 which is still used by other programs.
The filter builder no longer drops the last item from the IN list within SQL statements.
This bug occurred when a probe was connected to a failover ObjectServer pair and was configured such that SAF and polling were enabled. If the primary ObjectServer went down then the probe would crash when receiving a HUP signal. In the fixed version, it now correctly reloads its rules files when connected to the backup server as well as the primary server.
This fixes a rare condition in the process agent (PA) logging system. If an external process of the PA logged a message to the PA's log file at the exact point that it rolls over, the PA would continue to write to the "_old" log file instead of the new log file. This would continue to happen until the system's maximum file size was reached, at which point the PA would crash. This no longer happens.
| nco_libOpl | 5.10.27 |
| nco_libnobjserv | 5.10.29 |
| nco_libniduc_client | 5.10.27 |
| nco_libnetcool | 5.10.29 |
| nco_os_migrate | 5.10.27 |
| nco_objserv | 5.10.29 |
| nco_proxyserv | 5.10.27 |
| nco_libDaemon | 5.10.27 |
| nco_desktop_dll | 5.10.27 |
| nco_libngtk | 5.10.29 |
| nco_omnibus_scripts | 5.10.29 |
| nco_libniduc_server | 5.10.31 |
| nco_elct | 5.10.27 |
| nco_libnmemstore | 5.10.31 |
| nco_libngobjserv | 5.10.31 |
| nco_libnipc | 5.10.27 |
| nco_eventlist | 5.10.27 |
| nco_conductor | 5.10.27 |
| nco_patching | 5.10.29 |
| nco_g_objserv_uni | 5.10.32 |
| nco_g_objserv_bi | 5.10.32 |
| nco_confpack | 5.10.29 |
| nco_libnsecurity | 5.10.29 |
| nco_libncmd | 5.10.31 |