IBM Tivoli Netcool Performance Manager1.4.5Wireline ComponentDocument Revision R2E1

Troubleshooting Guide

IBM

Note

Before using this information and the product it supports, read the information in “Notices” on page147.

© Copyright International Business Machines Corporation 2011, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager............................ 1Troubleshooting a problem......................................................................................................................... 1Troubleshooting checklist for Tivoli Netcool Performance Manager......................................................... 2Known problems and solutions................................................................................................................... 3

Error when running bofDump.................................................................................................................3mde.sh fails to run due to java error..................................................................................................... 3Data flow obstruction at LDR................................................................................................................. 5Error when running DataView synchronize.sh command............................................................... 5Can drill down only once for a resource from a report created by using Dashboard Application

Services Hub Table widget................................................................................................................5Cognos reports fail to run on Jazz for Service Management 1.1.3.0 with Tivoli Common

Reporting 3.1.3.0...............................................................................................................................6dbMgr menu options is listed twice.......................................................................................................6Topology Editor displays a not responding message every time the Deployer is run..........................6Fail to discover DASH in Topology Editor...............................................................................................6No data in KPW1001 and KPW1005 workspace...................................................................................6Topology not populated in KPW1007 workspace despite all the DataChannel components

running .............................................................................................................................................. 7rootDirectory and inputDirectory is empty in KPW1009 workspace......................................7PW agent deployment status is showing "Failed"..............................................................................7Data does not flow to LDR and DLDR in DataChannel Remote configuration.......................................7Dashboard Application Services Hub configuration proceeds even though you provide a wrong

password in the Topology Editor...................................................................................................... 8Ignore the message that appears even after the Dashboard Application Services Hub

discovery completes......................................................................................................................... 8Bookmarking a report option does not work......................................................................................... 8A report is not rendered correctly in Defined Resource View on Dashboard Application

Services Hub in Internet Explorer.....................................................................................................8Switching between languages to view DataView components on Dashboard Application

Services Hub......................................................................................................................................8Manual configuration required to install Reporting Services as non root user.....................................9Perform the LDAP configuration only post installation of Jazz for Service Management.................. 10Issue in viewing selected resources in Diagnostic view based on a property that does not have

a value for all the selected resources.............................................................................................10Some settings from charts are not saved to the workspace...............................................................10The resmgr command for barwidth settings on a chart does not work..............................................10You cannot view DataView reports if you set the DATAVIEW_CONTEXT to a non-default value.... 11Do not use the DataChannel collector numbers 500 and above........................................................ 11Avoid deleting a DataChannel as all other DataChannels and associated DataLoad collectors

also get deleted...............................................................................................................................11The supported scripts that are used for collecting the sizing information do not work on DB2....... 11Change the password for PV User in a migrated UBA channel from topology.xml file................. 11Currently, High Availability Manager (HAM) unistallation is not supported....................................... 11Aggregated Data Extraction query fails to extract the results into an XML file..................................12Slow Dashboard Application Services Hub UI response time in Tivoli Netcool Performance

Manager with IBM DB2 as the database support.......................................................................... 12CMEs and cross collector CMEs might not start..................................................................................12

Troubleshooting tasks............................................................................................................................... 12MIB compilation fails with error message...........................................................................................12Unable to run provisoinfod on remote DataMart host...................................................................13DataMart tools are disabled in pvm GUI..............................................................................................14

iii

SYSAUX tablespace error is seen in the walkback file after a non-default installation.....................14Data in DataView reports is still shown after a manual database purge partition............................. 15Warning message seen when starting the launchpad........................................................................ 16DataView Real time reporter fails to deliver real-time subscription data.......................................... 16Run Remote Database Check prompts warning message for a non-default Tivoli Netcool

Performance Manager deployment................................................................................................ 17Memory fault or Segmentation fault might cause proviso database installation to fail.....................18LDR and DLDR components take time to reconnect after a DB2 database restart............................19Group Summary Tables (GST) reports showing null value...............................................................19DataView upgrade fails due to improper nofile value settings....................................................... 20Some of the Tivoli Netcool Performance Manager components still showing 1.4.3 version after

upgrade to 1.4.4..............................................................................................................................21Some additional UBA properties with no values are seen in a loaded topology in upgrade

scenario........................................................................................................................................... 21DataMart process pismgr not getting started after upgrade.............................................................21Viewing online help in Acrobat Reader on AIX 7.1..............................................................................22Real-time charts do not work as expected..........................................................................................22Error: ORA-00001:unique constraint (PV_ADMIN.PK_SEGM) violated............................................. 23MDE memory constraint.......................................................................................................................24Incomplete SNMPv3 metric collection................................................................................................24Collectors swapping from idle to running at startup...........................................................................25Specifying the Database Home directory path in the non-default DB2 installation ......................... 25Changing DB_USERNAME for installing UBA Alcatel-Lucent 5620 SAM 2.13.0.0............................. 26Load pending state...............................................................................................................................27LDR in unavailable state for long time................................................................................................. 28Data flow obstruction at LDR............................................................................................................... 29

Searching knowledge bases...................................................................................................................... 29

Chapter 2. Logs (Wireline Component)................................................................. 31Overview.....................................................................................................................................................31Logs by component....................................................................................................................................31

Installation log files .............................................................................................................................31DataChannel logs................................................................................................................................. 32DataLoad logs....................................................................................................................................... 34DataMart logs....................................................................................................................................... 35DataView logs....................................................................................................................................... 35Database log.........................................................................................................................................36

Logs messages format...............................................................................................................................36Logging configuration and information utilities........................................................................................ 37

DataChannel logs configuration...........................................................................................................37DataView logs configuration................................................................................................................ 40statGet utility........................................................................................................................................40

Configuring trace and logging....................................................................................................................42Default logging level.............................................................................................................................42Trace logging for DataView.................................................................................................................. 42The configure command.................................................................................................................. 42

Troubleshooting.........................................................................................................................................44Event IDs....................................................................................................................................................44

Chapter 3. Introduction SNMP inventory.............................................................. 45Overview.....................................................................................................................................................45Discovery....................................................................................................................................................45

Metrics and properties......................................................................................................................... 45Inventory synchronization and change management.............................................................................. 46

Change management for elements......................................................................................................46Change management for subelements................................................................................................47

Grouping subelements.............................................................................................................................. 47

iv

Where to go from here............................................................................................................................... 47

Chapter 4. SNMP inventory troubleshooting......................................................... 49Overview.....................................................................................................................................................49Discovery troubleshooting.........................................................................................................................51

Discovery does not start.......................................................................................................................51dataload.env gets corrupted...........................................................................................................56Discovery starts but issues warning messages...................................................................................57Discovery seems to hang or never finishes......................................................................................... 63

Synchronization troubleshooting.............................................................................................................. 65Synchronization (elements)................................................................................................................. 65Synchronization (subelements)........................................................................................................... 70

Grouping troubleshooting..........................................................................................................................73Monitoring the Tivoli Netcool Performance Manager log file................................................................... 73Tivoli Netcool Performance Manager log messages.................................................................................74Burned subelements................................................................................................................................. 74

Scenario 1 - instance shift causes disconnect.................................................................................... 74Scenario 2 - instance shift causes burn...............................................................................................75

Where to go from here............................................................................................................................... 76

Chapter 5. SNMP inventory management............................................................. 77Regular monitoring.................................................................................................................................... 77Routine SNMP inventory management tasks............................................................................................77

Finding elements and subelements about to reach their retry limit.................................................. 77Finding elements and subelements that have been retired............................................................... 78

Chapter 6. Messages............................................................................................81DataChannel error messages.................................................................................................................... 81

GYMDC10000W....................................................................................................................................81GYMDC10001F.....................................................................................................................................81GYMDC10002F.....................................................................................................................................81GYMDC10003F.....................................................................................................................................81GYMDC10004F.....................................................................................................................................81GYMDC10005W....................................................................................................................................81GYMDC10006F.....................................................................................................................................81GYMDC10007W....................................................................................................................................81GYMDC10008.......................................................................................................................................81GYMDC10009W....................................................................................................................................81GYMDC10010W....................................................................................................................................82GYMDC10011W....................................................................................................................................82GYMDC10012W....................................................................................................................................82GYMDC10013.......................................................................................................................................82GYMDC10014W....................................................................................................................................82GYMDC10015W....................................................................................................................................82GYMDC10016.......................................................................................................................................82GYMDC10017.......................................................................................................................................82GYMDC10019.......................................................................................................................................82GYMDC10020.......................................................................................................................................82GYMDC10021I..................................................................................................................................... 82GYMDC10022.......................................................................................................................................82GYMDC10023W....................................................................................................................................82GYMDC10024.......................................................................................................................................82GYMDC10025.......................................................................................................................................82GYMDC10026.......................................................................................................................................82GYMDC10027.......................................................................................................................................82GYMDC10028I..................................................................................................................................... 82GYMDC10029.......................................................................................................................................82

v

GYMDC10030.......................................................................................................................................82GYMDC10031.......................................................................................................................................82GYMDC10032.......................................................................................................................................82GYMDC10033W....................................................................................................................................82GYMDC10034W....................................................................................................................................82GYMDC10035W....................................................................................................................................83GYMDC10036W....................................................................................................................................83GYMDC10037W....................................................................................................................................83GYMDC10038W....................................................................................................................................83GYMDC10039W....................................................................................................................................83GYMDC10040W....................................................................................................................................83GYMDC10041W....................................................................................................................................83GYMDC10042W....................................................................................................................................83GYMDC10043W....................................................................................................................................83GYMDC10044W....................................................................................................................................83GYMDC10045W....................................................................................................................................83GYMDC10046W....................................................................................................................................84GYMDC10047W....................................................................................................................................84GYMDC10048W....................................................................................................................................84GYMDC10049W....................................................................................................................................84GYMDC10050.......................................................................................................................................84GYMDC10051W....................................................................................................................................84GYMDC10052W....................................................................................................................................84GYMDC10053W....................................................................................................................................84GYMDC10054W....................................................................................................................................84GYMDC10055W....................................................................................................................................84GYMDC10056.......................................................................................................................................84GYMDC10057.......................................................................................................................................84GYMDC10058.......................................................................................................................................84GYMDC10059.......................................................................................................................................85GYMDC10060W....................................................................................................................................85GYMDC10061I..................................................................................................................................... 85GYMDC10062W....................................................................................................................................85GYMDC10063I..................................................................................................................................... 85GYMDC10064W....................................................................................................................................85GYMDC10065.......................................................................................................................................85GYMDC10066.......................................................................................................................................85GYMDC10067W....................................................................................................................................85GYMDC10068W....................................................................................................................................85GYMDC10069W....................................................................................................................................85GYMDC10070W....................................................................................................................................85GYMDC10071.......................................................................................................................................85GYMDC10072W....................................................................................................................................85GYMDC10100W....................................................................................................................................85GYMDC10101W....................................................................................................................................85GYMDC10102W....................................................................................................................................85GYMDC10103W....................................................................................................................................85GYMDC10104F.....................................................................................................................................85GYMDC10105F.....................................................................................................................................86GYMDC10106F.....................................................................................................................................86GYMDC10107W....................................................................................................................................86GYMDC10108W....................................................................................................................................86GYMDC10109W....................................................................................................................................86GYMDC10110W....................................................................................................................................86GYMDC10111W....................................................................................................................................86GYMDC10112W....................................................................................................................................86GYMDC10113W....................................................................................................................................86GYMDC10114W....................................................................................................................................86

vi

GYMDC10115W....................................................................................................................................86GYMDC10117W....................................................................................................................................86GYMDC10118F.....................................................................................................................................86GYMDC10119W....................................................................................................................................86GYMDC10120W....................................................................................................................................87GYMDC10121W....................................................................................................................................87GYMDC10122W....................................................................................................................................87GYMDC10123W....................................................................................................................................87GYMDC10124W....................................................................................................................................87GYMDC10125W....................................................................................................................................87GYMDC10126W....................................................................................................................................87GYMDC10127W....................................................................................................................................87GYMDC10128W....................................................................................................................................87GYMDC10129W....................................................................................................................................87GYMDC10130W....................................................................................................................................87GYMDC10131I..................................................................................................................................... 87GYMDC10132W....................................................................................................................................87GYMDC10133W....................................................................................................................................87GYMDC10134W....................................................................................................................................87GYMDC10135W....................................................................................................................................88GYMDC10136W....................................................................................................................................88GYMDC10137W....................................................................................................................................88GYMDC10138W....................................................................................................................................88GYMDC10139F.....................................................................................................................................88GYMDC10140W....................................................................................................................................88GYMDC10141F.....................................................................................................................................88GYMDC10142F.....................................................................................................................................88GYMDC10143W....................................................................................................................................88GYMDC10144W....................................................................................................................................88GYMDC10145W....................................................................................................................................88GYMDC10146I..................................................................................................................................... 88GYMDC10147W....................................................................................................................................88GYMDC10148W....................................................................................................................................88GYMDC10149W....................................................................................................................................88GYMDC10150W....................................................................................................................................89GYMDC10151W....................................................................................................................................89GYMDC10152W....................................................................................................................................89GYMDC10153W....................................................................................................................................89GYMDC10154W....................................................................................................................................89GYMDC10155W....................................................................................................................................89GYMDC10156F.....................................................................................................................................89GYMDC10157W....................................................................................................................................89GYMDC10160W....................................................................................................................................89GYMDC10161W....................................................................................................................................89GYMDC10162W....................................................................................................................................89GYMDC10163W....................................................................................................................................89GYMDC10164W....................................................................................................................................90GYMDC10165W....................................................................................................................................90GYMDC10166W....................................................................................................................................90GYMDC10167W....................................................................................................................................90GYMDC10168W....................................................................................................................................90GYMDC10169W....................................................................................................................................90GYMDC10170W....................................................................................................................................90GYMDC10171W....................................................................................................................................90GYMDC10172W....................................................................................................................................90GYMDC10173I..................................................................................................................................... 90GYMDC10174W....................................................................................................................................90GYMDC10175W....................................................................................................................................90

vii

GYMDC10176W....................................................................................................................................90GYMDC10177W....................................................................................................................................90GYMDC10178I..................................................................................................................................... 90GYMDC10179I..................................................................................................................................... 91GYMDC10180W....................................................................................................................................91GYMDC10181W....................................................................................................................................91GYMDC10182W....................................................................................................................................91GYMDC10183W....................................................................................................................................91GYMDC10184W....................................................................................................................................91GYMDC10185I..................................................................................................................................... 91GYMDC10186W....................................................................................................................................91GYMDC10187I..................................................................................................................................... 91GYMDC10188W....................................................................................................................................91GYMDC10189W....................................................................................................................................91GYMDC10200W....................................................................................................................................91GYMDC10201W....................................................................................................................................91GYMDC10204W....................................................................................................................................91GYMDC10205W....................................................................................................................................92GYMDC10206W....................................................................................................................................92GYMDC10207W....................................................................................................................................92GYMDC10208W....................................................................................................................................92GYMDC10209W....................................................................................................................................92GYMDC10211W....................................................................................................................................92GYMDC10212W....................................................................................................................................92GYMDC10213W....................................................................................................................................92GYMDC10214W....................................................................................................................................92GYMDC10215W....................................................................................................................................92GYMDC10216W....................................................................................................................................92GYMDC10217W....................................................................................................................................92GYMDC10218W....................................................................................................................................92GYMDC10219W....................................................................................................................................92GYMDC10220W....................................................................................................................................93GYMDC10301W....................................................................................................................................93GYMDC10302W....................................................................................................................................93GYMDC10304W....................................................................................................................................93GYMDC10305W....................................................................................................................................93GYMDC10306W....................................................................................................................................93GYMDC10307W....................................................................................................................................93GYMDC10308W....................................................................................................................................93GYMDC10309W....................................................................................................................................93GYMDC10310W....................................................................................................................................93GYMDC10311W....................................................................................................................................93GYMDC10312W....................................................................................................................................93GYMDC10313W....................................................................................................................................94GYMDC10314W....................................................................................................................................94GYMDC10315W....................................................................................................................................94GYMDC10316W....................................................................................................................................94GYMDC10317W....................................................................................................................................94GYMDC10318W....................................................................................................................................94GYMDC10400W....................................................................................................................................94GYMDC10401W....................................................................................................................................94GYMDC10402W....................................................................................................................................94GYMDC10404W....................................................................................................................................94GYMDC10405W....................................................................................................................................94GYMDC10406W....................................................................................................................................94GYMDC10407W....................................................................................................................................94GYMDC10408W....................................................................................................................................94GYMDC10409W....................................................................................................................................95

viii

GYMDC10410W....................................................................................................................................95GYMDC10411W....................................................................................................................................95GYMDC10412W....................................................................................................................................95GYMDC10413W....................................................................................................................................95GYMDC10414W....................................................................................................................................95GYMDC10415W....................................................................................................................................95GYMDC10416W....................................................................................................................................95GYMDC10417W....................................................................................................................................95GYMDC10418W....................................................................................................................................95GYMDC10419W....................................................................................................................................95GYMDC10420W....................................................................................................................................95GYMDC10421W....................................................................................................................................95GYMDC10422W....................................................................................................................................96GYMDC10423W....................................................................................................................................96GYMDC10424W....................................................................................................................................96GYMDC10425W....................................................................................................................................96GYMDC10426W....................................................................................................................................96GYMDC10427W....................................................................................................................................96GYMDC10428W....................................................................................................................................96GYMDC10429W....................................................................................................................................96GYMDC10430W....................................................................................................................................96GYMDC10431W....................................................................................................................................96GYMDC10432W....................................................................................................................................96GYMDC10433F.....................................................................................................................................96GYMDC10434F.....................................................................................................................................96GYMDC10435W....................................................................................................................................97GYMDC10437W....................................................................................................................................97GYMDC10439W....................................................................................................................................97GYMDC10440W....................................................................................................................................97GYMDC10441W....................................................................................................................................97GYMDC10442W....................................................................................................................................97GYMDC10443W....................................................................................................................................97GYMDC10444W....................................................................................................................................97GYMDC10445W....................................................................................................................................97GYMDC10446W....................................................................................................................................97GYMDC10447W....................................................................................................................................97GYMDC10448W....................................................................................................................................97GYMDC10501W....................................................................................................................................98GYMDC10502W....................................................................................................................................98GYMDC10503W....................................................................................................................................98GYMDC10504W....................................................................................................................................98GYMDC10505W....................................................................................................................................98GYMDC10506W....................................................................................................................................98GYMDC10507W....................................................................................................................................98GYMDC10508W....................................................................................................................................98GYMDC10509W....................................................................................................................................98GYMDC10510W....................................................................................................................................98GYMDC10511W....................................................................................................................................98GYMDC10512W....................................................................................................................................98GYMDC10519W....................................................................................................................................98GYMDC10520W....................................................................................................................................99GYMDC10521W....................................................................................................................................99GYMDC10522W....................................................................................................................................99GYMDC10549W....................................................................................................................................99GYMDC10559W....................................................................................................................................99GYMDC10579W....................................................................................................................................99GYMDC10590W....................................................................................................................................99GYMDC10591W....................................................................................................................................99

ix

GYMDC10592W....................................................................................................................................99GYMDC10593I..................................................................................................................................... 99GYMDC10594W....................................................................................................................................99GYMDC10600W....................................................................................................................................99GYMDC10601W....................................................................................................................................99GYMDC10602W....................................................................................................................................99GYMDC10603W................................................................................................................................. 100GYMDC10604W................................................................................................................................. 100GYMDC10605W................................................................................................................................. 100GYMDC10606W................................................................................................................................. 100GYMDC10607W................................................................................................................................. 100GYMDC10608W................................................................................................................................. 100GYMDC10609W................................................................................................................................. 100GYMDC10610W................................................................................................................................. 100GYMDC10611W................................................................................................................................. 100GYMDC10612W................................................................................................................................. 100GYMDC10613W................................................................................................................................. 100GYMDC10614W................................................................................................................................. 100GYMDC10615W................................................................................................................................. 100GYMDC10616F...................................................................................................................................101GYMDC10617W................................................................................................................................. 101GYMDC10618W................................................................................................................................. 101GYMDC10619W................................................................................................................................. 101GYMDC10620W................................................................................................................................. 101GYMDC10621W................................................................................................................................. 101GYMDC10622W................................................................................................................................. 101GYMDC10623W................................................................................................................................. 101GYMDC10624W................................................................................................................................. 101GYMDC10625W................................................................................................................................. 101GYMDC10626W................................................................................................................................. 101GYMDC10628W................................................................................................................................. 101GYMDC10629W................................................................................................................................. 101GYMDC10630.....................................................................................................................................101GYMDC10631W................................................................................................................................. 101GYMDC10632W................................................................................................................................. 102GYMDC10633.....................................................................................................................................102GYMDC10634W................................................................................................................................. 102GYMDC10635W................................................................................................................................. 102GYMDC10636W................................................................................................................................. 102GYMDC10637W................................................................................................................................. 102GYMDC10638W................................................................................................................................. 102GYMDC10639W................................................................................................................................. 102GYMDC10640W................................................................................................................................. 102GYMDC10641W................................................................................................................................. 102GYMDC10642W................................................................................................................................. 102GYMDC10643W................................................................................................................................. 102GYMDC10644W................................................................................................................................. 102GYMDC10645W................................................................................................................................. 102GYMDC10646W................................................................................................................................. 103GYMDC10647W................................................................................................................................. 103GYMDC10648W................................................................................................................................. 103GYMDC10649W................................................................................................................................. 103GYMDC10650W................................................................................................................................. 103GYMDC10651W................................................................................................................................. 103GYMDC10652W................................................................................................................................. 103GYMDC10653W................................................................................................................................. 103GYMDC10654W................................................................................................................................. 103GYMDC10702W................................................................................................................................. 103

x

GYMDC10703W................................................................................................................................. 103GYMDC10704W................................................................................................................................. 103GYMDC10705W................................................................................................................................. 103GYMDC10706W................................................................................................................................. 103GYMDC10707W................................................................................................................................. 104GYMDC10708W................................................................................................................................. 104GYMDC10709W................................................................................................................................. 104GYMDC10710W................................................................................................................................. 104GYMDC10711W................................................................................................................................. 104GYMDC10712W................................................................................................................................. 104GYMDC10751I................................................................................................................................... 104GYMDC10752I................................................................................................................................... 104GYMDC10753I................................................................................................................................... 104GYMDC10754I................................................................................................................................... 104GYMDC10755I................................................................................................................................... 104GYMDC10756I................................................................................................................................... 104GYMDC10757I................................................................................................................................... 104GYMDC10758I................................................................................................................................... 104GYMDC10759I................................................................................................................................... 104GYMDC10760I................................................................................................................................... 104GYMDC10800W................................................................................................................................. 104GYMDC10801W................................................................................................................................. 104GYMDC10802W................................................................................................................................. 104GYMDC10803F...................................................................................................................................104GYMDC10804F...................................................................................................................................104GYMDC10805F...................................................................................................................................104GYMDC10806F...................................................................................................................................104GYMDC10807W................................................................................................................................. 104GYMDC10808W................................................................................................................................. 105GYMDC10809W................................................................................................................................. 105GYMDC10810.....................................................................................................................................105GYMDC10811W................................................................................................................................. 105GYMDC10812W................................................................................................................................. 105GYMDC10850I................................................................................................................................... 105GYMDC10851I................................................................................................................................... 105GYMDC10852.....................................................................................................................................105GYMDC10853.....................................................................................................................................105GYMDC10854I................................................................................................................................... 105GYMDC10855I................................................................................................................................... 105GYMDC10856.....................................................................................................................................105GYMDC10857I................................................................................................................................... 105GYMDC10858I................................................................................................................................... 105GYMDC10859I................................................................................................................................... 105GYMDC10860I................................................................................................................................... 105GYMDC10861I................................................................................................................................... 105GYMDC10862I................................................................................................................................... 105GYMDC10863I................................................................................................................................... 105GYMDC10864.....................................................................................................................................105GYMDC10865W................................................................................................................................. 105GYMDC10866W................................................................................................................................. 105GYMDC10900W................................................................................................................................. 105GYMDC10901W................................................................................................................................. 105GYMDC10902.....................................................................................................................................105GYMDC10903W................................................................................................................................. 105GYMDC10904W................................................................................................................................. 106GYMDC10905W................................................................................................................................. 106GYMDC11016W................................................................................................................................. 106GYMDC11017W................................................................................................................................. 106

xi

GYMDC11018W................................................................................................................................. 106GYMDC11019W................................................................................................................................. 106GYMDC12347W................................................................................................................................. 106GYMDC12349W................................................................................................................................. 106GYMDC12350W................................................................................................................................. 106GYMDC12351W................................................................................................................................. 106GYMDC12352W................................................................................................................................. 106GYMDC12356W................................................................................................................................. 107GYMDC12357W................................................................................................................................. 107GYMDC12358W................................................................................................................................. 107GYMDC12360W................................................................................................................................. 107GYMDL39001W..................................................................................................................................107GYMDL39002..................................................................................................................................... 107GYMDL39201..................................................................................................................................... 107GYMDL39205W..................................................................................................................................107GYMDL39206W..................................................................................................................................107GYMDL39207..................................................................................................................................... 107GYMDL39208W..................................................................................................................................107GYMDC39209W................................................................................................................................. 107GYMDL39209W..................................................................................................................................108GYMDL39210W..................................................................................................................................108GYMDC39211I................................................................................................................................... 108GYMDL39211W..................................................................................................................................108GYMDC39212W................................................................................................................................. 108GYMDL39212W..................................................................................................................................108GYMDL39213W..................................................................................................................................108GYMDL39214W..................................................................................................................................108GYMDL39215W..................................................................................................................................108GYMDL39217W..................................................................................................................................108GYMDL39218..................................................................................................................................... 108GYMDL39219..................................................................................................................................... 109GYMDL39220W..................................................................................................................................109GYMDL39221W..................................................................................................................................109GYMDL39222I....................................................................................................................................109GYMDL39223W..................................................................................................................................109GYMDL39224W..................................................................................................................................109GYMDL39225W..................................................................................................................................109GYMDL39226W..................................................................................................................................109GYMDL39801..................................................................................................................................... 109GYMDL39802..................................................................................................................................... 109GYMDL39805..................................................................................................................................... 109GYMDL39806..................................................................................................................................... 109GYMDL39807..................................................................................................................................... 109GYMDL39809I....................................................................................................................................109GYMDL39810I....................................................................................................................................109GYMDL39811W..................................................................................................................................110GYMDL39812W..................................................................................................................................110GYMDL42000..................................................................................................................................... 110GYMDL42001..................................................................................................................................... 110GYMDL42002W..................................................................................................................................110

DataLoad error messages........................................................................................................................110GYMDL30002F................................................................................................................................... 110GYMDL30004F................................................................................................................................... 110GYMDL30005F................................................................................................................................... 110GYMDL30006F................................................................................................................................... 111GYMDL30007F................................................................................................................................... 111GYMDL30100W..................................................................................................................................111GYMDL30101W..................................................................................................................................111

xii

GYMDL30102W..................................................................................................................................111GYMDL30106W..................................................................................................................................111GYMDL30107W..................................................................................................................................112GYMDL30108W..................................................................................................................................112GYMDL30112W..................................................................................................................................112GYMDL30113W..................................................................................................................................112GYMDL30114W..................................................................................................................................112GYMDL30115W..................................................................................................................................112GYMDL30116W..................................................................................................................................113GYMDL30117W..................................................................................................................................113GYMDL30118W..................................................................................................................................113GYMDL30119W..................................................................................................................................113GYMDL30120W..................................................................................................................................113GYMDL30121W..................................................................................................................................113GYMDL30122W..................................................................................................................................113GYMDL30128W..................................................................................................................................114GYMDL30129W..................................................................................................................................114GYMDL30130W..................................................................................................................................114GYMDL30131W..................................................................................................................................114GYMDL30132W..................................................................................................................................114GYMDL30133W..................................................................................................................................114GYMDL30134W..................................................................................................................................114GYMDL30135W..................................................................................................................................115GYMDL30135W..................................................................................................................................115GYMDL30136W..................................................................................................................................115GYMDL30137W..................................................................................................................................115GYMDL30138W..................................................................................................................................115GYMDL30139W..................................................................................................................................115GYMDL30140W..................................................................................................................................115GYMDL30142W..................................................................................................................................115GYMDL30143W..................................................................................................................................116GYMDL30145W..................................................................................................................................116GYMDL30146W..................................................................................................................................116GYMDL30148W..................................................................................................................................116GYMDL30150W..................................................................................................................................116GYMDL30151W..................................................................................................................................116GYMDL30160W..................................................................................................................................116GYMDL30161W..................................................................................................................................117GYMDL30162W..................................................................................................................................117GYMDL30163W..................................................................................................................................117GYMDL30164W..................................................................................................................................117GYMDL30165W..................................................................................................................................117GYMDL30166W..................................................................................................................................117GYMDL30167W..................................................................................................................................117GYMDL30168W..................................................................................................................................118GYMDL30169W..................................................................................................................................118GYMDL30170W..................................................................................................................................118GYMDL30171W..................................................................................................................................118GYMDL30172W..................................................................................................................................118GYMDL30173W..................................................................................................................................118GYMDL30174W..................................................................................................................................118GYMDL30175W..................................................................................................................................118GYMDL30176W..................................................................................................................................118GYMDL30177W..................................................................................................................................118GYMDL30178W..................................................................................................................................119GYMDL30179W..................................................................................................................................119GYMDL30180W..................................................................................................................................119GYMDL30181W..................................................................................................................................119

xiii

GYMDL30182W..................................................................................................................................119GYMDL30183W..................................................................................................................................119GYMDL30184W..................................................................................................................................119GYMDL30185W..................................................................................................................................120GYMDL30186W..................................................................................................................................120GYMDL30189W..................................................................................................................................120GYMDL30190W..................................................................................................................................120GYMDL30191W..................................................................................................................................120GYMDL30192W..................................................................................................................................120GYMDL30194W..................................................................................................................................121GYMDL30195W..................................................................................................................................121GYMDL30196W..................................................................................................................................121GYMDL30197W..................................................................................................................................121GYMDL30198W..................................................................................................................................121GYMDL30199W..................................................................................................................................121GYMDL30200W..................................................................................................................................121GYMDL30204W..................................................................................................................................121GYMDL30205W..................................................................................................................................121GYMDL30206W..................................................................................................................................122GYMDL30208W..................................................................................................................................122GYMDL30208W..................................................................................................................................122GYMDL30209W..................................................................................................................................122GYMDL30209W..................................................................................................................................122GYMDL30210W..................................................................................................................................122GYMDL30211W..................................................................................................................................122GYMDL30212W..................................................................................................................................122GYMDL30213W..................................................................................................................................122GYMDL30214W..................................................................................................................................123GYMDL30215W..................................................................................................................................123GYMDL30216W..................................................................................................................................123GYMDL30217W..................................................................................................................................123GYMDL30218W..................................................................................................................................123GYMDL30219W..................................................................................................................................123GYMDL30220W..................................................................................................................................123GYMDL30222W..................................................................................................................................123GYMDL30224W..................................................................................................................................124GYMDL30225W..................................................................................................................................124GYMDL30226W..................................................................................................................................124GYMDL30227W..................................................................................................................................124GYMDL30228W..................................................................................................................................124GYMDL30229W..................................................................................................................................124GYMDL30230W..................................................................................................................................124GYMDL30231W..................................................................................................................................124GYMDL30232W..................................................................................................................................124GYMDL30233W..................................................................................................................................125GYMDL30234W..................................................................................................................................125GYMDL30235W..................................................................................................................................125GYMDL30236W..................................................................................................................................125GYMDL30237W..................................................................................................................................125GYMDL30238W..................................................................................................................................125GYMDL30239W..................................................................................................................................126GYMDL30241W..................................................................................................................................126GYMDL30242W..................................................................................................................................126GYMDL30243W..................................................................................................................................126GYMDL30244W..................................................................................................................................126GYMDL30245W..................................................................................................................................126GYMDL30246W..................................................................................................................................126GYMDL30247W..................................................................................................................................127

xiv

GYMDL30248W..................................................................................................................................127GYMDL30249W..................................................................................................................................127GYMDL30250W..................................................................................................................................127GYMDL30251W..................................................................................................................................127GYMDL30253W..................................................................................................................................127GYMDL30254W..................................................................................................................................127GYMDL30255W..................................................................................................................................127GYMDL30256W..................................................................................................................................127GYMDL30257W..................................................................................................................................128GYMDL30258W..................................................................................................................................128GYMDL30259W..................................................................................................................................128GYMDL30261W..................................................................................................................................128GYMDL30262W..................................................................................................................................128GYMDL30263W..................................................................................................................................128GYMDL30264W..................................................................................................................................128GYMDL30265W..................................................................................................................................128GYMDL30266W..................................................................................................................................128GYMDL30271W..................................................................................................................................129GYMDL30272W..................................................................................................................................129GYMDL30273W..................................................................................................................................129GYMDL30274W..................................................................................................................................129GYMDL30275W..................................................................................................................................129GYMDL30276W..................................................................................................................................129GYMDL30277W..................................................................................................................................129GYMDL30278W..................................................................................................................................130GYMDL30279W..................................................................................................................................130GYMDL30280W..................................................................................................................................130GYMDL30281W..................................................................................................................................130GYMDL30282W..................................................................................................................................130GYMDL30283W..................................................................................................................................130GYMDL30284W..................................................................................................................................130GYMDL30285W..................................................................................................................................130GYMDL30286W..................................................................................................................................131GYMDL30287W..................................................................................................................................131GYMDL31001I....................................................................................................................................131GYMDL31003I....................................................................................................................................131GYMDL31004I....................................................................................................................................131GYMDL31005I....................................................................................................................................131GYMDL31006I....................................................................................................................................131GYMDL31007I....................................................................................................................................131GYMDL31009I....................................................................................................................................131GYMDL31010I....................................................................................................................................131GYMDL31011I....................................................................................................................................132GYMDL31012I....................................................................................................................................132GYMDL31014I....................................................................................................................................132GYMDL31015I....................................................................................................................................132GYMDL31016I....................................................................................................................................132GYMDL31017I....................................................................................................................................132GYMDL31018I....................................................................................................................................132GYMDL31019I....................................................................................................................................132GYMDL31020I....................................................................................................................................132GYMDL31021I....................................................................................................................................132GYMDL31022I....................................................................................................................................132GYMDL31023I....................................................................................................................................132GYMDL31024I....................................................................................................................................132GYMDL31051I....................................................................................................................................132GYMDL31052I....................................................................................................................................132GYMDL31053I....................................................................................................................................132

xv

GYMDL31054I....................................................................................................................................133GYMDL31055I....................................................................................................................................133GYMDL31056I....................................................................................................................................133GYMDL31057I....................................................................................................................................133GYMDL31058I....................................................................................................................................133GYMDL31059I....................................................................................................................................133GYMDL31060I....................................................................................................................................133GYMDL31061I....................................................................................................................................133GYMDL31062I....................................................................................................................................133GYMDL31063I....................................................................................................................................133GYMDL31064I....................................................................................................................................133GYMDL31065I....................................................................................................................................133GYMDL31066I....................................................................................................................................133GYMDL31067I....................................................................................................................................134GYMDL31068I....................................................................................................................................134GYMDL31069I....................................................................................................................................134GYMDL31070I....................................................................................................................................134GYMDL31071I....................................................................................................................................134GYMDL31072I....................................................................................................................................134GYMDL31077I....................................................................................................................................134GYMDL31078I....................................................................................................................................134GYMDL31079I....................................................................................................................................134GYMDL31084I....................................................................................................................................134GYMDL31085I....................................................................................................................................134GYMDL31086I....................................................................................................................................134GYMDL31087I....................................................................................................................................135GYMDL31088I....................................................................................................................................135GYMDL31089I....................................................................................................................................135GYMDL31090I....................................................................................................................................135GYMDL31091I....................................................................................................................................135GYMDL31092I....................................................................................................................................135GYMDL31093I....................................................................................................................................135GYMDL31094I....................................................................................................................................135GYMDL31095I....................................................................................................................................135GYMDL31096I....................................................................................................................................135GYMDL31098I....................................................................................................................................135GYMDL31099I....................................................................................................................................135GYMDL31100I....................................................................................................................................135GYMDL31101I....................................................................................................................................135GYMDL31102I....................................................................................................................................135GYMDL31103I....................................................................................................................................135GYMDL31105I....................................................................................................................................136GYMDL31106I....................................................................................................................................136GYMDL31107I....................................................................................................................................136GYMDL31108I....................................................................................................................................136GYMDL31109I....................................................................................................................................136GYMDL31111I....................................................................................................................................136GYMDL31112I....................................................................................................................................136GYMDL31113I....................................................................................................................................136GYMDL31114I....................................................................................................................................136GYMDL31115I....................................................................................................................................136

DataView operational messages.............................................................................................................136GYMVB0002E.....................................................................................................................................137GYMVB0003W....................................................................................................................................137GYMVB0004E.....................................................................................................................................137GYMVB0005E.....................................................................................................................................137GYMVB0006E.....................................................................................................................................137GYMVB0008E.....................................................................................................................................137

xvi

GYMVB0009E.....................................................................................................................................137GYMVB0010E.....................................................................................................................................137GYMVB0011E.....................................................................................................................................137GYMVB0012E.....................................................................................................................................137GYMB0013E....................................................................................................................................... 137GYMB0015E....................................................................................................................................... 137GYMVB0017E.....................................................................................................................................137GYMVB00018E...................................................................................................................................138GYMVB0019E.....................................................................................................................................138GYMVB0020W....................................................................................................................................138GYMVB0021E.....................................................................................................................................138GYMVB9000E.....................................................................................................................................138GYMVB90001E...................................................................................................................................138GYMVB9010E.....................................................................................................................................138GYMVC0000E..................................................................................................................................... 138GYMVC0002E..................................................................................................................................... 138GYMVC0003E..................................................................................................................................... 138GYMVC0005E..................................................................................................................................... 138GYMVC0006E..................................................................................................................................... 138GYMVC0007E..................................................................................................................................... 139GYMVC0009E..................................................................................................................................... 139GYMVC0010E..................................................................................................................................... 139GYMVC0011E..................................................................................................................................... 139GYMVC0049E..................................................................................................................................... 139GYMVC0050E..................................................................................................................................... 139GYMVC0064E..................................................................................................................................... 139GYMVC0076E..................................................................................................................................... 139GYMVC0090E..................................................................................................................................... 139GYMVC0091E..................................................................................................................................... 140GYMVC0092E..................................................................................................................................... 140GYMVC0094E..................................................................................................................................... 140GYMVC0095E..................................................................................................................................... 140GYMVC0096E..................................................................................................................................... 140GYMVC0100E..................................................................................................................................... 140GYMVC0101E..................................................................................................................................... 140GYMVC0102E..................................................................................................................................... 140GYMVC0103E..................................................................................................................................... 140GYMVC0105E..................................................................................................................................... 140GYMVC0106E..................................................................................................................................... 140GYMVC0110W....................................................................................................................................140GYMVD0001E.....................................................................................................................................140GYMVD0001W....................................................................................................................................141GYMVD0002E.....................................................................................................................................141GYMVD0002W....................................................................................................................................141GYMVD0003E.....................................................................................................................................141GYMVD0003W....................................................................................................................................141GYMVD0004E.....................................................................................................................................141GYMVD0004W....................................................................................................................................141GYMVD0005W....................................................................................................................................142GYMVD0006E.....................................................................................................................................142GYMVD0006W....................................................................................................................................142GYMVD0007E.....................................................................................................................................142GYMVD0007W....................................................................................................................................142GYMVD0008E.....................................................................................................................................142GYMVD0008W....................................................................................................................................142

Chapter 7. Contacting IBM support.....................................................................145

xvii

Exchanging information with IBM........................................................................................................... 145Sending information to IBM Support.................................................................................................145

Notices..............................................................................................................147Trademarks..............................................................................................................................................148Terms and conditions for product documentation.................................................................................149

xviii

Chapter 1. Troubleshooting Tivoli NetcoolPerformance Manager

You can use this troubleshooting and support information to troubleshoot problems with Tivoli NetcoolPerformance Manager.

This information assumes a working installation of Tivoli Netcool Performance Manager. For installation orupgrade problems, refer to the installation and upgrade information.

Troubleshooting a problemTroubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is todetermine why something does not work as expected and how to resolve the problem.

The first step in the troubleshooting process is to describe the problem completely. Problem descriptionshelp you and the IBM technical-support representative know where to start to find the cause of theproblem. This step includes asking yourself basic questions:

• What are the symptoms of the problem?• Where does the problem occur?• When does the problem occur?• Under which conditions does the problem occur?• Can the problem be reproduced?

The answers to these questions typically lead to a good description of the problem, which can then leadyou a problem resolution.

What are the symptoms of the problem?

When starting to describe a problem, the most obvious question is "What is the problem?" This questionmight seem straightforward; however, you can break it down into several more-focused questions thatcreate a more descriptive picture of the problem. These questions can include:

• Who, or what, is reporting the problem?• What are the error codes and messages?• How does the system fail? For example, is it a loop, hang, crash, performance degradation, or incorrect

result?

Where does the problem occur?

Determining where the problem originates is not always easy, but it is one of the most important steps inresolving a problem. Many layers of technology can exist between the reporting and failing components.Networks, disks, and drivers are only a few of the components to consider when you are investigatingproblems.

The following questions help you to focus on where the problem occurs to isolate the problem layer:

• Is the problem specific to one platform or operating system, or is it common across multiple platformsor operating systems?

• Is the current environment and configuration supported?

If one layer reports the problem, the problem does not necessarily originate in that layer. Part ofidentifying where a problem originates is understanding the environment in which it exists. Take sometime to completely describe the problem environment, including the operating system and version, allcorresponding software and versions, and hardware information. Confirm that you are running within an

© Copyright IBM Corp. 2011, 2019 1

environment that is a supported configuration; many problems can be traced back to incompatible levelsof software that are not intended to run together or have not been fully tested together.

When does the problem occur?

Develop a detailed timeline of events leading up to a failure, especially for those cases that are one-timeoccurrences. You can most easily develop a timeline by working backward: Start at the time an error wasreported (as precisely as possible, even down to the millisecond), and work backward through theavailable logs and information. Typically, you need to look only as far as the first suspicious event that youfind in a diagnostic log.

To develop a detailed timeline of events, answer these questions:

• Does the problem happen only at a certain time of day or night?• How often does the problem happen?• What sequence of events leads up to the time that the problem is reported?• Does the problem happen after an environment change, such as upgrading or installing software or

hardware?

Responding to these types of questions can give you a frame of reference in which to investigate theproblem.

Under which conditions does the problem occur?

Knowing which systems and applications are running at the time that a problem occurs is an importantpart of troubleshooting. These questions about your environment can help you to identify the root causeof the problem:

• Does the problem always occur when the same task is being performed?• Does a certain sequence of events need to occur for the problem to surface?• Do any other applications fail at the same time?

Answering these types of questions can help you explain the environment in which the problem occursand correlate any dependencies. Remember that just because multiple problems might have occurredaround the same time, the problems are not necessarily related.

Can the problem be reproduced?

From a troubleshooting standpoint, the ideal problem is one that can be reproduced. Typically, when aproblem can be reproduced you have a larger set of tools or procedures at your disposal to help youinvestigate. Consequently, problems that you can reproduce are often easier to debug and solve.However, problems that you can reproduce can have a disadvantage: If the problem is of significantbusiness impact, you do not want it to recur. If possible, re-create the problem in a test or developmentenvironment, which typically offers you more flexibility and control during your investigation.

• Can the problem be re-created on a test system?• Are multiple users or applications encountering the same type of problem?• Can the problem be re-created by running a single command, a set of commands, or a particular

application?

“Searching knowledge bases” on page 29

Troubleshooting checklist for Tivoli Netcool Performance ManagerBy answering a set of questions that are structured into a checklist, you can sometimes identify the causeof a problem and find a resolution to the problem on your own.

Answering the following questions can help you to identify the source of a problem that is occurring withTivoli® Netcool® Performance Manager:

2 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

1. Is your issue a known problem?2. Is the configuration supported?3. What are you doing when the problem occurs?

• Installing, upgrading, or migrating the product• Doing administration tasks• Doing authorization tasks• Networking• Using the product

4. What, if any, error messages or error codes were issued?5. If the checklist does not guide you to a resolution, collect additional diagnostic data. This data is

necessary for an IBM® technical-support representative to effectively troubleshoot and assist you inresolving the problem.

Known problems and solutionsA list of known problems and their solutions for Tivoli Netcool Performance Manager Wireline ComponentCore are described here.

When you encounter a problem while using Tivoli Netcool Performance Manager - Wireline component,the first thing to do is to check the detailed log files for that component. Most issues can be solved byreferring to the log files.

Error when running bofDump

Symptoms

You might see the following error message when you run the bofDump command after youhave upgraded to Tivoli Netcool Performance Manager 1.4.5.

$ bofDump 2019.06.10-06.45.00~000.NRAW.BOFShutting down the image with error: Message not understood: #style:

Resolving the problemPerform the following steps:

1. You have upgrade to Tivoli Netcool Performance Manager 1.4.5.2. Download and apply the following interim fix: 1.4.5.0-TIV-TNPM-IF0002

• The interim fix (1.4.5.0-TIV-TNPM-IF0002 ) contains the following files:

– 1.4.5.0-TIV-TNPM-AIX-FP0002.zip (11.07 KB)– 1.4.5.0-TIV-TNPM-IF0002.README (8.06 KB):

Refer to the readme on how to apply the patch.

mde.sh fails to run due to java error

Symptoms

You might see the following error message when you run the mde.sh script on an Oracle database setup.

# cd /opt/MDE/bin# ./mde.sh -u smadmin -p smadmin1 -host locathostname.ibm.com -port 16310 -s 2019-06-20T00:00:00+0800 -e 2019-06-21T00:00:00+0800 -query /opt/MDE/QueryDir/<query>.xml -o /opt/MDE/Results -f xml

Licensed Materials - Property of IBM

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 3

5724-W865724-X63(C) Copyright IBM Corporation 2009. All Rights Reserved.

GYMVC1004I: Executing query...Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64 at com.ibm.tivoli.tnpm.datalet.configuration.server.ServerConfiguration$BasicAuthenicationURLStreamHandler.openConnection(ServerConfiguration.java:582) at java.net.URL.openConnection(URL.java:982) at java.net.URL.openStream(URL.java:1048) at com.ibm.tivoli.tnpm.datalet.configuration.server.ServerConfiguration.getConfigurationInputStream(ServerConfiguration.java:272) at com.ibm.tivoli.tnpm.datalet.configuration.server.ServerConfiguration.load(ServerConfiguration.java:192) at com.ibm.tivoli.tnpm.datalet.configuration.server.ServerConfiguration.getDomains(ServerConfiguration.java:140) at com.ibm.tivoli.tnpm.datalet.container.Container.getContext(Container.java:377) at com.ibm.tivoli.tnpm.datalet.container.Container.execute(Container.java:309) at com.ibm.tivoli.tnpm.datalet.container.Container.execute(Container.java:276) at com.ibm.tivoli.tnpm.dal.mde.engine.DefaultEngine.execute(DefaultEngine.java:146) at com.ibm.tivoli.tnpm.dal.mde.engine.Engine.execute(Engine.java:477) at com.ibm.tivoli.tnpm.dal.mde.engine.Engine.extractResultset(Engine.java:263) at com.ibm.tivoli.tnpm.dal.mde.engine.Engine.extract(Engine.java:121) at com.ibm.tivoli.tnpm.dal.mde.client.Application.main(Application.java:65)Caused by: java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64 at java.net.URLClassLoader$1.run(URLClassLoader.java:367) at java.net.URLClassLoader$1.run(URLClassLoader.java:356) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:355) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:323) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 14 more

CausesThe issue is most likely cause by not setting the Java path correctly.

Resolving the problem

Make sure that you run the following steps (for non-default user) before you run the mde.sh.

1. Run the following commands to export the JAVA_HOME path:

$ export JAVA_HOME=/opt/IBM/java$ export PATH=$JAVA_HOME/bin:$PATH

Or

$ export JAVA_HOME=/opt/IBM/proviso/jvm$ export PATH=$JAVA_HOME/bin:$PATH

2. Verify the Java version:

$ java -versionsomeuser@somehost.com:/opt/MDE/bin$ java -version java version "1.8.0_191"Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.8.0_191-b12 26_Oct_2018_18_39 solaris sparcv9(SR5 FP25)) Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode) IBM Java ORB build orb80-20181016.00 XML build XL TXE Java 1.0.60 XML build IBM JAXP 1.6.1 XML build XML4J 4.5.30

3. Make sure that you set the MDE_JDBC_DRIVER for Oracle database to point directly to the requiredJDBC driver implementation.

<Oracle18_client-32bit_home>/jdbc/lib/ojdbc8.jar

For example,

export MDE_JDBC_DRIVER=/opt/oracle/product/18.1.0-client32/jdbc/lib/ojdbc8.jar

4 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Data flow obstruction at LDR

SymptomsIf you find that the data flow is obstructed at LDR, increase the size of thePV_PV_ADMIN_TEMP_001.dbf tablespace.

Resolving the problemIncrease the size of the PV_PV_ADMIN_TEMP_001.dbf tablespace by using the following command:

SQL> alter database tempfile '/raid_3/oradata/PV/PV_PV_ADMIN_TEMP_001.dbf' resize 3G

Specify the size as per your requirements.

Error when running DataView synchronize.sh command

SymptomsWhen you run the DataView synchronize.sh command, it exits with an error message: GYMVC0001E:Error occurred: exceptions.NameError: info

Resolving the problem

Copy the custom DataView content, such as JSP pages, CSS and images, from a remote DashboardApplication Services Hub to a local Dashboard Application Services Hub.

Can drill down only once for a resource from a report created by using DashboardApplication Services Hub Table widget

Symptoms

The Dashboard Application Services Hub component in the UI Services of IBM Jazz® for ServiceManagement product supports custom dashboards. The Dashboard Application Services Hub Tablewidget displays data from multivariate and structured data sets in tabular format.

You can drill down for a particular resource only once from a report that was created by using theDashboard Application Services Hub Table widget. If you click the same resource to drill down, the reportdoes not load.

Resolving the problem

On the Dashboard Application Services Hub portal, you can drill down to more detailed reports by clickingthe resources from the report view table.

Note: The following steps are applicable to reports that was created by using Dashboard ApplicationServices Hub Table widget.

1. Click Resource1 from Report1. It drills down to a more detailed report, Resource1_drilldown for thatspecific resource.

2. Close that particular report, Resource1_drilldown, and click the same resource, Resource1 again fromReport1. The Resource1_drilldown report does not load.

3. Click a different resource, Resource2 from Report1. It drills down to a more detailed report,Resource2_drilldown.

4. Close the Resource2_drilldown report and click the initial resource, Resource1 from Report1. TheResource1_drilldown report loads now.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 5

Cognos reports fail to run on Jazz for Service Management 1.1.3.0 with Tivoli CommonReporting 3.1.3.0

Symptoms

Wireline Cognos reports fail to run on Jazz for Service Management 1.1.3.0 with Tivoli Common ReportingV3.1.3.0.

This issue is seen with all the Tivoli Netcool Performance Manager Wireline common packs.

CausesIBM Cognos V10.2.2 that is available with Tivoli Common Reporting v3.1.3.0 does not support TivoliNetcool Performance Manager JDBC driver.

dbMgr menu options is listed twice

Symptoms

When you use the dbMgr command in the menu mode, the menu options (List of Procedures) are beinglisted twice.

Topology Editor displays a not responding message every time the Deployer is run

Symptoms

When you select Run > Run Deployer from the Topology editor, you see a pop up screen that reports thetopology_name.xml is not responding.

This issue is seen on RHEL 7.2, 7.3 environment.

Resolving the problem

Select Wait. The deployer works as normal.

Fail to discover DASH in Topology Editor

SymptomsUnable to auto discover Dashboard Application Services Hub from the Topology Editor if Tivoli CommonReporting is not installed in Jazz for Service Management.

Resolving the problemThis issue will be fixed in the next release of Tivoli Netcool Performance Manager.

No data in KPW1001 and KPW1005 workspace

SymptomsNo data found in KPW1001 and KPW1005 workspace.

Resolving the problemKPW1001 workspace

1. After installing the Tivoli Netcool Performance Manager Monitoring Agent (pw), you need torename the following script:

cd /opt/IBM/ITM/lx8266/pw/bin/mv dctopology.sh dctoplogy.sh

6 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

cd /opt/IBM/ITM/lx8266/pw/bin/mv itm_ldr_lag.sh itm_ldr_tag.sh

2. Ensure that you use the renamed scripts:

/opt/IBM/ITM/lx8266/pw/bin/dctoplogy.sh/opt/IBM/ITM/lx8266/pw/bin/itm_ldr_tag.sh

KPW1005 workspaceThis issue will be fixed in the next release.

Topology not populated in KPW1007 workspace despite all the DataChannel componentsrunning

SymptomsThe topology is not populated in KPW1007 workspace although all the DataChannel components arerunning.

Resolving the problem

1. You need to drag the topology icon manually into the workspace to populate the topology.

rootDirectory and inputDirectory is empty in KPW1009 workspace

Symptoms

The rootDirectory and inputDirectory is empty for some DataChannel components in KPW1009configuration workspace.

Resolving the problemThis issue will be fixed in the next release of Tivoli Netcool Performance Manager.

PW agent deployment status is showing "Failed"

Symptoms

From the following command, ./tacmd getdeploystatus -g <transaction_id>, the remotedeployment status of pw agent is showing "Failed" although the Tivoli Netcool Performance ManagerMonitoring Agent was successfully deployed.

Resolving the problemThis issue will be fixed in the next release of Tivoli Netcool Performance Manager.

Data does not flow to LDR and DLDR in DataChannel Remote configuration

SymptomsIn a DataChannel Remote configuration where the CME and FTE are on one server and LDR and DLDR areon a different server, data does not flow from FTE to LDR and DLDR.

Resolving the problemThis issue will be fixed in the next release of Tivoli Netcool Performance Manager.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 7

Dashboard Application Services Hub configuration proceeds even though you provide awrong password in the Topology Editor

When you try to update your topology to see the existing Dashboard Application Services Hub instanceson your system, even if you provide a wrong password, the configuration does not stop.

Even if you provide a password that is different from the Dashboard Application Services Hub installationpassword, the configuration continues. You might see the following error:Could not connect to specified server

For more information about Discovering existing Dashboard Application Services Hub, see Installing TivoliNetcool Performance Manager - Wireline Component.

Ignore the message that appears even after the Dashboard Application Services Hubdiscovery completes

You might see the following message after the discovery of Dashboard Application Services Hubcompletes in the Topology Editor:Running the DASH discovery. This could take a few minutes

You can ignore this message.

For more information about Discovering existing Dashboard Application Services Hub, see Installing TivoliNetcool Performance Manager - Wireline Component.

Bookmarking a report option does not workThis issue is seen in Mozilla Firefox ESR and Google Chrome browsers.

A report is not rendered correctly in Defined Resource View on Dashboard ApplicationServices Hub in Internet Explorer

SymptomsConsider the following scenario:

• You open a report from Defined Resource View and open any other tab at the same time fromDashboard Application Services Hub.

For example, you open a report from Defined Resource View and also from Diagnostic View.

In this scenario, you notice that the report on Defined Resource View does not display correctly. Thisissue is seen in Internet Explorer only.

Resolving the problemTo temporarily resolve this issue, click Refresh, the report is rendered correctly again.

Switching between languages to view DataView components on Dashboard ApplicationServices Hub

When you are switching between languages on Dashboard Application Services Hub, you might noticethat the previously selected language might appear even after you change the browse locale. This issue isseen on Internet Explorer only.

About this taskTo workaround this issue, change both browser locale and system locale as follows:

Note: On Mozilla Firefox, you can change the browser locale alone. For instructions, see https://support.mozilla.org/en-US/questions/794066

Procedure

1. Change the browser locale on Internet Explorer as in these instructions:

8 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

http://windows.microsoft.com/en-US/windows-vista/Change-your-Internet-Explorer-language-settings

2. Change the system locale as in these instructions:

http://windows7themes.net/en-us/how-to-change-the-system-locale-on-windows-7/

Manual configuration required to install Reporting Services as non root userWhen you install Jazz for Service Management as non root user, the installation fails at ReportingServices.

SymptomsWhen you install Jazz for Service Management as non root user, the Installation fails at ReportingServices. You might receive the following error:

Error during "post-install configure" phase:Failed in configuring Reporting Services Database./home/non_root_user_home/opt/IBM/JazzSM/install/fsconfig.xml:227: The following error occurred while executing this line:/home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/reporting_services_config.xml:17: The following error occurred while executing this line:/home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/reporting_services_config.xml:23: The following error occurred while executing this line:/home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/tcr_db_config.xml:54: The following error occurred while executing this line:/home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/tcr_db_config.xml:66: The following error occurred while executing this line:/home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/tcr_db_config.xml:123: The following error occurred while executing this line:/home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/tcr_db_config.xml:142: Failed in configuring Reporting Services Database.

Resolving the problemTo resolve this issue, do these steps manually:

• Go to REPORTING_HOME from user_home_directory and run the following command as non-rootuser:

./TCR_generate_content_store_db2_definition.sh database_name user_name

Wheredatabase_name

The name of the database to create for the Cognos Content Store. The database name can have upto 8 characters. To avoid potential problems, do not use special characters such as @, #, and $ inthe database name. The default database name that is used in a simple installation is tcrdb.

user_name

The user name to connect to the Content Store, that is, the database owner.

The user name can be:

– The common administrator user name that is created during the simple installation.– The database administrator that is created during DB2 setup.– The user name that is associated with the user account that was created on the database server

for the Content Store.

For example:

./TCR_generate_content_store_db2_definition.sh tcrdb db2inst1

This command generates the tcr_create_db2_cs.sql script.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 9

• Run the tcr_create_db2_cs.sql script by using the following command as db2 instance user:

db2 -vtf <user_home_dorectory>/<REPORTING_HOME>/tcr_create_db2_cs.sql

You receive the following message:The CREATE DATABASE command completed successfully.

After completing these tasks, proceed with the installation.

Perform the LDAP configuration only post installation of Jazz for Service ManagementPerform the LDAP configuration on Jazz for Service Management after you complete the installation ofJazz for Service Management by using the following information:

For more information on LDAP configuration, see LDAP configuration section in Installing Tivoli NetcoolPerformance Manager - Wireline Component.

Note: Do not configure LDAP during the installation of Tivoli Netcool Performance Manager from TopologyEditor.

Related informationConfiguring Jazz for Service Management for a central user registry

Issue in viewing selected resources in Diagnostic view based on a property that does nothave a value for all the selected resources

SymptomsWhen you want to view some resources based a property from Diagnostic View, and all selectedresources do not have that property value, your search yields no result. But if you search based oncommon properties such as Resource Name and Resource Label, you might not encounter this issue.

Some settings from charts are not saved to the workspace

SymptomsWhen you create charts in Diagnostic View and save them in a workspace, all the settings are not saved.For example, if you set the granularity to a value other than the non-default value, these settings are notsaved when you reopen the chart.

Resolving the problemTo work around this issue, you must reset the granularity settings every time you open the saved chart.

The resmgr command for barwidth settings on a chart does not work

SymptomsWhen you use resmgr command for barwidth settings on a DataView chart, the change does not reflect inthe chart.

Resolving the problemTo work around this issue, change the barwidth setting from DV Navigator.

10 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

You cannot view DataView reports if you set the DATAVIEW_CONTEXT to a non-defaultvalue

Do not change the DATAVIEW_CONTEXT in a non-root installation. The default value forDATAVIEW_CONTEXT must be PV.

Do not use the DataChannel collector numbers 500 and aboveIf you assign collector numbers 500 and above, the collectors might not work correctly. Currently,collector numbers 500 and above are not supported.

Avoid deleting a DataChannel as all other DataChannels and associated DataLoadcollectors also get deleted

It is a good practice to keep a copy of the previous topology before you update the DataChannelconfiguration. Typically, avoid deleting a DataChannel.

The supported scripts that are used for collecting the sizing information do not work onDB2

Currently, the following supported scripts that are used for collecting the sizing information:

• check_proviso_sizing_adv.sql• check_proviso_sizing.sql• check_proviso_db.sql

These scripts do not work on Tivoli Netcool Performance Manager with DB2 as the database support.

Change the password for PV User in a migrated UBA channel from topology.xml fileWhen you want to migrate a UBA DataChannel from one host to another host, change the password for PVUser from topology.xml file and deploy again.

Currently, High Availability Manager (HAM) unistallation is not supported

Symptoms

When you try to remove the Managed Definitions and spare collectors in a HAM environment fromTopology Editor, it results in corrupting the FTE source values of an unrelated DataChannel. You noticethis issue when more than one 3+2 Managed Definitions are present. Therefore, HAM uninstallation is notsupported currently.

For more information about HAM, see Installing Tivoli Netcool Performance Manager - WirelineComponent.

Diagnosing the problemIn the Topology Editor, the FTE source directory points to the primary collector SNMP.*.*/output sourceonly and not to the primary and spare SNMP.*.*/output sources. Hence, the NRAW files are not moved intothe FTE when there is a failover of primary collector to the spare collector. This results in data that isstuck in the spare collector's output directory.

Resolving the problemIf you have uninstalled and observe that the spare collector data is not moving into the FTE, follow thesesteps:

1. Load the topology from the database.2. Click High Availability Manager and go to the Managed Definition of the required HAM.3. Remove the Managed Definitions.4. Go to the Collector Process folder and remove all spare collectors.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 11

5. Create the HAM managed definitions and spare collector processes, and then save the definition.6. Run Deployer for Installation.7. Load the topology from the database.8. Check if the FTE contains two sources.9. Restart the dccmd processes.

Aggregated Data Extraction query fails to extract the results into an XML fileWhen you create an Aggregated Data Extraction by using Mass Data Extraction interface, the results arenot extracted into an XML file. Contact IBM Professional Services if you face this issue.

Slow Dashboard Application Services Hub UI response time in Tivoli NetcoolPerformance Manager with IBM DB2 as the database support

SymptomsIf you find that the Dashboard Application Services Hub UI performance is slow in Tivoli NetcoolPerformance Manager with IBM DB2 as the database support, run the package binding utility on the DB2database.

Resolving the problemTo improve the performance of the Dashboard Application Services Hub UI, follow these steps:

1. Make sure that there are no connections to the DB2 database by using the following command:

$ db2 list applications

2. To choose the latest statistics in the database, rebind all the packages in the database by using thefollowing command:

$ db2rbind pv -l db2rbind.log all

Note: Run the db2rbind utility whenever you notice the slow response on the database side.

For more information about the db2rbind command, see http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0001995.html?cp=SSEPGG_10.1.0%2F3-5-2-6-98

CMEs and cross collector CMEs might not startTypically, this issue is not seen. Occasionally, you might find that the CMEs and cross collector CMEs donot start. You notice continuous walkback files being created.

Troubleshooting tasksSome troubleshooting tasks in Tivoli Netcool Performance Manager are described here.

MIB compilation fails with error message

Symptoms

You might encounter an error message when compiling MIB files from the DataMart pvm GUI.

MIB files compilation is aborted with an error pop-up message as “Process completed witherrors”. The MIB Compiler Traces in displays the following error:

Error: cannot open file ‘/opt/oth/datamart/mibs/src/Standard/rfc1213-MIB-II’

12 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Causes

You most likely to see this issue on a mix deployment scenario where you have a distributed setup ofDataLoad and DataChannel on mix operating systems.

Resolving the problemTo work around this issue, perform the following steps:

1. Exit the MIB Compiler from pvm GUI.2. Exit pvm GUI.3. On the DataMart host, open a new console and login as pvuser.4. Source the DataMart environment.

$ . /opt/datamart/dataMart.env

5. Start the DataMart pvm GUI.

$ PVMHOME/bin/pvm

6. Start the MIB Compiler from the GUI and run the MIB files compilation again.

Unable to run provisoinfod on remote DataMart host

Symptoms

If you have DataMart installed on any remote AIX, Linux or Solaris system, you might see the followingissue on your remote DataMart host upon Tivoli Netcool Performance Manager deployment:

• Unable to run to run provisoinfod.

CausesThis issue might be due to some parameters in the /opt/datamart/conf/provisoinfo.conf file arestill pointing to the primary DataMart properties. Hence, connecting or starting the DataMart process inthe secondary host fails.

Resolving the problem

1. Login to the remote DataMart host as pvuser.2. Change to the following directory, <Datamart_HOME>/conf.

For example,

$ cd /opt/datamart/conf/

3. Edit the provisoinfo.conf file and replace the hostname properties to point to the correct host.

Ensure that the following properties is pointing to the secondary or remote DataMart host.

For example,

provisoinfo/listener/host=<remote-DataMart-hostname>provisoinfo/listener/port=3114provisoinfo/listener/provisoinfohostname=provisoinfo/manager/name=//<remote-DataMart-hostname>:3113/ProvisoInfoServer

4. Restart the DataMart process.

$ pismgr start

5. To check if the DataMart process is running: ps -eaf | grep datamart

For example,

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 13

ps -eaf | grep datamart

pvuser 35848348 655674 0 00:43:03 pts/4 0:02 /opt/datamart/java/jre/bin/java -DPVMHOME=/opt/datamart -DPPID=655674 -Djava.rmi.server.codebase=file:/opt/datamart/classes/provisoinfo.jar -Djava.security.policy=/opt/datamart/conf/policyRmi.policy com.quallaby.proviso.daemon.ProvisoCmd startpvuser 655674 1 0 00:43:03 pts/4 0:00 /bin/ksh /opt/datamart/bin/provisoinfod start

DataMart tools are disabled in pvm GUI

Symptoms

After installing or upgrading to Tivoli Netcool Performance Manager 1.4.5, the DataMart tools in pvm GUImight be disabled.

Resolving the problem

1. Log in as db2 (instance user).2. Run the following command to add an entry to the opt/db2/sqllib/cfg/db2cli.ini file.

$ db2 update cli cfg for section db2ci using StrWorkaround 1

The following line is added to the /opt/db2/sqllib/cfg/db2cli.ini file.

[db2ci] StrWorkaround=1

SYSAUX tablespace error is seen in the walkback file after a non-default installation

Symptoms

Walkback files are seen created after installing Tivoli Netcool Performance Manager on a non-defaultdistributed setup.

The following error is seen in the walkback file.

For example,

END OF WALKBACK00604: error occurred at recursive SQL level 1ORA-01658: unable to create INITIAL extent for segment in tablespace SYSAUXORA-06512: at "PV_ADMIN.PVM_DATALOAD", line 2314ORA-06512: at line 1 FACILITY_NAME: LDR.1-26021 Release: 1.4.4.0-393 Build: Noss.393 ORIGINATOR: an OracleThreadedSession( hstmt = 85981960 ) PARAMETER: #(an OracleError) TEXT: ORA-00604: error occurred at recursive SQL level 1ORA-01658: unable to create INITIAL extent for segment in tablespace SYSAUXORA-06512: at "PV_ADMIN.PVM_DATALOAD", line 2314ORA-06512: at line 1

Resolving the problem

Based on the walkback error, the SYSAUX tablespace needs to be increased.

Run the following steps to increase the SYSAUX tablespace.

14 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Note: In this example, SYSAUX tablespace is resize to 750 M. Resize your database SYSAUX tablespaceaccording to your environment setup.

1. As oracle user, run the following command.

$ sqlplus / as sysdba

SQL>alter database datafile '/raid_22/oradata/PVDB/PVDB_sysaux_01.dbf' resize 750MDatabase altered.

2. Run the SQL command to set the page size.

SQL>set pagesize 40;column "Tablespace Name" format a15 trunc;column "# Bytes" format 9999999999;column "# Used" format 9999999999;column "# Free" format 9999999999;column "% Free" format 99.999;

3. Run the following command to display the updated tablespace.

select b.file_id "File #", b.tablespace_name "Tablespace Name", b.bytes "# Bytes", (b.bytes - sum(nvl(a.bytes,0))) "# Used", sum(nvl(a.bytes,0)) "# Free", (sum(nvl(a.bytes,0))/(b.bytes))*100 "% Free"from sys.dba_free_space a, sys.dba_data_files bwhere a.file_id(+) = b.file_idgroup by b.tablespace_name, b.file_id, b.bytesorder by b.tablespace_name;

Example output:

.....

...File # Tablespace Name # Bytes # Used # Free % Free---------- --------------- ----------- ----------- ----------- ------- 4 PV_CFGD 262144000 26214400 235929600 90.000 5 PV_CFGI 262144000 38862848 223281152 85.175 6 PV_CFHD 524288000 21102592 503185408 95.975 7 PV_CFHI 209715200 5177344 204537856 97.531 12 PV_EVNT 209715200 13697024 196018176 93.469 15 PV_LOIS 157286400 65536 157220864 99.958 8 PV_PROH 524288000 2162688 522125312 99.588 14 PV_REPM 314572800 65536 314507264 99.979 13 PV_REPT 314572800 65536 314507264 99.979 11 PV_TBDE 209715200 65536 209649664 99.969 9 PV_THRH 104857600 327680 104529920 99.688 10 PV_TIDE 209715200 65536 209649664 99.969 16 PV_VOID 33554432 4259840 29294592 87.305 2 SYSAUX 786432000 513474560 272957440 34.708 1 SYSTEM 419430400 347062272 72368128 17.254 3 UNDO_DATA 1048576000 928317440 120258560 11.469

127 rows selected.

Data in DataView reports is still shown after a manual database purge partition

Symptoms

The data in DataView reports is still available after you have purged the available partitions manuallythrough dbMgr utility.

Resolving the problem

You need to restart the Jazz™ for Service Management application server after you have complete editingthe file for the changes to take effect.

See Changing the default purgeable window value.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 15

Warning message seen when starting the launchpad

Symptoms

You may observe the following warning message in your command console when you start the launchpadon a Solaris 11 environment using Mozilla Firefox version 38.4.

For example,

# firefox -vMozilla Firefox 38.4.0

# cd <DIST_DIR># ./launchpad.sh+ /usr/bin/firefox -P Profile_7598 -profile /tmp/IBM_LaunchPad_7598/Profile_7598 -chrome chrome://commonlaunchpad/content/commonlaunchpad.xul(firefox:7688): GnomeUI-WARNING **: While connecting to session manager:None of the authentication protocols specified are supported.1522044617668 addons.xpi WARN Disabling foreign installed add-on langpack-sv-SE@firefox.mozilla.org in app-global1522044618016 addons.xpi WARN Disabling foreign installed add-on langpack-sl@firefox.mozilla.org in app-global1522044618333 addons.xpi WARN Disabling foreign installed add-on langpack-lv@firefox.mozilla.org in app-global1522044618844 addons.xpi WARN Disabling foreign installed add-on langpack-es-AR@firefox.mozilla.org in app-global1522044619352 addons.xpi WARN Disabling foreign installed add-on langpack-pl@firefox.mozilla.org in app-global1522044619770 addons.xpi WARN Disabling foreign installed add-on langpack-hr@firefox.mozilla.org in app-global1522044620091 addons.xpi WARN Disabling foreign installed add-on langpack-ja@firefox.mozilla.org in app-global1522044620408 addons.xpi WARN Disabling foreign installed add-on langpack-he@firefox.mozilla.org in app-global1522044620729 addons.xpi WARN Disabling foreign installed add-on langpack-th@firefox.mozilla.org in app-global1522044621061 addons.xpi WARN Disabling foreign installed add-on langpack-ca@firefox.mozilla.org in app-global1522044621371 addons.xpi WARN Disabling foreign installed add-on langpack-fi@firefox.mozilla.org in app-global1522044621682 addons.xpi WARN Disabling foreign installed add-on langpack-ar@firefox.mozilla.org in app-global1522044621987 addons.xpi WARN Disabling foreign installed add-on langpack-hu@firefox.mozilla.org in app-global1522044622316 addons.xpi WARN Disabling foreign installed add-on langpack-be@firefox.mozilla.org in app-global1522044622640 addons.xpi WARN Disabling foreign installed add-on langpack-uk@firefox.mozilla.org in app-global1522044622982 addons.xpi WARN Disabling foreign installed add-on langpack-da@firefox.mozilla.org in app-global1522044623299 addons.xpi WARN Disabling foreign installed add-on langpack-pt-PT@firefox.mozilla.org in app-global1522044623619 addons.xpi WARN Disabling foreign installed add-on langpack-pt-BR@firefox.mozilla.org in app-global

Note: The <DIST_DIR> directory is the folder that holds the content of your Tivoli Netcool PerformanceManager distribution.

Resolving the problem

This addons.xpi warning message can be ignored in this case.

DataView Real time reporter fails to deliver real-time subscription data

Symptoms

Real-time charts provide a real-time view of performance metrics. Real-time charts are activated fromstatic (on-demand) charts that have been enabled with real-time capability.

From Dashboard Application Services Hub portal, the Near Real Time (NRT) data from the reporter is notloading or showing data.

You will see the following error message, GYMDC10161W, in the SystemOut.log file:

16 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

V1:1032 2018.07.12-08.52.00 UTC CMGR-34340:11454 ERR_RTDS GYMDC10161W Failed to write data to the subscriber: communication failureV1:1033 2018.07.12-08.52.00 UTC CMGR-34340:11454 RT_UNSUBSCRIBE 3 cancelling subscription

The SystemOut.log file is available in the following location: <dash_installation_path>/profile/logs/server1.

Causes

NRT data and Real Time Reports DataView need to have communication between DataView andDataChannel servers using ports 9001 and 9005 respectively.

Resolving the problem

Run the following steps to resolve the error message and to continue with the Tivoli Netcool PerformanceManager deployment.

For real-time reports to work, do the following security setting on the WebSphere Application Server:

1. Log in to Dashboard Application Services Hub as an administration user.2. Click Console Settings > General > WebSphere Administrative Console in the console navigation.3. Click Launch WebSphere administrative console.4. Enter the WebSphere administrator user ID and password, and click Log in.5. In the WebSphere Integrated Solutions Console, click Security > Global Security.6. Click RMI/IIOP Security > CSIv2 inbound communications.7. Select SSL-supported from the Transport field in CSIv2 Transport Layer section.8. Click Apply, and then OK.9. Restart the Dashboard Application Services Hub server.

Refer to Chapter 4~ Installing and Upgrading Jazz for Service Management~Stopping Jazz for ServiceManagement application servers and Starting Jazz for Service Management application servers topicsfrom Installing Tivoli Netcool Performance Manager - Wireline Component guide.

10. Re-log in to Dashboard Application Services Hub and check for NRT data from DataView reporter.

Related information“GYMDC10161W” on page 89errorDescription Failed to write data to the subscriber:

Run Remote Database Check prompts warning message for a non-default TivoliNetcool Performance Manager deployment

Symptoms

In your Tivoli Netcool Performance Manager distributed setup, Jazz for Service Management is installedwith a non-root user.

During Tivoli Netcool Performance Manager deployment, the Run Remote DataBase Check stepprompts a warning message indicating that the Remote Database Check script needs to be run asroot user.

For example,

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 17

CausesThe Remote Database Check script needs to be run as root user. Since the Jazz for ServiceManagement is installed using a non-default user, the script fails to run.

Resolving the problem

Run the following steps to resolve the warning message and to continue with the Tivoli NetcoolPerformance Manager deployment.

1. Take note of the run.sh script path from the warning prompt message.

In this example, the script is at: /tmp/ProvisoConsumer/Plan/MachinePlan_<hostname>/00002_CheckSys_DB_step_1_2/runtime/run.sh

2. From the warning prompt message, click OK.

The Run Remote DataBase Check status is now on the deployer is now changed to Success.3. On a new command prompt, log in as root.4. Change directory to the directory where the Remote Database Check run.sh script is.

# cd /tmp/ProvisoConsumer/Plan/MachinePlan_<hostname>/00002_CheckSys_DB_step_1_2/runtime/run.sh

5. Run the run.sh script.

For example,

# ./run.shInit DB check ...-->OK. Version Linux 7.-->OK. The /opt/oracle/product/12.1.0-client32/network/admin/tnsnames.ora file exists.-->OK. ORACLE_HOME does not contain symbolic links.-->OK. Oracle version 12.1.0.2.0-->OK. TNSPING response is: OK (20 msec).-->OK. 32 bit /opt/oracle/product/12.1.0-client32/bin/sqlplus.

Ensure that the remote database check output has no any issues from the run.sh command.6. Continue running the other remaining steps in the deployer.

Click Run All to run all the steps in sequence.

For more information, see Installing Tivoli Netcool Performance Manager - Wireline Component guideon Chapter 6. Installing in a distributed environment ~ Deploying the topology topic.

Memory fault or Segmentation fault might cause proviso database installation to fail

Symptoms

Memory fault or Segmentation fault might cause proviso database installation to fail.

Resolving the problem

Creating the zero length file can avoid the following issues:

18 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

• Memory fault or Segmentation fault when you connect to Oracle database on Linux 32-bit x86.• DataChannel’s findvisual components are not able to connect to the Oracle database after upgrading

the Linux operating system from RHEL 6.5 to RHEL 7.3 onwards.

To avoid this issue, perform the following procedure.

1. Create a zero length file as root user.

For example:

touch /etc/sysconfig/64bit_strstr_via_64bit_strstr_sse2_unaligned

2. To ensure you are not hitting any memory fault issues, run the sqlplus by using the sqlplus from theOracle 32-bit client version as oracle user.

For example:

/opt/oracle/product/12.1.0-client32/bin/sqlplus

LDR and DLDR components take time to reconnect after a DB2 database restart

Symptoms

If the DB2 database process stops, while the Tivoli Netcool Performance Manager components are up andrunning, you might see the following issues after the DB2 database is restarted:

• DataChannel components LDR and DLDR takes some time to reestablish the connections.• During this time, errors are logged in proviso log and walkback files are created.

For example, walkback file is written with the similar text:

FACILITY_NAME: LDR.1-2812Release: 1.4.4.0-10Build: Noss.10ORIGINATOR: a PROVISO.PvDB2Session( hstmt = 10001 )PARAMETER: OrderedCollection (a DB2Error a DB2Error)TEXT: [IBM][CLI Driver] SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt. SQLSTATE=55032

Causes

The DB2 database process is stopped or goes down while Tivoli Netcool Performance Managercomponents are up and running.

Resolving the problem

Start the DB2 database process.

If the DB2 database process goes down or stopped, all the Tivoli Netcool Performance Managercomponents reconnect once the DB2 database is up.

It is an expected behavior, as LDR or DLDR waits until the database to be connected. During this period,walkback files are created for the lost DB2 connection. Once the connection is restored, there would notbe any walkback files created.

Group Summary Tables (GST) reports showing null value

Symptoms

Group Summary Tables (GST) provide an overview of the behavior of multiple groups of resources that arecompared to a maximum of 10 metrics.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 19

In the DataView report, the Group Summary values are showing null after you complete the TivoliNetcool Performance Manager installation and its postinstallation tasks.

Resolving the problem

Note: The calculation of Resource Aggregations for particular metrics is controlled by doRA flag of thecollection requests. The doRA flag property needs to set to true/1 for the metrics that need ResourceAggregations (RA).

• 1 - requires resource aggregation• 0 - requires no resource aggregation

By default, the value of doRA is 0.

Run the following steps if your Resource Summary Table (RST) reports have data and GST reports areshowing null values:

1. Log in as root user.2. Run the following command to export the output to a file:

# resmgr -export segpreq -colNames "segp.npath fgp.nName se.dbIndex doRA" >><filename>

3. Update the doRA flag value to 1 in the exported file, <filename>.4. To update the changes, run the following command to import the file back by using below command:

# resmgr -import segpreq -colNames "segp.npath fgp.nName se.dbIndex doRA" –file <filename>

DataView upgrade fails due to improper nofile value settings

Symptoms

The following error message is seen while deploying the upgrade topology for DataView upgrade scenario.

WASX7120E: Diagnostic information from exception with text "com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for isc failed: see previous messages for details." follows:

com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for isc failed: see previous messages for details.at com.ibm.ws.scripting.AbstractShell.setAndThrowScriptingException(AbstractShell.java:1878)

Resolving the problem

This issue is seen due to improper ulimit value is set for your operating system. You must set the shelllimits for the nofile ulimit value.

1. Log in as root user.2. Add the following settings to the /etc/security/limits.conf file:

# vi /etc/security/limits.conf

* soft nofile 2048* hard nofile 10240

3. Write and quit the limits.conf file.4. On the DataView host, restart the Jazz for Service Management server by using the following

command:

# ./startServer server1 -username <WAS_admin_username> -password <WAS_admin_password>

5. Resume the upgrade procedure.

20 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Some of the Tivoli Netcool Performance Manager components still showing 1.4.3 versionafter upgrade to 1.4.4

Symptoms

Some of the Tivoli Netcool Performance Manager components are still showing version 1.4.3 afterupgrade to 1.4.4 from the Netcool/ProvisoInfo UI tool.

The Netcool/ProvisoInfo tool obtains its information from the Netcool/ProvisoInfo server daemon thatruns on the DataMart computer. The Netcool/ProvisoInfo server daemon refreshes from the databaseonce a day.

Resolving the problem

Restart the affected Tivoli Netcool Performance Manager component process, which is showing the olderversion.

After the component restart, you need to refresh the information you are viewing from the ProvisoInfobrowser. Select DataBase Refresh from the Options menu from the Database Information.

Sometimes it might take some time to refresh the component version after an upgrade.

Some additional UBA properties with no values are seen in a loaded topology in upgradescenario

SymptomsWhen you load a topology from the database, you might find some additional properties with no values inan upgrade scenario.

Resolving the problemTo resolve this issue, load the particular technology pack XSD file again. The original properties of thetechnology pack are loaded back.

DataMart process pismgr not getting started after upgradeDataMart process pismgr not getting started after Tivoli Netcool Performance Manager 1.4.5 upgrade.

Symptoms

After you upgrade to Tivoli Netcool Performance Manager 1.4.5, you might receive the following errorwhen you start the pismgr DataMart process:

$ pismgr start Thu Jun 2 16:26:09 IST 2015: Starting ProvisoInfo daemonThu Jun 2 16:26:39 IST 2015: Error : can't start ProvisoInfo daemon (/opt/proviso/datamart/bin/provisoinfod).

Or when you initiate the Database Information option from DataMart GUI, you see the following errormessage:“The server could not be contacted. May be the Server or Registry is stopped.”

Resolving the problem

1. Log in to the DataMart server as the DataMart software owner (by default, pvuser).2. Change to the following directory <Datamart_HOME>/bin.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 21

For example:

cd /opt/datamart/bin

3. Edit pismgr script by commenting the following line:

# rm $DAEMON_NO_CHECK 2>/dev/null

4. Save the pismgr script.5. Start the DataMart pismgr process.

Viewing online help in Acrobat Reader on AIX 7.1Unable to view the online help documents from Datamart GUI in AIX 7.1.

Symptoms

Unable to view online help because Acrobat Reader is not installed in AIX 7.1.

CausesTivoli Netcool Performance Manager DataMart supports an Adobe Acrobat PDF help system. To view theonline help on AIX 7.1, you need to add the acroread binary.

Resolving the problem

1. Start VNC server by using the following command:

/usr/bin/X11/vncserver -depth 24

2. Install Adobe® Acrobat Reader® version 7.0.9 for AIX.

Note: During the installation, you might see a warning message that indicates the Acrobat Reader willnot run on AIX 7.1. Click Yes to have Acrobat Reader proceed normally.

3. Start the DataMart GUI as pvuser.4. Click the Help from any of the options available in DataMart GUI.

You might see an error message on PPKLite.api, for example:

Error while loading PPKLite.api plugin. The plugin failed to initiate

To remove the error message, delete or rename /usr/lpp/Adobe/Acrobat7.0/Reader/rs6000aix/plug_ins/PPKLite.api, where /usr/lpp/Adobe/Acrobat7.0 is the installationpath.

5. Verify acroread binary is present in /usr/bin.

lrwxrwxrwx 1 root system 38 Apr 25 06:17 acroread -> /usr/lpp/Adobe/Acrobat7.0/bin/acroread

6. If the acroread binary is not present in /usr/bin, run the following command:

ln -s acroread /usr/lpp/Adobe/Acrobat7.0/bin/acroread

Verify that acroread binary is now present in /usr/bin.7. Relaunch the DataMart GUI and click Help to view any of the documentations available.

Real-time charts do not work as expected

SymptomsSometimes when you restart the Tivoli Netcool Performance Manager Channel Name Server (CNS) orChannel Manager (CMGR) component, your real-time charts no longer work as expected. Real-time charts

22 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

require a valid reference to the real-time subscriber object. A restart of these components can cause theChannel Name Server (CNS) to no longer provide a valid reference to the real-time subscriber object.

Resolving the problemTo restore the proper operation of your real-time charts in this situation:

User response:

1. On the DataChannel host, change to the $DCHOME/bin directory. For example:cd /opt/datachannel/bin

2. Find the PID of the DataChannel CNS component../findvisual | grep CNS_visualYou can see an output like the following:

pvuser 653 648 0 Apr 14 ?129:46 /opt/datachannel/bin/CNS_visual -nologo /opt/datachannel/bin/dc.im -a CNS -f /o

Note: The PID is the first number after your login ID. For example, in the previous output, the PID is653.

3. Stop CNS by using the following command:kill -9 CNS_pid

4. Find the PID of the DataChannel CMGR component by using the following command:./findvisual | grep CMGR_visual

5. Stop CMGR by using the following command:kill -9 CMGR_pid

6. On the DataView host, stop the Jazz for Service Management server by using the following command:./stopServer server1 -username <WAS_admin_username> -password<WAS_admin_password>

7. On the DataChannel host, change to the $DCHOME/bin directory. For example:cd /opt/datachannel/bin

8. Restart CNS and CMGR by running the following commands in the following order:

./cnsw

./cmgrwd

9. On the DataView host, restart the Jazz for Service Management server by using the followingcommand:./startServer server1 -username <WAS_admin_username> -password<WAS_admin_password>

Error: ORA-00001:unique constraint (PV_ADMIN.PK_SEGM) violatedAn unique constraint error is generated during inventory and grouping.

Symptoms

The following message is received in inventory and grouping output:-Error: ORA-00001:unique constraint (PV_ADMIN.PK_SEGM) violated-Reason: a static group membership link exists between a sub-elements and a group

CausesA user uses the resmgr command to insert a resource into a group and then runs inventory grouping. Ifinventory grouping tries to place the same resource into the group, a unique constraint error is generated.

Resolving the problemUsing the resmgr command, delete the grouping link.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 23

MDE memory constraintAn unique constraint error is generated when running an MDE query.

Symptoms

The following message is received you ttempt to run MDE query:GYMVD0002E: Unable to retrieve information from the data source" error.

orMon Feb 1 08:53:51 2010ORA-1652: unable to extend temp segment by 64 in tablespace PV_LOIS_TEMP

Causes

You are constrained by the available space in PV_LOIS_TEMP.

This is a TEMP tablespace that is shared across all MDE sessions.

A user uses the resmgr command to insert a resource into a group and then runs inventory grouping. Ifinventory grouping tries to place the same resource into the group, a unique constraint error is generated.

Resolving the problem

This error can be addressed with the following suggestions:

• Reduce the time period used in the MDE query. If the time range is halved then the space requiredshould be halved.

• Reduce the number of metrics requested. If the original request was for 5 metrics and you can reducethis by 1 metric, it should require approximately 20% less space.

• If neither option is possible, then you can increase the size of the PV_LOIS_TEMP tablespace.

Incomplete SNMPv3 metric collectionSome data loss can be observed from the “Expected measures” and “Produced measures” in the SNMPcollector log message.

Symptoms

Some data loss can be observed from the “Expected measures” and “Produced measures” in the SNMPcollector log message, especially when there is a sudden drop in “Produced measures” when comparedwith past hours of collection.

For example:

DL31066 I DL_PERF_SUMMARY Hour: 1s:hour subElmts: 2s:ses metrics: 3s:metrics requests: 4s:requests expMeas: 5s:expmeas prodMeas: 6s:prodmeas

GYMDL30287 W: SNMPJob jobdescr can not start in a dedicated thread. Internal error is err.

Causes

This is a thread-related issue that corresponds to insufficient resources to create another thread, or thereis a system-imposed limit on the number of threads to be created.

Resolving the problem

This resolution is applicable only if the following warning message is displayed first to indicate that this isa thread-specific issue as there are many other configuration issues that can cause data losses.

DL30287 W SNMPJOB_THREAD_ERR SNMPJob 1s:jobdescr can not start in a dedicated thread. Internal error is '2s:err'.

If the system resources cannot be increased, decrease the concurrency in the collector.

24 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Note: This decreases the overall performance of the collector.

Concurrency is controlled by the GLOBAL.SNMP.MAXASYNC parameter, which is given the default value of256. The default value can be changed by adding a Custom Datachannel parameter in the TNPM topology.This parameter can be added using the Topology Editor: GLOBAL.SNMP.MAXASYNC=value where valueis a number less than 256.

w

Collectors swapping from idle to running at startup

Symptoms

The situation may occur that a collector, upon startup, waits a period of time, then transitions itself torunning state only to be swapped to an idle state by the High Availability Manager (HAM).

Causes

At startup the Collector sits in 'Idle' state waiting to determine what it should do next ( if anything ). TheHAM (High Availability Manager) should probe the Collector, discover its state, and instruct it to 'start' orto 'stay in idle' or to 'load'

’Start’ leads to running (active collection), ’load’ leads to ready (a sort of hot-spare mode ) and stayingin ’idle’ means keep waiting.

If a network disconnect occurred between the collector and HAM, the Collector may have a configuration(channel & collector number) from its previous run state. The result would be that the collector waits aperiod of time, then transitions itself to running state only to be swapped to an idle state by the HAM. Thesymptom is a result of the timing of the HAM's probing, and the Collector's idle-timeout.

Resolving the problem

User response:

If you this behaviour a problem, you update either the polling interval of the HAM or the idle timeout ofthe collector:

• Increase the Collector's Idle Timeout by editing DataChannels > Global DataChannel Properties >Advanced Properties > IDLETIMEOUT, or

• Decrease the HAM's probe interval by editing DataChannels > Administrative Components > HighAvailibility Managers > <HAM identifier> > Properties > POLL_INTERVAL

Specifying the Database Home directory path in the non-default DB2 installationChange in the default value of Database_Home path does not update other required directory paths in theTopology Editor.

SymptomsAfter you install DB2 in a non-default location, you change the default path of Database_Home directorywhile you add new host in the Topology Editor. However, it does not correctly update the other requireddirectory paths.

For example, following are the directory paths where the non-default Database_Home directory path isnot updated.

• Database_Home_Root in Host’s properties• Target_Database_Home and DB2_BASE field in Database Configurations' properties

Resolving the problemFollowing procedure shows how to update other required directory paths in the Topology Editor in non-default DB2 installation.

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 25

User response:

1. The default DB2_BASE directory path is /opt/db2

For example, your DB2 home directory is /opt/db232. The default Database_Home directory path is opt/db2/product/10.1.0/.

For example, the directory where you install DB2 is /opt/db23/product/10.1.0.

a. Install and start the Topology Editor. For more information about installing and starting theTopology editor, see IBM Tivoli Netcool Performance Manager 1.3.3 Wireline Component:Installation Guide

b. Create new topology.c. Ensure to specify the Database_Home path /opt/db23/product/10.1.0 when you add a new

host.d. Continue to add required components into the topology.e. In Topology Editor, manually update the following values:

• Update the value of DB2_BASE in Database Configurations' properties to /opt/db23• Update the value of Database_Home_Root in host’s properties to /opt/db23/product• Update the value of Database_Home in Database Configurations' properties to /opt/db23/product/10.1.0

All the required directories in the Topology Editor get updated after you change the default DB2directory path.

Changing DB_USERNAME for installing UBA Alcatel-Lucent 5620 SAM 2.13.0.0Changing DB_USERNAME from PV_INVENTORY to PV_ADMIN in datachannel properties in xml file that isgenerated from Topology Editor.

SymptomsWhen you install UBA Alcatel-Lucent 5620 SAM 2.13.0.0 with default configurations, for SAMIFcomponent DB_USERNAME is PV_INVENTORY. Since in DB2, user name with more than 8 characterscannot have system level access like working with sysibm tables, you need to change the userPV_INVENTORY to PV_ADMIN.

Resolving the problemFollowing procedure shows how to change DB_USERNAME for UBA Alcatel-Lucent 5620 SAM2.13.0.0 in xml file.

User response:

1. The default configuration for UBA Alcatel-Lucent 5620 SAM 2.13.0.0 contains DB_USERNAMEas PV_INVENTORY.

26 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

2. Save topology.3. Open Topology xml file in an editor, for example, vi, search for PV_INVENTORY. Results are<DB_USERNAME>PV_INVENTORY </DB_USERNAME>

Change this line to <DB_USERNAME> PV_ADMIN </DB_USERNAME>.4. Save the xml file.5. Open the same topology file in topology editor, it appears something as,

6. Run the deployer for installation.

Load pending state

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 27

You can use queries to detect and remove the Load pending state.

SymptomsDuring a LOAD operation, you might get the following DB2 error:TEXT: [IBM][CLI Driver][DB2/LINUXX8664] SQL0668N Operation not allowed for reason code "3" on table <schema_name>.<table_name>. SQLSTATE=57016

SQL0668N reason code 3 indicates that the table is in the Load Pending state. A previous LOAD attempton this table resulted in failure. No access to the table is allowed until the LOAD operation is restarted orterminated.

Resolving the problemYou can use the following query to detect the Load pending state:

User response:

Select TABSCHEMA, TABNAME, LOAD_STATUS from SYSIBMADM.ADMINTABINFO where load_status = 'PENDING' and tabschema = "'<schema_name>'

Restart or terminate the previously failed LOAD operation on this table by issuing LOAD with the RESTARTor TERMINATE option.

You can use the following query to terminate the Load pending state:

Load from /dev/null of del terminate into '<schema_name>'.<table_name>

Example:

$ db2 connect to PV$ db2 "select TABSCHEMA, TABNAME, LOAD_STATUS from SYSIBMADM.ADMINTABINFO where load_status = 'PENDING' and tabschema = 'PV_METRIC'"$ load from /dev/null of del terminate into PV_METRIC.C02_1MGA_000_S0 nonrecoverable$ db2 disconnect PV

For more information, see

• http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.messages.sql.doc/doc/msql00668n.html

• http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.admin.dm.doc/doc/c0051300.html

LDR in unavailable state for long time

We get this error when the partition is locked for some table.

SymptomsLDR in unavailable state for long time and , you might get the following DB2 error:TEXT: [IBM][CLI Driver][DB2/LINUXX8664] SQL0438N Application raised error or warning with diagnostic text: "Table partition is in locked state". SQLSTATE=UD171

Resolving the problemYou can use queries to detect locked partitions.

User response:

Select * From syscat.datapartitions where tabschema = '<schema_name>' and STATUS ='L'"

28 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

If you find any rows that means the perticular partition is been locked by some application. You mustrestart or terminate the previously locked operation on this table. by issuing the following commandsfrom the db2 instance user.

select* from sysibmadm.LOCKWAITS

Identify the agent id of main application holding lock from column AGENT_ID_HOLDING_LK kill the culpritapplication using command:

db2 “force application (<agent_id>)"

Check if the lock gets removed by the following query.

Select* From syscat.datapartitions where tabschema = '<schema_name>' and STATUS ='L'"

$ db2 connect to PV$ db2 "select * from sysibmadm.LOCKWAITS"$ db2 “force application (19086) “$ db2 disconnect PV

Data flow obstruction at LDR

SymptomsIf you find that the data flow is obstructed at LDR, increase the size of thePV_PV_ADMIN_TEMP_001.dbf tablespace.

Resolving the problemIncrease the size of the PV_PV_ADMIN_TEMP_001.dbf tablespace by using the following command:

SQL> alter database tempfile '/raid_3/oradata/PV/PV_PV_ADMIN_TEMP_001.dbf' resize 3G

Specify the size as per your requirements.

Searching knowledge basesYou can often find solutions to problems by searching IBM knowledge bases. You can optimize yourresults by using available resources, support tools, and search methods.

About this task

You can find useful information by searching the information center for Tivoli Netcool PerformanceManager, but sometimes you need to look beyond the information center to answer your questions orresolve problems.

Procedure

To search knowledge bases for information that you need, use one or more of the following approaches:• Search for content by using the IBM Support Assistant (ISA).

ISA is a no-charge software serviceability workbench that helps you answer questions and resolveproblems with IBM software products. You can find instructions for downloading and installing ISA onthe ISA website.

• Find the content that you need by using the IBM Support Portal.

The IBM Support Portal is a unified, centralized view of all technical support tools and information forall IBM systems, software, and services. The IBM Support Portal lets you access the IBM electronicsupport portfolio from one place. You can tailor the pages to focus on the information and resourcesthat you need for problem prevention and faster problem resolution. Familiarize yourself with the IBMSupport Portal by viewing the demo videos (https://www.ibm.com/blogs/SPNA/entry/

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 29

the_ibm_support_portal_videos) about this tool. These videos introduce you to the IBM SupportPortal, explore troubleshooting and other resources, and demonstrate how you can tailor the page bymoving, adding, and deleting portlets.

• Search for content about Product X by using one of the following additional technical resources:

– Tivoli Netcool Performance Manager technotes– Tivoli Netcool Performance Manager Support Website– Tivoli support communities (forums and newsgroups)

• Search for content by using the IBM masthead search.You can use the IBM masthead search by typing your search string into the Search field at the top ofany ibm.com® page.

• Search for content by using any external search engine, such as Google, Yahoo, or Bing.If you use an external search engine, your results are more likely to include information that is outsidethe ibm.com domain. However, sometimes you can find useful problem-solving information about IBMproducts in newsgroups, forums, and blogs that are not on ibm.com.

Tip: Include "IBM" and the name of the product in your search if you are looking for information aboutan IBM product.

30 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Chapter 2. Logs (Wireline Component)Tivoli Netcool Performance Manager has various logs that can be used to examine processing results andproblems.

OverviewThe following table provides a high-level description of Tivoli Netcool Performance Manager logs.

Table 1. The Tivoli Netcool Performance Manager logs by component

Component Description

DataChannel

DataChannel manages the primary Tivoli Netcool Performance Manager proviso.log logfile. This log file collects data from each DataChannel component, and from the SNMP andBCOL collectors. DataChannel also creates the tnpmlog.log log file that contains all logsof interest to the user.

DataLoad Separate log files capture events about the daemon start-stop sequence, SNMP activity,and watchdog queries to determine that status of the daemon. Log data is also written tothe primary DataChannel log file.

DataView Records data about web transactions and database calls.

DataMart A number of log files containing messages related to inventory, internal Tivoli NetcoolPerformance Manager communications, and database status.

Database The standard database log file.

Logs by componentA description of Tivoli Netcool Performance Manager logs organized by component.

Installation log filesA list of log files created by the Tivoli Netcool Performance Manager Wireline Components duringinstallation. Where relevant, recommendations regarding the deletion of log files is provided.

Database

• /opt/Proviso/*

(do not delete these files as they are used during upgrades and for maintenance. Only delete these fileson uninstallation.)

• /var/tmp/PvInstall/install.cfg• /var/tmp/PvInstall/install.log

DataChannel

DataChannel installer logs to stdout and stderr so there are no logs resulting from the installationprocess.

DataView

• $home/DataView_InstallLog.log

© Copyright IBM Corp. 2011, 2019 31

DataLoad

• /tmp/dlSetup_install_`date +%Y.%m.%d`

DataMart

• /var/tmp/PvInstall/install.log

Installation

The log resulting from the installation of the Topology Editor is located at:

<topology Editor install location>/Topology_Editor_InstallLog.log.

The logs resulting from any run of the Deployer are created in /tmp/ProvisoConsumer.

The main log file is:

• /tmp/ProvisoConsumer/log.txt

Deployment plan logs:

• /tmp/ProvisoConsumer/Plan/logs/[INSTALL_<TIME_STAMP>

Deployer Ant logs:

• /tmp/ProvisoConsumer/Plan/MachinePlan_<MACHINE_NAME>/logs

The best cleanup method for installation logs is to remove the /tmp/ProvisoConsumer directory whenthe system has been running long enough to validate all aspects of a working installation. AProvisoConsumer directory is created in the /tmp directory of each server in the installation, not justfor the primary host.

Topology Editor logs are located at:<topology Editor install location>/topologyEditor/topologyEditorTrace.log

Note: A new log file is created each time the Topology Editor is run.

To change the log level in the topologyEditorTrace.log file, edit the log.properties file asfollows:

cd /opt/IBM/proviso/topologyEditor/logvi log.propertiescom.ibm.tivoli.icc.fileName = topologyEditorTrace.logcom.ibm.tivoli.icc.level = FINE

Note: The log levels are fatal, severe, warning, audit, info, config, detail, fine, finer, finest, or all.

DataChannel logsThe DataChannel logs include proviso.log, tnpmlog.log, walkback logs, and logs for individualDataChannel components. The default location of these logs is /DCHOME/log, where DCHOME is thelocation of DataChannel on your system.

Note: DataChannel component logs are generated only when you enable dual-logging for the component.When enabled, dual-logging writes information to proviso.log and tnpmlog.log, and to the individuallog for the DataChannel component. For information about dual-logging, see “DataChannel logsconfiguration” on page 37.

Proviso.logproviso.log is the core Tivoli Netcool Performance Manager log file. It is always running andcontinuously processing data.

The location of this log file is determined by the LOG.FILE configuration setting. For more information,see “Topology Editor log settings” on page 38. At the end of the day, a timestamp is added to the filename (for example, 2007.08.24_1188000000_proviso.log) and a new proviso.log file is createdfor current processing.

32 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

The key performance indicators of Tivoli Netcool Performance Manager are derived from Proviso log files.

The statistics are analyzed and an hourly system summary is provided per Tivoli Netcool PerformanceManager component. For example,

2013.04.09-08.32.42 UTC UBA.8.200-8664:12997 PERF_INPUT_PROCESSING GYMDC10021I SAM_INVENTORY-sam_inventory_2013-04-09-08-30.csv: processed 3145 records in 5.002 sec (37724.9 records/min), rejected 0 records.

This log file contains information about all DataChannel components and SNMP collectors. The types ofevents that are logged are determined by the LOG_FILTER setting, as described in “Topology Editor logsettings” on page 38.

tnpmlog.logtnpmlog.log contains a subset of the messages written to the proviso.log file. The subset ofmessages placed in the tnpmlog.log file are only those messages that are of interest to the user.

The location of this log is determined by the LOG.LOG.FILE configuration setting (for more information,see “Topology Editor log settings” on page 38).

DataChannel log formatThe current log format for log messages written to proviso.log and tnpmlog.log:<version and sequence number><UTC time stamp><Component>-PID:T ID<GYMXXXXXSeverity><Category><Message Text>

Message Components

Explanation of each component of the log format for the previous example:

• <version and sequence number>: V1:1234• <time stamp>: 2007.01.16-06.02.03 UTC• <Component>-PID:T ID: CME.1.1-25201:3456• <GYMXXXXXSeverity>:Unique ID format, for example GYMDC0412W, which consists of

– TNPM product identifier: "GYM"– Component: DC– Message identifier: 0412– Severity level character: W=warning (can also be I=information, E=error)

• Category: DISCARDED_RECORDS• Message Text: Got 4 duplicate records, Discarded 0, Total of 4 for mid: 2206rid: 200023263

If log messages do not have a message ID, then only the severity is shown.

Log message example:

V1:1234 2007.01.16-06.02.03 UTC CME.1.1-25201:3456 GYMDC0412W DISCARDED_RECORDS Got 4 duplicate records, Discarded 0, Total of 4 for mid: 2206 rid: 200023263 4|4|2006| 200023263

Walkback logsWalkback logs are generated when a Tivoli Netcool Performance Manager application encounters seriousproblems. In most cases, walkback logs are produced just before the application shuts down because ofthe error.

These logs are crucial for problem determination by IBM Technical Support. The name of the file beginswith walkback- and includes the DataChannel component and timestamp (for example, walkback-UBA.1.2-18032-2007.08.21-16.51.32.log).

Unless you have advanced knowledge of the DataChannel, only the first few lines of a walkback log areuseful. The following log entry is an example:

Chapter 2. Logs (Wireline Component) 33

EXCEPTION: ORA-01034: ORACLE not availableORA-27101: shared memory realm does not existSVR4 Error: 2: No such file or directoryFACILITY_NAME: LDR.1-11827 Release: 4.4.1 R2E2 Build: Guam.156 ORIGINATOR: 'an OracleThreadedConnection( hsvcctx = 245F374 )' PARAMETER: OrderedCollection (an OracleError) TEXT: ORA-01034: ORACLE not availableORA-27101: shared memory realm does not existSVR4 Error: 2: No such file or directory

EXCEPTION: DB2 not availableshared memory realm does not existSVR4 Error: 2: No such file or directoryFACILITY_NAME: LDR.1-11827 Release: 1.3.3 R2E2 Build: Pico.27 ORIGINATOR: ’a DB2ThreadedConnection( hsvcctx = 245F374 )’ PARAMETER: OrderedCollection (a DB2 Error) TEXT: DB2 not availableshared memory realm does not existSVR4 Error: 2: No such file or directory

Note: Walkback files must be manually deleted. Due to the DataChannel cron settings, a process that failsis repeated every 5 minutes. Since a new walkback log is generated upon every failure, the result can bemany unneeded files.

DataLoad logsDataLoad logs include the SNMP.log, pvmdmgr.log, and WatchDog.log logs. The default location ofthese logs is the /DLHOME/log directory, where DLHOME is the location of DataLoad on your system.

SNMP logThe SNMP log file contains detailed messages about all SNMP requests. All SNMP log files are createdwith the date in their name. Also, the name of the local SNMP log file also includes the collector number,for example: 2010.04.27SNMP.1.1.log

By default, SNMP logs include the following recurring events:

• Close hour events• Debug level changes• Start and stop messages

Note: Events reported in this log are also reported to the DataChannel log.

Only the current debug level can be set by using the Collector Information Tool as described in theConfiguring and Operating DataMart. On restart, the collector switches back to the permanent debug level(which by default is Fatal + Warning + Info messages). The permanent debug level is set through theTopology Editor. Changing the debug level is useful when a specific network device or device group doesnot respond correctly to SNMP requests.

Pvmdmgr.logThe pvmdmgr.log file stores events about the start and stop sequence of the daemon.

Occasionally, the PVM Collecting daemon is running message is displayed before the process isin complete run mode.

34 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

WatchDog logsThe daily DataLoad WatchDog.log file contains entries about pings sent to the collector to ensure thatthe daemon is still running. The name of this log begins with the date for which events are records, forexample 2007.08.16WatchDog.log.

DataMart logsDataMart does not have a central log. Instead, DataMart information is written to log files, such aslogFile.PVM or TraceInventory.log, that are associated with individual components or actions,such as Inventory. The default location of these logs is the /DMHOME/log directory, where DMHOME isthe location of DataMart on your system.

Note: The inventory process does NOT automatically create a log. If inventory is run as a cron entry, youmust redirect the data to a specified log file, otherwise no log data is stored. To show time stamps ininventory log initiated by cron, you must add the following lines to the dataMart.env file:

PVM_LOG_DATE=1export PVM_LOG_DATE

TraceInventory.logThis log is created when the SNMP Inventory GUI is used. The log file contains messages that sequentiallyindicate the processing status of an inventory. The following example shows a typical Discover_Analyzeentry in this log.

logFile.POLLPROFILE.{collector ID}This log contains messages related to bulk inventory, and one file is produced for each bulk collectorprofile. The file suffix follows the format .bulk_n, where n is the number of the collector.

logFile.*This type of log file records minor events related to GUI or module function and is generated as required.Examples of this type of log file include logFile.POLLINVENTORY and logFile.RESMGR.

provisoinfod*.logThis log contains messages about internal communications and is of limited use for troubleshooting. Atthe end of each day, a UNIX timestamp is appended to the file name (for example,provisoinfod1187726401534.log).

NotifyDBSpace*.log fileThe NotifyDBSpace*.log file is a daily automatic file containing messages about the status of thedatabase. At the end of each day, a UNIX timestamp is appended to the file name (for example,NotifyDBSpace1190102314443.log).

DataView logsDataView does not have a central log. Instead, DataView writes DataView traces to the Jazz for ServiceManagement.

Note: DataView log messages and configuration options are covered in the Using and AdministeringDataView, under Configuring trace and logging in Chapter 4: Administration tasks.

Chapter 2. Logs (Wireline Component) 35

Database log

The Tivoli Netcool Performance Manager database uses the Oracle-supplied log. The default location forthis log file is /ORACLEHOME/admin/PV/bdump/alert_PV.log directory, where ORACLEHOME is thelocation of Oracle on your system.

DB2 has two logs. These logs can be used based on your requirement.Notification log

Notification logs are readable. These logs log database activities/events, and also database start/stopevents. The default file is instance_name.nfy (db2.nfy).

Diagnostic logDiagnostic logs are not easy to read. These logs log all the logs from notification log plus some moreerror/warning logs. You can use them primarily for IBM support. The default file is db2diag.log.

The file name for these logs rotates.

For example,

db2diag.n.log and <instance>.n.nfy files, where n is an integer. 0 is default, when DIAGSIZEparameter is set to non-zero.

[db2@tnpminlnx10 db2dump]$ db2 get dbm cfg | grep -i DIAGSIZE

Size of rotating db2diag & notify logs (MB) (DIAGSIZE) = 9

Set the following path in DIAGPATH parameter.

[db2@tnpminlnx10 db2dump]$ db2 get dbm cfg | grep -i DIAGPATH

Where,

• Diagnostic data directory path DIAGPATH = /opt/db2/sqllib/db2dump/• Current member resolved DIAGPATH = /opt/db2/sqllib/db2dump/• Alternative diagnostic data directory path ALT_DIAGPATH = alternative path is used when the primary

diagnostic data path, DIAGPATH is unavailable.

For more information, see http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.admin.trb.doc/doc/c0020815.html

Logs messages formatIn general, each log message indicates the date, time, Tivoli Netcool Performance Manager component,severity code, event ID, and event description.

The following table describes log message elements.

36 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Table 2. Log message elements.

Field Description

Date andTime

Date and time using the following format:<year>.<month>.<day>-<hour>.<minute>.<second>

Timezone Always UTC.

Component Name of Tivoli Netcool Performance Manager component and its process ID separatedby a dash (-). Names of Tivoli Netcool Performance Manager components are definedprivately for each subsystem. DataChannel uses channel-based naming conventions (forexample, CME.1.1), other subsystems can develop their own conventions. Somecomponents include both the process ID and thread ID separated by a colon (forexample, CME.1.1-5638:415).

SeverityCode

Event severity code. For more information, see the description of the LOG_FILTER settingin “Topology Editor log settings” on page 38.

Event ID Event identifier. For more information, see “Event IDs” on page 44.

Description Description corresponding to the Event ID.

Logging configuration and information utilitiesYou can configure logging behavior or use information utilities to help troubleshoot Tivoli NetcoolPerformance Manager components.

DataChannel logs configurationConfiguration options that govern DataChannel logging behavior are set by using the Topology Editor andare maintained in the database. Logging behavior can be set at three levels: DataChannel, specificDataChannel components, and all DataChannel components or ‘global'. Logging settings are controlled bythe log configuration.

Table 3. DataChannel log configuration components.

Level Description

DataChannel Specify logging behavior for DataChannel, including the Channel Manager(CMGR), Channel Name Server (CNS), and Application Manager (AMGR). Theyoverride any conflicting options set using GLOBAL. To specify, use the followingsyntax:

LOG.<option>=<value>

where<option> = log configuration option (see XREF)<value> = value for the configuration optionExample: LOG.ROOT_DIRECTORY=/opt/datachannel

Chapter 2. Logs (Wireline Component) 37

Table 3. DataChannel log configuration components. (continued)

Level Description

DataChannelComponent

Specify logging behavior for DataChannel components (UBA, FTE, CME, LDR,DLDR). They override any conflicting options set using GLOBAL. To specify, usethe following syntax:

<component>.<channel>.<collector>.<option>=<value>

where<component> = 3- or 4-character string for the component(UBA, CME, FTE, LDR, DLDR)<channel> = DataChannel number.<collector> = Collector number.<option> = Configuration option (see XREF)<value> = ValueExample: CME.2.500.DUAL_LOGGING=true

Global Specify logging behavior for all DataChannel components. To specify, use thefollowing syntax:

GLOBAL.<option>=<value>

where<option> = Configuration option (see XREF)<value> = ValueExample: GLOBAL.FC_RETENTION_HOURS=48

Logging configuration changes in Tivoli Netcool Performance Manager can only be made by the Installer.All components must be restarted to apply the changes. The settings include enabling/disabling centraland local logging and tracing and changing the log levels for local/remote logging/tracing. This behavior isconsistent with the previous releases.

Topology Editor log settingsLog options that can be specified in the Topology Editor are described in the following table.

Table 4. Log options in Topology Editor

Option Levels Description

DUAL_LOGGING GLOBAL andComponent

Use true or false to turn dual logging on or off.When set to false at the GLOBAL level, only DataChannel logs are generated.When set to true at the GLOBAL level, individual logs for all DataChannelcomponents are generated, in addition to the DataChannel log. Default is false.Example: UBA.2.500.DUAL_LOGGING=true

LOG_PORT GLOBAL Port number of the log server for common log and trace files.Example: GLOBAL.LOG_PORT=25000

LOG_SERVER GLOBAL Host name of the log server for common log and trace log files.Example: GLOBAL.LOG_SERVER=cme4

MAX_LOGS GLOBAL Retention period for local trace files in days.Example: CME.1.1. MAX_LOGS=7

LOG_PORT GLOBAL Port number to use for logging.Example: GLOBAL.LOG_PORT=25000

LOG_SERVER GLOBAL Host name of the log server.Example: GLOBAL.LOG_SERVER=burlington.acme.com

38 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Table 4. Log options in Topology Editor (continued)

Option Levels Description

RENDER_MESSAGE_ARGUMENTS

GLOBAL Example: CME.1.1.RENDER_MESSAGE_ARGUMENTS=false

SYSLOG_FACILITY GLOBAL Enter 128 to set the syslog facility to localhost.Example: GLOBAL.SYSLOG_FACILITY=128

Note: The syslog daemon must be running locally to have access to the log hoston the network.

FILTER or LOG_FILTER ALL The event types to log:

• F = Failure (a hard process error)• E = Error (process termination or disk space problem)• W = Warning (frequent messages that require no specific action)• I = Information only messages• 1 = Level 1 debugging information• 2 = Level 2 debugging information• 3 = Level 3 debugging information

Example: UBA.2.500.LOG_FILTER=FE

LOG_FILE LOG Name of the common log file.Example: LOG.LOG_FILE=/opt/datachannel/log/tnpmlog.log

LOG_MAX_LOGS LOG Retention period for common log and trace files in days.Example: LOG.LOG_MAX_LOGS=7

LOG_RENDER_MESSAGE_ARGUMENTS

LOG Write message parameters to log file.Example: LOG.LOG_RENDER_MESSAGE_ARGUMENTS=FALSE

FILE LOG Name and location of the DataChannel log file.Example: LOG.FILE=/opt/datachannel/log/proviso.log

TRAP_HOST LOG Host to send traps generated from log rules.Example: LOG.TRAP_HOST=127.0.01

TRAP_PORT LOG Port to send traps generated from log rules.Example: LOG.TRAP_PORT=162

SMTP_HOST LOG Host to send emails generated from log rules.Example: LOG.SMTP_HOST=127.0.01

SMTP_PORT LOG Port to send emails generated from log rules.Example: LOG.SMTP_PORT=162

SMTP_TO LOG To address for emails generated from log rules.

LOG_FORWARD LOG Use true or false to enable/disable syslog forwarding.Example: LOG.LOG_FORWARD=false

LOG_FORWARD_FILTER

LOG Filter to use for forwarded log messages.Example: LOG.LOG_FORWARD_FILTER=FEWI 123

LOG_FORWARD_PORT

LOG UDP port used by the host defined in LOG_FORWARD_SERVER.Example: LOG.LOG_FORWARD_PORT=514

LOG_FORWARD_SERVER

LOG Host name of the syslog server to forward log messages.Example: LOG.LOG_FORWARD_SERVER=localhost

Chapter 2. Logs (Wireline Component) 39

Table 4. Log options in Topology Editor (continued)

Option Levels Description

LOG_TRAP_HOST LOG Host where SNMP traps for specific types of log messages are sent.Example: LOG.LOG_TRAP_HOST=localhost

Note: The rules file defining the message types must be installed and loaded.

LOG_TRAP_PORT LOG Port used by the host defined in LOG_TRAP_HOST.Example: LOG.LOG_TRAP_PORT=162

Note: The rules file defining the message types must be installed and loaded.

LOG_TRAPS If set to TRUE, traps sent by the CME as the result of threshold violations areadded to the CME log file.Example: CME.1.1.LOG_TRAPS=TRUE

MAX_LOGS ALL Maximum number of days to retain log files.Example: UBA.2.500.MAX_LOGS=3

ROOT_DIRECTORY LOG Root directory where DataChannel logs are generated. The logs are located inthelog directory directly under this root.Example: LOG.ROOT_DIRECTORY=/opt/datachannel

SUPPRESS_TIMESTAMP_ON_FORWARD

LOG Suppresses the timestamp.Example: LOG.SUPPRESS_TIMESTAMP_ON_FORWARD=true

Note: GLOBAL settings are used by all applications. LOG settings are application-specific settings thataffect only that application. ALL settings can be used as both global and application-specific settings.

DataView logs configurationNote: DataView log messages and configuration options are covered in the Using and AdministeringDataView, under Configuring trace and logging in Chapter 4: Administration tasks.

statGet utilitystatGet is a utility that is located at each collector and provides DataLoad statistics like the statisticsthat are accessible from the Collector Information Tool GUI. statGet can be run on any local server,and is located in the following default locations:

• /opt/dataload/bin/• /opt/datamart/bin/

Note: For remote systems, you must use the Collector Information Tool. For more information, see theConfiguring and Operating DataMart.

1. Log into the server that is running Tivoli Netcool Performance Manager SNMP DataLoad by entering theusername and password you specified when installing SNMP DataLoad.

2. Source the DataLoad environment file by entering the following command:

./$DLHOME/dataLoad.env -i <instance_no>3. statGet <OPTIONS>.

OR

statGet <OPTIONS> -n <COLLECTOR_ID>4. Run the statGet utility by using the following command:

40 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Syntax

statGet [-l {objects|instances|counters|stats|requests}] [-o <object>] [-i <instance>] [-c <counter>] [-D <debugLevel>] {-all | -n <collNumber> | [-S <server> [-P <port>]]} [-?] [--version]

Options

Table 5. Options for statGet utility

Option Description

[-l <objectType>] <objectType> is one of the following items:

• objects - Lists all main classes of statistics counters.• instances - Lists all instances of a specific statistic class.• counters - Lists all counters names of a specific statistic class.• stats - Lists all counters values for a specific class, instance, and so

on.• requests - List all requests configured inside the scheduler. The

requests objectType is the default objectType if no -l option isspecified.

[-o <object>] <object> is a flag that filters the result set for -l stats and -linstances.

[-i <instance>] <instance> is a flag that filters the result set for -l stats and -lcounters.

[-c <counter>] <counter> is a flag that filters the result set for -l stats.

[-D <debugLevel>] <debugLevel> is a number from 0 - 6, where 0 specifies nodebugging, and 6 specifies verbose debugging.

[-S <serverName>] <serverName> is the name of the server that hosts a specific SNMPcollector. If the flag is undefined, the PVM_SSDADDRESS environmentvariable is used. If the environment variable is also undefined, thevalue ‘localhost' is used.

[-P <portNumber>] <portNumber> is the number of the listening port number for thecollector. If the flag is undefined, the PVM_SSDPORT environmentvariable is used. If the environment variable is also undefined, thevalue 30023002 is used.

[-T <connectTimeout>] <connectTimeout> is the amount of time permitted to establish aconnection before a timeout. If the flag is undefined, a default value of20 seconds is used.

[-T2 <dialogTimeout>] <dialogTimeout> is the amount of time permitted for a connectionresponse. If the flag is undefined, a default value of 7200 seconds (2hours) is used.

-? Displays the statGet command reference page.

-version Displays the build version string.

Chapter 2. Logs (Wireline Component) 41

Examples

Table 6. Examples of statGet usage

Use Syntax

Dump all pending and current SNMP requests. statGet

Get all classes of statistics counters. statGet -l objects

Get all possible instances of the class of counters‘Targets'.

statGet -l instances -o Targets

Get values of all statistics counters of class Targets,for instance ‘_Total'.

statGet -l stats -o Targets -i_Total

Get all currently configured requests in DataLoad. statGet -l requests

Configuring trace and loggingThe default logging level can be set by using the configure command. You can manage logs and trace inthe Jazz for Service Management from the Websphere Administrative Console from the Settings >Websphere Administrative Console option.

Default logging levelYou use the configure command to configure the Jazz for Service Management logging level for TivoliNetcool Performance Manager packages or components.

You must restart the application server for your changes to take effect. When you have restarted theserver, the logging level you have selected becomes the default logging level.

Trace logging for DataViewNote: DataView log messages and configuration options are covered in the Using and AdministeringDataView, under Configuring trace and logging in Chapter 4: Administration tasks.

The configure commandConfigures the database connection information and the Dashboard Application Services Hub logginglevel for the Tivoli Netcool Performance Manager installation.

You must restart the application server for your changes to take effect. When you have restarted theserver, the logging level you have selected becomes the default logging level.

Location

<DASH_location>/products/tnpm/dataview/bin

Syntax

configure.sh -username <WAS_admin_username> -password <WAS_admin_password> -type jdbc[-driverhome <driver_home>] [-jdbcurl <jdbc_url>] [-jdbcuser <jdbc_username>] [-jdbcpassword <jdbc_password>]

configure.sh -username <WAS_admin_username> -password <WAS_admin_password> -typelogging [-level <level>] [-package <package_name>] [-module <module_name>]

configure.sh -username <WAS_admin_username> -password <WAS_admin_password> -typedebug [-state <on|off>]

42 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Parameters<DASH_location>

The Dashboard Application Services Hub installation directory, by default /opt/IBM/JazzSM.<WAS_admin_username>

A Dashboard Application Services Hub user name for the local Dashboard Application Services Hub.The default user name is smadmin .

<WAS_admin_password>The Dashboard Application Services Hub user password for the local Dashboard Application ServicesHub. This is the password that is specified at the time of installation.

<jdbc|logging|debug>The three types of configuration options.jdbc

Configures the JDBC database connection information.logging

Configures the Dashboard Application Services Hub logging level for the Tivoli NetcoolPerformance Manager installation.

debugConfigures the remote debugging.

Optional parameters<driver_home>

The JDBC driver location.<jdbc_url>

The database URL.<jdbc_username>

The database user name.<jdbc_password>

The database password.<level>

Set the level of logging detail: fatal, severe, warning, audit, info, config, detail, fine, finer, finest, or all.<package_name>

Set logging for this software package. Wildcards * and ? are supported.<module_name>

Set logging for this software component. Wildcards * and ? are supported.<on|off>

This is the remote debugging state.on

The remote debugging state is on.off

The remote debugging state is off.

Examples

The following command sets a Dashboard Application Services Hub logging level of detail. A wildcardselects all of the com.ibm.tivoli.tnpm.dal packages.

configure.sh -username <WAS_admin_username> -password <WAS_admin_password>logging -level detail -package com.ibm.tivoli.tnpm.dal.*

The following command sets the JDBC URL to jdbc:oracle:thin@:host1.company.com:1521:PV:

Chapter 2. Logs (Wireline Component) 43

configure.sh -username <WAS_admin_username> -password <WAS_admin_password> jdbc -driverhome "/opt/oracle/product/11.2.0/jdbc/lib" -jdbcurl jdbc:oracle:thin@:host1.company.com:1521:PV -jdbcuser <jdbc_username> -jdbcpassword <jdbc_password>

configure.sh -username <WAS_admin_username> -password <WAS_admin__password> jdbc -driverhome "/opt/db2/product/10.1.0/java" -jdbcurl jdbc:db2://host1.company.com:50000/PV -jdbcuser <jdbc_username> -jdbcpassword <jdbc_password>

TroubleshootingYou can use logs for a number of troubleshooting tasks.

• Use DUAL_LOGGING to write component-specific log files in addition to proviso.log.• CME “BUILD_TREE” messages indicate whether Formula Requests are deployed and for how many

subelements (Debug Level 2).• UBA “SCANNED_INPUT”, “PERF_ACQUIRE_ALL”, “START_INPUT”, and “METRIC_STREAM_INFO”

messages indicate if metric input is being retrieved and processed.• UBA PERF_INVFLUSH messages indicate when discovered elements and subelements are written to

the database.• Use StatGet to obtain SNMP DataLoad information.

Event IDsFor information about Event IDs that are used in Tivoli Netcool Performance Manager logs, see ErrorMessages section in this guide..

44 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Chapter 3. Introduction SNMP inventoryAn introduction to the Tivoli Netcool Performance Manager SNMP Inventory.

OverviewTivoli Netcool Performance Manager allows the operator to decide how much the Tivoli NetcoolPerformance Manager DataMart will rely upon the OSS Inventory system.

The Inventory system can be virtually anything from a full-featured commercial Inventory package, to anEMS or Node Manager like HP Open View, to a flat file like /etc/hosts . The minimum required is a list ofthe IP addresses of resources to monitor.

Tivoli Netcool Performance Manager can discover both elements (resources that have an IP address, suchas a router or a switch), and the sub-elements associated or contained with them, such as an interface ora port.

Tivoli Netcool Performance Manager supports the following three modes of element and sub-elementdiscovery:

Mode Inventory Contains Tivoli Netcool PerformanceManager Discovers

1 Nothing Elements, sub-elements

2 Elements Sub-elements

3 Elements, Sub-Elements Nothing

Most Tivoli Netcool Performance Manager deployments are in mode two. In this mode, Tivoli NetcoolPerformance Manager imports a list of elements and then walks through the MIB to discover the sub-elements. In the first mode, Tivoli Netcool Performance Manager sweeps the network to discover theelements and their associated sub-elements.

DiscoveryThe discovery capabilities of Tivoli Netcool Performance Manager include some powerful and flexibletools that allow you to determine exactly what Tivoli Netcool Performance Manager monitors, and howthe subelements are labeled and grouped.

These capabilities make it possible to initiate automatically data collection, threshold monitoring, andreporting on discovered elements.

Using a formula language, Tivoli Netcool Performance Manager can be configured to walk through anelement's MIBs to discover particular MIBs representing users, tunnels, protocols, service classes orother sub-elements. Particular OIDs can be used to automatically create a label for the subelement.

For example, the subelement label could be a combination of the element name, the interface, the portand the customer name, all taken from the MIB.

Metrics and propertiesIn addition to the identifier of the sub-element and the metrics collected for it, Tivoli Netcool PerformanceManager allows the operator to create any number of user-defined properties.

There are two main differences between metrics and properties. Metrics come from a monitored resourceand are used to calculate statistics that are the basis of performance reports and alarm thresholds.Metrics are generally numeric values that change frequently, like the number of packets transmitted or aresource's availability.

© Copyright IBM Corp. 2011, 2019 45

Properties, by contrast, are values that change less frequently, such as the CIR (committed informationrate) or the location of the element. Properties consist of metadata-like identifiers or labels for suchthings as the customer and/or the services using a particular sub-element.

The values for properties can be discovered automatically from the monitored resource, or they can beimported from Inventory, provisioning or from another OSS component.

Inventory synchronization and change managementSubelement properties such as the CIR or customer name can change. Tivoli Netcool PerformanceManager tracks the change and the time of the change, so that reports are displayed correctly.

For example, utilization may be calculated against CIR. After the CIR is updated, reports must reflect thenew value for utilization calculations. But reports that show dates prior to the CIR update must use theold CIR value. Tivoli Netcool Performance Manager manages this without error.

If a subelement is assigned to a new customer, the customer property will change. If the subelement is ina particular customer's group, this can cause the subelement to move to a new group. This can changethe collection, alarm thresholds and reporting for that subelement, automatically.

Change management for elementsThe Inventory must track changes so that continuity of meta-data associated with the elements can bemaintained.

Unfortunately, Inventory is not as simple as sweeping a range of IP addresses to identify the networkelements. That is just the beginning of the process. The Inventory must track changes so that continuityof meta-data associated with the elements (such as associations to customers, VPNs and services) can bemaintained. At least one additional challenge remains to keep the element Inventory accurate, as shownwith these two problem statements:

• IP Address changes• Problem: If you are tracking a router by its IP address, and you discover a router at a new IP address,

how do you know if it is a new router, or an existing router with a changed IP address?

Tivoli Netcool Performance Manager solves this problem by associating additional properties with eachelement which provide additional continuity and trace-ability in the face of IP address changes. Theseadditional properties can be discovered from the device itself, like SNMP sysName, or gatheredexternally, like the name resolved from the IP address of the element's management interface.

• Name changes• Problem: If you are tracking a router by its name, and you discover that the name has changed, how do

you know if it is a new router with that IP address, or an existing router with a changed name?

Tivoli Netcool Performance Manager does not track elements by their name or any other singleproperty. Instead, by tracking a combination of properties, Tivoli Netcool Performance Manager is ableto provide continuity to inventory even when any of these properties change.

By automatically tracking changes to an element, rather than discovering it as a new element or forcingthe operator to manually update the database, Tivoli Netcool Performance Manager helps reduceoperating costs as follows:

• Performance and trend reports for the element show the entire history of the element, withoutinterruption.

• Changes to the element are shown in historical reports so they can be correlated to problems orchanges in performance.

• Meta-data, such as location, community string, or other properties remains associated with theelement, saving the operator from having to re-enter this.

• Inventory accuracy is improved because the update operation is automatic, not manual, eliminatingerrors.

46 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

• Inventory accuracy is improved because synchronization is automated, eliminating manual delays.

Change management for subelementsIn addition to the challenge of detecting and correctly managing changes on subelements, it is importantto display this information correctly on reports.

From an external (customer) point of view, subelement changes should be invisible. From an internal(network operations) perspective, the change must be visible. Tivoli Netcool Performance Managermanages all of this automatically.

There are many reasons why the identifier (in SNMP, the Object Identifier, or OID) might change for aparticular subelement. Assuming that the subelement is a port or virtual circuit residing on an interface,some of the changes will be due to failure and recovery scenarios, or network reconfigurations due togrowth:

• Adding or removing an interface card can cause the SNMP indexes to shift for other sub-elements.• The interface the subelement resides upon might fail, forcing the service associated with the

subelement to be moved to another interface.• The service may be moved to a currently unused subelement. The service may be moved to a

subelement in use, and the service currently on the subelement is moved to another subelement

Most network changes should be invisible to customers. Their reports should reflect the quality of theirservice, and moves and changes to the network to preserve their service should be invisible to them. Thisis particularly important for SLA reporting. You certainly want to avoid forcing the customer to view tworeports, one for the original NIC and a second report for the replacement NIC.

Throughout the network changes, network operations and engineering staff must have an accurate viewof the actual sub-elements. For troubleshooting and capacity planning purposes, they should have ahistorical view of performance and traffic on a particular port, with information on changes that haveoccurred.

Grouping subelementsProperties can be used to automatically group subelements.

For example, sub-elements can be grouped according to technology, customer, service or site. Groupscan be hierarchical, so it is possible to create structures like the following:

• Site/Technology, to see all ATM SVCs in the New York POP.• Customer/Service, to show all of the services a particular customer has subscribed to.• Technology/Site, to see which sites are generating the most Frame Relay activity.

Subelements can exist in multiple groups simultaneously. For example, a subelement might be part of anetwork operations group and a particular customer's group.

Where to go from hereRelevant information.

For information on troubleshooting tasks to perform after a new SNMP Inventory has been run, see SeeSNMP Inventory Troubleshooting.

For information on periodic administrative tasks to perform, see See SNMP Inventory Management.

Chapter 3. Introduction SNMP inventory 47

48 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Chapter 4. SNMP inventory troubleshootingDiscusses SNMP Inventory troubleshooting for Tivoli Netcool Performance Manager.

OverviewThe major phases of SNMP inventory.

The Tivoli Netcool Performance Manager SNMP Inventory consists of the following three major phases,which usually happen sequentially:

• SNMP Discovery

Detects all resources on a target network and creates a virtual image of the network.• Synchronization

Compares the virtual network image generated by the Discovery with the records in the Tivoli NetcoolPerformance Manager database that were created by the previous Inventory run. Any modifications(new, missing, or renamed resources, for example) are then synchronized through the application ofvarious algorithms, and the new network image is written to the database.

• Grouping

Updates the grouping structure in the database, which determines the kind of information that is to becollected on each resource, element, sub-element, and so forth.

In almost all cases, Tivoli Netcool Performance Manager SNMP Inventory requires virtually no operatorintervention.

However, under certain circumstances, problems arise which you will need to address. The followingsections discuss the more common problems you are likely to encounter and - where possible -- providesuggestions for remedial actions.

It is strongly advised that you monitor the logs for potential error messages by doing one of the following:

• Running a Discovery from the command line.

If you run a Discovery from the command line, redirect STDER to a log file, as follows:

inventory -noX -action discovery -name lowell >output2>error_log

For a complete list of error messages written to the Tivoli Netcool Performance Manager log file, seeMessages section of this guide. For more information on using the Tivoli Netcool Performance Managerlog file, see See Monitoring the Log File.

• Running a Discovery from the DataMart GUI

If you use the DataMart GUI to initiate a Discovery, error messages will appear on the

DataMart GUI > Resource tab > Inventory Tool iconLive Information tab.

© Copyright IBM Corp. 2011, 2019 49

Figure 1. Errors Displayed in the DataMart GUI

The Inventory Tool prints out messages like the following every five seconds:

2005/12/09 13:46:52 [PL2DBS1, 238 sec, IP done.1/ SNMP done.1/ Elmt0.1.0/ SubElmt 0.0.0]

These messages explain the progress of the discovery as follows:

– IP done.1

Indicates that the IP phase of the discovery process has completed.– SNMP done.1

Indicates that the SNMP phase of the discovery process has completed.– Elmt 0.1.0

Indicates that progress of discovered elements, using the following syntax:

numberOfObjectsInInputQueue.numberOfThreadsRunning.numberOfElementsDiscovered

– SubElmt 0.0.0

Indicates that progress of discovered sub-elements, using the following syntax:

numberOfObjectsInInputQueue.numberOfThreadsRunning.numberOfSubElementsDiscovered

If after two minutes there is no change in these messages, the Inventory Tool displays a more detailedmessage like the following:

2005/12/09 13:46:57 Current activity @ 2005.12.09-18.46.54 2005/12/09 13:46:57 Stage: IP done.1 2005/12/09 13:46:57 Stage: SNMP done.1 2005/12/09 13:46:57 Stage: Elmt 0.1.0 2005/12/09 13:46:57 W: R00004/192.168.80.2 2005/12/09 13:46:57 Stage: SubElmt 0.0.0

The line that includes the run number and IP address (2005/12/09 13:46:57 W: R00004/192.168.80.2,for example) can be used to troubleshoot possible problems, as explained in See Discovery Seems toHang or Never Finishes.

50 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Discovery troubleshootingThe following sections address the more common problems that arise during Discovery.

Discovery does not startThe following sections offer the most common solutions to problems with Discovery not starting.

Discovery fails because Discovery server does not runWhat do to if the discovery fails.

About this task

If the Discovery server fails to start, an error message like the following is returned:

IIOP: couldn't connect to 192.168.68.251:34024: couldn't opensocket: connection refusedError: StartInventory Failed for Discovery Server :IDL:omg.org/CORBA/INTF_REPOS:1.0 {minor 0 completion_statusCOMPLETED_NO}

To troubleshoot this problem, do the following:

Procedure

1. Log in as pvuser on the system where the channel manager and log server are installed.2. Change your working directory to the $DC_HOME/bin directory, by entering the following command.

Note that $DC_HOME is defined as /opt/datachannel by default.

cd $DC_HOME/bin

3. Verify that the Discovery server is not running by entering the following command:

$ dccmd -action status -pattern DISC.*.*

If the Discovery server is not running, the dccmd command returns output like the following:

NUMBER FACILITY HOST STATUS ES DURATION EXTENDEDSTATUS

1 DISC unresponsive

What to do next

ACTION: If the Discovery server is not running, do the following:

1. Restart the Discovery server by entering a command like the following, specifying the Discovery serverfor your deployment (in this example we use DISC.DEV19.1):

dccmd -action bounce -pattern DISC.DEV19.1

2. Verify that the Discovery server is running by entering the following command:

dccmd -action status -pattern DISC.*.*

Chapter 4. SNMP inventory troubleshooting 51

If the Discovery server is running, the dccmd command returns output like the following:

NUMBER FACILITY HOST STATUS ES DURATION EXTENDEDSTATUS

1 DISC DEV19.QUALLA running 1 running

For more information about using the dccmd command, see the Command Line Interface .

Discovery fails because collector stops during discovery

About this task

If the collector stops during a Discovery, several different error messages are logged. The most commonerror messages are the following:

• Error: Aborted at March 14, 2005 10:21:58 pm• Error: Connection refused• Error: Discovery Server : Status of lowell : invalid CLIENTERR [DC1] R00015Connection refused (-I 682 -D 0 -profil lowell -collectordev19.quallaby.com:3002 -nbGetIfAddress 100 -invFileTxt /opt/datamart/conf/inventory_subelements.txt -vname {} -intcollector 1)

To troubleshoot this problem, do the following:

Procedure

1. Log in as pvuser (or the user name that you specified during installation) on the system whereDataMart is installed.

2. (Optional) Ensure that the database and Listener are running. For more information, see the TivoliNetcool Performance Manager Installation Guide.

3. Enter the following command, replacing DATAMART_ROOT with the root DataMart directory ( /opt/datamart by default):

DATAMART_ROOT/bin/pvm

The DataMart GUI appears.

Figure 2. DataMart GUI4. Click on the Collector Information icon. The Collector Information Tool appears.

52 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Figure 3. Collector Information Tool

The Collectors Tab lists all the collectors loaded from the database.5. Select the collector that you are troubleshooting. You look for the collector name in the output of the

Live Information tab of the Discovery trace, as follows (in this example, the collector isdev19.quallaby.com):

BeforeDiscovery for lowell : nothing to doRunning Discovery on profile : lowell (mode 1) Enforce SE invariant uniqueness per element : active (from profile)Duplicate IpAddress: active with collector number: 1(dev19.quallaby.com:3002) (from profile ) Sub-element configuration file:/opt/datamart/conf/inventory_subelements.txt (from profile )Discovery collector number: 1 (dev19.quallaby.com:3002) (fromprofile )

Start Reload formulas on dev19.quallaby.com:3002 ...

Figure 4. Stopped Collector

What to do next

ACTION: Restart the collector by entering the following command on the Collector server:

/opt/dataload/bin/pvmdmgr start

Chapter 4. SNMP inventory troubleshooting 53

Note: The collector cannot be restarted from the GUI.

Discovery does not start because inventory is lockedHow to troubleshoot Tivoli Netcool Performance Manager if discovery does not start because inventory islocked

About this task

To troubleshoot this problem, do the following:

Procedure

1. Log in as pvuser (or the user name that you specified during installation) on the system whereDataMart is installed.

2. (Optional) Ensure that the database and Listener are running. For more information, see the TivoliNetcool Performance Manager Installation Guide.

3. Enter the following command, replacing DATAMART_ROOT with the root DataMart directory ( /opt/datamart by default):

DATAMART_ROOT/bin/pvm

The DataMart GUI appears, as shown in See DataMart GUI.4. Click on the Resource tab > Inventory Tool icon. The Inventory Tool appears.

Figure 5. Inventory Tool5. Click Live Information. If the profile is locked, you will see a warning message like the one displayed

in See Inventory Tool.6. To confirm that the profile is locked, return to the DataMart GUI and click on the Monitor tab-

>DataMart Status icon. The DataMart Status Tool appears.

Figure 6. DataMart Status Tool

54 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

In this example, the Inventory profile lowell is locked by an Inventory process with a PID of 13458.7. Determine if the lock is valid and if the process is still running, by entering the following command,

replacing LOCK_PROCESS_PID with the PID of the locking process (13458 in our example):

ps -aef | grep LOCK_PROCESS_PID

What to do next

ACTION: If the process is active, the lock is valid and you should wait until the Inventory completesbefore running another Inventory.

ACTION: If the process is inactive, remove the lock and start another Inventory. To remove the lock, click

on the Remove Locks icon located in the upper left of the toolbar.

The qPing utility has incorrect settingsAs part of Discovery in Inventory Mode 1, Tivoli Netcool Performance Manager scans IP ranges using theDataLoad qPing utility. This utility will fail if group, user, and execute permissions are not set

About this task

The qPing utility will fail with the following error messages if group, user, and execute permissions are notset correctly on the file:Inventory Tool

To troubleshoot this problem, do the following:

Procedure

1. Log in as pvuser (or the user name that you specified during installation) on the system where theDataLoad server is installed.

2. Change your working directory to $PVMHOME/bin ( /opt/dataload/bin by default), and enter thefollowing command to check the settings on the qPing utility:

cd $PVMHOME/binls -l ./qPing

Chapter 4. SNMP inventory troubleshooting 55

The correct settings are as follows:

-r-sr-sr-- 1 root pvusers 1537814 Jan 14 15:31/opt/dataload/bin/qPing

3. If the settings are not correct, su to root and enter the following commands:

chown root $PVMHOME/bin/qPing chmod 6554 $PVMHOME/bin/qPingchgrp pvusers $PVMHOME/bin/qPing

4. Verify the settings by entering the ls -l command again

Note: The qPing utility and the DataLoad user must belong to the same group (in our example,pvusers). The sticky bit setting ("s" in the ls -l line) allows the utility to be executed as root by anyUNIX user belonging to the pvusers group.

dataload.env gets corruptedThe dataload.env may get corrupted due to many actions being performed such as adding or removingmultiple SNMP collectors.

About this task

Even though collectors are present on the host, dataload.env may give faulty representation such as:$source /opt/dataload/dataLoad.env|-------------------------------------------------------------------------------||INSTANCE_ID| COLLECTOR_ID| CHANNEL_ID|PORT|HAM_MODE||-------------------------------------------------------------------------------|| 1| NA| NA| NA| NA||-------------------------------------------------------------------------------|

When dataload.env has NA in its field, it means there are no SNMP collectors on that host. To triggergeneration of dataload.env, we need to perform either addition or removal of collector. As it displaysNA, we can only add collectors.

To troubleshoot this problem, do the following:

Procedure

1. Exit the Topology Editor.2. Go the location you have installed Topology Editor.

Default location: /opt/IBM/proviso/topologyEditor

Depending on your database go to location /ora/metadata/core/ for oracle or got tolocation /db2/metadata/core for DB2. So complete path for oracle is, cd /opt/IBM/proviso/topologyEditor/ora/metadata/core/.

3. Open host.xsd,4. Search for elements "SERVICE_PORTS", "DL_NUMBERS", "DC_NUMBERS" "DL_HA_MODES", inhost.xsd.

5. Set visible property for these elements to true.

<ext:visible>true</ext:visible>6. Save the file host.xsd.7. Start Topology Editor.8. Add SNMP collector, go to physical view, and then click on the host for which you have added

Collector.

Search for the properties, "SERVICE_PORTS", "DL_NUMBERS", "DC_NUMBERS" "DL_HA_MODES" inproperties section.

If the values are not updated properly, manually edit it with the correct values.9. Save topology, and run for Installation. Correct dataload.env is generated.

56 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

10. Check dataload.env

$ source /opt/dataload/dataLoad.env

Note: Next time if you want to add or remove collector, just confirm whether correct values are goinginto the above mentioned properties. If not, then repeat steps 8 to 10 and run for desired action.

Discovery starts but issues warning messagesThe following sections offer the most common solutions to warning messages that occur duringDiscovery.

IP addresses are rejectedIf an IP address is rejected during Discovery, errors will be written to the log or will display on theInformation Tab of the Inventory Tool.

About this task

The errors created are like the following:

Warning: IP Address 10.48.58.45 rejected because this IP addresshas been excluded.

Warning: IP Address 10.60.64.230 rejected because this IP addresshas been excluded.

In most cases, this is not a problem.

To troubleshoot this error message, do the following:

Procedure

1. Log in as pvuser (or the user name that you specified during installation) on the system whereDataMart is installed.

2. (Optional) Ensure that the database and Listener are running. For more information, see the TivoliNetcool Performance Manager Installation Guide.

3. Enter the following command, replacing DATAMART_ROOT with the root DataMart directory ( /opt/datamart by default):

DATAMART_ROOT/bin/pvm

The DataMart GUI appears, as shown in See DataMart GUI.4. Invoke the Discovery Tool Wizard by doing the following:

a) Select the Resource Tab->Inventory Tool icon. The Inventory Tool appears with theConfiguration displayed, as shown in See Inventory Tool Configuration Tab

Chapter 4. SNMP inventory troubleshooting 57

Figure 7. Inventory Tool Configuration Tab

b) Highlight a profile and then select Edit > Profile or click on the edit icon . The Inventory Tool Wizard appears, as shown in See Inventory Tool Wizard.

Figure 8. Inventory Tool Wizardc) Click the Next button twice to navigate to the Discovery Tool Wizard, as shown in See Discovery

Tool Wizard.

58 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Figure 9. Discovery Tool Wizard5. As shown in See Discovery Tool Wizard, check to see if the rejected IP addresses - either individually

or within a specified range - have been intentionally excluded. If they have not, contact IBM support.

Duplicate elements are foundIf the same element, a router for example, has more than one IP address associated with it, Tivoli NetcoolPerformance Manager will "discover" the element multiple times, reject the duplicates discoveries, andwrite warning messages to the log.

About this task

See Rejected Duplicate Elements, for example, shows Tivoli Netcool Performance Manager rejecting threeduplicate elements.

Figure 10. Rejected Duplicate Elements

This is expected behavior.

If these warning messages appear often, Discovery performance may be degraded, since Tivoli NetcoolPerformance Manager must spend a lot of time calculating and eliminating duplicate elements.

You may therefore want to exclude the duplicate addresses from the Discovery by doing the following:

Procedure

1. Invoke the Discovery Tool Wizard (DTW). For instructions on how to invoke the DTW, see See Invokethe Discovery Tool Wizard by doing the following:.

Chapter 4. SNMP inventory troubleshooting 59

2. Add the duplicated IP addresses to the IP address exclude area of the DTW, as shown in the followingfigure:

Figure 11. IP address exclude area of the DTW

Elements are not identified during discoveryIf DataLoad did not receive an SNMP answer using the community name configured in the Tivoli NetcoolPerformance Manager profile, warning messages are created.

About this task

Warning messages like the following are written to the log and displayed on the Live Information Tab ofthe Inventory Tool:

Warning: Unidentified Agents={192.168.1.201,192.168.1.100,192.168.1.84,192.168.1.75,192.168.1.103,192.168.1.93,192.168.1.98,192.168.1.92,192.168.1.60,192.168.64.103}

Warning: Unidentified Agents={192.168.1.48,192.168.64.1,192.168.64.113,192.168.64.106,192.168.127.253,192.168.1.242,192.168.1.181,192.168.1.182,192.168.1.254,192.168.1.62}

Devices may fail to respond for reasons like the following:

• The device is not reachable from DataLoad collector (for example, no network route).• The SNMP agent was not started in the device.• Tivoli Netcool Performance Manager has the wrong SNMP community name for the device.• The device Access List is preventing Tivoli Netcool Performance Manager DataLoad to act as an SNMP

Manager for this device.• The firewall configuration is preventing SNMP traffic with the device.

To troubleshoot this problem, follow these steps:

60 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Procedure

1. Log in as pvuser (or the user name that you specified during installation) on the system whereDataMart is installed.

2. (Optional) Ensure that the database and Listener are running. For more information, see InstallingTivoli Netcool Performance Manager.

3. Change your working directory to DATAMART_ROOT/bin, replacing DATAMART_ROOT with the rootDataMart directory ( /opt/datamart by default).

4. Perform an Internet Control Message Protocol (ICMP) query on the device, by entering the followingcommand, replacing IP_ADDRESS_OF_UNIDENTIFIED_DEVICE with the IP address of theunidentified device, and NAME_OF_COLLECTOR_SERVER_DOING_PING with the name of thecollector server doing the ping:

qPing IP_ADDRESS_OF_UNIDENTIFIED_DEVICE -SNAME_OF_COLLECTOR_SERVER_DOING_PING

If successful, the qPing command returns the IP address of the unidentified device, as follows:

$ qPing 192.168.68.33 -S dev19192.168.68.33:10

5. Connect to the device and verify whether or not the SNMP agent is enabled and running.6. Connect to the device and verify the community name.7. (Optional) You might have to change the community name in Tivoli Netcool Performance Manager, by

using the DataMart->Inventory->Discovery Wizard to add an "alternate" community name to theprofile.

To change the community name, follow these steps:

a) Invoke the Discovery Tool Wizard (DTW). For instructions on how to invoke the DTW, see SeeInvoke the Discovery Tool Wizard by doing the following:.

b) Add an alternate community name in the specified text box.c) Click Add to confirm your choice, as shown in the following figure:

Figure 12. Discovery Tool Wizard

Chapter 4. SNMP inventory troubleshooting 61

Elements skipped because no related subelementsWhen Tivoli Netcool Performance Manager discovers an element but cannot discover any relatedsubelements, warning messages are written to the log and displayed on the Information Tab of theInventory Tool:

About this task

The warning messages are like the following:

Skipping 3 elements (Set ('192.168.66.221_jeffs2''192.168.66.221_default' '192.168.66.221_jeffs1')) in output file,because they don't have related subElements

This is not expected behavior, and should be resolved immediately.

To troubleshoot this problem, follow these steps:

Procedure

1. Log in as pvuser (or the user name that you specified during installation) on the system whereDataChannel is installed.

2. Change your working directory to $DC_HOME/log (/opt/datachannel/log, by default), by enteringthe following command:

cd $DC_HOME/log

3. Enter the following command to search the proviso.log for the Discovery formula of the skippedelement, replacing EL_IP_AD, with the IP address of the skipped element:

grep DISC proviso.log | grep R00020 | grep ELS_IP_AD | grepCHKDISCOVERY

4. If he grep command returns no output.

If the grep command does not return output, the content of the following files in the $PVMHOME/confdirectory ($PVMHOME is defined as /opt/datamart, by default):

• $PVMHOME/conf/inventory_elements.txt• $PVMHOME/conf/inventory_sub_elements.txt

Contact IBM support.5. If the grep command returns output like the following:

2005.03.15-18.58.28 UTC DISC.DEV19.1-13308 2 CHKDISCOVERY R00020/192.168.68.173. Family:Generic~Agent, trydiscoveryFormula Formula (Basic_Element - 7486 string)

2005.03.15-18.58.43 UTC DISC.DEV19.1-13308 2 CHKDISCOVERY R00020/192.168.68.173. Family:1213_Device, trydiscoveryFormula Formula (1213_Device - 4851)

2005.03.15-18.58.45 UTC DISC.DEV19.1-13308 2 CHKDISCOVERY R00020/192.168.68.173. Family:IETF_IF, trydiscoveryFormula Formula (IETF_IF - 9885)

The following may be attempted:

a) If you believe that the device should in fact respond, try to discover the device manually andmonitor the trace, using the DataMart->Metric->Formula Editor, as shown in the following figure:

62 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Figure 13. Formula Editorb) Activate the relevant portion of the device MIB (for example SAA in the Cisco router).c) In some cases, SNMP attributes do not respond properly, and the Discovery formula for those

devices must be changed. In this event, contact IBM support.

Discovery seems to hang or never finishesIf the Discovery server shows no progress for several minutes it has probably encountered problems witha Discovery formula.

About this task

If the Discovery server shows no progress for several minutes (up to thirty minutes in some cases), asshown in the following trace log, it has probably encountered problems with a Discovery formula:

Figure 14. Discovery formula

Chapter 4. SNMP inventory troubleshooting 63

Problems - real or apparent - with Discovery formulas can be the result of the following:

• The SNMP agent is slow to respond.• The network latency is very long.• The Discovery formula is not well-suited to the SNMP agent.• Collector performance issues.

When Tivoli Netcool Performance Manager is in such a state one of two things result:

• The Discovery formula finally succeeds and the Inventory continues.• The Discovery hangs until the Inventory timeout occurs (two hours) when the following error message is

written to the log file:

Error: Profile is not progressing during the last 7201 seconds,aborting

Contact IBM support and provide them with the DATACHANNEL_ROOT/datachannel/log/[yyyy.mm.dd]SNMP.log

However, before contacting IBM support, and before the Discovery finishes or times out, do the following:

Procedure

1. Determine which Discovery formula is causing the problem by doing the following:a) Log in as pvuser (or the user name that you specified during installation) on the system where

DataChannel is installed.b) Change your working directory to DATACHANNEL_ROOT/log, replacing DATACHANNEL_ROOT with

the root DataMart directory ( /opt/datachannel by default).c) Enter the following command to search the proviso.log for the Discovery formula:

grep DISC proviso.log | grep R00010 | tail -1

2005.03.15-20.32.16 UTC DISC.PVDEMO2.1-1048 2 CHKDISCOVERY R00010/172.31.0.51. Family:Cisco_CBQoS_Action, trydiscoveryFormula Formula (Cisco_CBQoS_Action - 7784)

In this example, the Discovery formula is Cisco_CBQoS_Action.2. Determine the internal request ID that is stuck by doing the following:

a) Log in as pvuser (or the user name that you specified during installation) on the system where theDataMart or DataLoad server is installed.

b) Change your working directory to DATAMART_ROOT/log, replacing DATAMART_ROOT with the rootDataMart directory ( /opt/datamart by default).

c) Enter the following command to find the internal request ID, replacing SERVER_NAME with thename of the Tivoli Netcool Performance Manager DataMart server:

statGet -S SERVER_NAME| grep -i once

+ [33] ID 96627,{CAL none (ONCE)(next=2005/03/15 20:32:16)}(P3)ACTIVE (LastExec):ServiceForm:(Trgt=(string)172.31.0.51)(Form=(form)Cisco_CBQoS_Action)(Inst=)(RComm=public)

+ [40] ID 96683,{CAL none (ONCE)(next=2005/03/15 20:48:19)}(P1)ACTIVE (LastExec): ServiceSTAT (LONG)

In this example, the internal request ID is 96627.

Important: If the command returns no output, contact IBM support.3. Enable limited debugging on the collector server in order to populate the log with additional

information by doing the following:a) Change your working directory to /opt/dataload/contribs .

64 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

b) Enter the following command, replacing TASKID with the Internal request ID you found in SeeDetermine the internal request ID that is stuck by doing the following:.

dialogTest2 Debug 6.TASKID

Tivoli Netcool Performance Manager outputs a message like the following:

Set debug level to 6 for taskId 96627.

Debug configuration:> Global Level= 1; Mask=FW> ID 96627 Level= 6; Mask=FWI1234WARNING: DO NOT USE THE GLOBAL COLLECTOR DEBUGGER.

Synchronization troubleshootingAddress the more common problems that arise during synchronization.

Synchronization (elements)During the synchronization phase, Tivoli Netcool Performance Manager compares the virtual networkimage generated by the Discovery with the records in the Tivoli Netcool Performance Manager databasethat were created by the previous Inventory run.

Any modifications (new, missing, or renamed resources, for example) are then synchronized through theapplication of various algorithms, and the new network image is written to the database.

In order to track elements and sub-elements through subsequent inventories, Tivoli Netcool PerformanceManager identifies them with a unique, never-changing identifier, called an invariant.

The default element invariant, for example, is a concatenation of the following three attributes:

• The MIB II sysName• The first IP address responding to the ICMP scan (in Inventory mode 1) or the one given in the the mode

2 Inventory file• The fist valid physAddress (MAC address) in the MIB II ifTable

See Synchronization Invariant Logic illustrates the logic used to determine if a "newly-discovered"element is actually new or is an existing element that has moved or changed.

Synchronization Invariant Logic

Element Attributes inDatabase

MIB II sysName IP Address physAddress New Element If ...

Defined Defined Defined Two or three attributeshave changed.

Empty Defined Defined Two attributes havechanged.

Empty Empty Empty The resolved name isdifferent from resolvedname in the database.

If an element does not respond to one of these three MIB II attributes, contact IBM support.

To avoid synchronization errors, we strongly recommend that you limit device configuration changes toone attribute between two runs of an Inventory (Discovery and Synchronization).

Chapter 4. SNMP inventory troubleshooting 65

Pre-synchronization summaryAs Tivoli Netcool Performance Manager prepares for synchronization, it compiles a list of elements

The list contains the following types of elements:

• New• Updated• Burned• Unchanged• Not Found• Histo Reject

See Pre-synchronization summary shows the display written to the DataMart > Inventory Tool > LiveInformation, with this summary information highlighted:

Figure 15. Pre-synchronization Summary

The following sections discuss this summary in more detail.

Identifying not found elementsIf the Pre-Synchronization summary lists any contact IBM support.

An example of not found elements can be found in Pre-synchronization summary, which contains threeexamples.

66 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Identifying burned elementsHow to identify burned elements

In cases where the MIB II sysName, IP address, and physAddress are all defined for an element (the firstrow in See Synchronization Invariant Logic), Tivoli Netcool Performance Manager may encounter a specialsituation if the MIB II sysName and phyAddress have changed, but the IP address remains unchanged.

In this special case, Tivoli Netcool Performance Manager creates a new element and writes it to thedatabase. However, since the IP address for "both" elements is the same, so too is the resolved name,which means that the elements would be seen by Tivoli Netcool Performance Manager as the sameelement.

To prevent this situation, Tivoli Netcool Performance Manager renames the initial elment with a "Burned"prefix, as shown in “Identifying burned elements” on page 67:

Figure 16. Burned Element

When Synchronization completes, a list of burned elements is written to the following file:

PROFILE_HOME/PROFILE_NAME/synchro/e_burned.dat

e_burned.dat file

If you have an e_burned.dat file, contact IBM support.

The burned elements and their sub-elements are duplicated, and the statistics attached to theseresources are not continuous in reports.

Preventing burned elementsTivoli Netcool Performance Manager relies quite heavily on the sysName when calculating invariants.When using sysName you need to prevent burned elements.

About this task

To prevent burned elements, so the following:

Procedure

1. Do not change the sysName on a device when the lowest physAddress has also changed.2. Ensure that the sysName is defined and not left empty.3. Ensure that the sysName is defined with a unique value.

Chapter 4. SNMP inventory troubleshooting 67

4. Minimize any changes to the sysName once they have been set, unless you want Tivoli NetcoolPerformance Manager to see the device as new and interrupt the continuity of statistics.

Detecting too many new elementsIf there has been extensive configuration changes before an Inventory run (for example, if two attributeswere changed simultaneously on a router), Tivoli Netcool Performance Manager will discover and create anew element in the database.

About this task

The consequences are severe:

• The element and its sub-elements are duplicated.• The statistics attached to these resources are not continuous in the reports.• Double polling might happen on "both", until the "first" device is "retired" by the Inventory.

Aside from limiting device configuration changes to one attribute between two runs of an Inventory, thereis no way to prevent this situation from occurring.

When Synchronization completes, a list of new elements is written to the following file. Note that$PVMHOME is defined as /opt/datamart , by default:

$PVMHOME/importexport/PROFILE_NAME/synchro/new_e.dat

Procedure

1. If you have a new_e.dat file, check to ensure that the number of new elements is not unexpected.2. If the number is unexpected, contact IBM support.

Note: A large new_e.dat file is to be expected the first time a network is discovered.

Detecting different elements resolved with the same nameIf the name resolution system (for example, DNS) assigns identical names to the IP addresses of differentdevices - a configuration mistake - Tivoli Netcool Performance Manager will an error duringSynchronization.

About this task

The error will look like the following:

Warning: IP Address 10.48.58.45 rejectedWarning: IP Address 10.60.64.230 rejected

When Synchronization completes, a list of rejected elements is written to the following file:

PROFILE_HOME_DIRECTORY/PROFILE_NAME/synchro/duplicateElement_e.reject

If you have a duplicateElement_e.reject file, do the following:

Procedure

1. From the DataMart server, resolve the name of both conflicting IP addresses, in order to confirm theidentical naming resolution.

2. Fix the naming resolution system and start the same Inventory again.

68 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Do not delete incorrectly named elements that define SNMP community namesConfiguring Tivoli Netcool Performance Manager involves associating elements with their SNMPCommunity name.

About this task

When initially configuring Tivoli Netcool Performance Manager, you use the SNMP Configuration Tool, asshown in See Configuring SNMP Community Names, to associate elements with their SNMP Communityname so that Tivoli Netcool Performance Manager can read from the devices.

Figure 17. Configuring SNMP Community Names

The SNMP Configuration Tool writes this information to the database.

During the next Inventory run, the synchronization process sees the elements that were newly enteredinto the database by the SNMP Configuration Tool as missing all three invariant attributes (see row threein See Synchronization Invariant Logic).

Tivoli Netcool Performance Manager then attempts to determine if a new element needs to be created bycomparing the resolved names of the devices, with the following results:

• If the name that was entered into the SNMP Configuration Tool was the correct resolved name of thedevice, Tivoli Netcool Performance Manager will not create a new element and will instead update theattributes for the existing element with the discovered values.

• If the name that was entered into the SNMP Configuration Tool was the incorrect resolved name of thedevice, Tivoli Netcool Performance Manager will create a new element. On subsequent Discoveries,Tivoli Netcool Performance Manager will rediscover and eventually update this element and ignore theelement with the incorrect resolved name.

Chapter 4. SNMP inventory troubleshooting 69

Procedure

Do NOT remove the element with the wrong resolved name from the database.

Results

Tivoli Netcool Performance Manager continues to use that entry for SNMP Community name mapping. Ifthe entry is removed, Tivoli Netcool Performance Manager will lose the SNMP Community mapping andwill not be able to read from that resource.

Failed synchronizationPay particular attention to failed elements while monitoring the Synchronization process

About this task

While monitoring the Synchronization process, pay particular attention to failed elements.

Figure 18. Failed Elements and the Inventory Tool

Procedure

If Synchronization reports failed elements (greater than 0), contact IBM support immediately.

Synchronization (subelements)The subelement invariant is defined in the Discovery Formulas referenced in the file $PVMHOME/conf/inventory_sub_elements.txt .

Note that $PVMHOME is defined as /opt/datamart by default.

70 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

This invariant is usually defined differently per object type (for example, an SAA probe) and vendor (Cisco,for example).

The logic used to decide if a "newly-discovered" subelement is in fact new, depends on the following:

• If the invariant is not defined, the subelement name (usually the concatenation of the element nameand the SNMP instance) is used to determine if a new subelement should be created or an existing oneshould be updated.

Any change to the name between two subsequent Discovery runs triggers the creation of a newsubelement.

An SNMP index (instance) change will trigger the creation of a new subelement (because the SNMP indexis part of the name), which will cause reporting discontinuity.

• If an invariant is defined, the parameter " Enforce Sub-Element Invariant uniqueness per element " isused, which is set in the DataMart > Inventory > Discovery Wizard, as shown in the following figure:

If the option highlighted in the figure is checked, uniqueness is verified on a per element basis; if leftunchecked, uniqueness is verified across the entire profile.

Identical subelement invariantIf an invariant is defined for a particular type of subelement (for example, Cisco SAA), Tivoli NetcoolPerformance Manager will check the uniqueness of that invariant during an SNMP Inventory.

About this task

If Tivoli Netcool Performance Manager detects two subelements with the same invariant, it displays anerror message like the following:

Warning: Identical invariant detected for invariant172.31.0.51-1_CBQoS-172.31.0.51-class-default-Match any -output-1(172.31.0.51-1,CBQoS<1107><1123> and172.31.0.51-1,CBQoS<1107><1177>).

Note: When identical invariants are detected, neither subelement is stored in the database.

To resolve this situation, follow these steps:

Procedure

1. Use the DataMart > Metric > Mib Browser utility to verify that the two invariants are in fact identical.2. If they are identical, the following needs to be done:

• The Discovery formula needs to be changed to ensure the uniqueness of either the element or theprofile. This is usually done by concatenating more OIDs to the invariant.

Chapter 4. SNMP inventory troubleshooting 71

• The SNMP OID value, used for building the invariant, needs to be changed. For example, if you usethe Cisco ifAlias settable OID, its value might not be unique (among other things, a configurationerror may exist due to a non-unique Customer contract number, which should be fixed.

• Discovery should then be re-triggered, so that both subelements can be discovered.3. Contact IBM support for assistance in making these changes.

Checking the TraceInventory.log fileViewing the summary information in the $PVMHOME/log/TraceInventory.log file.

Note that $PVMHOME is defined as /opt/datamart by default.

Figure 19. TraceInventory.log File

You should review the $PVMHOME/log/TraceInventory.log file and check for the following:

Large number of subelements not foundA large mount of "missing" sub-elements (discovered before, but not rediscovered), may be because alarge portion of your network is not reachable.

About this task

If the same sub-elements are continually not found during subsequent Inventories, they will eventuallybe retired. For more information, see “Finding elements and subelements about to reach their retry limit”on page 77.

Procedure

If your network is reachable, the sub-elements exist, and you are still receiving error messages, contactIBM support.

Rejected subelementsThe log may report types of rejected subelements.

Procedure

If the log reports any of the following types of rejected sub-elements, contact IBM support:

• histo reject• dup reject

Burned subelementsProcedure for dealing with burned subelements.

About this task

A burned subelement is determined as follows:

• The subelement has an invariant in the database (for example, inv1).• The subelement has a name (for example, name1).

72 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

• During an Inventory, a new subelement is discovered and created with the same name (for example,name1) and a different invariant for example, inv2).

In this case, two different subelements are about to be created in the database with the same name.

To prevent this duplication, Tivoli Netcool Performance Manager renames the initial subelement with a"Burned" prefix, so that each subelement can be stored in the database with a unique name.

A list of burned subelements is written to the following file:

PROFILE_HOME/PROFILE_NAME/synchro/burned_seinv.dat1

Procedure

• If the log reports any burned subelements, contact IBM support.

Disconnected subelementsProcedure for dealing with disconnected subelements.

About this task

A disconnected subelement is determined as follows:

• The subelement has an invariant in the database (for example, inv1).• The subelement has a name (for example, name1).• During an Inventory, a subelement is discovered with the same name (for example, name1) and an

empty invariant.

An empty invariant typically happens when an invariant is used to assign physical resources (ports, forexample) to customers.

In this case, the empty invariant is interpreted as a "disconnection" between the customer and theresource.

If a subelement is determined to be disconnected, no new subelement is created, and the initialsubelement is marked as disconnected.

A list of disconnected subelements is written to the following file:

PROFILE_HOME/PROFILE_NAME/synchro/disconnected_seinv.dat1

Procedure

• If the log reports any disconnected subelements, contact IBM support.

Grouping troubleshootingIf all problems with discovery and synchronization have been solved - or none arise - it is unlikely that youwill encounter problems with grouping.

Monitoring the Tivoli Netcool Performance Manager log fileThe Tivoli Netcool Performance Manager log file is located in the DataChannelInstallROOT/logdirectory (/opt/datachannel/log, by default) and should be monitored on a regular basis.

Currently, only DataChannel and DataLoad write to the Tivoli Netcool Performance Manager log. Log filesfor other components can be found in $PVMHOME/log ( /opt/datamart/log, by default) andSILVERSTREAM_HOME/log ( /opt/silverstream/log, by default).

You can write a program to do monitor the Tivoli Netcool Performance Manager log file (recommended) oryou can check the Tivoli Netcool Performance Manager log file by hand, using the grep command.

Chapter 4. SNMP inventory troubleshooting 73

For example, the following command checks the Tivoli Netcool Performance Manager log file for a fatalloader error:

grep CMGR proviso.log | grep -w F982348945 2001.02.16-18.42.25 CMGR F ERROR There was a problemloading the domain database

Tivoli Netcool Performance Manager log messagesFor a complete list of log messages written to the Tivoli Netcool Performance Manager log, see Messagessection.

Burned subelementsReasons why a subelement (SE) can be in a `burned' state

There are two reasons a subelement (SE) can be in a `burned' state.

• If its Element is burned• An SE is not in Discovery and another SE with Invariant is discovered with the same element and

Instance

Scenario 1 - instance shift causes disconnectInitial discovery finds three subelements, all with Invariant.

Elt dbIndex Elt Name Instance SE dbIndex SE Name Invariant State MissingCount

200000431 alm00142061.elt01 <04> 200000450 alm00142061.elt01.seinv04

I:01:04 on 0

200000431 alm00142061.elt01 <05> 200000449 alm00142061.elt01.seinv05

I:01:05 on 0

200000431 alm00142061.elt01 <06> 200000448 alm00142061.elt01.seinv06

I:01:06 on 0

During a subsequent Discovery the following occurs:

• The SE with Invariant I:01:05 is not found• The SE with Invariant I:01:06 is found, but at Instance <05>

Result:

• The SE with Invariant I:01:05 is marked missing because it is not in the Discovery• The SE with Invariant I:01:05 becomes Disconnected because it is not in Discovery and another SE was

discovered with the same Element and Instance• The SE with Invariant I:01:06 is updated (Instance, Name, Label, etc.), but retains the same dbIndex

and Invariant

Elt dbIndex Elt Name Instance SE dbIndex SE Name Invariant State MissingCount

200000431 alm00142061.elt01 <04> 200000450 alm00142061.elt01.seinv04

I:01:04 on 0

200000431 alm00142061.elt01 <05> 200000449 alm00142061.elt01.seinv05

I:01:06 on 0

200000431 alm00142061.elt01 Disconnected_200000449_<05>

200000448 Disconnected_200000449_alm00142061.elt01.seinv05

I:01:05 off 1

74 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

In theory, a Disconnected resource could come back; the Invariant is the unique identifier to indicate thereturn of the SE. The Disconnected resource attempting to return would also have to have a differentInstance in order to return. Element Name and Instance are required to be unique across allsubelements.

Scenario 2 - instance shift causes burnInitial Discovery finds three subelements without Invariant and three subelements with Invariant.

Elt dbIndex Elt Name Instance SE dbIndex SE Name Invariant State MissingCount

200000432 alm00142061.elt02 <01> 200000437 alm00142061.elt02.seinv01

on 0

200000432 alm00142061.elt02 <02> 200000436 alm00142061.elt02.seinv02

on 0

200000432 alm00142061.elt02 <03> 200000435 alm00142061.elt02.seinv03

on 0

200000432 alm00142061.elt02 <04> 200000447 alm00142061.elt02.seinv04

I:02:04 on 0

200000432 alm00142061.elt02 <05> 200000446 alm00142061.elt02.seinv05

I:02:05 on 0

200000432 alm00142061.elt02 <06> 200000445 alm00142061.elt02.seinv06

I:02:06 on 0

During a subsequent Discovery the following occurs:

• The SE that was at Instance <03> is not found in Discovery• The SE with Invariant I:01:06 is found, but at Instance <03>

Result:

• The SE that was at Instance <03> is marked missing because it is not present in Discovery• The SE that was at Instance <03> is Burned because it is not present in Discovery and another SE in

Discovery has the same Element and Instance• The SE with Invariant I:01:06 is updated (Instance, Name, Label, etc.), but retains the same dbIndex

and Invariant

Elt dbIndex Elt Name Instance SE dbIndex SE Name Invariant State MissingCount

200000432 alm00142061.elt02 <01> 200000437 alm00142061.elt02.seinv01

on 0

200000432 alm00142061.elt02 <02> 200000436 alm00142061.elt02.seinv02

on 0

200000432 alm00142061.elt02 <03> 200000445 alm00142061.elt02.seinv03

I:02:06 on 0

200000432 alm00142061.elt02 <04> 200000447 alm00142061.elt02.seinv04

I:02:04 on 0

200000432 alm00142061.elt02 <05> 200000446 alm00142061.elt02.seinv05

I:02:05 on 0

200000432 alm00142061.elt02 Burned_200000435_<03>

200000435 Burned_200000435_alm00142061.elt02.se03

off 1

Burned resources cannot come back, there is no Invariant to uniquely identify the SE in Discovery as thatwhich was Burned. If the Burned resource attempted to come back without Invariant and with the sameInstance, Inventory would reject both because of a duplication on Element Name and Instance thatcannot be resolved.

Chapter 4. SNMP inventory troubleshooting 75

Where to go from hereRelevant information

For information on periodic administrative tasks to perform, see Chapter 3, “Introduction SNMPinventory,” on page 45

76 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Chapter 5. SNMP inventory managementDiscusses SNMP inventory troubleshooting for Tivoli Netcool Performance Manager.

Regular monitoringMonitoring actions have to be performed regularly to keep the SNMP Inventory process of Tivoli NetcoolPerformance Manager performing optimally.

If your SNMP Inventory is triggered every day, we recommend performing these monitoring actions atleast once a week.

If your SNMP Inventory is triggered several times a day (for example, every six hours), we recommendperforming these monitoring actions at least once a day.

Routine SNMP inventory management tasksThe following sections discuss routine SNMP Inventory management tasks:

Finding elements and subelements about to reach their retry limitWhen elements and subelements reach their retry limit, they are retired from the Inventory, which meansthat Tivoli Netcool Performance Manager stops collecting on them and removes them from some groups.

About this task

The retry limit is set and managed in the DataMart > Inventory Tool > Edit Profile > SynchronizationWizard. The default is three retries and a resource that is older than seven days, as shown in thefollowing figure. BOTH limits must be met in order for a subelement to be retired.

Figure 20. Synchronization Wizard

© Copyright IBM Corp. 2011, 2019 77

To find elements and subelements about to reach their retry limit, do the following:

Procedure

1. Log in as pvuser (or the user name that you specified during installation) on the system whereDataMart is installed.

2. Enter the following commands, noting that $PVMHOME is defined as /opt/datamart by default.

The commands look for elements and subelements approaching their retry counter, using greater than2 (>2) for the retry count and 3 (the default) to specify the age of the resource.

• Elements:

$PVMHOME/bin/resmgr/-noHead -export elt -colNames "dbIndex originname profil state missing" -filterRule "%(elt.profil) not like'%bulk%' AND %(state)='on' AND %(missing) >2"

The resmgr command returns output like the following:

200000004|_|inventory|_|skywalker.quallaby.com-1|_|lowell|_|on|_|8|_|

200000024|_|inventory|_|ducks.quallaby.com-1|_|lowell|_|on|_|4|_|

200001383|_|inventory|_|192.168.82.8-1|_|lowell|_|on|_|7|_|

• Sub-elements:

$PVMHOME/bin/resmgr -noHead -export se -colNames "dbIndex originname label elt.profil invariant state missing" -filterRule"%(elt.profil) not like '%bulk%' AND %(state)='on' AND %(missing)>2"

The resmgr command returns output like the following:

200000029|_|inventory|_|bbpser170-1_processID<12074>|_|bbpser170-1_"bbpser170""AMGR_visual" pid 12074 |_|unix|_|AMGR_visual|_|on|_|3|_|

For more information on the resmgr command, see the Tivoli Netcool Performance ManagerCommand Line Interface Guide.

What to do next

ACTION: If the elements or subelements are in the "off" state, then they will be retired. If they are in the"on" state, but are approaching both their age limit and retry limit, they are about to be retired. Thecommands in this section search for elements and subelements that are in the "on" state, but will soon beretired.

To address this problem, do the following:

1. Fix the connectivity problem so that Tivoli Netcool Performance Manager can discover the element orsubelement about to be retired.

2. Check to see if there is a problem with the SNMP community name that is preventing Tivoli NetcoolPerformance Manager from taking to the resource.

3. Increase either the retry count or the resource age setting (or both) in the Synchronization Wizard.

Finding elements and subelements that have been retired

About this task

As explained in “Finding elements and subelements about to reach their retry limit” on page 77, when anelement or subelement exceeds its Inventory Retry and Inventory Timeout limits, it is changed to the"off" state and retired from the Inventory.

78 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

To detect elements and subelements that have been retired, do the following:

Procedure

1. Log in as pvuser (or the user name that you specified during installation) on the system whereDataMart is installed.

2. Enter the following commands, noting that $PVMHOME is defined as /opt/datamart by default.

The commands look for elements and subelements that have been move to the "off" state.

• Elements:

$PVMHOME/bin/resmgr -noHead -export elt -colNames "dbIndex originname profil state missing" -filter "state(off)"

The resmgr command returns output like the following:

200028920|_|inventory|_|Delete_200028920_192.168.1.5-1|_|lowell|_|off|_|72|_|

• Sub-elements:

$PVMHOME/bin/resmgr -noHead -export se -colNames "dbIndex originname state missing" -filter "state(off)"

The resmgr command returns output like the following:

200000724|_|inventory|_|Delete_200000724_kafka.com-2_If<1>|_|off|_|7|_|

200000880|_|inventory|_|Delete_200000880_192.168.1.84-2_<NULL>|_|off|_|8|_|200000916|_|inventory|_|Delete_200000916_192.168.1.84-2_If<1>|_|off|_|8|_|200001205|_|inventory|_|Delete_200001205_192.168.1.84-2_If<2>|_|off|_|8|_|

For more information on the resmgr command, see the Tivoli Netcool Performance ManagerCommand Line Interface Guide.

What to do next

IBM recommends the following Best Practices when dealing with retired elements and subelements:

• Group them in a special group (for example, the retired group) and periodically check its content.• Delete them using the Resource Editor if you confirm that they have been permanently removed from

the network.

Note: This does not remove their statistics from the database. It just marks them "deleted" in thedatabase, so they will not overload the "retired" group, which will be kept at a manageable size.

Chapter 5. SNMP inventory management 79

80 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Chapter 6. MessagesA list of error and operational messages generated by the Tivoli Netcool Performance Managercomponents.

DataChannel error messagesLists reference format error messages produced by DataChannel. Whenever possible, explanations areoffered, as well as remedial actions.

GYMDC10000W

error_description Restartingbecause of unknown error:

Explanation:An unknown error occurred

User response:Contact technical support

GYMDC10001F

Explanation:Configuration of specified Corba service (i.e. nameservice, event service) failed at component startup.

User response:Contact technical support

GYMDC10002F

Explanation:Component startup failure. Incorrect configuration ormissing components

User response:Verify Netcool/Proviso configuration file

GYMDC10003F No collectors defined in registrytable

Explanation:Database configuration for collectors/channel is notspecified properly

User response:Check installation for this (sub)channel

GYMDC10004F error_description Shutting downthe image with error:

Explanation:Unhandled fatal runtime exception -- applicationproduces walkback file and shuts down

User response:If the condition causing failure is transient, theapplication will restart automatically and in manycases will continue. If the problem persists, contacttechnical support

GYMDC10005W

end start rid mid Timed Out duringTS query for mid:

Explanation:CME experienced a timeout during a tuple storagequery

User response:Check connectivity and make sure other componentsare running

GYMDC10006F end start rid mid app name labelTimed Out during tuple query forlabel

Explanation:PBL is paused pending manual intervention. Contacttechnical support to fix FRMI bug and have formula ->label data manually corrected

User response:Manually fix the problem and remove STOP file in thePBL root directory. If problem persists, contacttechnical support

GYMDC10007W

Too many failed acquisitionattempts, giving up on remainderof input acquisitions

Explanation:While trying to acquire input files, multiple errorsoccurred and no further attempts will be made toacquire files on this poll. Acquisition will resume onthe next poll.

User response:Look for messages in the logs that indicate failures toacquire specific files and troubleshoot the reasons forthe failures. Try and acquire the problematic filesmanually using FTP or SFTP and check that theexpected files and directories exist and can beaccessed.

GYMDC10008 schema_names Waiting For DataFor Schemas:

GYMDC10009W

Stopping plan builder becauseplan save to db failed

Explanation:The plan builder has been stopped because saving theplan to the database has failed

User response:

© Copyright IBM Corp. 2011, 2019 81

Review the proviso.log file for any previously reportedwarning messages from the plan builder

GYMDC10010W

specificLabels timeSeriesspecificFormulas There aremultiple specific formulas:

Explanation:You cannot have multiple specific formulas for thesame resource doing a specific to generic conversionwhere the specific timeseries are in different labelsbecause the plan builder does not know which label toassign to the generic timeseries. The plan builder withpick any of the specific labels to assign to the generictimeseries.

User response:Review all specific formulas for this generic formulaand review all specific formulas for this resource.

GYMDC10011W

timeseries Skipped building inputfor

Explanation:Unable to build input becuase subelement is inactive,or it has no element or elements collector is wrong

User response:Check to to see if subelement is active and has anelement and the collector is right

GYMDC10012W

requests timeseries There are toomany specific formula requests for

Explanation:There should only be one specific formula request fora timeseries

User response:Figure out why there are more than one specifictimeseries for the same resource and formula. Checkrequests.

GYMDC10013

GYMDC10014W

errorDescription

Explanation:An exception occurred while trying to contact the SAMserver

User response:Check that server is reachable

GYMDC10015W

schema_name Not acquiring databecause do directory at max hoursfor

Explanation:Indicates that the UBA has stopped acquiring databecause the "do" directory has too many hours worthof data queued up to be processed.

User response:

It may not be necessary to do anything. As the UBAprocesses data and catches up, this situation willcorrect itself. The amount of data allowed in the "do"directory is controlled by the FC_MAX_DO_HOURSconfiguration setting.

GYMDC10016 count Acquired files in

GYMDC10017 count count count periodstream_name

GYMDC10019 count_seconds total_count countFound

GYMDC10020 count_seconds count Acquired

GYMDC10021I

GYMDC10022 reason period stream_name

GYMDC10023W

file name Skip processing

Explanation:The given input file is not being processed because acollector number could not be determined.

User response:Double check that the input filename and contents arenot malformed.

GYMDC10024

GYMDC10025

GYMDC10026

GYMDC10027

GYMDC10028I

GYMDC10029

GYMDC10030

GYMDC10031 count count count periodstream_name

GYMDC10032 count_seconds total_count countFound

GYMDC10033W

error description file name schemaname Failed to acquire

Explanation:The UBA failed to acquire the indicated file.

User response:Check the connectivty between the UBA and the file,ftp or sftp server. Connect to the file, ftp or sftp serverby hand from the same host and user id as the UBAand make sure the directory and file indicated in theURI exists.

GYMDC10034W

reason Timezone database failedto load:

Explanation:

82 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

The timezone database failed to load from theZoneInfo(TZ) DB on the host.

User response:Double check the installation of the ZoneInfo(TZ)database on the host where the problem is occurring.

GYMDC10035W

Explanation:An upstream PvUrl was registered with missinginformation

User response:Check the upstream component's AMGR settings fordisk usage server DUS

GYMDC10036W

Explanation:This message is an indication of a misconfiguration orthat an upstream component (CME) was not runningyet so it had not registered itself yet, or the upstreamCME was failing to register itself because CNS ishaving problems

User response:1. Check that CME is properly configured in thesystem. 2. Check CME is running. 3. Check CNS isrunning

GYMDC10037W

Call to getDurationsForIntervals()expects an array as the firstargument

Explanation:The call to getDurationsForIntervals() was invokedwith something other than an array for the firstargument

User response:Update ecmascript code

GYMDC10038W

Call togetAccumulatedDurationForIntervals() expects an array as the firstargument

Explanation:The call to getAccumulatedDurationForIntervals() wasinvoked with something other than an array for thefirst argument

User response:Update ecmascript code

GYMDC10039W

required Needs to be inJMS_FILTER:

Explanation:A required event is missing in the filter

User response:Check the JMS_FILTER

GYMDC10040W

file Does not exist or is not a file:

Explanation:JAR path does not exist or is not a file

User response:Check that JAR path does exist

GYMDC10041W

path Does not exist or is not a file:

Explanation:Java path does not exist or is not a file

User response:Check that Java path does exist

GYMDC10042W

Call togetAccumulatedDurationForTuples() expects an array as the firstargument

Explanation:The call to getAccumulatedDurationForTuples() wasinvoked with something other than an array for thefirst argument

User response:Update ecmascript code

GYMDC10043W

periodStart Call togetAccumulatedDurationForTuples() expects a positive integer asthe second argument. Invalidargment:

Explanation:The call to getAccumulatedDurationForTuples() wasinvoked with something other than an integer for thesecond argument

User response:Update ecmascript code

GYMDC10044W

periodEnd Call togetAccumulatedDurationForTuples() expects a positive integer asthe third argument. Invalidargment:

Explanation:The call to getAccumulatedDurationForTuples() wasinvoked with something other than an integer for thethird argument

User response:Update ecmascript code

GYMDC10045W

Call to getIntervalsForTuples()expects an array as the firstargument

Explanation:

Chapter 6. Messages 83

The call to getIntervalsForTuples() was invoked withsomething other than an array for the first argument

User response:Update ecmascript code

GYMDC10046W

periodStart Call togetIntervalsForTuples() expects apositive integer as the secondargument. Invalid argment:

Explanation:The call to getIntervalsForTuples() was invoked withsomething other than an integer for the secondargument

User response:Update ecmascript code

GYMDC10047W

periodEnd Call togetIntervalsForTuples() expects apositive integer as the thjrdargument. Invalid argment:

Explanation:The call to getIntervalsForTuples() was invoked withsomething other than an integer for the third argument

User response:Update ecmascript code

GYMDC10048W

count

Explanation:Lists number of calculation errors for a metric in anhour

User response:Review the formula code for potential defects

GYMDC10049W

timestamp node name tuples orheartbeat Discarded out ofsequence

Explanation:Tuples or data were produced that were out ofsequence.

User response:Verify that the system resumes processing normallyand check for any lost data.

GYMDC10050 status

GYMDC10051W

Explanation:This message is an indication of either acommunications problem, or a failure to process arequest coming from another process.

User response:

If the issue does not resolve itself, check for physicalconnectivity between the processes involved in therequest.

GYMDC10052W

incoming_record existing_recordtime_series Record types don'tmatch for TS

Explanation:There is a mismatch between existing and newrecomputed values during the operator state upgrade

User response:Contact technical support

GYMDC10053W

recomputed existing time_seriesRecomp wrapper should haveoriginal: TS

Explanation:There is a mismatch between existing and newrecomputed values during the operator state upgrade

User response:Contact technical support

GYMDC10054W

incoming existing time_seriesValues don't match for TS

Explanation:There is a mismatch between existing and newrecomputed values during the operator state upgrade

User response:Contact technical support

GYMDC10055W

host The host address is theloopback interface,

Explanation:This messages indicates that a process will be unableto communicate with processes located on otherhosts. Objects the affected process will be advertisingthemselves to other processes using the loopbackaddress, and as such, processes on other hosts will failto be able to communicate with objects this process.

User response:Check the /etc/hosts file for an entry thatcorresponding to this host name that maps to127.0.0.1. Also check DNS and host name resolutionconfiguration.

GYMDC10056 SLA features are disabled

Explanation:SLA features are disabled but the application hasattempted to use some SLA related features such asRCM or the PBL COL_FORMULAS feature

User response:Enable SLA features

GYMDC10057

GYMDC10058

84 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

GYMDC10059

GYMDC10060W

error_description Reason:

Explanation:An error occurred while contacting the CMGR

User response:Check connectivity between CME and CMGR

GYMDC10061I nodes Nodes Found:

GYMDC10062W

error_description Reason:

Explanation:RCM cannot contact CMGR to obtain CME labels

User response:Check that CMGR is running and check connectivitybetween RCM and CMGR

GYMDC10063I labels CME Labels Found:

GYMDC10064W

incoming existing time_seriesRecomp Values don't match: TS

Explanation:There is a mismatch between existing and newrecomputed values during the operator state upgrade

User response:Contact technical support

GYMDC10065 outputFilename Merging multipleBOFs to:

GYMDC10066 bofFilename Sorting BOF:

GYMDC10067W

currentHour time unitOfWorkDiscover deactivated for unit ofwork:

Explanation:Discovery was deactivated for this unit of work

User response:None

GYMDC10068W

value attribute subelement Notdiscovered:

Explanation:The subelement/attribute/value was not discovered

User response:Check configuration or try again

GYMDC10069W

value attribute element Notdiscovered:

Explanation:The element/attribute/value was not discovered

User response:Check configuration or try again

GYMDC10070W

value attribute resource Notdiscovered:

Explanation:The resource/attribute/value was not discovered

User response:Check configuration or try again

GYMDC10071

GYMDC10072W

errorDescription Error whileconnecting to the database:

Explanation:An error occurred while connecting to the database

User response:Check database is accessible and that username andpassword are correct

GYMDC10100W

error detail port host responseFailed to process response:

Explanation:Unexpected response to 3002 request (request toSNMP Collector)

User response:If problem persists, contact technical support

GYMDC10101W

response Lost response:

Explanation:Unexpected response to 3002 request (request toSNMP Collector)

User response:If problem persists, contact technical support

GYMDC10102W

result process id Killed sqlldr pid=

Explanation:Piped merge did not complete, LDR kills Oracle SQLloader

User response:If problem persists, contact technical support

GYMDC10103W

result process id Killing stucksqlldr pid=

Explanation:An instance of stuck Oracle SQL loader was foundbefore starting piped merge. LDR kills stuck instance

User response:If problem persists, contact technical support

GYMDC10104F

Explanation:Oracle error encountered during database load. Theactual error message is displayed

User response:

Chapter 6. Messages 85

If problem persists, contact technical support

GYMDC10105F

Explanation:Oracle SQL loader task is not found

GYMDC10106F

Explanation:Attempt to load end-of-period data failed. Loading isstopped pending manual intervention

User response:Fix the problem and remove STOP file in the loaded (ordaily loader) root directory. If problem persists,contact technical support

GYMDC10107W

error details stored procedure name

Explanation:Storage procedure invocation failed

User response:Check that database is running and accessible. Ifproblem persists, contact technical support

GYMDC10108W

filename Unable to get next metricrecord from

Explanation:Failure to read record from one of the input files

User response:If problem persists, call technical support

GYMDC10109W

file Recovery file

Explanation:Recovery file does not exist

User response:None

GYMDC10110W

errorDescription sqlStatement ASQL error has occurred for the SQLstatement: (

Explanation:Non-fatal SQL error

User response:Fix the database privileges and ensure the database isworking properly

GYMDC10111W

directory error message Error:

Explanation:An error occured while trying to get disk consumptionfor a disk usage server root directory

User response:Try to run the du command manually on the samedirectory to see what error occurs

GYMDC10112W

errorDescription

Explanation:Naming server cannot be accessed or failed to look upobject in the naming service

User response:Start CNS or check network

GYMDC10113W

errorMessage

Explanation:Channel component failed to register with CorbaNaming Service

User response:Start CNS, check network and check that port isn't inuse

GYMDC10114W

errorDescription

Explanation:Failed to start Corba for channel component

User response:Check configuration

GYMDC10115W

errorDescription

Explanation:Failed to stop Corba for channel component

User response:Check configuration

GYMDC10117W

No metadata resources loadedfrom database.

Explanation:Metadata load did not load any resources

User response:Make sure inventory has run

GYMDC10118F

Explanation:Piped merge did not complete, LDR kills Oracle SQLloader

User response:If problem persists, contact technical support

GYMDC10119W

record Out of order record:

Explanation:Out of order record in BOF file

User response:Call technical support

86 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

GYMDC10120W

log_contents result_descriptionerror_description General SFTPerror:

Explanation:General SFTP error

User response:Check datachannel configuration

GYMDC10121W

error host Unable to connect toremote host:

Explanation:FTP failed to connect to specified host

User response:Check datachannel configuration

GYMDC10122W

count The failure limit of

Explanation:FTP failed to transfer file after several retries

User response:Check configuration

GYMDC10123W

directory Unable to change remoteworking dir:

Explanation:FTP failed to change to specified directory

User response:Check configuration

GYMDC10124W

error description uri Unable to getremote file

Explanation:There was a failure when attempting to retrieve a fileusing FTP.

User response:Check configuration

GYMDC10125W

localDirPath Unable to make localdir:

Explanation:FTP failed to create specified directory

User response:Check configuration

GYMDC10126W

directory Unable to remove remotedirectory:

Explanation:FTP failed to remove specified directory

User response:Check configuration

GYMDC10127W

remoteURI Unable to removeremote file:

Explanation:FTP failed to remove specified file

User response:Check configuration

GYMDC10128W

file Unable to remove remote closehour file:

Explanation:Unable to remove remote close our file

User response:Check configuration

GYMDC10129W

Explanation:Missing input source definition referred to in xlogcommand.

User response:Check configuration

GYMDC10130W

sqlStatement object SQL insert ofupdate for

Explanation:Insert or update failed

User response:Check Database connectivity

GYMDC10131I uri error_description

GYMDC10132W

new_name old_name Failedrenaming file from:

Explanation:FTP failed to rename specified file

User response:Check datachannel configuration

GYMDC10133W

There is more than one top-levelstream operator specified

Explanation:The structure of the UBA operators is invalid. There ismore than one operator that has no output operators.Operators without any outputs are called rootoperators and are the ones that actually emit metrics.

User response:Contact technical support for help with a possible techpack bug.

GYMDC10134W

timestamp file name File

Explanation:A file needs to be reprocessed after a restart of theUBA.

User response:No action is necessary

Chapter 6. Messages 87

GYMDC10135W

error formula id calculate Errorduring

Explanation:An error occured during the calculate() method

User response:Check formula syntax, check formula arguments,protect access to tuple lists

GYMDC10136W

error formula value Invalid formularesult

Explanation:An error occurred while producing a formula result

User response:Check formula code, check formula arguments,especially returned value

GYMDC10137W

message tuple

Explanation:A bad tuple was encountered.

User response:Check for iFixes for the tech pack that correct theissue.

GYMDC10138W

Explanation:The TIME_GRANULARITY setting defines what oneperiod of time is. This data file contains data for morethan one period of time.

User response:Check configuration

GYMDC10139F slelabel Can't load, SLE

Explanation:Can't load, SLE is already running

GYMDC10140W

Explanation:An error ocurred while trying to establish the localtimezone. We will use the default seconds from GMT

User response:Contact techical support

GYMDC10141F

Explanation:Attempt to load recomputed data failed. Loading isstopped pending manual intervention

User response:Fix the problem and remove STOP file in the recomproot directory. If problem persists, contact technicalsupport

GYMDC10142F

Explanation:Attempt to recover recomputation failed. Running isstopped pending manual intervention

User response:Fix the problem and remove STOP file in the recomproot directory. If problem persists, contact technicalsupport

GYMDC10143W

slelabel Can't unload, SLE

Explanation:Can't unload, SLE is not currently running

User response:Do not try to move an SLE that is not running

GYMDC10144W

cmelabel slelabel Can't start SLE

Explanation:Can't start SLE, current CME is not owner of thefilesystem

User response:Contact technical support

GYMDC10145W

Explanation:Failed looking up PvURL for directory from AMGR

User response:Ensure AMGR,CMGR are running and check the DUSseciton of the AMGR config

GYMDC10146I Tenuring of load sets turned offbecause too much work

GYMDC10147W

errorDescription Log initializationerror:

Explanation:Proceedable error during initialization of logger

User response:Check error message, verify and change configuration

GYMDC10148W

destinationPvURL sourcePvUrlerrorDescription Error:

Explanation:An error occurred while acquiring an input file

User response:Make sure that no manual file deletes are hapeningand that file permissions are set properly on thesource file

GYMDC10149W

Explanation:

88 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

An error occurred while collecting input files frominputDirPvURL. Upstream CMEs publish theiroutputDirPvURL so that downstream LDRs can usethese as a inputDirPvURL. LDR looks up theoutputDirPvURL for each of its INPUT_COMPONENTSin the configuration.

User response:1. Review the error shown in this log message andmake sure that the inputDirPvUrl is valid. 2. Check theconfiguration settings for disk usage server (DUS). 3.Try to do a file copy or ftp/sftp get from thisinputDirPvURL to make sure that it is accessible

GYMDC10150W

error detail application nameFailed testing for runningapplication:

Explanation:AMGR received an error while trying to check if anapplication is running

User response:Check system status

GYMDC10151W

Explanation:AMGR received an error while trying to kill anapplication

User response:Check system status

GYMDC10152W

Explanation:AMGR received an error while trying to start anapplication

User response:Check system status

GYMDC10153W

Explanation:AMGR received an error while trying to get the statusof an application

User response:Check system status

GYMDC10154W

Explanation:AMGR received an error while trying to stop anapplication

User response:Check system status

GYMDC10155W

Explanation:AMGR failed to kill the specified application

User response:Check system status

GYMDC10156F

GYMDC10157W

directory error message Error:

Explanation:An error occured while trying to get disk free space fora disk usage server root directory

User response:Check that libproviso.so is available and has properpermissions

GYMDC10160W

Collector unknown for realtime

Explanation:Collector specified in real-time data services requestis not found

User response:Make sure collector is running. Check configuration

GYMDC10161W

errorDescription Failed to writedata to the subscriber:

Explanation:There was a failure to deliver real-time subscriptiondata to subscriber

User response:Problem should correct itself

Related information“DataView Real time reporter fails to deliverreal-time subscription data” on page 16

GYMDC10162W

Explanation:The subscription request is invalid due to bad resourceor incorrect formula in the request

User response:Make sure the resource and metric are correctlydefined in the database for the realtime chart that failsits subscription request

GYMDC10163W

Explanation:Unable to find SNMP formula for a generic id

User response:Check request's formula to make sure generic formulaexists

Chapter 6. Messages 89

GYMDC10164W

router id Router Id

Explanation:Attempt to use a Cisco SAA router feature with a nonSAA router.

User response:Check router configuration to ensure that SAA isenabled

GYMDC10165W

attribute name Missing mandatoryattribute:

Explanation:A mandatory attribute is missing from a probe.

User response:Check the health of DataView.

GYMDC10166W

Collector unavailable for realtime

Explanation:Collector specified in real-time data services requestis not available

User response:Make sure collector is running. Check connectivity andconfiguration

GYMDC10167W

target_id Unknown or incompletetarget Id

Explanation:Uknown or incomplete target id

User response:Resync collector or restart collector

GYMDC10168W

apiCall Invalid arguments to APIcall to

Explanation:The collector library has been called by CMGR/DataView with invalid arguments.

User response:Contact technical support.

GYMDC10169W

target_name target_id SNMPTimeout or invalid communitystring on target Id:

Explanation:SNMP Timeout or invalid community string on target Id

User response:Check network connectivity and SNMP configuration

GYMDC10170W

description

Explanation:An error occurred while monitoring probes

User response:

Contact technical support

GYMDC10171W

subelement id No subelement withid:

Explanation:A CORBA client to the SAA probe monitor issued arequest with an invalid subelement id

User response:Resync collector or restart collector

GYMDC10172W

error description subelement idError resyncing probes for router

Explanation:An error occurred while attempting to resync theprobes on a router.

User response:Check network connectivity, review SNMPconfiguration for that router

GYMDC10173I probe index subelement id Probe:

Explanation:A monitored probe was redeployed on a router tosynchronize its settings with those stored in Proviso.

GYMDC10174W

Unknown collector error

Explanation:An unknown error has occurred.

User response:Contact technical support.

GYMDC10175W

type name Undefined probe type:

Explanation:Probe type is unknown or unsupported

User response:Review imported configuration in DataView and checksupported probe types in documentation

GYMDC10176W

subelement id probe indexUnknown probe at index '

Explanation:Unable to modify probe because of invalid index.

User response:Review imported configuration in DataView.

GYMDC10177W

name subelement id Router

Explanation:Probe type is unknown or unsupported

User response:Review imported configuration in DataView and checksupported probe types in documentation

GYMDC10178I subelement id Router

90 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Explanation:A router reboot was detected.

User response:No action necessary.

GYMDC10179I subelement id Resyncing probes onrouter

Explanation:Probes in a router are being resynced with the probesettings stored in Proviso.

User response:No action necessary.

GYMDC10180W

error description subelement idError trying to detect reboot ofrouter

Explanation:An error occurred while attempting to detect if a routerwas rebooted.

User response:Review the error described in the message

GYMDC10181W

This collector is currently inactive

Explanation:A collector client sent a probe configuration messageto an inactive collector.

User response:Contact technical support

GYMDC10182W

description Failed to load probemonitor configuration from thedatabase:

Explanation:Failed to load the probe monitor configuration from thedatabase.

User response:Investigate connectivity with the database

GYMDC10183W

The server is too busy to acceptnew probe monitoring requests.

Explanation:Too many probe monitoring requests are currentlyactive. Rejecting further requests.

User response:DataView Client should retry automatically. No actionrequired.

GYMDC10184W

The router is too busy to acceptnew probe monitoring requests.

Explanation:Too many probe monitoring requests are currentlyactive for the given router. Rejecting further requests.

User response:

DataView Client should retry automatically. No actionrequired.

GYMDC10185I subelement id Router

Explanation:A router check can not be completed at that time

User response:No action necessary.

GYMDC10186W

name attribute name Unsupportedattribute '

Explanation:An unknown attribute was sent for probe type

User response:If the attribute is a user specified attribute they shouldreview the router documentation.

GYMDC10187I max_time subelement id Target Id

Explanation:Collector is busy. Client should retry.

User response:DataView Client should retry automatically. No actionrequired.

GYMDC10188W

subelement id probe index Unableto modify probe type at index '

Explanation:Unable to modify probe type.

User response:Use delete/create instead.

GYMDC10189W

The probe has expired

Explanation:A probe has reached its expiration date and should beremoved.

User response:Remove the probe.

GYMDC10200W

errorMessage Moving file causedproblem:

Explanation:Failed to move (rename) specified file

User response:Check bulk collector configuration

GYMDC10201W

errorMessage Moving file to donecaused problem:

Explanation:Failed to move (rename) specified file

User response:Check bulk collector configuration

GYMDC10204W

file Saved file

Chapter 6. Messages 91

Explanation:Problem when accessing BOF file

User response:If problem persists, contact technical support

GYMDC10205W

lineErrorMessage A metadata erroroccurred -

Explanation:The metadata was requested without a valid name.

User response:Analyze input files or contact technical support

GYMDC10206W

formatType

Explanation:The parser field description attempted to specify anincorrect value type

User response:Contact technical support

GYMDC10207W

file No data found in data file:

Explanation:Input bulk file is empty

User response:Check input data

GYMDC10208W

ftpResult directory Unable to CD toprofile directory:

Explanation:Bulk collector failed to change directory to remoteinventory directory (FTP error)

User response:Check connectivity and configuration

GYMDC10209W

errorMessage ftpServer Unable toconnect to ftp site

Explanation:Bulk collector failed to connect to remote inventorydirectory (FTP error)

User response:Check connectivity and configuration

GYMDC10211W

ftpResult localFilename Unable tosend inventory file

Explanation:Bulk collector failed sending file

User response:Check connectivity and configuration

GYMDC10212W

ftpResult filename Unable torename inventory file

Explanation:

Bulk collector failed rename file in remote inventorydirectory (FTP error)

User response:Check connectivity and configuration

GYMDC10213W

errorDescription line Unexpectedinput in data file. Offending line is:

Explanation:Unexpected input in data file -- offending line shown

User response:Check input data file

GYMDC10214W

file

Explanation:No valid file format can be identified with specified file

User response:Check input data file

GYMDC10215W

line Unexpected input in data file.Offending line is:

Explanation:Unexpected input in data file -- offending line shown

User response:Check input data file

GYMDC10216W

errorDescription file messageMalformed timestampencountered while processing file.

Explanation:Malformed timestamp encountered while processingfile

User response:Check input data file

GYMDC10217W

file message The format typedetection algorithms fail to detectthis file.

Explanation:The format type detection algorithms fail to detect thisfile

User response:Analyze input files and contact technical support

GYMDC10218W

file errorDescription Internal error:

Explanation:Internal error while processing file

User response:Contact technical support

GYMDC10219W

schemaName No schema named

Explanation:

92 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Error while processing specified file (invalid schemaname)

User response:Check input data file

GYMDC10220W

Explanation:Error while processing input data file

User response:Check input data file

GYMDC10301W

A communications error occurredbetween channel manager,application manager andapplication.

Explanation:A communications error occurred

User response:Check connectivity between CMGR, AMGR andapplication and that CMGR and AMGR

GYMDC10302W

reason A communications erroroccurred between command lineinterface and the channel manager(

Explanation:A communications error occurred

User response:Check connectivity between command line interfaceand the channel manager

GYMDC10304W

Explanation:Inable to reach application

User response:Check connectivity

GYMDC10305W

Explanation:Getting labels failed during near real-time query

User response:Check connectivity to database.

GYMDC10306W

error_description application_nameFailed getting metric records from:

Explanation:CMGR received an error while trying to get metricrecords from an application

User response:Check connectivity between CMGR host andapplication host

GYMDC10307W

error_string application_nameFailed testing for runningapplication:

Explanation:CMGR received an error while trying to test if anapplication is running already

User response:Check system status and connectivity between CMGRhost and application host

GYMDC10308W

Explanation:CMGR received an error while trying to kill anapplication

User response:Check connectivity between CMGR host andapplication host

GYMDC10309W

Explanation:CMGR received an error while trying to start anapplication

User response:Check connectivity between CMGR host andapplication host

GYMDC10310W

Explanation:CMGR received an error while trying to get the statusof an application

User response:Check connectivity between CMGR host andapplication host

GYMDC10311W

Explanation:CMGR received an error while trying to stop anapplication

User response:Check connectivity between CMGR host andapplication host

GYMDC10312W

Abandoned request because clientdisconnected prematurely

Explanation:Abandoned request because client disconnectedprematurely

User response:Check connectivity

Chapter 6. Messages 93

GYMDC10313W

hostname application name Noconfigured component matchesname:

Explanation:No component matches the given name, applicationand host patterns.

User response:Check the name, application and host patterns.

GYMDC10314W

Explanation:CMGR received an error while trying to contact anapplication

User response:Check connectivity between CMGR host andapplication host

GYMDC10315W

Explanation:No configured CME matches the given CME name

User response:Add an entry to configuration for the CME in questionand bounce CMGR, then start that CME.

GYMDC10316W

Explanation:SLE is already assigned to another CME

User response:Contact technical support

GYMDC10317W

Explanation:SLE has not been assigned to any CME

User response:Contact technical support

GYMDC10318W

Explanation:Currently do not support moving SLEs across filesystems.

User response:Contact technical support

GYMDC10400W

file name count error description Afile read error:

Explanation:An error occurred while trying to read and processtuples in a file.

User response:Check the input file.

GYMDC10401W

error detail metric record Metricrecord

Explanation:CME was sent data that is either not covered byrequests or is in an invalid format

User response:Check input data

GYMDC10402W

metric id count

Explanation:Lists the number of bad records in input file by metricid

User response:Review requests and resource groups for requests

GYMDC10404W

class Bad

Explanation:lasthour file is corrupted

User response:Contact technical support

GYMDC10405W

gerneric id resource request Badrequest:

Explanation:If it is an SNMP generic formula, the collector alreadysends us metrics with generic formula ID, so thegeneric formula should exist

User response:Check request's formula to make sure generic formulaexists

GYMDC10406W

mid Metric id is invalid:

Explanation:Formula refers to invalid input binding

User response:Check formula definition

GYMDC10407W

errorDescription Formula wasremoved because of compile error:

Explanation:Formula could not be loaded because of compile error

User response:Check formula definition

GYMDC10408W

debugInfo errorDescriptionformulaClassName An erroroccured while running buildingoutput metric record for formula:

Explanation:

94 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Formula refers to invalid input binding

User response:Check formula definition

GYMDC10409W

debug info errorDescriptionformulaName formulaClassNameAn error occured while runningcalculation for formula:

Explanation:An error occurred while computing formula value

User response:Check formula definition

GYMDC10410W

errorDescription classNameCompiler error for Smalltalkformula:

Explanation:Error compiling formula

User response:Check formula definition

GYMDC10411W

errorDescription rid gid mid rid midAn error occured during thresholdprocessing of a metric record(mid=

Explanation:A failure has occurred in threshold processing

User response:Send exception details to support team

GYMDC10412W

timeseries id total count discardedcount duplicate count Got

Explanation:CME discovered and discarded duplicate records whenflushing them to disk

User response:Check for duplicate data being sent to CME. Contacttechnical support

GYMDC10413W

Error sending trap, resetting SNMPengine

Explanation:Error occured during sending trap

User response:Check connectivity

GYMDC10414W

total count discarded countduplicate count Got

Explanation:CME found duplicate records or some records werediscarded because of invariant change

User response:Check system configuration. In case of invariantchange the system should handle it automatically

GYMDC10415W

filename filename Configurationfile

Explanation:The configuration file is newer than the state file.

User response:Check system configuration.

GYMDC10416W

errorDescription rid gid mid Anerror occured when attempting tosend a trap for (mid=

Explanation:An error occurred when creating or sending a trap PDU

User response:Contact technical support

GYMDC10417W

rid gid mid Mid/Gid/Rid =

Explanation:Reset Baseline state due to missing Baseline History inDB

User response:Check that LDR is loading OK

GYMDC10418W

error_details destination_URIsource_URI Failed to copy

Explanation:An error occured during an attempt to copy a file

User response:Review the error details. Check file permissions.Attempt to copy the source URI to the desitnation URImanually to see what error occurs.

GYMDC10419W

error_description uri Failed todelete

Explanation:An error occured during an attempt to delete a file

User response:Review the error details. Check file permissions.Attempt to delete the source URI manually to seewhat error occurs.

GYMDC10420W

error_description destination_URIsource_URI Failed to link

Explanation:An error occured during an attempt to link one URI toanother

User response:Review the error details. Check file permissions.Attempt to link the URIs manually to see what erroroccurs.

GYMDC10421W

error_description destination_URIsource_URI Failed to move

Explanation:

Chapter 6. Messages 95

An error occured during an attempt to move a file

User response:Review the error details. Check file permissions.Attempt to move (rename) the source URI to thedesitnation URI manually to see what error occurs.

GYMDC10422W

error_message souce_code_uri URI:

Explanation:A syntax error was detecting while compilingECMAScript code.

User response:Check the syntax in the indicated file and correct it.

GYMDC10423W

URI Failed to retrieve file size:

Explanation:Unable to retrieve the file size of a URI

User response:Check file permissions. Attempt to check fileinformation for a URI using ls command.

GYMDC10424W

destination_size destination_URIsource_size source_URI Copied filesize does not match source(source:

Explanation:After a copy the file sizes do not match

User response:Manually copy the source URI to some desintation onthe same partition and/or different partition as thedestination to see if they are the same file size.

GYMDC10425W

uri_list Failed to copy file, givingup (

Explanation:Retried too many times to copy a file

User response:Check file permissions. Review the error detailsAttempt to manually copy a URI to see what erroroccurs.

GYMDC10426W

error detail formula resourcerequest Build error on request:

Explanation:An error has occurred during the tree build

User response:Contact technical support

GYMDC10427W

Explanation:Bad input: can't resolve <input kind> tsId: <id> from:<db row>

User response:Contact technical support

GYMDC10428W

input time series time seriessequence number No argumentwith s/n

Explanation:When attempting to update a formula input, noargument with the indicated sequence number wasfound.

User response:Contact technical support

GYMDC10429W

row time_series No complexformula for:

Explanation:No complex formula for: <id>

User response:Contact technical support

GYMDC10430W

tupleContainer timestamp Metricswith timestamps starting at

Explanation:Metrics have already been received for this time.Duplicate data will be ignored.

User response:If the tuple container is from a collector, check if thatcollector is actually producing duplicate data by usingbofDump on the output files that it produces

GYMDC10431W

label Data from label

Explanation:Data from label <label> is not used here

User response:Contact technical support

GYMDC10432W

error description Failed to writeBOF file because of

Explanation:Failed to write tuples to disk.

User response:Double check disk space and permissions.

GYMDC10433F error_description row Errorbuilding time series from:

Explanation:Error building time series from: {db row}, reason: {areson}

User response:Contact Proviso support

GYMDC10434F error_description row Errorbuilding input from:

Explanation:

96 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Error building input from: {db row}, reason: {a reson}

User response:Contact Proviso support

GYMDC10435W

error description record Errorprocessing record

Explanation:An error occurred while processing a record.

User response:Take steps to correct the problem based on theinformation given in the error description.

GYMDC10437W

time_series No formula for:

Explanation:RCM cannot locate the formula for a timeseries

User response:Check plan consistency and that formula exists fortimeseries

GYMDC10439W

Problem contacting tuple storage,will retry every 60 seconds.

Explanation:RCM cannot contact tuple storage

User response:Check connectivity between RCM and CMEs

GYMDC10440W

error description Error runningtuple query (will retry in 60seconds):

Explanation:The recomputation engine has a problem queryingother components or the database.

User response:Ensure all CMEs, FTEs and the database are running.

GYMDC10441W

A timeout occured while fetchingthe results of a tuple query. Thequery will be retried.

Explanation:A timeout occurred while querying tuples.

User response:Contact technical support

GYMDC10442W

reason label Remote query of label

Explanation:An attempt to query a remote process for data failed.

User response:Ensure all components are running.

GYMDC10443W

Explanation:

A file needs to be partially reprocessed after a restartof the UBA in order to finish processing the file.

User response:No action is necessary.

GYMDC10444W

operator schedule modifier Failedto apply repeat modifier

Explanation:The system failed to interpret the repeat modifierspecified in a formula or in a subelement property.

User response:Check the subelement property used for the repeatmodifier and make sure the correct syntax was used.Also verify that the calendar used in the formula iscompatible with the property.

GYMDC10445W

time_series modifier Failed toapply timezone repeat modifier

Explanation:Failed to apply a timezone modifier based on asubelement property.

User response:Check subelement property value used for thetimezone modifier.

GYMDC10446W

operator calendar name Invalidcalendar/duration:

Explanation:An invalid reference to a calendar or duration wasencountered in a formula.

User response:Double check the calendar name or duration specifiedin the formula and make sure it is defined using theDataMart calendar manager.

GYMDC10447W

timestamp name

Explanation:An aggregator in a UBA failed to recover its state fromdisk.

User response:Check for data loss and determine whether someonemay have inadvertently manipulated the UBA's statefiles.

GYMDC10448W

timestamp timestamp name

Explanation:An aggregator in a UBA failed to recover its state fromdisk. The UBA will attempt to use older aggregatorstate instead.

User response:Check for data loss and determine whether someonemay have inadvertently manipulated the UBA's statefiles.

Chapter 6. Messages 97

GYMDC10501W

Explanation:The definition for the profile cannot be found in thedatabase. Current execution is aborted

User response:Refresh or bounce the GUI, to resync the content

GYMDC10502W

Explanation:The file inventory_element.txt is missing for executingthe profile

User response:Check suggested path, and add corresponding file tothat location

GYMDC10503W

Explanation:The file inventory_subelement.txt is missing forexecuting the profile

User response:Check suggested path, and add corresponding file tothat location

GYMDC10504W

Explanation:A formula specified in files inventory_element.txt orinventory_subelement.txt is unknown in the database

User response:Check database and file for formula spelling

GYMDC10505W

Explanation:One of the configuration parameter for the profile hasan invalid value

User response:Contact technical support

GYMDC10506W

probe componentName CNSreturned incomplete list of targetsfor:

Explanation:All component names were not found when lookingthem up in CNS

User response:Check that all components are running

GYMDC10507W

id Invalid id:

Explanation:

Inconsistent data was found while serializing ordeserializing timeseries and input data

User response:Check that the formula and resource for this input bothexist in the database

GYMDC10508W

tuple error description operatorname

Explanation:An error occurred while trying to process an outgoingtuple.

User response:Check for an iFix to the tech pack running on this UBAthat corrects this issue.

GYMDC10509W

probe errorDescription Error

Explanation:An error occurred while trying to execute a monitoringprobe

User response:Check script and review error message

GYMDC10510W

Explanation:One input file, specified by the profile is missing

User response:Check the file name and path, either fix the profile ofthe file name

GYMDC10511W

Explanation:The file inventory_element.txt is missing for executingthe profile

User response:Check suggested path, and add corresponding file tothat location

GYMDC10512W

Explanation:The file inventory_subelement.txt is missing forexecuting the profile

User response:Check suggested path, and add corresponding file tothat location

GYMDC10519W

ipAddress tag

Explanation:This IP address is out of range, or has been explicitelyexcluded within the profile

98 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

User response:No action required

GYMDC10520W

errorDescription tag

Explanation:The ping sweep did not execute properly on thecollector machine

User response:Check qPing files permissions on the collectormachine

GYMDC10521W

finalList count tag

Explanation:A subset of IP address(es) has been forced on thecommand line used to start the discovery. The set ofIP address(es) the inventory is going to work on is theintersection between the set defined by the profile(mode 1 or 2), and the forced set. This filter usuallytakes place during partial re-discovery triggerred byinvariant change detection mechanism.

User response:No action required

GYMDC10522W

errorDescription tag IP DISC didnot execute properly on thecollector machine:

Explanation:An error occured when the IP DISC did not executeproperly on the collector machine

User response:Check configuration

GYMDC10549W

ipAddresses tag

Explanation:This is a warning message about IP addresses thathave not been discovered

User response:Check snmp configuration and connectivity

GYMDC10559W

element element invariant tag

Explanation:An element with the same characteristics has alreadybeen discovered during this execution. The twoelements have been identified as true duplicate, andsecond instance is ignored

User response:No action required

GYMDC10579W

errorDescription tag

Explanation:

A network related error has occurred

User response:Contact technical support

GYMDC10590W

Explanation:Ther was an error when trying to write to a file.

User response:Check the disk utilization and the process' permissionsto access this file and directory.

GYMDC10591W

Explanation:A retriable database error occurred

User response:This message should go away after it retries. If it doesnot, contact technical support.

GYMDC10592W

additionalInfo errorDescriptionsqlStatement Statement (

Explanation:Bulk database insert or update failed

User response:Review the error description and the additionalinformation

GYMDC10593I

GYMDC10594W

errorDescription domainManagerInitial load for

Explanation:Loading initial metadata from database failed. Willretry.

User response:If message persists, check that database is workingproperly and check connectivity

GYMDC10600W

Explanation:Re-Inventory request failed

User response:Check connectivity, system status

GYMDC10601W

error details application nameFailed to register

Explanation:Registering application version failed with an error

User response:Check connectivity and check database status

GYMDC10602W

maxRetries profileName ipAddressFailed to run inventory for:

Chapter 6. Messages 99

Explanation:Re-Inventory request failed

User response:Check inventory command line in log file, dc.cdf,priviliges of datachannel user

GYMDC10603W

line Unexpected line in stored QCFdata:

Explanation:Bad data was encountered in the QCIF state journalfiles.

User response:Inspect files and/or run full 5620 dump and verify theintegrity of the file system used to store QCIF's state.

GYMDC10604W

formula name Relation

Explanation:Relation specified in design file is not defined in thesystem

User response:Check design file for proper relation name or addrelation description (entry in FRML_DESC)

GYMDC10605W

property name Property

Explanation:Property specified in 5620 design file is not defined inthe system.

User response:Check design file for proper property name or addproperty description (entry in FRML_DESC).

GYMDC10606W

error_description Flush aborteddue to

Explanation:A serious error occurred while saving data in thedatabase. Flush aborted

User response:Check database connectivity or contact technicalsupport

GYMDC10607W

processName errorDescription5620 Error:

Explanation:A Corba exception was triggered on message send to5620

User response:Alert operator of potential problem with the primarydevice

GYMDC10608W

processName errorDescriptionqc_server Connection to

Explanation:Attemp to connect to device failed

User response:Alert operator of potential problem with one of the5620 devices

GYMDC10609W

qc_server Switching from

Explanation:Switching from specified device to the backup devicehas started

User response:No action required

GYMDC10610W

errorDescription eventChannelIORFailed to reuse stored eventchannel reference:

Explanation:Attempt to reuse stored QC event channel referencefailed

User response:No action required. Application will create a new eventchannel automatically

GYMDC10611W

Successfully reused storedsession reference

Explanation:Attempt to reuse stored QC session reference failed

User response:No action required. Application will create a newsession automatically.

GYMDC10612W

5620 is out of sync, some eventshave been lost!

Explanation:Event buffer on 5620 has been flushed, queued eventsare lost

User response:Consider running manual full dump to resync

GYMDC10613W

Element is not specified for

Explanation:An element is not specified for a subelement.Subelement will be skipped

User response:No action required

GYMDC10614W

anOid Object with oid

Explanation:An error occurred during the QC getAttributes call

User response:No action required

GYMDC10615W

reason file_name Error readingevents journal file

100 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Explanation:An error occurred while reading the events journal file

User response:No action required

GYMDC10616F

GYMDC10617W

errorDescription anObject Erroradapting object

Explanation:An error occurred while adapting an object

User response:Check script and refer to error description in themessage

GYMDC10618W

Device is unavailable (Failed toresolve QCF_System orQC_network)

Explanation:QCF device is unavailable

User response:Check that QCF device available and reachable

GYMDC10619W

reason

Explanation:A problem was encountered while attempting aprimary device switchover

User response:Check primary device to make sure it is available

GYMDC10620W

oid Failed to refetch object orevent at

Explanation:Unable to refetch object or event with oid

User response:Check that object with oid exists

GYMDC10621W

object errorDescription Error

Explanation:An error occurred while processing object

User response:Review message for error details

GYMDC10622W

object id Auto-inserted missingnode at

Explanation:QCIF auto created a missing node in the path of a5620 object identifier.

User response:Force a full inventory dump.

GYMDC10623W

port host dbEnvironment Switchingfrom database:

Explanation:Switching from specified device to the backup devicestarted

User response:No action required

GYMDC10624W

errorDescription filename Errorloading

Explanation:An error occurred while trying to load a script file

User response:Check script file

GYMDC10625W

anOid Oid

Explanation:An error occurred during the QC getAttributes call

User response:No action required

GYMDC10626W

oid Failed to set attributes for oid:

Explanation:Error during QC getAttributes call

User response:No action required

GYMDC10628W

Explanation:The directory defined in the dynamic library path ismissing

User response:Remove the missing directory from the dynamic librarypath

GYMDC10629W

Explanation:RCM cannot locate the timeseries id for arecomputation action

User response:Check plan consistency

GYMDC10630

GYMDC10631W

Explanation:RCM has received a bad recomputation record

User response:Check input data to make sure RCM is fedrecomputation records only

Chapter 6. Messages 101

GYMDC10632W

Explanation:RCM has received a duplicate recomputation record

User response:Check input data to make sure RCM is not fed anyduplicate recomputation records

GYMDC10633 error description uri Failed todelete file:

Explanation:Failed to delete SAM export file.

User response:Check that the process has proper permission todelete the indicated file.

GYMDC10634W

relation name Relation

Explanation:A UBA script tried to create a relation for which therelation name is not defined.

User response:Reinstall the tech pack

GYMDC10635W

5620 Error: Failed to senduserName

Explanation:An error occurred while getting userName

User response:Alert operator of potential problem with the primarydevice

GYMDC10636W

property name Property

Explanation:Property refers to non-existent formula

User response:Check property in database

GYMDC10637W

errorDescription databaseConnection to

Explanation:An exception occurred while attempting to login toInformix

User response:Check that Informix is available

GYMDC10638W

subelementName Owning elementnot specifed for subelement

Explanation:No owning element specified for subelement

User response:Review script

GYMDC10639W

resource relationFormula Norelation member is specified forrelation:

Explanation:No relation member was specified for relation /resources

User response:Review script

GYMDC10640W

subeleement2 subelement1relationFormula No relation indexis specified for relation

Explanation:No relation index was specified for relation / member

User response:Review script

GYMDC10641W

relation subelementName Nosubelement named

Explanation:No subelement was found for relation

User response:Review script

GYMDC10642W

Explanation:An inventory object that the UBA is being requested tocreate has a conflict with another inventory objectalready present in the system.

User response:Make sure the UBA is processing data for the mostcurrent inventory in the database that is assigned to itscollector number.

GYMDC10643W

current seconds resync secondsResync time (

Explanation:The timestamp on a record is earlier than the currentprocessing time of the UBA. Records should beemitted in timestamp order by the tech pack.

User response:Double check the validity of data being fed into theUBA and investigate a possible tech pack bug.

GYMDC10644W

Failed to connect to SAM service.

Explanation:Unable to connect to SAM service

User response:Check primary SAM service availability

GYMDC10645W

errorDescription Error connectingto event channel:

102 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Explanation:An error was encounterd while trying to connect to theQCF event channel

User response:Check that QCF device available and reachable

GYMDC10646W

errorDescription event Errorprocessing event

Explanation:An error occurred while processing an event

User response:Review message for error details

GYMDC10647W

Check for primary SAM serveravailability

Explanation:Reconnecting to primary SAM server

User response:Check for primary SAM server availability

GYMDC10648W

errorDescription object Errorwriting id map entry for

Explanation:An internal error occurred that caused the idmapentries not to be written

User response:Check file permissions. Contact techical support

GYMDC10649W

Check for primary cwm serveravailability

Explanation:A problem was encountered. Attempting a primarydevice switchover

User response:Check primary device to make sure it is available

GYMDC10650W

error detail

Explanation:Attempt to purge files in done directory failed

User response:Check file permissions and user privileges

GYMDC10651W

Successfully switched back toprimary cwm server

Explanation:A problem was encountered with the primary device.Successfully switched back to primary cwm server.

User response:No action required

GYMDC10652W

Successfully switched back toprimary SAM server

Explanation:

Switched back to primary SAM server

User response:No action required

GYMDC10653W

uri Switching from SAM SOAPservice:

Explanation:About to switch from primary SAM SOAP server toalternate service

User response:Check primary SAM SOAP server availability

GYMDC10654W

Domain model is not configured inecmascript environment

Explanation:The domain model is not configured in the ecmascriptenvironment

User response:Contact technical support

GYMDC10702W

collector profile Fail over profile

Explanation:A fail over has been initiated

User response:Investigate cause of failover

GYMDC10703W

list profile Profile

Explanation:A fail over required but there is no available colletor tofail over to

User response:Investigate cause of failovers and review configurationand log message

GYMDC10704W

limit percent stat_name collectorCollector

Explanation:Collector is not suitable for failover because a statisticis over the theshold

User response:Check network connectivity and CPU utilization

GYMDC10705W

errorDescription port host Lostconnection to collector

Explanation:Connection to the collector was lost

User response:Check connectivity and that collector is still running

GYMDC10706W

list Redundant collectorsdetected:

Explanation:

Chapter 6. Messages 103

Redundant collectors were detected

User response:Check that GRACE_PERIOD configuration setting islonger than your current collector startup time

GYMDC10707W

collector Collector

Explanation:Collector is not in HA mode

User response:Check that collector is configured to be in HA mode

GYMDC10708W

collector Unable to communicatewith collector

Explanation:Unable to communicate with collector

User response:Check network connectivity and check that collector isrunning

GYMDC10709W

message error_description clientClient

Explanation:Encountered an error when sending message tocollector

User response:Check network connectivity

GYMDC10710W

relation_id Missing relationformula with id

Explanation:Relation refers to a non-existent formula

User response:Check that relation refers to a formula that exists. If itdoes, contact technical support.

GYMDC10711W

resyncAction relationFormulasubelementId Missing endpointsubelement with id

Explanation:Relation refers to a non-existent subelement

User response:Check that relation refers to existing subelements. If itdoes, contact technical support.

GYMDC10712W

file name schema name Unknownschema:

Explanation:An input descriptor was encountered that isassociated with an unknown input schema. The inputdescriptor will be ignored and discarded.

User response:If the file needs to be processed, it may be necessaryto re-stage the file in the input directory, otherwise no

action is necessary and the warning was likely due torenaming an input schema.

GYMDC10751I list count Issuing probe #

GYMDC10752I list Results per collector:

GYMDC10753I results Results per profile:

GYMDC10754I collector profile Starting profile

GYMDC10755I profile collector Stopping collector

GYMDC10756I duration collector profilePreloading configuration

GYMDC10757I collector duration Extendingtimeout by

GYMDC10758I collector Disabling expiration forcollector

GYMDC10759I profile collector Re-registeringcollector

GYMDC10760I profile collector Pausing collector

GYMDC10800W

y x Received trap number

Explanation:Received trap out of sequence

User response:No action required

GYMDC10801W

y x n Unable to recover

Explanation:Received trap out of sequence on recovery

User response:No action required

GYMDC10802W

port host Failed to get sysUpTimefrom RTM Service Agent at

Explanation:Failed to get sysUpTime from RTM Service Agent

User response:Check communications, RTM server

GYMDC10803F

GYMDC10804F Both RTM event channels cannotuse the same local port.

GYMDC10805F

GYMDC10806F

GYMDC10807W

endpointDbKey Invalid deleteenpoint:

Explanation:Ignoring delete of an enpoint

User response:Check resources should be loaded in memory

104 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

GYMDC10808W

errorDescription trap Errorprocessing trap

Explanation:Handling PDU failed

User response:Contact technical support

GYMDC10809W

errorDescription port host Errorrenewing registration with serviceagent

Explanation:An error occured while renewing registration

User response:No action required

GYMDC10810 dbKey No endpoint found for key:

Explanation:No endpoint was found for key

User response:Check endpoint exists in database

GYMDC10811W

subelement_date subelement dateObsolete date

Explanation:An obsolete date was encountered while writing outinventory. Subelement will be skipped

User response:No action required

GYMDC10812W

pdu errorDescription Trapprocessing error:

Explanation:An error was encountered while processing a trap

User response:Review message for error information

GYMDC10850I port host Registering with RTMService Agent at

GYMDC10851I port host Unregistering with RTMService Agent at

GYMDC10852 port host Renewing registrationwith RTM Service Agent at

GYMDC10853 trap pdu Received trap

GYMDC10854I port host Starting resync with RTMService Agent at

GYMDC10855I port host trapnumber Recoveredtrap number

GYMDC10856 pdu Received response:

GYMDC10857I port Starting SNMP listener on port

GYMDC10858I Starting RTM registration renewaljob

GYMDC10859I Stopping RTM registration renewaljob

GYMDC10860I port Stopping SNMP listener onport

GYMDC10861I username database Starting Glorpsession for database

GYMDC10862I Successfully connected to cwmtrap server

GYMDC10863I last trap number trap numberIncoming RTM trap number (

GYMDC10864 port host Registration renewedwith RTM Service Agent at

GYMDC10865W

port host Failed to renewregistration with RTM ServiceAgent at

Explanation:Unable to renew registration with RTM Service Agent

User response:Check registration configuration

GYMDC10866W

reason Unable to connect to cwmtrap server because:

Explanation:Unable to connect to CWM trap server

User response:Check that trap server is available and thatconfiguration is valid

GYMDC10900W

value key Failed to convert:

Explanation:Failed to convert key value pair from configuration

User response:Check configuration

GYMDC10901W

error detail Error:

Explanation:An error has occurred during the linking of formuladependencies

User response:Contact technical support

GYMDC10902 error description Bad PDU received

Explanation:A bad PDU was received.

User response:Verify the correct operation of other systems withwhich the affected component is communicating.

GYMDC10903W

errorDescription Error locating andloading Mibs :

Chapter 6. Messages 105

Explanation:An error was encountered while locating and lodingMibs

User response:Check mibs location and review this error message

GYMDC10904W

errorDescription A command erroroccurred:

Explanation:A request failed

User response:Contact technical support

GYMDC10905W

object_type object_name Failed toadapt

Explanation:There was an error in trying to emit either an elementor a subelement created by a tech pack.

User response:Verify that the input data is correct. Contact yoursystem administrator or technical support if the inputdata looks correct and you are unable to resolve theissue.

GYMDC11016W

file name Attempt to inject tuples,but one or more files is missing orin the wrong location:

Explanation:An attempt was made to inject tuples with a tuplecontainer that has missing or invalid files.

User response:Contact your Proviso system administrator.

GYMDC11017W

error_description time label Failedto acquire tuples (label:

Explanation:Failed to acquire files from an up stream component.

User response:Double check that the process can access the outputdirectory of the up stream component over the filesystem, ftp or stfp (depending on the systemconfiguration).

GYMDC11018W

node_name Name server (CNS)lookup failed for node

Explanation:An attempt to lookup a tuple communications nodefailed.

User response:Make sure the CNS, FTEs and CMEs are running.

GYMDC11019W

error_description node_name Acommuncations error occurredwith node

Explanation:

An attempt to communicate with a tuple node failed.

User response:Make sure the FTEs and CMEs are running and checktheir logs for any warning or fatal messages.

GYMDC12347W

symbol Error inFormulaOperator>>update:with:as a result of responding to

Explanation:An error occured while handling internal eventnotification

User response:Contact technical support

GYMDC12349W

arguments size inputs Something iswrong with inputs:

Explanation:Something is wrong with the number of inputsbecause it does not match what was expected basedon the formula

User response:Check the formula arguments to make sure they arevalid properties/formulas/calendars

GYMDC12350W

argument operator id Operator

Explanation:The formula specifies an argument but there is noinput for that argument which means the subelementcould be missing an expected relation, property orcalendar

User response:Check that the necessary relations, properties andcalendars exist

GYMDC12351W

formula operator id argument Can'tbuild input for argument

Explanation:Unable to build input because argument formula ismissing

User response:Check to see if argument formula was deletedmanually

GYMDC12352W

error label Failed while contactingthe plan builder to see if a resyncis required for

Explanation:CME has failed to contact the PBL to see if there areplan changes within the current hour. CME contactingPBL is an optimization. Since it failed, CME will simplydo a database resync of plan changes for the currenthour.

User response:Check PBL and make sure it is running well

106 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

GYMDC12356W

Explanation:Pending xlog commands are replayed on restart tocomplete transactions. A failure occured during thisreplay

User response:Review the error description and ensure necessaryresources like the database are available. Contactsupport

GYMDC12357W

metric description problemdescription

Explanation:An attempt was made to create a metric with invalidstate.

User response:Verify the data being fed to the UBA for accuracy andcheck the tech pack script for bugs.

GYMDC12358W

Unable to produce a recordbecause there is no adaptor toprocess it

Explanation:There is no adaptor to handle metric records that areemitted by the script.

User response:Double check the UBA settings and the script. Makesure the correct version of the tech pack script isconfigured. Check for any iFixes for the tech pack thatwould correct the issue.

GYMDC12360W

error description Failed whilecontacting the plan builder:

Explanation:The UBA failed to contact the plan builder while tryingto inform it about unexpected metrics that it is seeing.

User response:Check network connectivity and make sure thechannel management components are running.

GYMDL39001W

seconds tag

Explanation:A profile is not progressing and will be aborted

User response:Check profile

GYMDL39002 problem description Full inventorydump is being retried due to thefollowing reason:

Explanation:A full dump of inventory objects had an error and isbeing retried.

User response:Initiate another full dump.

GYMDL39201 error_msg record_number Record #

Explanation:An error was encountered during record processing.The specific error is reported in the log message. Thismessage does not necessarily indicate a problem.

User response:Investigate the reason for the error to determinewhether or not it's a normal condition or a legitimateproblem.

GYMDL39205W

string Unknown timezone:

Explanation:The configured timezone could not be found in thezoneinfo (tz) database.

User response:Double check the TIMEZONE configuration setting andverify that it is in the zoneinfo (tz) database on the hostwhere the UBA is running and change theconfiguration as necessary.

GYMDL39206W

license_name License(

Explanation:The shared library that the UBA uses for ODBCconnectivity does not have correct OEM licensinginformation.

User response:Contact technical support.

GYMDL39207 timezone_used timezone_requestedTimezone requested:

GYMDL39208W

No Adaptors deployed

Explanation:No adaptors were specified in the design file (or nodesign file was found).

User response:Double check DESIGNFILE and INSTANCES settings inthe configuration file.

GYMDC39209W

Processing paused because outputat maximum

Explanation:The output directory or tuple storage queue containsmore than the maximum allowed number of hours ofdata waiting to be picked up by a downstreamcomponent

User response:Start downstream component(s)

Chapter 6. Messages 107

GYMDL39209W

file name No availability filesfound for metric file

Explanation:The BLB failed to find any availability metric files fromthe CWMIF that correspond with the other metric filescoming from the input URI.

User response:Check the status of the CWMIF and make sure it isrunning. Check the logs for CWMIF warnings or fatalmessages and take the corrective action suggested forthose messages.

GYMDL39210W

uri schema name Late input:

Explanation:No input files have been found at the indicated URI fora significant period of time (configurable via theLATELIMITSECONDS setting).

User response:Double check the input URI settings for the UBA andmake sure the UBA process can access the file system,ftp server or sftp server indicated by the URI (be sureto check using the same unix user id that the UBAprocess runs under).

GYMDC39211I Processing unpaused because nolonger at max output

GYMDL39211W

file name No availability filesfound for metric file

Explanation:The BLB failed to find any availability metric files fromthe QCIF that correspond with the other metric filescoming from the input URI.

User response:Check the status of the QCIF and make sure it isrunning. Check the logs for QCIF warnings or fatalmessages and take the corrective action suggested forthose messages.

GYMDC39212W

timestamp uri schema name Inputhas timestamp in future:

Explanation:An input has a timestamp from the future relative tothe current system time (in UTC). The UBA will notprocess an input whose timestamp is in the futureuntil the system clock catches up with that input'stimestamp.

User response:Make sure "date -u" reports the correct UTC time andmake sure the timestamps on the files being fed to theUBA are in UTC.

GYMDL39212W

bytes bytes uri File size is too smallfor uri:

Explanation:The size of the acquired file is smaller than theconfigured limit and will not be processed.

User response:Check that the MINFILESIZE configuration setting isset appropriately then check the system that producesthe data for the UBA for problems.

GYMDL39213W

error description

Explanation:An unexpected error occured while processing aninput.

User response:No specific advise is available.

GYMDL39214W

file name Input file

Explanation:An input descriptor for the given input file name wasnot found in the input descriptor repository. As aconsequence, the indicated file will not be processed.Since the data file will not be processed, data loss willlikely result.

User response:Try and identify how the descriptor repository mayhave been deleted or corrupted and take steps toprevent it from happening in the future.

GYMDL39215W

file name Alcatel MR file

Explanation:A file expected to be located in the do directory ismissing. The input descriptor for the file will bedeleted and the file will not be processed.

User response:Determine why the file in the do directory was deletedand take steps to ensure it does not happen again inthe future. If the file needs to be processed, findanother copy of the file and re-stage it in the inputdirectory.

GYMDL39217W

message uri There was an errorcommunicating with the SAMinterface

Explanation:An error occurred in the SAM JMS communicationprotocol

User response:Contact technical support

GYMDL39218 process id The SAM JMScommunication process hasstarted (pid:

Explanation:

108 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

The SAM JMS communication process has stopped.

User response:No action required.

GYMDL39219 process id The SAM JMScommunication process hasstopped (pid:

Explanation:The SAM JMS communication process has stopped.

User response:No action required.

GYMDL39220W

process id The SAM JMScommunication process is hung(pid:

Explanation:A request to stop the JMS process has been issued,but the process is still running

User response:Contact technical support.

GYMDL39221W

problem description Full inventorydump was unable to complete dueto the following reason:

Explanation:A full dump of inventory objects was interrupted.

User response:Initiate another full dump.

GYMDL39222I The SAM JMS connection has beenestablished (a keep-alive messagewas received)

Explanation:The SAM JMS connection has been established.

User response:No action required.

GYMDL39223W

The SAM JMS connection is stale,the JMS process will be restarted.

Explanation:The SAM JMS keep-alive timeout has been exceeded,the JMS process will be restarted.

User response:Check SAM server availability.

GYMDL39224W

errorDescription Error processingJMS event:

Explanation:An error occurred while processing a JMS event.

User response:Contact the system administrator.

GYMDL39225W

file_name Error parsing

Explanation:There was an error while trying to parse a CWM bulkstatistics file.

User response:Use the CWM statsreader utility to analyze the file andcheck for problems.

GYMDL39226W

child description Unable to createchild/parent relationship for::

Explanation:A parent and child have the same id which is notallowed

User response:Correct invalid group to group entries

GYMDL39801 Starting Inventory transfer andsynchronization

GYMDL39802 code Inventory transfer andsynchronization completed withstatus code=

GYMDL39805 URI schema Start processinginput:

Explanation:The adaptor is starting to process the named file

User response:None. If this message does not occur it can be anindicator that a file was not present, or that the fileglob configuration did not find a matching file

GYMDL39806 uri input_name Completedprocessing input:

Explanation:The adaptor completed processing of the named input

User response:If records were rejected, this could indicate amalformed file, file with missing fields (specified in anobject adaptor and with no "default value" or problemwith adaptor configuration

GYMDL39807 acquired_count ignored_countfound_count time schema Scannedinput:

Explanation:The UBA scanned remote URIs for an input and foundn1, n2 were ignored by parseRemoteURI and n3 werealready present in the do or done directory

GYMDL39809I URI Ignoring input - error parsingURI for timestamp info:

GYMDL39810I acceptable_count saw_count hourAn incorrect number of files wasprocessed for hour

Chapter 6. Messages 109

GYMDL39811W

timestamp limit The threshold forinput files containing record errors(

Explanation:The number of files allowed to have one or morerecord processing errors in a given hour has beenexceeded. The limit is configured with theERRORFILELIMIT setting.

User response:Check the system that is feeding data into the UBA anddouble check that the ERRORFILELIMIT setting isn'tset too low.

GYMDL39812W

uri error description Unable toretrieve a list of URIs for

Explanation:An error occured while the UBA was attempting toretrieve a list of files for the indicated input URI.

User response:Double check the input URI setting and verify that thefile, ftp or sftp server is running and configuredcorrectly. Attempt to connect to the file, ftp or sftpserver by hand from the same host and userid as theUBA. Verify that the directory indicated in the inputURI exists.

GYMDL42000 timeslot SAM metric export isabout to be issued for timeslot:

Explanation:A SOAP request for SAM to export metric data is aboutto be issued.

User response:No action required.

GYMDL42001 timeslot SAM metric export hasbeen requested for time slot:

Explanation:An export request has been sent to SAM.

User response:No action required.

GYMDL42002W

detailed_error_msg timeslot SAMmetric export request failed fortimeslot:

Explanation:A SOAP request for SAM to export metric data hasfailed. This can be caused by temporary loss ofconnectivity with SAM.

User response:If this message persists, check connectivity with the5620 SAM system.

DataLoad error messagesDescribes reference format error messages produced by DataLoad. Whenever possible, explanations areoffered, as well as remedial actions.

GYMDL30002F A time bomb function has fired,check previous error DL30138 fordetails. The process will exit, andbe restarted by the watchdogprocess.

Explanation

Some operations are required to complete within agiven time frame. This message indicates that aparticular operation didn't complete within thehardcoded maximum time.

System action

The process will exit, and be restarted automaticallyby it's watchdog process.

Programmer response

If the issue repeats itself, this could be related to adatabase problem, with a SQL query that never ends.Look for specific error or trace files for the SQL client.

GYMDL30004F Start command failed.

Explanation

The attempt to restart the pvmd process by thewatchdog has failed. Unless HAM is deployed, and hasswitched collections to a different host, collections forthat particular profile will NOT happen. This problemmust be fixed immediately.

User response

Search in the log for the previous information messagewith ID DL31088. This message will indicate thearguments used to attempt to restart the pvmdprocess. Inspect each of the arguments. Try thecommand on a shell, look for errors on the console, orin the log/pvmd.log, or log/pvmdmgr.log files.

Programmer response

The wrong arguments are in the start command line,unable to find path for binaries, or the dataloadenvironment is not present.

GYMDL30005F cmd Error: Unable to kill processwith command '

110 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Explanation

The watchdog is unable to terminate a failing pvmdprocess using the specified command. Either theprocess was already terminated by the time thewatchdog issues that command, or the process cannot be terminated because of permission issues.

User response

Check process list on the machine with ps. Try the killcommand from a shell, using same credentials as thewatchdog process.

GYMDL30006F SNMPv3 cryptography support cannot be loaded. Aborting.

Explanation

The configuration explicitly requires full SNMP v3support with encryption, but the cryptographic librarycan not be located or loaded.

System action

The process will exit, and all further attempts torestart the process without changing the configurationwill fail with the same error.

User response

Either install the cryptographic library, and make surethe library is in the standard search path, andaccessible for the current user, or edit the collectorconfiguration to allow startup of the process withoutthe cryptography library.

GYMDL30007F function Call to unimplementedcryptography function '

Explanation

The system is configured to use advanced encryption,but the OpenSSL library being used does notimplement the encryption type.

System action

The process will exit, and be restarted by thewatchdog process. Any further attempt to reuse thesame problematic encryption mechanism will causethe same error.

User response

Verify the correct version of the OpenSSL library is inthe library search path.

Programmer response

Check version and accessibility of the libcrypto.

GYMDL30100W

Fail to checkout new MIBs fromdatabase, using local cache forcollections.

Explanation

Database is not reachable, or is down at the time.Compiled MIB files are stored in the database, andcached on the collector file system. Updated MIB filesare downloaded at collector startup, and every time areload MIBs message is received.

User response

This is not a serious issue as long as MIB files are stillcached on the collector file system. Collector willcomplete downloading MIBs, once the databaseconnection is restored.

GYMDL30101W

reason Server is shutting downbecause of '

Explanation

The administrator user has issued the command:pvmdmgr stop. Otherwise an error occurred during thestartup phase of the collector.

System action

The pvmd process is stopping. All collections will stopon that host.

User response

Nothing to do if administrative command. Otherwise,check the reason field.

GYMDL30102W

time name pid Process #

Explanation

Process pvmd is down (crashed), or overloaded. Thewatchdog is monitoring the pvmd process, andexpects periodic heartbeat messages from thecollector. This error indicates an absence of heartbeatmessage for an extended period of time.

System action

The watchdog will terminate that instance of the pvmd(if still running), and start a new instance.

User response

Nothing to do. Verify that the new process is properlyrunning.

GYMDL30106W

mibfile name Unknown or missingstructure definition for type '

Chapter 6. Messages 111

Explanation

There was an error in the original source file for theMIB, or some dependencies were missing at the timeof the compilation.

User response

Re-compile the original MIB, check for and fix eventualerrors.

GYMDL30107W

err host Host '

Explanation

This error occurs when a SNMP session can not beinitialized with the specified target. The reason andinternal error code are printed. This is usually causedby incorrect SNMP V3 credentials.

User response

Check error description, check SNMP credentials.

GYMDL30108W

tnsentry login Unable to connect todatabase using '

Explanation

Incorrect user/password specified, incorrect databaseenvironment specified, or the listener is down on thedatabase server.

User response

Verify database user/password information. Verifydatabase environment configuration. Verify thedatabase listener is operating.

GYMDL30112W

msg

Explanation

The parsing or the execution of the formula failedbecause of an unrecognized token, an invalid numberof arguments for a function, or an unexpected value foran argument. The message indicates the exactlocation of the problem.

User response

If the error indicates a syntax error in the formula,correct the offending function or argument in theformula definition, and bounce the collector. If theerror indicates a runtime error with a particular valuefor an argument, and the error is occurring repetitively,check the formula logic, and if the value is a validinput, extend the formula to handle it. Then bouncethe collector.

GYMDL30113W

correctmib originalmib id FormulaID#

Explanation

There used to be an issue with the formula Editor, thatwould produce syntactically incorrect content for thedependent MIBs. Formulas saved at that time mayhave that problem.

System action

System will automatically convert the configuration toa valid entry and proceed.

User response

Edit, and save again the formula using the formulaeditor to regenerate the MIB attachments, and preventthe message to reappear.

GYMDL30114W

Collector is unable to reconnect todatabase.

Explanation

Database is down, listener process is down, networkbetween collector and database is down.

System action

Collector will make periodical attempts to reconnectto the database if the connection is interrupted.

User response

Check database status. Let the collector reconnect byitself when the database is available again.

GYMDL30115W

miblist oid Oid '

Explanation

A particular OID used in the formula expression hasnot been found in any of the Mibs associated with theformula. The formula can not be executed as is, andwill not produce any result.

User response

Check that the particular mib file is present in themibs/oid directory on the collector machine. Edit andsave the formula to force the formulaEditor toregenerate the list of associated Mibs.

Programmer response

Check if alm00206651 issue applies.

112 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

GYMDL30116W

filename Empty or missing MIB file'

Explanation

A Mib file, required by a formula is not found on thelocal filesystem. The formula can not be executed asis, and will not produce any result.

User response

Issue a confReload pvmMibs command, check if theMib file is copied. Try to recompile the source Mib file.

GYMDL30117W

duration port host fromto Socket

Explanation

There has been no traffic on a TCP connection to thecollector for a long time. Idle connections areautomatically stopped, and associated resources arefreed.

Programmer response

The duration is controlled by this configuration setting:TUNING.IDLESOCKETTIMEOUT

GYMDL30118W

message key Item #

Explanation

An inconsistency has been detected in the model. Thedetail is part of the message. Inconsistencies canoccur when several modifications are performed byvarious modules, and resync messages are notsystematically sent to the collectors following themodifications.

System action

The collector will perform a full reload, instead of anincremental reload, of the model in order to catchupwith all past changes, and retrieve a consistent model.

Programmer response

One type of inconsistency can be created by thegrouping tool, where subElements are marked assubelement.state='off', but are still part of a groupwith a relation content.state='on'.

GYMDL30119W

Unable to register current moduleversion in database.

Explanation

The collector failed to update it's version informationin the component version tables.

User response

Check SQL credentials used by the collector to accessthe database.

GYMDL30120W

lang NLS_LANG is not defined, andshould be set toNLS_LANG=AMERICAN_AMERICA.

Explanation

The environment variable NLS_LANG is used by thedatabase client to encode/decode string information.The configuration of the client must match the one ofthe database.

User response

Edit file dataLoad.env, and set NLS_LANG to therecommended value. Source the environment again,and bounce the collector.

GYMDL30121W

desc id state System overflow.Attempting to reactivate a

Explanation

The scheduler has detected that a periodic task is stillrunning from it's previous execution. In order to avoidoverload of the system, the current execution of thetask is cancelled.

System action

Collector will skip one execution of the task

User response

If the message is repeated throughout the day, this isa sign of a serious performance problem, where thecollector is overloaded. Load should be reduced, byeither splitting collections with another collector,removing some requests, or when possible optimizingcollection formulas.

Programmer response

See troubleshooting tips from http://w3.tap.ibm.com/w3ki/x/p9MJ

GYMDL30122W

msg

Explanation

An explicit error PDU has been returned by the SNMPagent, in place of the expected answer PDU.

Chapter 6. Messages 113

System action

The collector will correct it's configuration accordingly,and when possible reissue a valid PDU to the device.In that case there will be no data loss.

Programmer response

If message 'usmStatsNotInTimeWindows' is repeatedabundantly in the log, this could be a sign that severaldevices share the same SNMP V3 engine ID. This canbe investigated with the tool `dialogTest2SNMPV3CacheDump all`. Conflicting engine ID is aninvalid situation, and represent a performanceproblem for the collector.

Possible values are: Host '(host)', ERROR:usmStatsNotInTimeWindows, adjusting values usingdevice's parameters. Host '(host)', ERROR: returnedREPORT PDU with (something) Host '(host)', ERROR:returned empty REPORT PDU"; Host '(host)', ERROR :PDU too big, can't reduce size anymore (already (size))Host '(host)', ERROR : PDU too big, splitting by half ->(newsize)

GYMDL30128W

reqid calid calname Calendar '

Explanation

A request is deployed using a calendar that has nomore execution dates. The request will never beactivated.

User response

Inspect the calendar definition, and the purpose of therequest. either fix the calendar, or delete the request.

Programmer response

Collection calendars are not supported thru therequestEditor GUI. The only way to assign a collectioncalendar is thru resmgr. This feature will bedeprecated soon, and should not be recommended/deployed.

GYMDL30129W

entry Missing

Explanation

A mandatory configuration entry is missing, and thereis no acceptable default value.

User response

Check shell environment, source dataLoad.env isabsent, and bounce the collector. Check configurationentries using Topology Editor.

GYMDL30130W

key log error

Explanation

When a configuration error is found on an agent, thenall collections that have been already queued for thatagent and are using the exact same configurationparameters, are immediately aborted and will reportthe same failure.

User response

Check nature of failure. Adjust SNMP configuration, oragent's configuration.

GYMDL30131W

errmsg Select function error:

Explanation

This is an internal error of the SNMP listening thread.

User response

Contact IBM support if the error happens again after acollector restart.

GYMDL30132W

errortext version hostname Host '

Explanation

This is an internal error. A probe PDU for the versioncheck has not been sent properly. The version checkwill be limited or will fail.

User response

This error may happen while the collector is shuttingdown, and can be ignored in that situation.

GYMDL30133W

hostname Host '

Explanation

The collector failed to determine witch of SNMP V1 orV2c should be used for that target. Agent or device isdown, or community has changed and has not beenupdated in Proviso SNMP configuration table.

User response

Check device is alive with a ping (if supported by thedevice). Check SNMP community string. Checkpermissions on agent/firewall, for UDP traffic on port161, between the collector and the device.

GYMDL30134W

shortdescr id error Error:

114 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Explanation

The task has encountered an unexpected error andhas generated an exception.

System action

This task will be removed from the Scheduler in orderto avoid further errors.

User response

Check error message for probable cause.

GYMDL30135W

sql pvdescr pvcode oradescroracode Error ORA

Explanation

A SQL error has occurred.

User response

If the error is a connection problem, check databaseand access credentials. If error is a SQL order, checkdatabase logs for database related problems.

GYMDL30135W

sql pvdescr pvcode dbdescr sqlcodeError DB2

Explanation

A SQL error has occurred.

User response

If the error is a connection problem, check databaseand access credentials. If error is a SQL order, checkdatabase logs for database related problems.

GYMDL30136W

Database connection is down,model has only been partiallyretrieved from files.

Explanation

The model has been retrieved from saved files ratherthat from database.

Programmer response

This mode is only available as an explicit load optionfrom the command line, when -usedatabase no isused.

GYMDL30137W

Unable to Start, unknown Channelor Collector number.

Explanation

An order to start collection has been received, but theChannel and Collector number has not been specified.

System action

Start order will be ignored.

GYMDL30138W

modulename duration Failure toreset internal timeout since

Explanation

An operation that is required to complete in a giventime has reached it's timeout.

System action

Operation will be aborted.

GYMDL30139W

msgtype oid packetdumpSequencing error:

Explanation

A loop has been detected in a device's SNMPresponse. The same OID has been returned twiceduring the same table scan.

System action

Table scan is automatically aborted, to prevent infiniteloop situation.

User response

Per SNMP standard, table scan should never loop.Check vendor of SNMP device, check patches forSNMP device operating system.

GYMDL30140W

jobdecr errindex Agent error,invalid errorIndex=

Explanation

The SNMP response PDU does not contain a valid errorindex value, possibly due to a corrupted data packet.

System action

The first response variable will be used as the errorindex in an attempt to processes the packet.

GYMDL30142W

threshold One or severalbandwidth limitations are at ornear capacity (check list inprevious DL31020 messages). Thisis a likely cause for lostcollections, and current threadavail (

Chapter 6. Messages 115

Explanation

Collections may be lost because at least one collectionis consuming excessive bandwidth.

User response

If a specific target from the DL31020 messages isconsistently causing the excessive bandwidth,consider disabling the target.

GYMDL30143W

method deletion of a stillregistered job in

Explanation

An internal error has occurred within the collector.

User response

Contact IBM support.

Programmer response

Consult development as this message is disabled bydefault.

GYMDL30145W

msg Unable to invoke callbackwith:

Explanation

Unable to invoke callback because one or more keyparameters is null.

User response

If manually invoking a system command via the UI,check input values. Otherwise contact IBM support.

Programmer response

Investigate the system for possible configurationissues.

GYMDL30146W

phase Phase '

Explanation

The specified phase of the configuration dumpoperation has failed.

System action

The tool will continue to the next phase to try andprocess as much information as possible.

User response

Ensure the specified output directory is not in readonly mode and the output device is not out of space.

Also ensurethe database configuration is correct andthe database is active.

GYMDL30148W

oraerror function Call to '

Explanation

The database library can not be loaded, the librarydoes not contain an expected oci function, or thedatabase proxy is unreachable.

User response

Check the log for previous DL30150 or DL30213 errorsto determine the exact cause of the failure.

GYMDL30150W

Can't connect the oraProxy in thehost application (or oraProxy is notproperly initialized), attempting toload the Oracle library instead.

Explanation

The system is unable to contact the database proxy.Either the proxy is not available or is not configuredproperly.

System action

The system will attempt to load the database libraryinstead to directly query the database.

Programmer response

This may indicate a configuration and/or installationissue if not expected.

GYMDL30151W

function Call to '

Explanation

The specified function is not supported via thedatabase proxy.

User response

Ensure the command is started with the appropriateoptions. The -useOraProxy switch should be used todisable the use of the database proxy.

Programmer response

Ensure the system is configured and/or installedproperly as this may be an indicator of a configurationissue.

GYMDL30160W

filename Load failed. Library file '

116 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Explanation

The OpenSSL library filename specified in the messagewas not found via the standard library search path inthe environment.

User response

Ensure the OpenSSL library file is in the standardlibrary search path for the application, or update thesearch path toinclude the location of the file listed inthe message.

GYMDL30161W

prev current prev devnameRFC1213LIB, Non compliancedetected for device '

Explanation

The system detected a time difference of less than 1second between the current change value and the lastchange value with no other status change for thedevice. This could indicate a non-compliance device ora potential device failure.

System action

The system will continue after adjusting to use theprevious change time.

User response

If this message occurs regularly, but is not expected,the device should be investigated for potentialproblems.

GYMDL30162W

Configuration validation failed.

Explanation

At least one configuration entry is not valid. Check thelog for other messages providing more details as towhich entry is incorrect.

User response

If the configuration was recently edited, makecorrections based on the other messages in the logand rerun the previous command.

GYMDL30163W

Unable to Start, process iscurrently shutting down.

Explanation

The current process is already started, or is still in theprocess of shutting down.

User response

Verify the process is not already started. If recentlyrequested the process to stop, wait a short time beforeattempting to start the process.

GYMDL30164W

state Currently

Explanation

The process is in the specified state. It can not bestarted while in that state.

User response

If recently requested the process to stop, wait a fewmoments before attempting to start the process.

GYMDL30165W

Unable to Start with a differentconfiguration, use Stop first.

Explanation

Attempting to start with a different channel number orcollector number without stopping the existingprocess.

User response

Use the current channel number and collector numberto start the process, or stop the process first.

GYMDL30166W

Unable to Start, improperconfiguration, or invalid databaseconnection.

Explanation

Unable to start the process. Either the specifiedchannel and collector number are incorrect, or thedatabase connection is incorrect.

User response

Ensure the channel and collector number are valid.Also ensure the database is operational andconfigured properly.

GYMDL30167W

Unable to Stop, process is alreadyshutting down.

Explanation

The process is already being shutdown. Unable toissue a stop command at this time.

User response

Wait a few moments and verify the process hasstopped.

Chapter 6. Messages 117

GYMDL30168W

state Currently

Explanation

The process is in the specified state. It can not bestopped while in that state.

User response

If recently requested the process to start, wait a fewmoments before attempting to stop the process.

GYMDL30169W

Can't Stop from other that Readyor Running states.

Explanation

The process is not in a ready or running state. It canonly be stopped while in one of those two states.

GYMDL30170W

Unable to Load, unknown Channelor Collector number.

Explanation

Unable to load the configuration for the collectorbecause the channel or collector number is not knownby the system.

User response

Ensure the channel and collector number are valid.Attempt the load operation after any corrections aremade.

GYMDL30171W

Unable to Load, process iscurrently shutting down.

Explanation

The process is already being shutdown. Unable toissue a load command at this time.

User response

Wait a few moments and verify the process hasstopped. Then issue command to load theconfiguration.

GYMDL30172W

state Currently

Explanation

The process is in the specified state. Newconfiguration can not be loaded while in that state.

User response

If recently requested the process to stop, wait a fewmoments before attempting to load new configuration.

GYMDL30173W

Can't Load from Ready or Runningstate.

Explanation

The process is in a ready or running state. Newconfiguration can not be loaded while in one of thosetwo states.

User response

Try stopping the process before loading newconfiguration.

GYMDL30174W

Unable to Load, improperconfiguration, or invalid databaseconnection.

Explanation

Unable to load new configuration. Either the specifiedchannel and collector number are incorrect, or thedatabase connection is incorrect.

User response

Ensure the channel and collector number are valid.Also ensure the database is operational andconfigured properly.

GYMDL30175W

Unable to Pause, process iscurrently shutting down.

Explanation

The process is already being shutdown. Unable toissue a pause command at this time.

User response

Wait a few moments and verify the process hasstopped.

GYMDL30176W

Can't Pause from Idle or Readystate.

Explanation

The process already in an idle or ready state. Unable topause the process while in one of those two states.

GYMDL30177W

Database connection is down,model can not be retrieved.

Explanation

The model could not be retrieved from the database.

118 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

User response

Verify the database is operational.

GYMDL30178W

port invalid values forTUNING.SERVICEPORT=

Explanation

The service port must be between 1025 and 65535.

User response

Correct the service port value and try the commandagain.

GYMDL30179W

dir entry Entry '

Explanation

The directory configuration specified in the entry doesnot exist in the file system or is not a directory.

User response

Either create the directory specified, or update theconfiguration to a valid value.

GYMDL30180W

MissingDATAMANAGER.FILENAMINGVALIDITY,DATAMANAGER.HEARTBEAT_FREQUENCY orDATAMANAGER.TIME_GRANULARITY configuration.

Explanation

Some configuration settings related to BOF fileproduction are missing.

System action

Collector will fail initialization and quit.

User response

Use Topology Editor to configure the missingconfiguration entries.

GYMDL30181W

fnv hbfDATAMANAGER.HEARTBEAT_FREQUENCY (=

Explanation

Incompatible values have been detected betweenconfiguration settings.

System action

Collector will fail initialization and quit.

User response

Use Topology Editor to reconfigure the invalidconfiguration entries.

GYMDL30182W

hbf tgDATAMANAGER.TIME_GRANULARITY (=

Explanation

Incompatible values have been detected betweenconfiguration settings.

System action

Collector will fail initialization and quit.

User response

Use Topology Editor to reconfigure the invalidconfiguration entries.

GYMDL30183W

WATCHMGR.MANAGERPORT cannot be NULL

Explanation

An invalid value has been detected for the watchdogprocess management port. The port can not be empty.

System action

Collector will fail initialization and quit.

User response

Use Topology Editor to reconfigure the invalidconfiguration entries.

GYMDL30184W

collectornumber channelnumberinvalid values forTUNING.CHANNELNUMBER=

Explanation

Invalid values have been detected for collector andcollector's channel number.

System action

Collector will fail initialization and quit.

User response

Use Topology Editor to reconfigure the invalidconfiguration entries. Redeploy the collector files.Ensure that the local dataLoad.env has been updated.

Chapter 6. Messages 119

Programmer response

The local dataLoad.env contains theDL_CHANNEL_NUMBER andDL_COLLECTOR_NUMBER environment variable. TheDeployer does not refresh that file unless the 'upgrade'mode is selected. Usually the file has to be manuallyedited, even if the topology has been corrected.

GYMDL30185W

Configuration incomplete.

Explanation

Some configuration entry is missing or invalid. Usuallythe exact error is displayed in a precedent message.

System action

Collector will fail initialization and quit.

User response

Locate missing or invalid entry. Use Topology Editor toreconfigure the invalid configuration entries.

GYMDL30186W

msgtype oid oid packetdumpSequencing error:

Explanation

An OID out of order has been detected in a table scanresult. The SNMP protocol specifies that OIDs shouldbe returned in a strictly ascending order.

System action

The table scan will be aborted. The response set couldbe incomplete.

User response

Investigate with device's vendor if a patch is availableto correct this behavior.

Programmer response

Some devices like Huawei are known to return resultsin non strictly ascending order. If you can confirm thatthere is no risk of infinite loop, it is possible totemporarly reconfigure the collector to ignore out oforder OIDs, and proceed with the table scan. Set entrySNMP.CHECKMIBORDER to false.

GYMDL30189W

port host Can't create socket to

Explanation

Unable to resolve the IP address to the specified hostor unable to create a socket object.

User response

Verify the host is accurate. This information may beprovided via configuration or the command line. Alsocheck to verifyoperating system limits have not beenexceeded.

GYMDL30190W

reason port host Connect to

Explanation

Unable to establish a connection to the specified hostand port.

User response

Verify the port specified via configuration or thecommand line is correct.

Programmer response

It is possible the listener at the host and port is notactive. Verify all dependent processes are running.

GYMDL30191W

maxsize socket Socket

Explanation

The system is attempting to send data bigger than themaximum output buffer.

System action

The system will truncate the message to the maximumoutput buffer size and continue to send the message.

Programmer response

If this regularly occurs it could cause secondaryproblems where message data is incomplete.

GYMDL30192W

socket Socket

Explanation

Unable to send data to the target system because theremote buffer is full and the number of retries wasexhausted.

System action

The message will not be sent to the target system.

Programmer response

This could be an indication that the target process isoverloaded or unresponsive.

120 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

GYMDL30194W

field Error, empty '

Explanation

The specified field is not specified when doingdiscovery operations via qPing.

User response

Specify a value for the missing field and retry the qPingcommand.

GYMDL30195W

port host Can't contact pvmdprocess at

Explanation

Unable to establish a connection to the pvmd processrunning on the specified host and port.

User response

Verify the pvmd process is running. Verify the host andport are correct.

GYMDL30196W

host Can't resolve IP for hostname

Explanation

Unable to resolve the IP address for the specified host.

User response

Verify the host listed is correct and make anynecessary corrections.

GYMDL30197W

ip Incorrect address

Explanation

The specified IP address is not valid.

User response

Correct the IP address in the discovery configurationor specified on the command line when invoking qPing.

GYMDL30198W

command reason CreateProcessfailed. Reason:

Explanation

Unable to run the specified command for the providedreason.

User response

Verify the specified command is executable. Correctany issues listed by the reason listed in the message.

Programmer response

Verify the operating system resources are notexhausted. Some may be correctable by adjusting theoperating system configuration.

GYMDL30199W

cmd Unable to kill process usingcommand `

Explanation

The system failed to terminate a running process usingthe specified command.

User response

Verify the process listed in the command is stillrunning. If not, then the process may have endedbefore the command was issued.If the process is stillrunning, then additional DL30198 messages willprovide details on why the command failed.

GYMDL30200W

filename Unable to open file '

Explanation

A configuration file has been specified on thecommand line, but that file can not be located or read.

User response

Check command line. Check file path. Check filepermissions.

Programmer response

Using configuration files has been obsoleted in Proviso4.4.3 with the introduction of the Topology editor andthe central database configuration. This option is onlypresent in the code to support debugging and internalUnit test scenarios.

GYMDL30204W

duration Exit process timeout(more than

Explanation

A time boxed operation has reached it's limit. Theoperation will be aborted, and the process will exit.

GYMDL30205W

facilityname No configurationrecords have been retrieved fromREG$DCCONFIG forDCCONFIG.GLOBAL norDCCONFIG.

Explanation

The database table that contains the module'sconfiguration is empty.

Chapter 6. Messages 121

User response

Run Topology Editor to save the topology in thedatabase.

GYMDL30206W

Unable to read DCCONFIGregistry.

Explanation

The database table that contains the module'sconfiguration can not be read.

User response

Check database connectivity from the collectormachine. Check database connection configuration.

GYMDL30208W

tnsentry login Unable to connect todatabase using bootstrapconnection '

Explanation

The connection to the database can not be establishedwith the provided user, password and TNS ID.

User response

Check user, password and TNS ID in dataLoad.env.Check database connectivity with database tools.

GYMDL30208W

Unable to connect to databaseusing bootstrap connection '

Explanation

The connection to the database can not be establishedwith the provided user, password and Database name.

User response

Check user, password and Database name indataLoad.env. Check database connectivity with DB2tools.

GYMDL30209W

dir 'DATABASE.ORACLE_HOME=

Explanation

The ORACLE_HOME environment variable does notpoint to a valid directory, or does not contain theexpected lib32 or lib64 sub directories.

User response

Check ORACLE_HOME in dataLoad.env and checkOracle install on that machine.

GYMDL30209W

dir'DATABASE.DATABASE_HOME=

Explanation

The DATABASE_HOME environment variable does notpoint to a valid directory, or does not contain theexpected lib32 or lib64 sub directories.

User response

Check DATABASE_HOME in dataLoad.env and checkDB2 install on that machine.

GYMDL30210W

entry configuration entry '

Explanation

A mandatory configuration entry has no value.

User response

Run Topology Editor to set a value for theconfiguration entry.

GYMDL30211W

limit entry configuration entry '

Explanation

The value of a configuration entry exceeds themaximum expected size for such configuration.

User response

Run Topology Editor to change the value for theconfiguration entry.

GYMDL30212W

value entry configuration entry '

Explanation

The password listed is not obfuscated properly or iscorrupt.

User response

Run Topology Editor to update the password for thelisted entry.

GYMDL30213W

libname Can't load the Oraclelibrary '

Explanation

The expected Oracle client library file can not beloaded, or does not provide the expected OCI calls.

122 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

User response

Check ORACLE_HOME and dynamic library path indataLoad.env. Check permissions for TNPM user onthe Oracle files. Check version of Oracle.

GYMDL30214W

oraerr Can't 'Disconnect', reason '

Explanation

The database library is no longer available, yet there isan existing connection to the database.

System action

In most cases the system is shutting down and willproceed to shutdown ignoring this error.

Programmer response

If occurring during a shutdown, this could be anindicator of a sequencing problem inside the collector.If it occurs at another time something caused thelibrary to be unloaded prior to the connection beingclosed.

GYMDL30215W

path name

Explanation

The directory path specified does not exist, is notwritable, or is not a directory.

User response

Validate all directories in the path are not read-onlyand are directories.

GYMDL30216W

sql phase

Explanation

The specified query failed to complete in the databasepossibly due to the database being unavailable.

User response

Verify the database is operational.

Programmer response

If a proxy is used to query data verify the$DL_LOG_HOME/tmp directory used to hold queryresults exists and is writable.If the query consistentlyfails, then it is possible some sort of configurationissue is causing the problem within the database.Verify the query can be successfully completed

outside of the collector and expected results arereturned.

GYMDL30217W

Unable to use command to stopprocess.

Explanation

The command to stop the watch dog process failed torun.

User response

Check the log for DL30198 errors which will providemore details on why the command failed.

GYMDL30218W

pid Unable to use kill process #

Explanation

Failed to terminate the process listed in the message.

User response

If the process is still running, check for other DL30005and DL30198 messages in the log for details on whythe process failed to terminate.

GYMDL30219W

argname Unknown or missing '

Explanation

Failed to specify the listed argument.

User response

Check the usage for the last command that was runand try again with the proper argument.

GYMDL30220W

Callback didn't return result,timing out.

Explanation

An expected result did not return in the time allotted.

Programmer response

This is primarily the result of trying to execute asmalltalk command from the collector.

GYMDL30222W

command taskid hexaddr Unableto invoke callback=

Explanation

Unable to invoke the call back routine because it isnull, the task id is 0, or the command is not specifiedor is null.

Chapter 6. Messages 123

Programmer response

Investigate configuration or install issues that maylead to incomplete data being used to try and invokethe SmallTalk interface.

GYMDL30224W

num fid Formula #

Explanation

The formula listed has a different data type than theformula associated with the save alias.

System action

The alias is ignored and formula processing willcontinue checking other possible save alias values.

GYMDL30225W

num fid Formula #

Explanation

The formula listed uses a formula ID that does notexist.

System action

The alias is ignored and formula processing willcontinue checking other possible save alias values.

GYMDL30226W

dbnum num fid Formula #

Explanation

The formula is already associated with a save alias inthe database. The new save alias is not the samevalue.

System action

The new save alias is ignored and the formula will beassociated with the save alias already in the database.

GYMDL30227W

dblang systlang Values forNLS_LANG differs between thesystem (

Explanation

The environment variable NLS_LANG is used by thedatabase client to encode/decode string information.The configuration of the client must match the one ofthe database.

User response

Edit file dataLoad.env, and set NLS_LANG to thedatabase value. Source the environment again, andbounce the collector.

GYMDL30228W

ERROR, remote connection isdown, removing task

Explanation

The collector was unable to transmit results to theremote client.

User response

Ensure all processes are active that depend oncollector results.

GYMDL30229W

id name Unable to compile/installformula '

Explanation

There was an error processing the expression of thelisted formula or the formula was unable to be parsed.

User response

If the formula was recently edited, verify the formula iscorrect.

GYMDL30230W

Execution failed due to invalidSNMP symbols in formulaexpression

Explanation

Unable to process the SNMP symbols for the formula.

User response

If the formula was recently edited, verify the formula iscorrect.

GYMDL30231W

Initialization failed due to syntaxproblem in OIDs list.

Explanation

Failed to parse the OID list associated with theformula.

User response

Verify the OID list is correct, and retry the formula.

GYMDL30232W

Unable to start Watchdog thread.

Explanation

The system was unable to start the watch dog thread.

124 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Programmer response

Verify the operating system resources are notexhausted. Some may be correctable by adjusting theoperating system configuration.

GYMDL30233W

Unable to start WatchDog process,Aborting WatchDog thread.

Explanation

Unable to start the watch dog process for thecollector.

User response

Check the log for other DL30198 errors which shouldprovide more information as to why the process failedto start.

GYMDL30234W

Unable to communicate withWatchDog process, AbortingWatchDog thread.

Explanation

The collector is unable to communicate with the watchdog process.

User response

Check the log for other DL30189 and DL30190 errorswhich may explain why the communication failed.

GYMDL30235W

gid seid Can't get Elmt or Instanceinfo for SubElmt#

Explanation

The sub-element listed is missing an association withan element or is missing instance info. The sub-element is used in collections and becauseof themissing information, will cause missing results.

System action

The sub-element will be skipped due to the missinginformation. Since it is used in a collection it will causemissing results.

User response

Try running discovery again which could fix the modeleither by retiring all connected objects, or byrecreating the missing ones.

GYMDL30236W

gid seid Can't get Elmt or Instanceinfo for SubElmt#

Explanation

The sub-element listed is missing an association withan element or is missing instance info.

System action

The sub-element will be skipped due to the missinginformation.

User response

Try running discovery again which could fix the modeleither by retiring all connected objects, or byrecreating the missing ones.

GYMDL30237W

seid Can't get Elmt info forSubElmt#

Explanation

The sub-element listed is missing an association withan element. The sub-element is used in collectionsand becauseof the missing information, will causemissing results.

System action

The sub-element will be skipped due to the missinginformation. Since it is used in a collection it will causemissing results.

User response

Try running discovery again which could fix the modeleither by retiring all connected objects, or byrecreating the missing ones.

GYMDL30238W

port host servicename Incompletedefinition for

Explanation

Either the service name is not known to the collector,or the request is incomplete or corrupted.

System action

System will ignore the request and continue normaloperations.

User response

Attempt to re-issue the request or re-run thecommand line tool issuing the request that failed ifknown.

Programmer response

If this happens often, there could be a compatibilityissue from the component running on the specified

Chapter 6. Messages 125

host/port or with the command line script issuing therequest.

GYMDL30239W

ip name Reboot detected on device'

Explanation

The collector detected that the named device at thelisted IP address was rebooted. A device reboot mayresult in dataloss if a collection was attempted duringthe reboot cycle.

User response

Ensure the device is operating normally if the rebootwas not expected.

GYMDL30241W

Unable to initializeDataBaseAccess Library.

Explanation

Failed to initialize the database access library.

Programmer response

This is likely a very rare occurrence. If it does occur itlikely means operating system resource limits havebeen hit.

GYMDL30242W

errno Unable to determine maxopen files per process. errno=

Explanation

Unable to obtain the max number of open files fromthe operating system.

User response

Check to ensure the number of open files is set via theulimit command.

Programmer response

This is a rare failure. Ensure the collector binary isvalid and ensure the ulimit is not being changed priorto the binary starting.

GYMDL30243W

syst est Max open files (estimated)of

Explanation

The max number of open files required by the collectorconfiguration exceeds the maximum value set for theoperating system.

User response

Ensure the operating system maximum is set to areasonable value. If not, adjust the operating systemvalue. Otherwise usethe topology editor to adjust theconfiguration settings listed in the message. Note, thecollector requires 8 additional open files in addition tothetotal for the configuration settings.

GYMDL30244W

syst est Max simultaneous threadsvalue of

Explanation

The number of threads required by the collector isgreater than the maximum number of threads allowedby the operating system.

User response

Ensure the operating system maximum is set to areasonable value. If not, adjust the operating systemvalue. Otherwise usethe topology editor to adjust theconfiguration setting listed in the message. Note, thecollector requires 12 additional threads in addition totheconfiguration setting value.

GYMDL30245W

max_value Scheduler quotaexceeded. Unable to create morethan

Explanation

More jobs have been requested to be scheduled thanis allowed by the current configuration.

User response

If more jobs are desired, adjust the listed configurationvariable.

Programmer response

If the schedule limit is already quite large, this couldbe indicating that several jobs are consuming toomuch time or the collector is overloaded.

GYMDL30246W

reason port call Socket

Explanation

The specified operating system call did not completesuccessfully using the port listed.

System action

In the case of calls to select() and accept(), thecollector will try to reset the socket and continue ifsuccessful.

126 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

User response

Ensure no other process is using the port listed.

GYMDL30247W

Too many attempts, bind failed.

Explanation

The collector was unable to bind to a port.

User response

Check for DL30246 messages in the log which shouldlist the port that is having problems. Ensure the port isnot used by another process.

GYMDL30248W

max_value Too many clients at thesame time, no more than

Explanation

More clients have established connections to thecollector than the collector will handle.

User response

Ensure the clients are operating normally. If not,restart or stop the client. Ensure the collector isoperating normally. If not, restart the collector.

GYMDL30249W

manager request Undefined errorwhen applying request

Explanation

An error occurred within the model hierarchy whiletrying to apply the request.

System action

The system will ignore the request and continuenormal operations.

User response

Try running discovery again which could fix the modeleither by retiring all connected objects, or byrecreating the missing ones.

GYMDL30250W

file Filesystem '

Explanation

The file system that would host the listed file is out ofspace.

User response

Clean out any unnecessary files from the file system tocreate free space.

GYMDL30251W

err field host Host '

Explanation

The SNMP V3 read community syntax is not correct forthe listed host.

User response

Edit the read community value for the specified host tocorrect the problem.

GYMDL30253W

cmd Unable to start externalWatchdog process using '

Explanation

Failed to start the watch dog process with the listedcommand.

User response

Check the log for other DL30198 errors which shouldprovide more information as to why the commandfailed to run.

GYMDL30254W

Aborting WatchDog thread.

Explanation

The watch dog thread detected an unknown state. Thethread will stop immediately.

Programmer response

This is a very rare occurrence. If occurs regularly, it isrecommended development become involved.

GYMDL30255W

entry host Host '

Explanation

The SNMP V3 parameter in the listed entry is emptyfor the specified host.

User response

Correct the SNMP V3 authentication for the host to theproper format.

GYMDL30256W

line key host Host '

Explanation

The SNMP V3 parameter value for the listed key isempty for the specified host.

Chapter 6. Messages 127

User response

Correct the SNMP V3 authentication for the host to theproper format.

GYMDL30257W

line key host Host '

Explanation

Incorrect SNMP V3 parameter specified for the listedhost.

User response

Correct the SNMP V3 authentication for the host to theproper format.

GYMDL30258W

param host Host '

Explanation

The mandatory parameter listed is missing for theSNMP V3 entry for the specified host.

User response

Correct the SNMP V3 authentication for the host to theproper format.

GYMDL30259W

val host Host '

Explanation

An unknown access mode was provided for the SNMPV3 authentication for the specified host.

User response

Correct the SNMP V3 authentication for the host to usea valid access mode.

GYMDL30261W

name Host '

Explanation

The mandatory parameter SecurityName was notlisted for the SNMP V3 authentication for the specifiedhost.

User response

Correct the SNMP V3 authentication for the host toprovide the SecurityName parameter.

GYMDL30262W

host Host '

Explanation

Unable to generate a security authentication keybased on the SNMP V3 authentication information forthe specified host.

User response

Verify the SNMP V3 authentication for the host iscorrect. If so check for DL30007 errors which mayindicate a secondary error.

GYMDL30263W

host Host '

Explanation

The mandatory parameter PrivPasswd was not listedfor the SNMP V3 authentication for the specified host.

User response

Correct the SNMP V3 authentication for the host toprovide the PrivPasswd parameter.

GYMDL30264W

host Host '

Explanation

Unable to generate a security privacy key based on theSNMP V3 authentication information for the specifiedhost.

User response

Verify the SNMP V3 authentication for the host iscorrect. If so check for DL30007 errors which mayindicate a secondary error.

GYMDL30265W

hostname line file Insert of emptysession in list in

Explanation

The collector is processing an incorrect SNMP sessionfor a job associated with the specified host.

Programmer response

Contact development with the error and message todetermine futher diagnostic steps.

GYMDL30266W

msg

Explanation

The parsing or the execution of the formula failedbecause of an unrecognized token, an invalid numberof arguments for a function, or an unexpected value for

128 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

an argument. The message indicates the exactlocation of the problem.

User response

If the error indicates a syntax error in the formula,correct the offending function or argument in theformula definition, and bounce the collector.If theerror indicates a runtime error with a particular valuefor an argument, and the error is occurring repetitively,check the formula logic, and if the value is a validinput, extend the formula to handle it. Then bouncethe collector.

GYMDL30271W

number elapsedtime unknowntimedowntime uptime curlastchangecurstate curcoltime currentuptimeprevlastchange prevstateprevcoltime prevuptime nameRFC1213LIB, discardedifAvailability result forSubElement '

Explanation

The collector discarded the ifAvailability result for thelisted sub-element because one or more data itemsare out of range.

System action

The collector will discard the result.

User response

If this message occurs regularly, but is not expected,the device should be investigated for potentialproblems.

GYMDL30272W

Some new inconsistencies havebeen detected, a full model reloadis attempted.

Explanation

The collector detected inconsistencies in the model.

System action

The collector will request a full reload of the model totry and correct the inconsistencies.

User response

If the problem persists, try running discovery againwhich could fix the model either by retiring allconnected objects, or by recreating missing ones.

GYMDL30273W

expression fid Formula #

Explanation

The specified formula has an incorrect expression.

System action

The incorrect formula will be ignored by the collector.

User response

Correct the expression in the formula definition, andbounce the collector.

GYMDL30274W

Formula HostNeeds / DataType isnot defined, probably invalid ID.

Explanation

The formula host needs, or data type is not specified.Possibly the formula is using an unknown or incorrectID.

User response

If formula was edited recently, verify the formulaspecification is correct.

GYMDL30275W

Formula expression is not defined,probably invalid ID.

Explanation

The formula expression is not specified. Possibly theformula is using an unknown or incorrect ID.

User response

If formula was edited recently, verify the formulaspecification is correct.

GYMDL30276W

error cmd OraProxy command '

Explanation

The specified command failed with an error whenrunning via the database proxy.

Programmer response

The proxy either is not operational, the file system isfull, or there is a problem with the query.

GYMDL30277W

curid OraProxy expected result filefor cursor '

Explanation

Unable to find the specified cursor file either becausethe file does not exist, or the cursor id was notprocessed correctly.

Chapter 6. Messages 129

User response

Ensure directory $DL_LOG_HOME/tmp exists, iswritable, and the file system is not out of space.

GYMDL30278W

rid mid Invalid Metric Record withNaN Value Found (MetricId: '

Explanation

Found a record with a not a number value, but isexpected a valid floating point number.

System action

The metric will not be saved because the system cannot process these values.

GYMDL30279W

formulaPath Missing or non-readable formula file '

Explanation

The specified formula file does not exist or is notreadable.

User response

Verify the file is readable. If the file does not exist,contact IBM support.

GYMDL30280W

scriptPath Missing or non-executable script '

Explanation

The specified script does not exist or is not readable.

User response

Verify the file is readable. If the file does not exist,contact IBM support.

GYMDL30281W

errorString cmd Error whileexecuting command '

Explanation

The collector was not able to run the commandspecified.

User response

Verify the specified command is executable from thecommand line.

Programmer response

Verify the operating system resources are notexhausted. Some may be correctable by adjusting theoperating system configuration.

GYMDL30282W

SNMPv3 support is limited toAuth(None,MD5) x Priv(None).

Explanation

SNMPv3 cryptography support can not be loaded.Collections requiring advanced encryption supportmay result in lost collections.

System action

The system will start with limited encryption support.Uses of advanced encryption support will result inDL30007 messages.

User response

Either install the cryptographic library, and make surethe library is in the standard search path, andaccessible for the current user.

GYMDL30283W

filename Load failed. Found file '

Explanation

The OpenSSL library filename specified in the messagewas found via the standard library search path,however does not implement all required functions.

User response

Ensure the proper version of the OpenSSL library file isfound first in the standard library search path for theapplication.

GYMDL30284W

hostname Unable to resolve IPaddress for '

Explanation

The system is unable to determine the IP address forthe specified host name.

User response

Ensure the host name is spelled correctly. If it iscorrect it may need to be fully qualified with a domain.Also verify the name is what is stored in DNS or thelocal hosts file.

GYMDL30285W

scriptPath Command '

Explanation

The specified command returned unexpected results.

130 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Programmer response

Verify the command returns valid results when runfrom the command line.

GYMDL30286W

The configuration contains IPv6address(es). IPv6 is not currentlysupported on this machine.

GYMDL30287W

SNMPJob jodescr can not start in adedicated thread. Internal error is' err

ExplanationIncomplete SNMPv3 metric collection Some data losscan be observed from the “Expected measures” and“Produced measures” in the SNMP collector logmessage, especially when there is a sudden drop in“Produced measures” when compared with past hoursof collection.

For example:

DL31066 I DL_PERF_SUMMARY Hour: <1s:hour>subElmts: <2s:ses> metrics: <3s:metrics>requests: <4s:requests> expMeas:<5s:expmeas> prodMeas: <6s:prodmeas>

This is a thread-related issue that corresponds toinsufficient resources to create another thread, orthere is a system-imposed limit on the number ofthreads to be created. The attached workaround isapplicable only if the following warning message isdisplayed first to indicate that this is a thread-specificissue as there are many other configuration issues thatcan cause data losses.

DL30287 W SNMPJOB_THREAD_ERR SNMPJob<1s:jobdescr> can not start in a dedicated thread.Internal error is '<2s:err>'.

User response

If the system resources cannot be increased, decreasethe concurrency in the collector.

Note: This decreases the overall performance of thecollector.

Concurrency is controlled by theGLOBAL.SNMP.MAXASYNC parameter, which is giventhe default value of 256. The default value can bechanged by adding a Custom Datachannel parameterin the TNPM topology. This parameter can be addedusing the Topology Editor:GLOBAL.SNMP.MAXASYNC=<value> where <value>is a number less than 256.

GLOBAL.SNMP.MAXASYNC=256

GYMDL31001I id level Set log generation level to '

Explanation

The collector is now using the new specified logginglevel for the specified taskId or channel Id.

GYMDL31003I version Version:

Explanation

A message indicating the current version number ofthe collector.

GYMDL31004I reason terminating collectorbecause of

Explanation

The collector is being stopped due to the specifiedreason.

GYMDL31005I schema tns login Connected to DB '

Explanation

Message indicating the collector successfullyconnected to the database and the schema versionbeing used.

GYMDL31006I err

Explanation

A message indicating any errors that occurred duringan SNMP set request.

User response

If the errors are consistent then this may indicate therequest is incorrect or is not supported by the target.

GYMDL31007I file line Ignoring line '

Explanation

The specified line was skipped in the specified file.

User response

Check the log for related DL31093 or DL31095messages. Other causes are bad formatting or the typerefers to an SNMP trap.

GYMDL31009I data fid Formula #

Explanation

The specified formula has been marked as complexand may cause performance problems.

GYMDL31010I Collector is now reconnected todatabase.

Chapter 6. Messages 131

Explanation

The collector detected the database connection waslost and was successfully able to reconnect.

GYMDL31011I type arg oid Oid '

Explanation

Failed to decode the specified OID.

GYMDL31012I descr id TaskId #

Explanation

The specified SNMP task is still in the initialized stateand can not be scheduled.

GYMDL31014I msg

Explanation

This is a status message indicating the current actionbeing taken against the collector.

GYMDL31015I state HAState changed to

Explanation

The HA state was updated to the specified state value.

GYMDL31016I tot n area Reload '

Explanation

The reload successfully completed. An indicator ofhow many tasks were synchronized out of the totalnumber of tasks is also provided.

GYMDL31017I jobdescr Performance warning:Job

Explanation

The specified job consistently does not return resultsfor the number of PDUs associated with it. It maycause performance problems within the collector.

User response

Consider disabling or correcting the job if performanceproblems are occurring. Other messages associatedwith the job may indicate a cause.

GYMDL31018I descr id returnedcode Taskreturned TASK_RESULT_ZOMBIE (

Explanation

The specified task is no longer operational. Deletingthe task.

GYMDL31019I capacity_percent quota usagenumber capacity_percenttarget_percent quota estimatedusage collMeasuredKbps:

Explanation

The bandwidth for the collector was adjusted. The newvalues are listed.

GYMDL31020I usedcapacity quota usage nameBandwidthLimiter:

Explanation

The collector output the current performancesummary for the specified bandwidth limiter.

GYMDL31021I port Listener started on TCP port

Explanation

The listener was successfully started on the specifiedport and is ready to accept connections.

GYMDL31022I requests mibs metric segrpmbrsegrp se prop elmt Elmt:

Explanation

A message indicating the model counts for each typeof object.

GYMDL31023I Starting full model reload.

Explanation

The collector has started a full model reload operation.

GYMDL31024I Starting incremental modelreload.

Explanation

The collector has started an incremental model reloadoperation.

GYMDL31051I phase Phase '

Explanation

The specified phase of the configuration dumpoperation has succeeded.

GYMDL31052I level Set global log generationlevel to '

Explanation

The logging threshold was updated to the new levelindicated in the message.

GYMDL31053I sql cnxid Err CnxId=

132 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Explanation

An error occurred accessing the database, see log forother messages. This message is showing the contextid and SQL that was issued when the error occurred.This message is controlled by theDIAG.SQL.SHOWSELECT configuration setting.

GYMDL31054I sql curid cnxid OK CnxId=

Explanation

The last SQL command was successful. This messageis showing the context id and SQL that was issued.This message is controlled by theDIAG.SQL.SHOWSELECT configuration setting.

GYMDL31055I curid Error in CurId=

Explanation

This message indicates no result set was generateddue to an error in the last database operation. Thismessage is controlled by theDIAG.SQL.SHOWRESULTSET configuration setting.

GYMDL31056I result curid OK CurId=

Explanation

This message is displaying the result of the lastdatabase operation. This message is controlled by theDIAG.SQL.SHOWRESULTSET configuration setting.

GYMDL31057I dstcollnum srccollnum eltnameMarking element cache as dirty,element

Explanation

The element listed is being marked dirty because it isbeing moved to another collector.This message iscontrolled by theDIAG.DBUPDATE.COLLECTORCHANGE configurationsetting.

GYMDL31058I Process successfully stopped.returned code = 0

Explanation

The process indicated by message DL31091 hassuccessfully been stopped.

GYMDL31059I name EmptyTask:

Explanation

Message indicating the task is being cleared oremptied because it was completed, deleted orstopped.This message is controlled by theDIAG.SCHED.EMPTYTASK configuration setting.

GYMDL31060I rid mid taskid index Refusing tostop task (index=

Explanation

Refusing to stop the specified task because it is usedin the model.This message is controlled by theDIAG.SCHED.STOPINMODEL andDIAG.SCHED.STOPCHECKMODEL configurationsettings.

GYMDL31061I taskid index Allowing task (index=

Explanation

The system is allowing the specified task to bestopped because it is not used in the model.Thismessage is controlled by theDIAG.SCHED.STOPOUTOFMODEL andDIAG.SCHED.STOPCHECKMODEL configurationsettings.

GYMDL31062I hour Create CLOSE_HOUR file forhour

Explanation

The system created the CLOSE_HOUR file for thespecified hour.

GYMDL31063I hour Skip CLOSE_HOUR file forhour

Explanation

The system is skipping creating the CLOSE_HOUR filebecause requests are currently disabled.

GYMDL31064I memused dbavail quotaavailuptime overflowrisk threadavailitemscount hour Hour:

Explanation

A message outputting collector statistics for the lasthour.

GYMDL31065I inpdutot outpdutot inpdudiscoutpdudisc snmpsuccess resptimehour Hour:

Explanation

A message outputting collector statistics for the lasthour.

GYMDL31066I prodmeas expmeas requestsmetrics ses hour Hour:

Chapter 6. Messages 133

Explanation

A message outputting collector statistics for the lasthour.

GYMDL31067I err SNMPJob failed to completewith error: '

Explanation

An SNMP job failed with the specified error. Thismessage is controlled by theDIAG.FORMULA.SNMPJOBFAILURES configurationsetting.

GYMDL31068I now timeout lastcloseNEXT_HOUR_TIMEOUT detected.Last closed hour=

Explanation

The system detected the hour timeout and is startingto create a new close hour file.

GYMDL31069I taskid Scheduler task

Explanation

The system has detected a task that needs to besynchronized.This message is controlled by theDIAG.CMPLXCACHE.RESYNCINSERTION,DIAG.LIBCACHE.RESYNCINSERTION, andDIAG.LITECACHE.RESYNCINSERTION configurationsettings.

GYMDL31070I taskid Registering synchronizationon scheduler task

Explanation

The system has detected a task that needs to besynchronized, however the task has already beenregistered for deletion.This message is controlled bythe DIAG.CMPLXCACHE.RESYNCDELETE,DIAG.LIBCACHE.RESYNCDELETE, andDIAG.LITECACHE.RESYNCDELETE configurationsettings.

GYMDL31071I taskid Scheduler task

Explanation

The system has detected a task that needs to bedeleted.This message is controlled by theDIAG.CMPLXCACHE.DELETEINSERTION,DIAG.LIBCACHE.DELETEINSERTION, andDIAG.LITECACHE.DELETEINSERTION configurationsettings.

GYMDL31072I taskid Registering deletion onscheduler task

Explanation

The system has detected a task that needs to bedeleted, however it is already registered to besynchronized.This message is controlled by theDIAG.CMPLXCACHE.DELETERESYNC,DIAG.LIBCACHE.DELETERESYNC, andDIAG.LITECACHE.DELETERESYNC configurationsettings.

GYMDL31077I Altering return value from ZOMBIEto VALID.

Explanation

Resetting the result from ZOMBIE to VALID perconfiguration setting.This functionality and message iscontrolled by theDIAG.FORMLITE.EXECUTERETURNVALUEconfiguration setting.

GYMDL31078I form InitMetric (in cache) returnedan error for:

Explanation

The system detected an error initializing a cachedmetric.This message is controlled by theDIAG.FORMLITE.RESETFORM configuration setting.

GYMDL31079I form InitMetric (not in cache)returned an error for:

Explanation

The system detected an error initializing a metric notcurrently in the cache.This message is controlled bythe DIAG.FORMLITE.RESETFORM configurationsetting.

GYMDL31084I Disable SNMP log generation

Explanation

The system is disabling SNMP log generation based onthe new debug level.

GYMDL31085I Disable DBDriver log generation

Explanation

The system is disabling DBDriver log generation basedon the new debug level.

GYMDL31086I level Set DBDriver log generationlevel to

Explanation

The system is enabling DBDriver log generation to thespecified level.

134 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

GYMDL31087I Start command successfullyexecuted. Returned code = 0

Explanation

The command listed in the previous DL31088message started successfully.

GYMDL31088I cmd name Starting new process '

Explanation

The system is about to attempt to start a new processusing the specified command.

GYMDL31089I name pid Killing process #

Explanation

The system is about to terminate the specifiedprocess, using a kill signal.

GYMDL31090I pid Process #

Explanation

The process requested to be stopped does notcurrently exist.

System action

The system is skipping the attempt to stop the processand attempt to start it again.

GYMDL31091I cmd name pid Stopping process #

Explanation

The system is about to attempt to stop the processusing the specified command.

GYMDL31092I text

Explanation

Unable find a name for current result.

GYMDL31093I line type Unknown SNMP Type '

Explanation

Found an unknown SNMP type processing MIBs from afile.

GYMDL31094I descr level Set SNMP loggeneration level to

Explanation

The system is enabling SNMP log generation to thespecified level.

GYMDL31095I line access Unknown Access Type '

Explanation

Found an unknown access type processing MIBs froma file.

GYMDL31096I mib type missing type '

Explanation

Unable to find type in specified MIB file.

GYMDL31098I msg

Explanation

The current statistics of the model after it wassynchronized.

GYMDL31099I error[BUILD_RESULTS_FORMLITE]SNMPJob failed to complete witherror

Explanation

The SNMP job failed to complete with the specifiederror.This message is controlled by theDIAG.FORMULA.SNMPJOBFAILURES configurationsetting.

GYMDL31100I mib type missing type '

Explanation

The system was unable to find the type specified in thefile listed. It was able to find an alternate definition inanother file.

GYMDL31101I Altering closure return value fromZOMBIE to VALID.

Explanation

Resetting the result from ZOMBIE to VALID perconfiguration setting.This functionality and message iscontrolled by theDIAG.FORMLITE.EXECUTECLOSURERETURNVALUEconfiguration setting.

GYMDL31102I Altering return value (was0:failure) changed to 1:success.

Explanation

Updating the return value to success from failure perconfiguration setting.This functionality and message iscontrolled by theDIAG.FORMLITE.RESETFORMRETURNVALUEconfiguration setting.

GYMDL31103I curdevuptime curlastchangecurstatus curvalidcoltime

Chapter 6. Messages 135

curdevuptime prevlastchangeprevstatus prevvalidcoltimeprevdevuptime senameRFC1213LIB, invalid lastChangetimestamp for SubElement '

Explanation

The system discovered an incorrect timestamp for thespecified sub-element. The system is forcing the lastchange timestamp to the previous up time.

GYMDL31105I timgmt timeclean Set tool time to

Explanation

Updated the tool time to the values listed based on the-t parameter used on the command line.

GYMDL31106I Internal, task must beTASK_ACTIVE, TASK_ASLEEP orTASK_ZOMBIE to be validated

Explanation

The task does not have an expected status and isbeing marked as failed.

GYMDL31107I taskid Empty'ing TaskId #

Explanation

Clearing task because the status is zombie.

GYMDL31108I indexsize storagesize StatManagerstorage=

Explanation

Current memory usage by the statistic manager.Thismessage is controlled by the DEBUG.LOGMEMUSEconfiguration setting.

GYMDL31109I efficiency jobdescr SNMPJob

Explanation

The system is stopping an expensive SNMP job beforeit runs.This message and functionality is controlled by

the SNMP.ABORTEXPENSIVEJOBS configurationsetting.

GYMDL31111I Process successfully killed.

Explanation

The process mentioned in the previous DL31089message was successfully killed.

GYMDL31112I versioncode versionstring nameLibrary '

Explanation

The SSL library was successfully loaded. The file nameand version are provided.

GYMDL31113I name Library '

Explanation

The open SSL library listed was not used as directedby configuration.This message and functionality iscontrolled by the TUNING.USE_OPENSSLconfiguration setting.

GYMDL31114I Full SNMPv3 supportAuth(None,MD5,SHA-1) xPriv(None,DES,AES) is available.

Explanation

The open SSL library was loaded providing full SNMPV3 support.

GYMDL31115I name Library '

Explanation

The open SSL library was removed from the collector.Partial encryption support now in effect for SNMP V3.

DataView operational messagesA list of error messages generated by the DataView component.

The message severity indicates how critical it is for the situation to be resolved in order to resume normaloperations. The severity code indicator is identified by a character at the end of the message ID. They areas follows:

• ‘E' – Error

Typically, errors describe events that represent an unrecoverable error within a server that affect itsability to service some requests, but not all operations are affected.

136 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

• ‘W – Warning

Typically, warnings represent recoverable errors.• I - Informational

Typically, informational messages represent events like normal conditions, events supplied to clarifyoperations, e.g. state transitions, operational changes.

Note: In this guide informational messages are not documented as they are self explanatory and do notrequire any user action.

GYMVB0002E Settings have not been saved.

Explanation:See message.

User response:Try again. Contact the system administrator if thisproblem persists.

GYMVB0003W No settings are currently enabledfor configuration.

Explanation:See message.

GYMVB0004E A valid email address is required.Type a valid email address.

User response:See message.

GYMVB0005E Unable to set your email addressat present.

Explanation:See message.

User response:Contact the system administrator if this problempersists.

GYMVB0006E The email address has beensuccessfully set.

Explanation:See message.

GYMVB0008E Changes could not be saved.

Explanation:See message.

Administrator response:Check the network and database connectivity.

GYMVB0009E A valid email address is required.

Explanation:See message.

User response:Type a valid email address.

GYMVB0010E A valid number is required.

Explanation:See message.

User response:Type the number by using the digits 0 through 9 only.

GYMVB0011E The time format is not valid.

Explanation:See message.

User response:Type the time in 24-hour notation format (HH:mm:ss).

GYMVB0012E Changes were not applied. Thefollowing DataView server isalready configured:PDF Server

Explanation:See message.

Administrator response

1. Configure the settings for the server used togenerate PDF files.

2. After applying these settings, click Export to PDFthat is available in the Defined Resource Viewstoolbar for users with privileges to create PDF files.

3. In the PDF Server column, type the fully qualifiedURL of the PDF Server.

4. In the Additional URL Parameters column, typeany other parameters that the server requires.

5. Set the email address for the Contact button in theDefined Resource Views toolbar. Typically, this isthe address of an administrator or customersupport.

GYMB0013E Unable to load user.

Explanation:See message.

GYMB0015E Changes could not be applied.

Explanation:See message.

Administrator response:Check the network and database connectivity.

GYMVB0017E Changes could not be applied.

Explanation:See message.

Administrator response:

Chapter 6. Messages 137

Check the network and database connectivity.

GYMVB00018E Unable to load profile.

Explanation:See message.

GYMVB0019E A valid number is required.

Explanation:See message.

User response:Type the number by using the digits 0 through 9 only.

GYMVB0020W Missing the required informationto display the threshold violationdata.

Explanation:See message.

GYMVB0021E An error occurred while obtainingand rendering data.

Explanation:See message.

System action:Event representing the setting of a set of contextparameters.Event representing the setting of a report runtimeparameter.Event representing the successful generation of areport.

GYMVB9000E The following DataView server isalready configured:<server name>

Explanation:See message.

GYMVB90001E A value is required for this textfield.<text field name>

Explanation:See message.

GYMVB9010E Unable to open workspace. Pleaseensure that the workspacedefinition is valid.

Explanation:You might encounter this error, when you try to open apreviously saved workspace. Typically, you encounterthis error if the workspace is invalid.

User response:Contact the system administrator if this problempersists.

GYMVC0000E DataView is not installed in eWas!

Explanation:

The tool executed by you is unable to locate aninstalled version of Dataview in the eWas applicationserver.

System action:The tool will print the above message to inform youthat Dataview is not installed.

User response:You must contact a system administrator.

GYMVC0002E Can not connect to eWAS/TIP.

Explanation:The tool was not able to connect to the applicationeWas sevrer.

System action:The tool prints the message to inform you that theapplication server is not running.

User response:You must contact an administrator or start up theapplication server.

GYMVC0003E Can not locate the'legacyDataview.war' file!

Explanation:The tool cannot find the legacyDataview war file that itrequires to execute the tool.

System action:Dataview is not correctly installed.

User response:You must contact the administrator.

GYMVC0005E Unable to determine DataView'scurrent context root!

Explanation:The tool is not able to determine the location of theDataView context root in the eWas application server.

System action:DataView is not correctly installed.

User response:You must contact the administrator.

GYMVC0006E Action not specified or supported.Available actions are:

Explanation:You tried to use the configure tool to execute an actionthat is not supported by the tool.

System action:The system will print the above message followed bythe supported actions.

User response:You must execute the configure tool with one of thesupported actions that is displayed.

138 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

GYMVC0007E Command not specified orsupported. Available commandsare:

Explanation:You passed no value or an invalid value for the typeparameter.

System action:The system will print the above message followed bythe supported type of commands for the configuretool.

User response:You must execute the configure tool by passing one ofthe supported commands that is just displayed as thevalue for the type parameter.

GYMVC0009E At least one of the followingparameters is required for the jdbccommand: -jdbcUrl, -jdbcUser, or -jdbcPassword

Explanation:You executed a command of type jdbc but did notprovide any valid values for that type of command.

System action:The system will print the above message to show whatparameters are expected when executing a commandof type jdbc.

User response:You must execute the tool by passing one or more ofthe supported jdbc parameters that is displayed.

GYMVC0010E Logging level not specified orsupported. Available levels are:

Explanation:You executed a command of type logging but did notprovide a valid values for that type of command.

System action:The system will print the above message followed bythe valid values it accepts for the level parameter.

User response:You must execute the tool by passing one of the validvalues for the level parameter.

GYMVC0011E Debug state not specified orsupported. Available states are.

Explanation:You executed the configure tool with an invalid valuefor the Debug parameter.

System action:The system will print the above message followed bythe valid values it accepts for the Debug parameter.

User response:You must run the command again by giving a validvalue that is displayed.

GYMVC0049E Invalid JDBC home

Explanation:The location passed for the <driverhome> parameter isincorrect as the tool could not locate the jar files itneeds.

User response:You must check the location and provide the correctlocation.

GYMVC0050E Unsupported database type {0}

Explanation:The tool is unable to connect to the url provided in the<jdbcurl> parameter

System action:The above message is displayed followed by theinvalid url.

User response:You must check the database url and provide a validone.

GYMVC0064E Error occurred: {0}

Explanation:This is a reused message to inform that the migratetool encountered an error.

User response:You must examine the error message to determinewhat to do next.

GYMVC0076E Unable to connect to SilverStreamat: {0}

Explanation:The migrate tool is unable to connect to theSilverstream server with the information passed by theuser in the <ssurl>,<ssuser>, and <sspassword>parameters.

System action:The system prints the message above followed by the<ssurl> value.

User response:You must check if the Silverstream server is runningand also that you passed the correct connection info.

GYMVC0090E Unknown Host: {0}

Explanation:The client could not connect to the host that youpassed in the host parameter.

System action:The system displays the message followed by the hostparameter.

User response:You must check that the host is running. Correct hostinfo if necessary and try again.

Chapter 6. Messages 139

GYMVC0091E Unable to connect to DataView at:{0}

Explanation:There is a problem connecting to the DataView server.

System action:The system displays the message followed by url thetool attempted to connect by using all the parametersprovided.

User response:You must check that the check the DataView server isrunning.

GYMVC0092E Authentication Failure.

Explanation:There is a problem authenticating to the host.

System action:

User response:Check your given user and password credentials.

GYMVC0094E Wrong context: {0}

Explanation:There is a problem with the context info supplied byyou.

System action:

User response:Check the context you supplied is valid.

GYMVC0095E Wrong Protocol: {0}

Explanation:The protocol supplied you is incorrect or invalid.

User response:Supply a valid protocol.

GYMVC0096E Wrong Port: {0}

Explanation:The port number supplied by you is incorrect.

User response:Supply a valid port.

GYMVC0100E Wrong Directory

Explanation:The directory supplied by you is incorrect.

User response:Supply a valid directory.

GYMVC0101E Wrong Port: {0}

Explanation:The port number supplied by you is incorrect.

User response:Supply a valid port.

GYMVC0102E Wrong context: {0}

Explanation:There is a problem with the context info supplied byyou.

System action:

User response:Check the context you supplied is valid.

GYMVC0103E Wrong Protocol: {0}

Explanation:The protocol supplied you is incorrect or invalid.

User response:Supply a valid protocol.

GYMVC0105E Unknown Host: {0}

Explanation:The client could not connect to the host that youpassed in the host parameter.

System action:The system displays the message followed by the hostparameter.

User response:You must check that the host is running. Correct hostinfo if necessary and try again.

GYMVC0106E Unable to connect to DataView at:{0}

Explanation:There is a problem connecting to the DataView server.

System action:The system displays the message followed by url thetool attempted to connect by using all the parametersprovided.

User response:You must check that the check the DataView server isrunning.

GYMVC0110W No files found matching pattern:{0}

Explanation:The export tool did not find any files matching thepattern provided by you.

System action:The export tool did not export any files.

User response:You need to consider if you passed the right fileextension.

GYMVD0001E Unable to dynamically generateSQL

Explanation:The system is unable to create the SQL used toretrieve the requested information from the database.

System action:

140 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

The system is unable to retrieve the requestedinformation from the database. You will be notified ofthe error and no data will be returned.

User response:You must ensure that the required parameter valuesare supplied to the API and that the provided valuesare valid.

GYMVD0001W User has not been granted accessto group: User = {0}, Group = {1}

Explanation:You made an API request that is not granted access toinformation pertaining to the specified group.

System action:The system will not process the API request and nodata will be returned.

User response:You must ensure that the specified group has accessgranted or contact the administrator to obtain accessto this specific group.

GYMVD0002E Unable to retrieve informationfrom the data source

Explanation:The system is unable to connect to or read from thedata source containing the requested information.

System action:The system is unable to retrieve the requestedinformation. You will be notified of the error and nodata will be returned.

Administrator response:The administrator must verify that the networkconnectivity between the application and databaseservers is valid and that the database is running. Checkthe application server log file for error messages thatmay indicate a problem configuring the data source.

GYMVD0002W Time period does not align withaggregation period; Daily pre-aggregated data will be used

Explanation:A request is made to retrieve the pre-aggregated datafrom the database, but the specified start/end timesdo not align with the aggregation periods.

System action:The system will process the request by using the dailypre-aggregated data that best fits within the timeperiod specified by you.

User response:To avoid this situation, you must ensure that the startand end times specified for the API request align withthe aggregation periods configured within the system.

GYMVD0003E Specified entity name(s) are notunique: {0}

Explanation:The name(s) provided as API parameters are notuniquely identify specific entities.

System action:The system is unable to uniquely identify the entity forwhich information is requested. You will be notified ofthe error and no data will be returned.

Administrator response:The administrator must determine where the similarlynamed entities reside within the database and assignunique names.

GYMVD0003W Monthly dates do not align withaggregation period; Daily pre-aggregated data will be used

Explanation:A request is made to retrieve the monthly pre-aggregated data from the database, but the specifiedstart/end times do not align with the aggregationperiods.

System action:The system will process the request by using the dailypre-aggregated data that best fits within the timeperiod specified by you. Using the daily aggregateddata is less efficient than using the monthlyaggregated data.

User response:For best performance, you must ensure that the startand end times specified for the API request align withthe aggregation periods configured within the system.

GYMVD0004E Unable to determine numericidentifier(s) for entity name(s)

Explanation:The system is unable to locate the named entities inthe database.

System action:The system is unable to retrieve the requestedinformation from the database for the named entity.No data will be returned for that entity.

User response:You must ensure that the entity name(s) provided asAPI parameters are valid and that those entities exist.

GYMVD0004W Weekly dates do not align withaggregation period; Daily pre-aggregated data will be used

Explanation:A request is made to retrieve the weekly pre-aggregated data from the database, but the specifiedstart/end times do not align with the aggregationperiods.

System action:

Chapter 6. Messages 141

The system will process the request by using the dailypre-aggregated data that best fits within the timeperiod specified by you. Using the daily aggregateddata is less efficient than using the weekly aggregateddata.

User response:For best performance, you must ensure that the startand end times specified for the API request align withthe aggregation periods configured within the system.

GYMVD0005W Unable to retrieve registry value{0}

Explanation:The API request is not able to retrieve from theregistry the value corresponding to the specifiedregistry key.

System action:The system will attempt to process the request asappropriate without the registry value.

Administrator response:The administrator must examine the server logs forwarning or error messages that may indicate aproblem reading from the registry or verify that theregistry entry exists.

GYMVD0006E Unable to identify namedproperty: {0}

Explanation:The system is unable to locate the named property inthe database.

System action:The system is unable to retrieve the requestedinformation from the database for the named property.No data will be returned for that property.

User response:You must ensure that the property name provided asan API parameter is valid and that the property exists.

GYMVD0006W Unable to retrieve registry value{0}; Default value of {1} will beused

Explanation:The API request is not able to retrieve from theregistry the value corresponding to the specifiedregistry key. The specified default value will be used.

System action:The system will attempt to process the request byusing the default value.

Administrator response:The administrator must examine the server logs forwarning or error messages that may indicate aproblem reading from the registry or verify that theregistry entry exists.

GYMVD0007E Unable to identify named user: {0}

Explanation:The system is unable to locate the named user in thedatabase.

System action:The system is unable to retrieve the requestedinformation from the database for the named user. Nodata will be returned for that user.

User response:You must ensure that the user name provided as anAPI parameter is valid and that the user exists.

GYMVD0007W Unable to initialize the CORBAORB

Explanation:The system is unable to initialize and/or configure thecommunication between the DataView andDataChannel components necessary to support near-real time metric data or probe configuration.

System action:Near-real time metric data is not included in the APIresponse and the user will be unable to configureprobes.

Administrator response:The administrator must examine the server logs forwarning or error messages that may indicate thereason for the initialization failure.

GYMVD0008E Invalid time period: start time ={0}, end time = {1}

Explanation:The system is unable to retrieve the requestedinformation because the specified time period is notvalid.

System action:The system is unable to retrieve the requestedinformation from the database for the specified timeperiod. No data will be returned to the user.

User response:You must ensure that the start and end time are validand that the start time precedes the end time.

GYMVD0008W Unable to establish connection tonear-real time service

Explanation:The system is unable to initialize and/or configure thecommunication between the DataView andDataChannel components necessary to support near-real time metric data functionality.

System action:Near-real time metric data will not be included in theAPI response

User response:The administrator must examine the server logs forwarning or error messages that may indicate

142 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

networking problems. The DataChannel logs shouldalso be examined to determine whether CORBAconnections are being accepted.

Chapter 6. Messages 143

144 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Chapter 7. Contacting IBM supportIBM Support provides assistance with product defects, answering FAQs, and performing rediscovery.

Before you beginAfter trying to find your answer or solution by using other self-help options such as technical notes, youcan contact IBM Support. Before contacting IBM Support, your company must have an active IBMmaintenance contract, and you must be authorized to submit problems to IBM. For information about thetypes of available support, see the Support portfolio topic in the Software Support Handbook.

Procedure

Complete the following steps to contact IBM Support with a problem:1. Define the problem, gather background information, and determine the severity of the problem. For

more information, see the Getting IBM support topic in the Software Support Handbook.2. Gather diagnostic information.3. Submit the problem to IBM Support in one of the following ways:

• Using IBM Support Assistant (ISA):• Online through the IBM Support Portal: You can open, update, and view all your Service Requests

from the Service Request portlet on the Service Request page.• By phone: For the phone number to call in your country, see the Directory of worldwide contacts

web page.

ResultsIf the problem that you submit is for a software defect or for missing or inaccurate documentation, IBMSupport creates an Authorized Program Analysis Report (APAR). The APAR describes the problem indetail. Whenever possible, IBM Support provides a workaround that you can implement until the APAR isresolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support website daily, so thatother users who experience the same problem can benefit from the same resolution.

Exchanging information with IBMTo diagnose or identify a problem, you might need to provide IBM Support with data and information fromyour system. In other cases, IBM Support might provide you with tools or utilities to use for problemdetermination.

Sending information to IBM SupportTo reduce the time that it takes to resolve your problem, you can send trace and diagnostic information toIBM Support.

Procedure

To submit diagnostic information to IBM Support:1. Open a problem management record (PMR).2. Collect the diagnostic data that you need. Diagnostic data helps reduce the time that it takes to resolve

your PMR. You can collect the diagnostic data manually or automatically:

• Collect the data manually.• Collect the data automatically.

3. Compress the files by using the ZIP or TAR format.4. Transfer the files to IBM. You can use one of the following methods to transfer the files to IBM:

© Copyright IBM Corp. 2011, 2019 145

• IBM Support Assistant• The Service Request tool• Standard data upload methods: FTP, HTTP• Secure data upload methods: FTPS, SFTP, HTTPS• Email

All of these data exchange methods are explained on the IBM Support site.

146 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Notices

This information was developed for products and services offered in the US. This material might beavailable from IBM in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply that onlythat IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

© Copyright IBM Corp. 2011, 2019 147

Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.

The performance data discussed herein is presented as derived under specific operating conditions.Actual results may vary.

The client examples cited are presented for illustrative purposes only. Actual performance results mayvary depending on specific configurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to actual people or business enterprises isentirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work must include a copyright noticeas follows:

© (your company name) (year).Portions of this code are derived from IBM Corp. Sample Programs.© Copyright IBM Corp. _enter the year or years_.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks ortrademarks of Adobe Systems Incorporated in the United States, other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer and TelecommunicationsAgency which is now part of the Office of Government Commerce.

148 Notices

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon,Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation orits subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, orboth.

ITIL is a registered trademark, and a registered community trademark of The Minister for the CabinetOffice, and is registered in the U.S. Patent and Trademark Office.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos aretrademarks or registered trademarks of Oracleand/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, othercountries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. andQuantum in the U.S. and other countries.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBM website.

Personal use

You may reproduce these publications for your personal, noncommercial use provided that all proprietarynotices are preserved. You may not distribute, display or make derivative work of these publications, orany portion thereof, without the express consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within your enterprise provided thatall proprietary notices are preserved. You may not make derivative works of these publications, orreproduce, distribute or display these publications or any portion thereof outside your enterprise, withoutthe express consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, eitherexpress or implied, to the publications or any information, data, software or other intellectual propertycontained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use ofthe publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

Notices 149

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS AREPROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

150 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

IBM®