error messages guide - ibm - united states and follow the instructions. ibm support assistant the...

Netcool/OMNIbusVersion 7 Release 3

Error Messages Guide

SC14-7612-00

NotesBefore using this information and the product it supports, read the information in Notices on page 469.

This edition applies to version 7, release 3, modification 1 of IBM Tivoli Netcool/OMNIbus (product number5724-S44) and to all subsequent releases and modifications until otherwise indicated in new editions.

Copyright IBM Corporation 2011.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . . . vIntended audience . . . . . . . . . . . . vWhat this publication contains . . . . . . . . vPublications . . . . . . . . . . . . . . vAccessibility . . . . . . . . . . . . . . viiTivoli technical training . . . . . . . . . . viiSupport information . . . . . . . . . . . viiConventions used in this publication . . . . . viii

Chapter 1. Error messages generated bythe server-side components . . . . . . 1ALD . . . . . . . . . . . . . . . . . 1APM . . . . . . . . . . . . . . . . 10AUT. . . . . . . . . . . . . . . . . 15BRI . . . . . . . . . . . . . . . . . 18CHE. . . . . . . . . . . . . . . . . 41CMD . . . . . . . . . . . . . . . . 42DBI . . . . . . . . . . . . . . . . . 43ETC . . . . . . . . . . . . . . . . . 50GOB. . . . . . . . . . . . . . . . . 60GTK . . . . . . . . . . . . . . . . 101IDC . . . . . . . . . . . . . . . . 144IDS. . . . . . . . . . . . . . . . . 150IVM . . . . . . . . . . . . . . . . 163OAM . . . . . . . . . . . . . . . . 181OBJ. . . . . . . . . . . . . . . . . 185OBX . . . . . . . . . . . . . . . . 187POS . . . . . . . . . . . . . . . . 213PRO . . . . . . . . . . . . . . . . 214PRX . . . . . . . . . . . . . . . . 220REG . . . . . . . . . . . . . . . . 230SEC . . . . . . . . . . . . . . . . 238

STB. . . . . . . . . . . . . . . . . 244STK . . . . . . . . . . . . . . . . 249STO . . . . . . . . . . . . . . . . 256STR . . . . . . . . . . . . . . . . 259

Chapter 2. Error messages generatedby the Web GUI component . . . . . 261HEMAW . . . . . . . . . . . . . . . 261HEMBT . . . . . . . . . . . . . . . 277HEMDA . . . . . . . . . . . . . . . 301HEMEC . . . . . . . . . . . . . . . 325HEMEE . . . . . . . . . . . . . . . 329HEMEM . . . . . . . . . . . . . . . 343HEMEN . . . . . . . . . . . . . . . 349HEMEO . . . . . . . . . . . . . . . 355HEMEP . . . . . . . . . . . . . . . 364HEMES . . . . . . . . . . . . . . . 365HEMEU . . . . . . . . . . . . . . . 374HEMFV . . . . . . . . . . . . . . . 378HEMHA . . . . . . . . . . . . . . . 397HEMHB . . . . . . . . . . . . . . . 403HEMIM . . . . . . . . . . . . . . . 408HEMIP . . . . . . . . . . . . . . . 419HEMJS . . . . . . . . . . . . . . . 422HEMUP . . . . . . . . . . . . . . . 462

Notices . . . . . . . . . . . . . . 469Trademarks . . . . . . . . . . . . . . 471

Index . . . . . . . . . . . . . . . 473

Copyright IBM Corp. 2011 iii

iv IBM Tivoli Netcool/OMNIbus: Error Messages Guide

About this publication

Tivoli Netcool/OMNIbus is a service level management (SLM) system that deliversreal-time, centralized monitoring of complex networks and IT domains.

The IBM Tivoli Netcool/OMNIbus Error Messages Guide is a reference guide thatdescribes system messages in Tivoli Netcool/OMNIbus and how to respond tothose messages.

Intended audienceThis publication is intended for administrators who are responsible for configuringTivoli Netcool/OMNIbus.

What this publication containsThis publication contains the following sections:v Chapter 1, Error messages generated by the server-side components, on page 1

Lists and describes the error messages generated by the TivoliNetcool/OMNIbus server-side components.

v Chapter 2, Error messages generated by the Web GUI component, on page 261Lists and describes the error messages generated by the Web GUI server-sidecomponent.

PublicationsThis section lists publications in the Tivoli Netcool/OMNIbus library and relateddocuments. The section also describes how to access Tivoli publications online andhow to order Tivoli publications.

Your Tivoli Netcool/OMNIbus library

The following documents are available in the Tivoli Netcool/OMNIbus library:v IBM Tivoli Netcool/OMNIbus Installation and Deployment Guide, SC14-7604

Includes installation and upgrade procedures for Tivoli Netcool/OMNIbus, anddescribes how to configure security and component communications. Thepublication also includes examples of Tivoli Netcool/OMNIbus architectures anddescribes how to implement them.

v IBM Tivoli Netcool/OMNIbus Administration Guide, SC14-7605Describes how to perform administrative tasks using the TivoliNetcool/OMNIbus Administrator GUI, command-line tools, and process control.The publication also contains descriptions and examples of ObjectServer SQLsyntax and automations.

v IBM Tivoli Netcool/OMNIbus Web GUI Administration and User's Guide, SC14-7606Describes how to perform administrative and event visualization tasks using theTivoli Netcool/OMNIbus Web GUI.

v IBM Tivoli Netcool/OMNIbus User's Guide, SC14-7607Provides an overview of the desktop tools and describes the operator tasksrelated to event management using these tools.

Copyright IBM Corp. 2011 v

v IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide, SC14-7608Contains introductory and reference information about probes and gateways,including probe rules file syntax and gateway commands.

v IBM Tivoli Monitoring for Tivoli Netcool/OMNIbus Agent User's Guide, SC14-7610Describes how to install the health monitoring agent for TivoliNetcool/OMNIbus and contains reference information about the agent.

v IBM Tivoli Netcool/OMNIbus Event Integration Facility Reference, SC14-7611Describes how to develop event adapters that are tailored to your networkenvironment and the specific needs of your enterprise. This publication alsodescribes how to filter events at the source.

v IBM Tivoli Netcool/OMNIbus Error Messages Guide, SC14-7612Describes system messages in Tivoli Netcool/OMNIbus and how to respond tothose messages.

v IBM Tivoli Netcool/OMNIbus Web GUI Administration API (WAAPI) User's Guide,SC22-5403-00Shows how to administer the Tivoli Netcool/OMNIbus Web GUI using the XMLapplication programming interface named WAAPI.

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical termsrelated to Tivoli software. The Tivoli Software Glossary is available at the followingTivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology Web site at thefollowing Web address:

http://www.ibm.com/software/globalization/terminology

Accessing publications online

IBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Information Center Website at:

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp

Note: If you print PDF documents on other than letter-sized paper, set the optionin the File > Print window that allows Adobe Reader to print letter-sized pages onyour local paper.

Ordering publications

You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

vi IBM Tivoli Netcool/OMNIbus: Error Messages Guide

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htmhttp://www.ibm.com/software/globalization/terminologyhttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsphttp://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss

In other countries, contact your software account representative to order Tivolipublications. To locate the telephone number of your local representative, performthe following steps:1. Go to the following Web site:

http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss2. Select your country from the list and click Go. The Welcome to the IBM

Publications Center page is displayed for your country.3. On the left side of the page, click About this site to see an information page

that includes the telephone number of your local representative.

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully.

With this product, you can use assistive technologies to hear and navigate theinterface. You can also use the keyboard instead of the mouse to operate somefeatures of the graphical user interface.

Tivoli technical training

For Tivoli technical training information, refer to the following IBM TivoliEducation Web site:

http://www.ibm.com/software/tivoli/education

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineGo to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html and follow the instructions.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceabilityworkbench that helps you resolve questions and problems with IBMsoftware products. The ISA provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe ISA software, go to http://www.ibm.com/software/support/isa.

DocumentationIf you have a suggestion for improving the content or organization of thisguide, send it to the Tivoli Netcool/OMNIbus Information Developmentteam at:

mailto://[email protected]

About this publication vii

http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wsshttp://www.ibm.com/software/tivoli/educationhttp://www.ibm.com/software/support/probsub.htmlhttp://www.ibm.com/software/support/probsub.htmlhttp://www.ibm.com/software/support/isamailto://[email protected]

Conventions used in this publicationThis publication uses several conventions for special terms and actions andoperating system-dependent commands and paths.

Typeface conventions

This publication uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip: and Operating system considerations:)

v Keywords and parameters in textItalic

v Citations (examples: titles of publications, diskettes, and CDs)v Words defined in text (example: a nonswitched line is called a

point-to-point line)v Emphasis of words and letters (words as words example: "Use the word

that to introduce a restrictive clause."; letters as letters example: "TheLUN address must start with the letter L.")

v New terms in text (except in a definition list): a view is a frame in aworkspace that contains data

v Variables and values you must provide: ... where myname represents....Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Operating system-dependent variables and paths

This publication uses the UNIX convention for specifying environment variablesand for directory notation.

When using the Windows command line, replace $variable with %variable% forenvironment variables, and replace each forward slash (/) with a backslash (\) indirectory paths. For example, on UNIX systems, the $NCHOME environmentvariable specifies the path of the Netcool home directory. On Windows systems,the %NCHOME% environment variable specifies the path of the Netcool homedirectory. The names of environment variables are not always the same in theWindows and UNIX environments. For example, %TEMP% in Windowsenvironments is equivalent to $TMPDIR in UNIX environments.

If you are using the bash shell on a Windows system, you can use the UNIXconventions.

viii IBM Tivoli Netcool/OMNIbus: Error Messages Guide

Operating system-specific directory names

Where Tivoli Netcool/OMNIbus files are identified as located within an archdirectory under NCHOME, arch is a variable that represents your operating systemdirectory, as shown in the following table.

Table 1. Directory names for the arch variable

Directory name represented by arch Operating system

aix5 AIX systems

hpux11 HP-UX PA-RISC-based systems

hpux11hpia HP-UX Integrity-based systems

linux2x86 Red Hat Linux and SUSE systems

linux2s390 Linux for System z

solaris2 Solaris systems

win32 Windows systems

About this publication ix

x IBM Tivoli Netcool/OMNIbus: Error Messages Guide

Chapter 1. Error messages generated by the server-sidecomponents

The following error messages are generated by the server-side components ofTivoli Netcool/OMNIbus.

ALDMessages related to LDAP authentication.

E-ALD-102-001 The system has been configured forFIPS but the LDAP authenticationmodule is not configured to use SSL

System action: Not applicable.

User response: Not applicable.

Administrator response: Not applicable.

E-ALD-102-002 Failure occurred in configuring LDAPinterface for FIPS (%0d:%1s)




E-ALD-102-003 Failed to initialise the SSLenvironment. (%0d:%1s)




E-ALD-102-004 Failed to bind to LDAP server usingv2 protocol for user %0s. (%1d:%2s)




E-ALD-102-005 Failed to initialise connection toLDAP server. Host %0s. Port %1d. Error- %2d:%3s




Copyright IBM Corp. 2011 1

E-ALD-102-006 Failed to initialise LDAP SSLconnection. Host %0s. Port %1d




E-ALD-102-007 Failed to bind to LDAP server foruser %0s. (%1d:%2s)




E-ALD-102-008 The LDAP Server is not reachable




E-ALD-102-009 Failed to unbind from the LDAPserver: %0d:%1s




E-ALD-102-010 Failed to initialise the connectionprior to reconnecting




E-ALD-102-011 LDAP Server message receivedduring bind. %0s




E-ALD-102-012 ldap_open failed to LDAP server.Host %0s. Port %1d. Error - %2d:%3s.




E-ALD-102-006 E-ALD-102-012

2 IBM Tivoli Netcool/OMNIbus: Error Messages Guide

E-ALD-102-013 Failed to initialise the connection forSSL prior to reconnecting




E-ALD-102-014 Failed to bind to LDAP server foruser %0s. ldap_result failed. (%1d:%2s)




E-ALD-102-015 Timeout while attempting to bind toLDAP server for user %0s. (%1d:%2s)




E-ALD-102-016 Failed to bind to LDAP server foruser %0s. (%1d:%2s)




E-ALD-102-017 Failed to fetch value for property %0s. (%1d:%2s)




E-ALD-102-018 Datatype mismatch for property %0sin value extraction. (%1d:%2s)




E-ALD-102-019 Datatype not supported for property%0s in value extraction. (%1d:%2s)




E-ALD-102-013 E-ALD-102-019

Chapter 1. Server-side error messages 3

E-ALD-102-020 Failed to bind during reconnectionattempt. Error %0s.




E-ALD-102-020


E-ALD-102-021 Error occurred while trying toestablish bind connection. Error %0s




E-ALD-102-021


E-ALD-102-022 %0s in %1s, line %2d near %3s




E-ALD-102-022


E-ALD-102-023 %0s in %1s, line %2d




E-ALD-102-023


E-ALD-102-024 Failed to decode properties file %0s:%1d:%2s




E-ALD-102-024


E-ALD-102-025 Failed to define the encryptionproperties. %0d:%1s




E-ALD-102-025


W-ALD-103-001 Failed to load properties file %0s:%1s




APMMessages related to Pluggable Authentication Modules (PAM) authentication.

E-APM-102-001 PAM message for user %0s: %1s




E-APM-102-003 Failed to initialise the underliningOS PAM sub-system. Application: %0s.PAM Error [%1d][%2s].




E-APM-102-004 Failed to set the user name on thePAM handle [%0d][%1s].




E-APM-102-005 User authentication of user %0s , hasfailed. [%1d][%2s]




E-APM-102-006 User %0s is not known.




E-APM-102-007 Unknown error has occurred duringauthentication. [%0d][%1s]




W-ALD-103-001 E-APM-102-007


E-APM-102-008 Authentication Token Update hasfailed. [%0d][%1s]




E-APM-102-008


E-APM-102-009 Unknown error has occurred duringauthentication token update. [%0d][%1s]




E-APM-102-009


E-APM-102-010 Account Management of user %0s ,has failed. [%1d][%2s]




E-APM-102-010


E-APM-104-002 Unknown PAM conversion type: %0d




E-APM-104-002


E-APM-104-011 %0s : PAM module in use is broken.Application user data has not beenpassed to conversation function.




AUTMessages related to automations and triggers.

E-AUT-001-013 Failed to recover event \%0s\




E-AUT-001-014 Failed to recover trigger group \%0s\




E-AUT-001-015 Failed to recover trigger \%0s\




E-AUT-002-006 Trigger \%0s\: action executionfailed: %1s

Explanation: The following examples show how thismessage is written to the log.

Example 1:

E-AUT-002-006: Trigger "deleteitm":action execution failed:Attempt to insert duplicate row

Example 2:

E-AUT-002-006:Trigger "connection_watch_disconnect":action execution failed:Not enough space

Example 3:

E-AUT-002-006: Trigger "log_all_event":action execution failed:There is not enough memory available now.The external procedure (log_event) was notexecuted.

The example messages indicate that ObjectServertriggers are not being executed, possibly because thereis not enough memory to process the operation.



Administrator response: In example message 1, adeduplication trigger does not exist for the table wherethe event is being inserted. In this case, you can add adeduplication trigger to handle duplicate rows in thetable concerned.

The following example trigger drops the incomingduplicate event data and does not make any updates:

create or replace trigger custom_dedupgroup default_triggersdebug falseenabled truepriority 1

comment Deduplication processing forcustom.statusbefore reinsert on custom.statusfor each rowbegin

cancel;

end;

In example messages 2 and 3, there is a problem withthe amount of memory available. Monitor the memoryusage of the ObjectServer and the host system over anextended time period to determine whether the systemrequires more physical memory.

For information about triggers and automations, see theIBM Tivoli Netcool/OMNIbus Administration Guide.

E-AUT-002-009 Trigger \%0s\: action executionfailed: %1s: %2s




E-AUT-003-001 Trigger \%0s\: %1s on line %2d near%3s




E-APM-104-011 E-AUT-003-001


E-AUT-003-002 Trigger \%0s\: %1s on line %2d




E-AUT-003-004 Trigger \%0s\: recursive raisedetected. Aborting execution

Explanation: The following example shows how thismessage is written to the log:

Error: E-AUT-003-004:Trigger "test_correlation": recursive raisedetected. Aborting execution

This error indicates that the affected trigger isperforming an action that might lead to the triggerbeing executed recursively, thereby degradingObjectServer performance. When the ObjectServerdetects that it is recursively invoking a trigger, itprevents execution of the trigger and returns this errormessage.

In the example message, a custom database trigger,test_correlation, fires on an update to thealerts.status table. However, the trigger itself performsan update to alerts.status, thus starting a recursiveloop.



Administrator response: The response to this errorwill depend on your system configuration. The solutionto the problem in the example is to either alter thetrigger to prevent recursion, or to use a temporaltrigger instead of a database trigger.

E-AUT-003-005 %0s at or near %1s on line %2d of%3s




E-AUT-003-007 Failed to recover %0d of %1d triggers




E-AUT-003-002 E-AUT-003-007


E-AUT-003-008 Trigger recovery failed: %0s




E-AUT-003-009 Trigger \%0s\ execution failed inevaluate clause : %1s




E-AUT-003-010 Trigger \%0s\ execution failed inaction clause : %1s




E-AUT-003-011 %0s raising signal %1s. CounterpartObjectServer is not available for failoveror failback.




W-AUT-004-001 Failed to raise trigger statisticslogging signal: %0s




W-AUT-004-002 A callback servicing an alter triggergroup event (%0d) for trigger group %1sreturned: %2s (%3d)




W-AUT-004-003 A callback servicing an alter triggerevent (%0d) for trigger %1s returned:%2s (%3d)




E-AUT-003-008 W-AUT-004-003


W-AUT-004-004 Invocation of trigger \%0s\ will notbe timed due to stop watch creationproblem (%1s:%2d). Time statistics willbe incorrect for this trigger.




BRIMessages related to the firewall bridge server utility (nco_bridgeserv).

E-BRI-102-002 [BridgeServer]: Failed to initialiseproperty manager with the NIPC clientproperties. (%0d:%1s)




E-BRI-102-003 [BridgeServer]: Failed to initialiseproperty manager with the bridgeservers properties. (%0d:%1s)




E-BRI-102-004 [BridgeServer]: Failed to initialiseargument manager with the NIPC clientarguments. (%0d:%1s)




E-BRI-102-005 [BridgeServer]: Failed to initialiseargument manager with the bridgeservers arguments. (%0d:%1s)




E-BRI-102-006 [BridgeServer]: Failed to updateproperty manager with the bridgeservers properties affected by namechange. (%0d:%1s)




W-AUT-004-004 E-BRI-102-006


E-BRI-102-007 [BridgeServer]: Failed to initialise theNIPC client library. (%0d:%1s)




E-BRI-102-008 [BridgeServer]: Failed to fetch all ofthe required server property values.(%0d:%1s)




E-BRI-102-009 [BridgeServer]: Failed to create a clientdata connection structure. (%0d:%1s)




E-BRI-102-010 [BridgeServer]: Failed to challengeclient for login details. (%0d:%1s)




E-BRI-102-011 [BridgeServer]: Failed to validateclients login credentials. (%0d:%1s)




E-BRI-102-012 [BridgeServer]: Failed to inform theprocess agent %0s that we have started. (%1d )




E-BRI-102-007 E-BRI-102-012


E-BRI-102-013 [BridgeServer]: %0s: The thread hasterminated unexpectedly. Server may beshutdown. (%1d:%2s)




E-BRI-102-014 [BridgeServer]: %0s: Failed to spawnthe client connection handling thread.(%1d:%2s)




E-BRI-102-015 [BridgeServer]: Failed to join theclient connection handling thread andwait for it to shutdown. (%0d:%1s)




E-BRI-102-016 [BridgeServer]: Client Thread: Failedto create session structure. (%0d:%1s)




E-BRI-102-017 [BridgeServer]: Client Thread: Failedto install challenge callback on nipcsession structure. (%0d:%1s)




E-BRI-102-018 [BridgeServer]: Client Thread: Failedto install session name callback on nipcsession structure. (%0d:%1s)




E-BRI-102-013 E-BRI-102-018


E-BRI-102-019 [BridgeServer]: Client Thread: Failedto connect to remote ObjectServer %0s .(%1d:%2s)




E-BRI-102-020 [BridgeServer]: Client Thread: Failedto disconnect from remote ObjectServer%0s . (%1d:%2s)




E-BRI-102-021 [BridgeServer]: Client Thread: Failedto destroy the session structure.(%0d:%1s)












E-BRI-102-024 [BridgeServer]: %0s: Failed to spawnthe thread pool worker thread.(%1d:%2s)




E-BRI-102-019 E-BRI-102-024


E-BRI-102-025 [BridgeServer]: %0s: Failed to join thethread pool worker thread and wait forit to shutdown. (%1d:%2s)




E-BRI-102-026 [BridgeServer]: Invalid value %0sdefined for bridge role property %1s .




E-BRI-102-027 [BridgeServer]: Unknown bridge modein start-up handler. Unable to determineservers operational start-up sequence.(%0u)




E-BRI-102-028 [BridgeServer]: Unknown bridge modein stop handler. Unable to determineservers operational shutdown sequence.(%0u)




E-BRI-102-029 [BridgeServer]: %0s: Failed to createthe server access point listening socket.(%1d:%2s)




E-BRI-102-030 [BridgeServer]: %0s: Failed to createthe client access point listening socket.(%1d:%2s)




E-BRI-102-025 E-BRI-102-030


E-BRI-102-031 [BridgeServer]: %0s: Failed to createall of the required elements foroperation. Shutting down the server.(%1d:%2s)




E-BRI-102-032 [BridgeServer]: %0s: Fatal errordetected in operation. Terminating thethread.




E-BRI-102-033 [BridgeServer]: %0s: Failed to allocatethe threads operational data structure(%1d:%2s)




E-BRI-102-034 [BridgeServer]: %0s: Failed to accept aconnection on the server access pointlistening port %1u . (%2d:%3s)




E-BRI-102-035 [BridgeServer]: %0s: Failed to accept aconnection on the client access pointlistening port %1u . (%2d:%3s)




E-BRI-102-036 [BridgeServer]: %0s: Failed to readcommand from client connection onsocket %1u [%2s:%3s]. (%4d:%5s)




E-BRI-102-031 E-BRI-102-036


E-BRI-102-037 [BridgeServer]: %0s: Failed to look upthe associated connection structure foractive socket %1u . Fatal conditiondetected.




E-BRI-102-038 [BridgeServer]: %0s: Failed to look upthe associated connection structure foractive socket %1u . Unexpected errorcondition detected. (%2d:%3s)




E-BRI-102-039 [BridgeServer]: Failed to acceptconnection on listening socket %0u .(%1d:%2s)




E-BRI-102-040 [BridgeServer]: Failed to create a rawconnection data handle acceptedconnection (%0d:%1s)




E-BRI-102-041 [BridgeServer]: %0s: Failed to spawnthe client access point commandhandling thread. (%1d:%2s)




E-BRI-102-042 [BridgeServer]: Failed to join theclient access point command handlingthread. (%0d:%1s)




E-BRI-102-037 E-BRI-102-042


E-BRI-102-043 [BridgeServer]: Failed to make aconnection to %0s on port %1u .(%2d:%3s)




E-BRI-102-044 [BridgeServer]: Failed to create a rawconnection data handle for establishedconnection to %0s port %1u . (%2d:%3s)




E-BRI-102-045 [BridgeServer]: %0s: Fatal errordetected in operation. Terminating thethread.




E-BRI-102-046 [BridgeServer]: %0s: Unable toestablish connection bridge for clientconnection as no command connectionhas been established between the serveraccess point. Dropping client connectionon socket %1u .




E-BRI-102-047 [BridgeServer]: %0s: Failed to readcommand from current connection onsocket %1u [%2s:%3s]. (%4d:%5s)




E-BRI-102-048 [BridgeServer]: %0s: Failed to connectto client access point server port.Retrying in %1u seconds. (%2d:%3s)




E-BRI-102-043 E-BRI-102-048


E-BRI-102-049 [BridgeServer]: %0s: Failed to look upthe associated peer connection structurefor socket %1u . Unable to establish alink-up on requesting socket %2u .Dropping connection. (%3d:%4s)




E-BRI-102-050 [BridgeServer]: Failed to read %0dbytes from raw connection data handle.(%1d:%2s)




E-BRI-102-051 [BridgeServer]: %0s: Failed to addlinked up data flow raw connections tothread pool manager. Droppingassociated sockets %1u and %2u .(%3d:%4s)




E-BRI-102-052 [BridgeServer]: %0s: An unknownserver command of type %1u has beenreceived from client connection onsocket %2u [%3s:%4s]. Droppingcommand and attempting to continue.




E-BRI-102-053 [BridgeServer]: %0s: Failed to handlethe read ready status of data pendingreceived from client connection onsocket. Attempting to continue.(%1d:%2s)




E-BRI-102-049 E-BRI-102-053


E-BRI-102-054 [BridgeServer]: %0s: An unrecoverablecondition has been detected and thethread is not able to continue. Request ashutdown of the bridge server.




E-BRI-102-055 [BridgeServer]: SrvCmd: Invalidheader detected in server command.




E-BRI-102-056 [BridgeServer]: SrvCmd: Versionedserver command is not supported bycurrent code base. Server command is0x%0x , but only support up to version0x%1x




E-BRI-102-057 [BridgeServer]: SrvCmd: Failed todetermine the number of bytes pendingon client connection socket %0u[%1s:%2s]. Disconnecting the client fromthe server. (%3d:%4s)




E-BRI-102-058 [BridgeServer]: SrvCmd: Clientdisconnection detected on clientconnection socket %0u [%1s:%2s].Disconnecting the client from the server.




E-BRI-102-054 E-BRI-102-058


E-BRI-102-059 [BridgeServer]: SrvCmd: Insufficientbytes available for server commandheader from client connection socket%0u [%1s:%2s]. Expected %3u , but onlygot %4u . Dropping the data andattempting to continue.




E-BRI-102-060 [BridgeServer]: SrvCmd: Failed tosend server command to clientconnection socket %0u [%1s:%2s].(%3d:%4s)




E-BRI-102-061 [BridgeServer]: %0s: Failed todetermine the number of bytes pendingon client connection socket %1u[%2s:%3s]. Disconnecting the client dataflow from the server. (%4d:%5s)




E-BRI-102-062 [BridgeServer]: %0s: Clientdisconnection detected on clientconnection socket %1u [%2s:%3s].Disconnecting the client data flow fromthe server.




E-BRI-102-063 [BridgeServer]: %0s: Failed to read thepending data from source clientconnection socket %1u [%2s:%3s].(%4d:%5s)




E-BRI-102-059 E-BRI-102-063


E-BRI-102-064 [BridgeServer]: %0s: Failed to writethe pending data to destination clientconnection socket %1u [%2s:%3s].Disconnecting the client data flow fromthe server. (%4d:%5s)




E-BRI-102-065 [BridgeServer]: TPMgr: Failed to checkall threads in the thread pool for anavailable free slot. (%0d:%1s)




E-BRI-102-066 [BridgeServer]: TPMgr: Failed to starta new worker thread within the threadpool. (%0d:%1s)




E-BRI-102-067 [BridgeServer]: %0s: Failed to processan active data flow between[%1u:%2s:%3s]->[%4u:%5s:%6s].(%7d:%8s)




E-BRI-102-068 [BridgeServer]: %0s: Failed to allocatethe threads operational data structure(%1d:%2s)




E-BRI-102-069 [BridgeServer]: %0s: Disconnecting theclient connections that represent theactive data flow between[%1u:%2s:%3s]->[%4u:%5s:%6s] anddropping the work item.




E-BRI-102-064 E-BRI-102-069


E-BRI-102-070 [BridgeServer]: %0s: Fatal errorcondition in the thread and canpotentially not continue. Return ingfailure condition which may result inserver shutdown.




E-BRI-102-071 [BridgeServer]: Failed to build theconnection list for ObjectServer %0s .(%1d:%2s)




E-BRI-102-072 [BridgeServer]: Failed to establish araw client connection to ObjectServer%0s .




E-BRI-102-073 [BridgeServer]: %0s: Failed to readacknowledge command from new clientconnection on socket %1u [%2s:%3s].(%4d:%5s)




E-BRI-102-074 [BridgeServer]: %0s: Failed to wait foracknowledge command from new clientconnection on socket %1u [%2s:%3s].(%4d:%5s)




E-BRI-102-075 [BridgeServer]: %0s: Invalid servercommand received from new clientconnection on socket %1u [%2s:%3s].(%4d:%5s)




E-BRI-102-070 E-BRI-102-075


E-BRI-102-076 [BridgeServer]: %0s: Failed to establisha raw client connection to theObjectServer %1s . (%2d:%3s)




E-BRI-102-077 [BridgeServer]: %0s: Failed to establisha link-up raw client connection with theclient access point bridge server %1sport %2u . (%3d:%4s)




E-BRI-102-078 [BridgeServer]: %0s: Failed to addlinked up data flow raw connections tothread pool manager. Droppingassociated sockets %1u and %2u .(%3d:%4s)




E-BRI-102-079 [BridgeServer]: %0s: Failed to lock thethread pool workers mutex lock.(%1d:%2s)




E-BRI-102-080 [BridgeServer]: %0s: Failed to start upall of the threads required operationalelements. Shutting down the server.(%1d:%2s)




E-BRI-102-081 [BridgeServer]: %0s: Failed to sendfailure error code back to client accesspoint for link up request using client id%1u . (%2d:%3s)




E-BRI-102-076 E-BRI-102-081


E-BRI-102-082 [BridgeServer]: %0s: Server accesspoint has failed to established the dataflow on its side. Dropping associatedclient connection sockets %1u .(%2d:%3s)




E-BRI-102-083 [BridgeServer]: Failed to open theSybase interfaces file %0s . (%1d:%2s)




E-BRI-102-084 [BridgeServer]: %0s: Receivedunknown server command %1u fromcurrent connection on socket %2u[%3s:%4s].




E-BRI-102-085 [BridgeServer]: SrvCmd: Unable toencode/decode unknown servercommand %0u .




E-BRI-102-086 [BridgeServer]: Client CommandParser: Failed to parse client command.Error: nrc=%0s : msg=%1s : line=%2u :token=%3s




E-BRI-102-087 [BridgeServer]: Client CommandParser Error: msg=%0s : line=%1u :token=%2s




E-BRI-102-082 E-BRI-102-087


E-BRI-102-088 [BridgeServer]: Failed to parse theclient language command %0s .(%1d:%2s)




E-BRI-102-097 [BridgeServer]: Failed to issue bridgeserver shutdown request. (%0d:%1s)




E-BRI-102-100 [BridgeServer]: %0s: Failed todetermine whether client connectionfrom hostname %1s (%2s) on socket %3uis from a trusted IP address. Droppingconnection. (%4d:%5s)




E-BRI-102-101 [BridgeServer]: %0s: Client connectionfrom hostname %1s (%2s) on socket %3uis from an untrusted IP address.Dropping connection.




E-BRI-102-103 [BridgeServer]: Trusted Hosts FileParser: Failed to parse trusted hostdefinition. Error: nrc=%0s : msg=%1s :line=%2u : token=%3s




E-BRI-102-104 [BridgeServer]: Trusted Hosts FileParser Error: msg=%0s : line=%1u :token=%2s




E-BRI-102-088 E-BRI-102-104


E-BRI-102-105 [BridgeServer]: Failed to parse thetrusted hosts file %0s . (%1d:%2s)




E-BRI-102-106 [BridgeServer]: Failed to open thetrusted hosts file %0s . (%1d:%2s)




E-BRI-102-107 [BridgeServer]: IPv4 address%0d.%1d.%2d.%3d is invalid in trustedhosts file.




E-BRI-102-108 [BridgeServer]: IPv4 network prefix%0d is invalid in trusted hosts file.




E-BRI-102-109 [BridgeServer]: IPv6 address %0s isinvalid in trusted hosts file.




E-BRI-102-110 [BridgeServer]: IPv6 network prefix%0d is invalid in trusted hosts file.




E-BRI-102-111 [BridgeServer]: Failed to execute theclient language command %0s .(%1d:%2s)




E-BRI-102-105 E-BRI-102-111


E-BRI-102-114 PAM: Unknown PAM conversion type:%0d




E-BRI-102-115 PAM: Failed to initialise theunderlining OS PAM sub-system. PAMError [%0d][%1s].




E-BRI-102-116 PAM: Cannot set thread specific data.(%0d:%1s)




E-BRI-102-117 PAM: Failed to set the user name onthe PAM handle [%0d][%1s].




E-BRI-102-118 PAM: User authentication of user %0s, has failed. [%1d][%2s]




E-BRI-102-119 PAM: User %0s is not known.




E-BRI-102-120 PAM: Unknown error has occurredduring authentication. [%0d][%1s]




E-BRI-102-114 E-BRI-102-120


E-BRI-102-121 PAM: Account Management of user%0s , has failed. [%1d][%2s]




E-BRI-102-122 PAM: PAM message for user %0s: %1s.




E-BRI-102-123 [BridgeServer]: %0s: Failed to sendheartbeat to client access point(%1d:%2s).




E-BRI-102-124 [BridgeServer]: %0s: Failed to sendheartbeat to server access point(%1d:%2s).




E-BRI-102-125 [BridgeServer]: %0s: Failed todetermine whether server connectionfrom hostname %1s (%2s) on socket %3uis from a trusted IP address. Droppingconnection. (%4d:%5s)




E-BRI-102-126 [BridgeServer]: %0s: Server connectionfrom hostname %1s (%2s) on socket %3uis from an untrusted IP address.Dropping connection.




E-BRI-102-121 E-BRI-102-126


E-BRI-102-127 [BridgeServer]: %0s: Failed to createlink-up request command structure forconnection from hostname %1s (%2s) onsocket %3u . Dropping connection.(%4d:%5s)




E-BRI-102-127


E-BRI-102-128 [BridgeServer]: %0s: Failed to sendlink-up request to server access pointfor connection from hostname %1s (%2s)on socket %3u . Dropping connection.(%4d:%5s)




E-BRI-102-128


W-BRI-103-001 [BridgeServer]: Failed to look uphostname for IP address %0s . Usingdefault system hostname %1s .(%2d:%3s)




W-BRI-103-001


W-BRI-103-002 [BridgeServer]: %0s: Failed to readcommand from client connection onsocket %1u [%2s:%3s]. Disconnectingclient from the server. (%4d:%5s)




W-BRI-103-002


W-BRI-103-003 [BridgeServer]: %0s: Failed to readcommand from current connection onsocket %1u [%2s:%3s]. Disconnectingfrom the client. (%4d:%5s)




CHEMessages related to the memstore checkpoint verification utility (nco_check_store).

W-BRI-103-003


E-CHE-001-001 Verification failed for %0s: %1s




CMDMessages related to SQL command processing.

E-CHE-001-001


E-CMD-001-002 Divide by zero error




DBIMessages related to the database initialization utility (nco_dbinit).

E-DBI-002-001 %0s in file %1s at or near %2s on line%3d of statement %4s




E-DBI-002-002 %0s in file %1s on line %2d ofstatement %3s




E-DBI-002-003 Security startup failed: %0s




E-DBI-002-004 Security property startup failed: %0s




E-DBI-002-005 Failed to copy ObjectServer propertyfile: %0s




E-DBI-002-008 Failed to process file: %0s




E-CMD-001-002 E-DBI-002-008


E-DBI-002-028 An error has occurred whileprocessing the .sql files. See log formore details




E-DBI-002-028


E-DBI-002-029 No Futher Data will be imported tothe objectserver from this file: %0s




E-DBI-002-029


E-DBI-002-030 Failed to convert error string to a widestring




E-DBI-002-030


E-DBI-002-031 Custom config file %0s does not exist




E-DBI-002-031


E-DBI-002-032 Failed to open property file %0s : %1s




E-DBI-002-032


E-DBI-002-033 Error occurred appending propertiesto props file %0s : %1s




E-DBI-002-033


W-DBI-004-001 Unable to append properties to propsfile because CopyPropsFile is false




ETCMessages related to the core Netcool/OMNIbus libnetcool library.

E-ETC-003-012 Failed to initialise NTimer forCLOCK tick




E-ETC-003-013 Failed to create NTimerHandler forCLOCK tick_timer




E-ETC-003-014 Failed to create NEvent for CLOCKtick




E-ETC-003-015 Failed to create tick_list_lock




E-ETC-003-016 Failed to create timer_mutex




E-ETC-004-001 %0s in %1s, line %2d near %3s




W-DBI-004-001 E-ETC-004-001


E-ETC-004-002 %0s in %1s, line %2d




E-ETC-004-008 THREAD MGR: thread %0s (%1p)*EXIT*: %2s




E-ETC-102-002 No global key set and no keyprovided




E-ETC-102-003 Could not open file %0s for reading,Error: %1s




E-ETC-102-004 File length found does not matchexpected file length: %0s




E-ETC-102-005 Key file formatted incorrectly, lengthmismatch %0s




E-ETC-102-006 Key file formatted incorrectly, noseparator found %0s




E-ETC-004-002 E-ETC-102-006


E-ETC-102-007 Attempt made to read data fromempty file: %0s




E-ETC-102-008 Failed to define property %0s .(%1d:%2s)




E-ETC-102-009 Failed to define callback for property%0s . (%1d:%2s)




E-ETC-102-010 Encryption algorithm not found: %0s




E-ETC-102-011 Key file formatted incorrectly, nonnumeric characters in length: %0s




E-ETC-102-021 Failed to open ICU converter, errorcode: %0d error message: %1s




E-ETC-102-022 Failed to open ICU collator, error code%0d error message %1s




E-ETC-102-007 E-ETC-102-022


E-ETC-102-023 libncrypt error: %0s




E-ETC-102-024 libncrypt error code out of range: %0d




E-ETC-102-025 libncrypt error: %0s %1d




E-ETC-102-026 FIPS mode set and non FIPS ciphermode detected: %0s




E-ETC-102-027 Failed to convert UTF-16 string tocode page: %0s




E-ETC-102-028 Failed to convert string: %0s toUTF-16: %1s




E-ETC-102-029 Failed to set ICU from Unicodeconversion call back function: %0s




E-ETC-102-023 E-ETC-102-029


E-ETC-102-030 Failed to set ICU to Unicodeconversion call back function: %0s




E-ETC-102-031 Failed to set ICU substitutioncharacter call back function: %0s




E-ETC-102-032 Failed to set thread specific data forICU Converter. (%0d:%1s)




E-ETC-102-033 Failed to create thread specific ICUConverter. (%0d:%1s)




E-ETC-102-034 Invalid date/time format: %0s.




E-ETC-102-035 Fail to format date with format: %0s.Error code: %1s




E-ETC-102-036 Fail to parse date string: %0s usingformat: %1s. Error code: %2s


Error: E-ETC-102-036: Fail to parse date string:Tue DEC 19 18:33:11 JST 2010using format: %a %b %e %T %Y.Error code: U_PARSE_ERROR

This error messages indicates that a probe failed toparse a date string.

The example error message was written to a probe logfile. In this example, the error occurs because the dateand time pattern %a %b %e %T %Y does not match thedate string, which includes time zone information (JST).



Administrator response: To address the problemindicated by the example error message, add the timezone information to the pattern. For example, use thepattern %a %b %e %T %Z %Y to define the time string TueDEC 19 18:33:11 JST 2010.

However, because JST is not a standard time zoneidentifier supported by ICU, the time string Tue DEC 1918:33:11 JST 2010 still causes a parse error. Thesolution is to use an unambiguous time zone identifierequal to JST, for example, Tue DEC 19 18:33:11 GMT+92010.

This error does not occur in versions of TivoliNetcool/OMNIbus earlier than V7.3 because thoseversions ignore time zone information. In TivoliNetcool/OMNIbus V7.3, POSIX date and time patternswere deprecated in favor of Locale Data MarkupLanguage (LDML) date and time patterns that areprovided by International Components for Unicode(ICU) libraries. Whenever possible, replace POSIXpatterns in probe rules files with LDML patterns.

For more information about the change from POSIX toLDML date and time formats, see the IBM TivoliNetcool/OMNIbus Installation and Deployment Guide.

For more information about using date and timefunctions in rules files, see the IBM TivoliNetcool/OMNIbus Probe and Gateway Guide.

W-ETC-004-060 Undefined argument: %0s




W-ETC-004-066 Failed to load properties file %0s:%1s

Explanation: The following examples show how thismessage is written to the log:

W-ETC-004-066: Failed to load properties file/opt/netcool/omnibus/etc/NCOMS.props:No such file or directory

W-ETC-004-066: Failed to load properties file/nco731/tivoli/netcool/omnibus/etc/NCOMS.props:A file or directory in the path namedoes not exist.

The example messages indicate that the ObjectServerproperties file does not exist, or that part of the pathname is incorrect.

E-ETC-102-030 W-ETC-004-066




Administrator response: To address the problemindicated by the example message, ensure that theObjectServer properties file exists. The default locationis $NCHOME/omnibus/etc.

You can use the ObjectServer -propsfile option to setthe properties file:

nco_objserv -propsfile $NCHOME/omnibus/etc/NCOMS.props

This error can occur when you attempt to start anObjectServer without having first run the databaseinitialization utility (nco_dbinit) to create the databasefiles and the default properties file.

For information about creating and runningObjectServers, see the IBM Tivoli Netcool/OMNIbusAdministration Guide.

W-ETC-102-002 Invalid character %0x found whenconverting from Unicode.




W-ETC-102-003 Invalid character %0x found whenconverting to Unicode.




W-ETC-102-006 Invalid character %0x replaced by[space] in SQL command at index %1d




W-ETC-102-007 Code page:%0s is detected,backslash(0x5c) character is defined asYen symbol in this code page, string cant be escaped and unescaped properly




W-ETC-102-002 W-ETC-102-007


W-ETC-103-001 Accessing property %0s via alias %1s- this alias may be removed in a futureversion




W-ETC-103-001


W-ETC-103-002 Failed to load IP address networkmodule %0s . (%1d:%2s)




W-ETC-103-002


W-ETC-103-003 Failed to lookup access function inIP address network module %0s .




W-ETC-103-003


W-ETC-103-004 Failed to successfully call accessfunction in IP address network module%0s .




W-ETC-103-004


W-ETC-103-005 Failed to get file statistics on file%0s, trying to read as ascii.




GOBMessages related to ObjectServer gateways.

E-GOB-102-001 [ngobjserv]: Failed to create theproperty set for ObjectServer datamapper %0s . (%1d:%2s)




E-GOB-102-002 [ngobjserv]: Failed to add theproperty set of the ObjectServer datamapper %0s to the properties manager.(%1d:%2s)




E-GOB-102-003 [ngobjserv]: Failed to add theargument set of the ObjectServer datamapper %0s to the arguments manager.(%1d:%2s)




E-GOB-102-004 [ngobjserv]: Failed to update theproperty set of the ObjectServer datamapper %0s with the propertiesmanager. (%1d:%2s)




E-GOB-102-005 [ngobjserv]: Failed to get theproperty set values for the ObjectServerdata mapper %0s from the propertiesmanager. (%1d:%2s)




W-ETC-103-005 E-GOB-102-005


E-GOB-102-006 [ngobjserv]: Failed to create theproperty set for ObjectServer reader %0s. (%1d:%2s)




E-GOB-102-007 [ngobjserv]: Failed to add theproperty set of the ObjectServer reader%0s to the properties manager.(%1d:%2s)




E-GOB-102-008 [ngobjserv]: Failed to add theargument set of the ObjectServer reader%0s to the arguments manager.(%1d:%2s)




E-GOB-102-009 [ngobjserv]: Failed to update theproperty set of the ObjectServer reader%0s with the properties manager.(%1d:%2s)




E-GOB-102-010 [ngobjserv]: Failed to get theproperty set values for the ObjectServerreader %0s from the properties manager.(%1d:%2s)




E-GOB-102-011 [ngobjserv]: Failed to create theproperty set for ObjectServer writer %0s. (%1d:%2s)




E-GOB-102-006 E-GOB-102-011


E-GOB-102-012 [ngobjserv]: Failed to add theproperty set of the ObjectServer writer%0s to the properties manager.(%1d:%2s)




E-GOB-102-013 [ngobjserv]: Failed to add thearguments set of the ObjectServer writer%0s to the argument manager. (%1d:%2s)




E-GOB-102-014 [ngobjserv]: Failed to update theproperty set of the ObjectServer writer%0s with the properties manager.(%1d:%2s)




E-GOB-102-015 [ngobjserv]: Failed to get theproperty set values for the ObjectServerwriter %0s from the properties manager.(%1d:%2s)




E-GOB-102-016 [ngobjserv]: Failed to create theproperty set for ObjectServerreader/writer %0s . (%1d:%2s)




E-GOB-102-017 [ngobjserv]: Failed to add theproperty set of the ObjectServerreader/writer %0s to the propertiesmanager. (%1d:%2s)




E-GOB-102-012 E-GOB-102-017


E-GOB-102-018 [ngobjserv]: Failed to add thearguments set of the ObjectServerreader/writer %0s to the argumentsmanager. (%1d:%2s)




E-GOB-102-019 [ngobjserv]: Failed to update theproperty set of the ObjectServerreader/writer %0s with the propertiesmanager. (%1d:%2s)




E-GOB-102-020 [ngobjserv]: Failed to get theproperty set values for the ObjectServerreader/writer %0s from the propertiesmanager. (%1d:%2s)




E-GOB-102-021 [ngobjserv]: Table ReplicationDefinition Parser: Failed to parse tablereplication definition. Error: nrc=%0s :msg=%1s : line=%2u : token=%3s




E-GOB-102-022 [ngobjserv]: Table ReplicationDefinition: Parser Error: msg=%0s :line=%1u : token=%2s




E-GOB-102-023 [ngobjserv]: Failed to open the tablereplication definition file %0s .(%1d:%2s)




E-GOB-102-018 E-GOB-102-023


E-GOB-102-024 [ngobjserv]: Failed to parse the tablereplication definition file %0s .(%1d:%2s)




E-GOB-102-025 [ngobjserv]: Failed to identify theversion of the connect ObjectServer dueto a fatal error condition. (%0d:%1s)




E-GOB-102-035 [ngobjserv]: Failed to create theresynchronisation manager. (%0d:%1s)




E-GOB-102-036 [ngobjserv]: Failed to start theresynchronisation manager. (%0d:%1s)




E-GOB-102-037 [ngobjserv]: %0s: Failed to connect tothe ObjectServer %1s . (%2d:%3s)




E-GOB-102-038 [ngobjserv]: %0s: Fatal error occurredin the attempt to determine whether theconnected ObjectServer is a primary ornot. (%1d:%2s)




E-GOB-102-024 E-GOB-102-038


E-GOB-102-039 [ngobjserv]: %0s: Failed to check andsend the required flush IDUCcommand. (%1d:%2s)




E-GOB-102-040 [ngobjserv]: %0s: Failed to parse thetable replication definition file %1s .(%2d:%3s)




E-GOB-102-041 [ngobjserv]: %0s: Reader has failed toconnect to the ObjectServer %1s .(%2d:%3s)




E-GOB-102-042 [ngobjserv]: %0s: Reader has suffereda fatal error in the attempt to determinewhether the connected ObjectServer is aprimary or not. (%1d:%2s)




E-GOB-102-043 [ngobjserv]: %0s: Reader has failed tocheck and send the required flush IDUCcommand. (%1d:%2s)




E-GOB-102-044 [ngobjserv]: %0s: Writer has failed toconnect to the ObjectServer %1s .(%2d:%3s)




E-GOB-102-039 E-GOB-102-044


E-GOB-102-049 [ngobjserv]: Failed to read and fetchall of the iduc data from theObjectServer. (%0d:%1s)




E-GOB-102-050 [ngobjserv]: Failed to add the nipcclient library properties to the propertymanager. (%0d:%1s)




E-GOB-102-051 [ngobjserv]: Failed to add the nipcclient library arguments to the argumentmanager. (%0d:%1s)




E-GOB-102-052 [ngobjserv]: Failed to initialise thenipc client library. (%0d:%1s)




E-GOB-102-053 [ngobjserv]: %0s: Failed to connect tothe ObjectServer %1s . (%2d:%3s)




E-GOB-102-054 [ngobjserv]: %0s: Writer has suffereda fatal error in the attempt to determinewhether the connected ObjectServer is aprimary or not. (%1d:%2s)




E-GOB-102-049 E-GOB-102-054


E-GOB-102-055 [ngobjserv]: %0s: Fatal error occurredin the attempt to determine whether theconnected ObjectServer is a primary ornot. (%1d:%2s)




E-GOB-102-057 [ngobjserv]: Failed to send thecommand to the ObjectServer. (%0d:%1s)


Error: E-GOB-102-057: [ngobjserv]:Failed to send the command to the ObjectServer.(-19: General failure)

The example error message was written to abidirectional ObjectServer gateway log file andindicates that the gateway cannot send a command tothe ObjectServer.



Administrator response: This error can be caused bymany different conditions. Verify that the ObjectServeris running correctly and that it is managing the currentload.

To monitor ObjectServer performance, ensure that theObjectServer Profile property is enabled, and reviewthe profile and trigger statistics logs in the$NCHOME/omnibus/logs/ObjectServer_name_profiler_report.log1 and$NCHOME/omnibus/logs/ObjectServer_name_trigger_stats.log1 files.

Ensure that the total time from client requests andautomations in both the profile and trigger statisticslogs is less than the ObjectServer Granularity propertysetting (the default is 60 seconds).

If the total time is regularly longer than theGranularity property setting, ObjectServer performancemight degrade. Troubleshoot the clients and triggersthat are identified in the log files as consuming themost IDUC cycles. The client time might be longer thanthe granularity period because of ObjectServermultithreading.

For information about monitoring ObjectServerperformance, see the IBM Tivoli Netcool/OMNIbusAdministration Guide.

E-GOB-102-055 E-GOB-102-057


E-GOB-102-059 [ngobjserv]: Failed to create the nipcclient session structure. (%0d:%1s)




E-GOB-102-060 [ngobjserv]: Failed to destroy thenipc client session structure. (%0d:%1s)




E-GOB-102-061 [ngobjserv]: Failed to connect to theserver %0s . (%1d:%2s)




E-GOB-102-063 [ngobjserv]: Failed to create andsetup a command structure for SQL %0s. (%1d:%2s)




E-GOB-102-064 [ngobjserv]: Failed to determinewhether server connection is dead.Assuming that it is dead. (%0d:%1s)




E-GOB-102-066 [ngobjserv]: Failed to create the selfdescribing result set structure. (%0d:%1s)




E-GOB-102-059 E-GOB-102-066


E-GOB-102-067 [ngobjserv]: Failed to disconnectfrom the server. (%0d:%1s)




E-GOB-102-073 [ngobjserv]: Failed to set user data onnipc client session structure. (%0d:%1s)

System action: Not

error messages guide - ibm - united states and follow the instructions. ibm support assistant the...

Documents