Troubleshooting
Problem
Tivoli Netcool/OMNIbus 7.4 is not compatible with the Tivoli Network Manager 3.9 installer on Linux and Solaris platforms. To integrate Tivoli Netcool/OMNIbus 7.4 and Network Manager 3.9 on Linux or Solaris, you must install and configure Tivoli Netcool/OMNIbus before installing Network Manager 3.9 using the Tivoli Netcool/OMNIbus installer, and the configuration script provided later in this note.
Symptom
When attempting to install Tivoli Netcool/OMNIbus 7.4 using the Network Manager 3.9 installer on Linux, the installation aborts during the DE bootstrap portion of the Tivoli Netcool/OMNIbus installation, and the Tivoli Netcool/OMNIbus log file contains a java stack showing the message that DE is already in use by another process.
When attempting to configure Tivoli Netcool/OMNIbus 7.4 using the Network Manager 3.9 installer on either Linux or Solaris, the installation aborts with an error code 8 and a message that installing the Netcool Knowledge Library failed. An examination of the temporary file given in the error message shows a java stack with a NoClassDefFoundError message.
Resolving The Problem
The Linux version of Tivoli Netcool/OMNIbus 7.4 uses a newer version of DE than Network Manager 3.9. When Tivoli Netcool/OMNIbus is installing, DE attempts to upgrade itself, but fails because the Network Manager 3.9 installer has a lock on the DE files. To avoid this problem, install and configure Tivoli Netcool/OMNIbus 7.4 before installing Network Manager 3.9, and then select "connect to an existing OMNIbus on another server" in the "Select components to install" screen of the Network Manager 3.9 custom installation step. The Network Manager 3.9 installation can connect to a local Tivoli Netcool/OMNIbus installation by using the system's host name in the Tivoli Netcool/OMNIbus server host name field of the "Connect to an existing ObjectServer" screen.
The Linux and Solaris versions of Tivoli Netcool/OMNIbus 7.4 lay down two JREs within the Tivoli Netcool/OMNIbus installation - one 32 bit and one 64 bit. The ConfigOMNI script used by the Network Manager 3.9 installer does not handle multiple JREs, and will fail causing the error described above. Attached to this note is an upgraded copy of the ConfigOMNI script that works in that environment and can be run manually.
The script requires an sql file "create_itnm_triggers.sql". The script expects the sql file to be in one of the following folders:
$NCHOME/precision/scripts/create_itnm_triggers.sql
$SCRIPTDIR/../data/create_itnm_triggers.sql
$SCRIPTDIR/../PrecisionIP/scripts/create_itnm_triggers.sql
This script must be copied into one of the folders mentioned (folders can be created if necessary). The sql can also be run manually against the objserver.
$NCHOME/omnibus/bin/nco_sql -server <objectserver_name> -user <username> -password <password> < <path_to_file>/create_itnm_triggers.sql
Documentation for using the ConfigOMNI script can be found by running the script with no arguments, or at the following url:
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21615671