Tivoli Netcool/OMNIbus 7.3.0 Fix Pack 5, 7.3.0-TIV-NCOMNIbus-FP0005

Download Description

This is a cumulative fix pack for Tivoli Netcool/OMNIbus version 7.3.0.

7.3.0-TIV-NCOMNIbus-FP0005 Fixes
====================================

IZ89336
Not true WHERE clauses are not being optimized correctly.
Example:
where not true and Severity = 2
where not not true and Severity = 2
where not not not true and Severity = 2


IZ89804
A probe would randomly fail to connect to an Object Server and
would report server validation errors in the log. This issue has
been fixed.


IZ89246
APAR IZ89246: It is not possible to prevent a UNIX Process Agent
(nco_pad) from expanding environment variables within external
action command line strings sent from an ObjectServer.
The UNIX Process Agent (nco_pad) now applies UNIX style quoting
rules that allow environment variables to be expanded or
preserved based on quoting. The quoting rules allow all possible
strings to be represented. Scanning the string from left to
right:-
* Single quotes within double quotes have no special meaning.
* Double quotes within single quotes have no special meaning.
* Environment variables within single quotes are not expanded.
Examples:-
(A fixed width font will make this information easier to read as
this requires a mixture of single and double quotes.)
Passing an argument of:-
$PATH
causes $PATH to be expanded because it is not enclosed in single
quotes.
Passing an argument of:-
'$PATH'
does not cause $PATH to be expanded because it is enclosed in
single quotes.
If the string '$PATH' (with single quotes) is required to be
output, then we use:-
"'"'$PATH'"'"
Reading from left to right we encounter a doubled string
containing a single quote, so the single quote is output.
We then encounter a single quote string containing $PATH, so
$PATH is output without being expanded.
Next is a double quoted string containing a single quote, so the
single quote is output.
This gives an output of:
'$PATH'
with no expansion, as required.
The same behaviour should be seen when trying the commands at a
UNIX command prompt, as follows:
$ echo "'"'$PATH'"'"
'$PATH'
The expansion behaviour on Windows has not been modified.


IZ93135
Previous code changes caused regression in the syntax checking of
the lookup(), exists() and scanformat() statements. Also the use
of '$*' on the right hand side of an assignment statement
incorrectly caused a syntax error to be reported. These errors
have now been fixed.


IZ83167
When a GID is set in a procedure the GID would always be 0 no
matter what the set GID was.
This has been fixed. The set GID is the GID used.


IZ89652
Duplicate entries in the alerts.journal table can be created by
the WebGUI. A new trigger, deduplicate_journal, has been created
to resolve the problem.


IZ90120
nco_pad crashes on AIX machines configured with multiple network
interfaces. This problem has been resolved.


IZ90590
The bi-directional gateway between two ObjectServers is not
forwarding the journal entries correctly. This problem has been
resolved.


IZ90595
Log files created using the 'create or replace file' SQL command,
or via the Administrator (nco_config) did not roll over when they
reached their defined maximum size on Windows 2008. This problem
has been fixed.


IZ90998
The ObjectServer crashes when running SQL syntax check from
nco_config. This problem has been resolved.


IZ91033
If you use a row parameter in an SQL procedure, the procedure
might be removed if the table is altered from which the row
originates (such as adding or removing a column).
create or replace procedure test_proc ( in myrow row of
alerts.status )
begin
write into logger values ( myrow.Node );
end;
alter table alerts.status add column newcol int;
The alter table command will result in the procedure being
removed.


IZ91353
If you install 7.3.0 FP5 on a base level of OMNIbus 7.3.0, the
$NCHOME/jre directory will not be created. However, if you have
an older fix pack already installed then the $NCHOME/jre
directory will not be removed.


IZ91625
The ObjectServer will core if the "IN ARRAY" syntax is used while
the ObjectServer is running with MessageLevel debug. This
problem has been resolved.


IZ92035
Due to other code changes introduced in fixpack 4, a probe would
crash if the rules contained a details() statement which was
followed by a genevent() statement further down the rules
processing. This issue has been fixed.


IZ92158
Gateway Updates and Inserts are logged incorrectly under certain
conditions. With this fix the update and insert counts will
reflect the actual updates and inserts counts during a gateway's
IDUC cycle.


IZ87156
A login with a blank password is authenicated when LDAP is
configured. A blank password now fail authentications.


IZ88638
When the DeleteLogging configuration property is set to TRUE, the
ObjectServer exited with a core dump when it attempted to write
an entry to the deletes log file. This only happened on some
operating systems, such as Solaris. The issue has been fixed.


IZ93232
The query optimizer was not optimizing like OR/AND queries.
Example:
... where Node like 'com' or Node like 'sol'
should be optimized to:
... where Node like any ('com','sol')


IZ94582
The memory growth of probes upon first SIGHUP is reduced when
using large lookup tables and there is little or no change to the
data in the lookup tables since they were last read.


IZ91372
When a file created from the SQL interface reached its maximum
size for the first time after an ObjectServer has restarted, it
did not roll over to the next version correctly. This issue has
been fixed.


IZ94560
The ObjectServer cored if a value originating from a row variable
was passed into a procedure as an "in out" argument.
To resolve this problem, make sure you have two different
variables: one in-variable and one out-variable.


IZ94812
A memory leak occurred with string-to-time functions issued by
probe rules or ObjectServer SQL commands. This memory leak has
been fixed.


IZ95387
Probe updates on deduplication were not reflected in an alternate
ObjectServer when the registertarget() and genevent() probe rules
were used. This has been fixed.


IZ95056
If a user creates a trigger that has a nested sub select of depth
2 or more, any variables that they want to use inside the deepest
level will not be found by OMNIbus. This was due to incorrect
passing of variables during subsequent sub selects. This problem
has been resolved.


IZ95606
The EIF include files provided under the extensions directory
that support ITM integrations for virtual management and
predictive analytics have been upgraded to work with the new EIF
v10.0.0 probe release.


IZ92421
After a reboot or process agent restart ProcessAgent to
ProcessAgent communications would not be re-established properly.
The first external action request sent to a newly restarted
ProcessAgent could be lost. This has been fixed.


IZ95999
When installing probes or gatesways on Windows using
nco_install_integration.vbs, an error would occur if a response
file was given using a path with a space in it. This has been
fixed.


IZ95859
A new gateway property has been added, which will allow
alerts.details and alerts.journal to be passed up the tiers in
the multi -tier setup. The new property is called
IgnoreStatusFilter in the group Gate.Reader. If it is set to true
then the alerts.status filters are ignored when finding new rows
for alerts.details and alerts.journals to be passed across a gateway.

In addition to this gateway property the follow steps need to be
taken to allow alerts.journal and alerts.details to be forwarded to
the aggregation layer:
For alerts.journal, modify the agg_new_row trigger at the aggregation layer to remove the remade server name and server serial. This is achieved by removing the following lines -
set new.ServerName = getservername();
set new.ServerSerial = new.Serial;

In the gateway table replication file (C_TO_A_GATE_P_1.tblrep.def
and C_TO_A_GATE_B_1.tblrep.def) replication for the alerts.journal
and alerts.details tables must be changed from "ALL" to
"INSERTS, UPDATES".
See the alerts.status table as an example.
This will block delete operations from being sent up to
aggregation layer after the alerts.journal and alerts.details
have been cleared from the collection layer.

IZ96030
Memory usage reported by %OplStatsMemoryInUse property in probe
rules file was returning 0 KB on some versions of HP-UX 11i. This
has been fixed.


IZ90073
Probes may set the ProbeSubSecondId incorrectly when LastOccurrence
is set in the rules file. Refer to the technote here for information
on resolving the issue:
http://www.ibm.com/support/docview.wss?uid=swg21469238


IZ92957
Updates were made to the default rules file provided for integration
with Tivoli Application Dependency Discovery Manager (TADDM).

These updates are as follows:

@Identifier
Concatenate 'attribute_name' + 'old_value' + 'new_value' to
distinguish events of the same type on the same object+attribute
combination. These three tokens are optional. Not all TADDM events
will contain these tokens.

@Summary
Improve readability: No longer prefixed with $object_name and
$attribute_name.

@FirstOccurrence, @LastOccurrence
Use incoming event data rather than local time.

@Severity
Use incoming $severity on event otherwise default to '1'.

@BSM_Identity
Set this column value for use by
Tivoli Business Services Manager (TBSM).
By default this setting is commented out. Uncomment these lines
if integration with TBSM is desired.

NOTE: Applying the fix pack will overwrite the current rules file
at NCHOME/omnibus/extensions/taddm/tivoli_eif_taddm.rules without
prompting the end user.