with ibm corp. · chapter 1. t roubleshooting t ivoli netcool performance manager y ou can use this...

IBM Tivoli Netcool Performance Manager 1.4.2Wireline ComponentDocument Revision R2E2

Troubleshooting Guide

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 173.

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

Contents

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

Fail to discover DASH in Topology Editor . . . 3Error when running DataView synchronize.shcommand . . . . . . . . . . . . . . 3Some of the Tivoli Netcool Performance Managercomponents still showing 1.4.1 version afterupgrading to Tivoli Netcool Performance Manager1.4.2 . . . . . . . . . . . . . . . . 4Database version is still showing 1.4.1 afterinstalling Tivoli Netcool Performance Manager1.4.2 . . . . . . . . . . . . . . . . 5

Troubleshooting tasks . . . . . . . . . . . 5DataMart process pismgr not getting started afterupgrade . . . . . . . . . . . . . . . 5Viewing online help in Acrobat Reader on AIX 7.1 6Real-time charts do not work as expected. . . . 7Error: ORA-00001:unique constraint(PV_ADMIN.PK_SEGM) violated . . . . . . 8MDE memory constraint . . . . . . . . . 8Incomplete SNMPv3 metric collection . . . . . 8Collectors swapping from idle to running atstartup . . . . . . . . . . . . . . . 9Specifying the Database Home directory path inthe non-default DB2 installation . . . . . . 10Changing DB_USERNAME for installing UBAAlcatel-Lucent 5620 SAM 2.13.0.0 . . . . . . 11Load pending state . . . . . . . . . . . 11LDR in unavailable state for long time . . . . 12

Searching knowledge bases . . . . . . . . . 13

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

Installation log files. . . . . . . . . . . 15DataChannel logs . . . . . . . . . . . 17DataLoad logs . . . . . . . . . . . . 19DataMart logs . . . . . . . . . . . . 19DataView logs . . . . . . . . . . . . 20Database log . . . . . . . . . . . . . 20

Logs messages format . . . . . . . . . . . 21Logging configuration and information utilities . . 22

DataChannel logs configuration . . . . . . 22DataView logs configuration. . . . . . . . 25statGet utility. . . . . . . . . . . . . 25

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

Troubleshooting . . . . . . . . . . . . . 29Event IDs . . . . . . . . . . . . . . . 29

Chapter 3. Introduction SNMPinventory. . . . . . . . . . . . . . 31Overview . . . . . . . . . . . . . . . 31Discovery . . . . . . . . . . . . . . . 31

Metrics and properties. . . . . . . . . . 32Inventory synchronization and change management 32

Change management for elements . . . . . . 32Change management for subelements . . . . 33

Grouping subelements. . . . . . . . . . . 34Where to go from here . . . . . . . . . . 34

Chapter 4. SNMP inventorytroubleshooting . . . . . . . . . . . 35Overview . . . . . . . . . . . . . . . 35Discovery troubleshooting . . . . . . . . . 36

Discovery does not start . . . . . . . . . 36dataload.env gets corrupted. . . . . . . . 42Discovery starts but issues warning messages . . 43Discovery seems to hang or never finishes . . . 49

Synchronization troubleshooting . . . . . . . 51Synchronization (elements) . . . . . . . . 51Synchronization (subelements) . . . . . . . 57

Grouping troubleshooting . . . . . . . . . 61Monitoring the Tivoli Netcool Performance Managerlog file . . . . . . . . . . . . . . . . 61Tivoli Netcool Performance Manager log messages 61Burned subelements . . . . . . . . . . . 61

Scenario 1 - instance shift causes disconnect . . 61Scenario 2 - instance shift causes burn . . . . 62

Where to go from here . . . . . . . . . . 63

Chapter 5. SNMP inventorymanagement . . . . . . . . . . . . 65Regular monitoring. . . . . . . . . . . . 65Routine SNMP inventory management tasks . . . 65

Finding elements and subelements about to reachtheir retry limit . . . . . . . . . . . . 65Finding elements and subelements that havebeen retired . . . . . . . . . . . . . 67

Chapter 6. Messages. . . . . . . . . 69DataChannel error messages. . . . . . . . . 69DataLoad error messages . . . . . . . . . 125DataView operational messages . . . . . . . 158

Chapter 7. Contacting IBM support 171Exchanging information with IBM . . . . . . 171

Sending information to IBM Support . . . . 172

Notices . . . . . . . . . . . . . . 173Trademarks . . . . . . . . . . . . . . 175Terms and conditions for product documentation 176

© Copyright IBM Corp. 2011, 2016 iii

iv IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

Chapter 1. Troubleshooting Tivoli Netcool PerformanceManager

You can use this troubleshooting and support information to troubleshootproblems with Tivoli Netcool Performance Manager.

This information assumes a working installation of Tivoli Netcool PerformanceManager. For installation or upgrade problems, refer to the installation andupgrade information.

Troubleshooting a problemTroubleshooting is a systematic approach to solving a problem. The goal oftroubleshooting is to determine why something does not work as expected andhow to resolve the problem.

The first step in the troubleshooting process is to describe the problem completely.Problem descriptions help you and the IBM technical-support representative knowwhere to start to find the cause of the problem. This step includes asking yourselfbasic questions:v What are the symptoms of the problem?v Where does the problem occur?v When does the problem occur?v Under which conditions does the problem occur?v Can the problem be reproduced?

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

What are the symptoms of the problem?

When starting to describe a problem, the most obvious question is “What is theproblem?” This question might seem straightforward; however, you can break itdown into several more-focused questions that create a more descriptive picture ofthe problem. These questions can include:v Who, or what, is reporting the problem?v What are the error codes and messages?v 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 themost important steps in resolving a problem. Many layers of technology can existbetween the reporting and failing components. Networks, disks, and drivers areonly a few of the components to consider when you are investigating problems.

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

© Copyright IBM Corp. 2011, 2016 1

v Is the problem specific to one platform or operating system, or is it commonacross multiple platforms or operating systems?

v Is the current environment and configuration supported?

If one layer reports the problem, the problem does not necessarily originate in thatlayer. Part of identifying where a problem originates is understanding theenvironment in which it exists. Take some time to completely describe the problemenvironment, including the operating system and version, all correspondingsoftware and versions, and hardware information. Confirm that you are runningwithin an environment that is a supported configuration; many problems can betraced back to incompatible levels of software that are not intended to run togetheror have not been fully tested together.

When does the problem occur?

Develop a detailed timeline of events leading up to a failure, especially for thosecases that are one-time occurrences. You can most easily develop a timeline byworking backward: Start at the time an error was reported (as precisely as possible,even down to the millisecond), and work backward through the available logs andinformation. Typically, you need to look only as far as the first suspicious eventthat you find in a diagnostic log.

To develop a detailed timeline of events, answer these questions:v Does the problem happen only at a certain time of day or night?v How often does the problem happen?v What sequence of events leads up to the time that the problem is reported?v 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 whichto investigate the problem.

Under which conditions does the problem occur?

Knowing which systems and applications are running at the time that a problemoccurs is an important part of troubleshooting. These questions about yourenvironment can help you to identify the root cause of the problem:v Does the problem always occur when the same task is being performed?v Does a certain sequence of events need to occur for the problem to surface?v Do any other applications fail at the same time?

Answering these types of questions can help you explain the environment inwhich the problem occurs and correlate any dependencies. Remember that justbecause multiple problems might have occurred around the same time, theproblems are not necessarily related.

Can the problem be reproduced?

From a troubleshooting standpoint, the ideal problem is one that can bereproduced. Typically, when a problem can be reproduced you have a larger set oftools or procedures at your disposal to help you investigate. 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 ofsignificant business impact, you do not want it to recur. If possible, re-create the

2 IBM Tivoli Netcool Performance Manager: Troubleshooting Guide

problem in a test or development environment, which typically offers you moreflexibility and control during your investigation.v Can the problem be re-created on a test system?v Are multiple users or applications encountering the same type of problem?v Can the problem be re-created by running a single command, a set of

commands, or a particular application?“Searching knowledge bases” on page 13You can often find solutions to problems by searching IBM knowledge bases.You can optimize your results by using available resources, support tools, andsearch methods.

Troubleshooting checklist for Tivoli Netcool Performance ManagerBy answering a set of questions that are structured into a checklist, you cansometimes identify the cause of a problem and find a resolution to the problem onyour own.

Answering the following questions can help you to identify the source of aproblem that is occurring with Tivoli® Netcool® Performance Manager:1. Is your issue a known problem?2. Is the configuration supported?3. What are you doing when the problem occurs?v Installing, upgrading, or migrating the productv Doing administration tasksv Doing authorization tasksv Networkingv 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 toeffectively troubleshoot and assist you in resolving the problem.

Known problems and solutionsA list of known problems and their solutions are described here.

For a list of known problems, see Release summary for Tivoli Netcool PerformanceManager 1.4.2.

Fail to discover DASH in Topology EditorSymptomsUnable to auto discover Dashboard Application Services Hub from the TopologyEditor if Tivoli Common Reporting is not installed in Jazz™ for ServiceManagement.

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

Error when running DataView synchronize.sh commandSymptoms

Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 3

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

Resolving the problemCopy the custom DataView content, such as JSP pages, CSS and images, from aremote Dashboard Application Services Hub to a local Dashboard ApplicationServices Hub.

Some of the Tivoli Netcool Performance Manager componentsstill showing 1.4.1 version after upgrading to Tivoli NetcoolPerformance Manager 1.4.2

SymptomsSome of the Tivoli Netcool Performance Manager components are still showingversion 1.4.1 after upgrade to Tivoli Netcool Performance Manager 1.4.2.

Resolving the problem

1. Log in as root user.2. Change to the following directory by using the following command:

cd <DIST_DIR>/proviso/<OS>/UPGRADE

For example:cd /TNPM142Installers/proviso/RHEL/UPGRADE

3. Run the following patch script manually by using the following command:./ptcload DB_patch_1410_1420

4. When you see a prompt message: “Do you want to continue (Y/N) [Y] ?”,enter “Y” to continue.

5. Enter all the required password based on your system setup.For example:Netcool/Proviso Patch loader - [settings] DB_patch_1410_14201. PROVISO_HOME : /opt/proviso2. ORACLE_HOME : /opt/oracle/product/12.1.03. ORACLE_SID : PV4. DB_USER_ROOT : PV5. DB_USER_PASSWD : *****6. ORACLE_OWNER : oracle7. SYSTEM_USER : system8. SYSTEM_PASSWORD : ******9. SYS_PASSWORD : ******10. DISCONNECT_CLIENTS_Y_N : Y11. Continue0. Exit

Choice [11] (type ?<n> to get help on item <n>)>

By default, the value for DB_USER_PASSWD is PV.By default, the value for SYSTEM_PASSWORD is manager.By default, the value for SYS_PASSWORD is oracle.

6. To continue with the patch script, enter 11. You will see the following messageupon completion. For example:Netcool/Proviso Database upgraded successfully !!!THIS INSTRUCTIONS FILE: /opt/proviso/patch/DB_patch_1410_1420/all_todo.txtGenerated : Tue May 24 2016 17:12====================================================================

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


DB_patch_1410_1420 : Upgrade from 1.4.1.0 to 1.4.2.0= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =Nothing else to do...

>>> Detailed information was logged in /opt/proviso/patch/log/PV/DB_patch_1410_1420.log

7. Run the command again to check the Tivoli Netcool Performance Managercomponent versions. It will now show the correct versions.

Note: The Tivoli Integrated Portal (TIP) version is still showing 1.4.1. This issuewill be fixed in the next release of Tivoli Netcool Performance Manager.

All Tivoli Netcool Performance Manager components are still

showing 1.4.1as the version. This issue will be fixed in the next release of TivoliNetcool Performance Manager.

Database version is still showing 1.4.1 after installing TivoliNetcool Performance Manager 1.4.2

SymptomsThe Database (DB) version is still showing 1.4.1 when you check the DatabaseInformation - Proviso Version from the DataMart GUI after installing TivoliNetcool Performance Manager 1.4.2.

Resolving the problem

1. Log in as root user.2. Change to the following directory by using the following command:

cd <DIST_DIR>/proviso/<OS>/UPGRADE

For example:cd /TNPM142Installers/proviso/RHEL/UPGRADE

3. Run the following patch script manually by using the following command:./ptcload DB_patch_1410_1420

This issue will be fixed in the next release of Tivoli NetcoolPerformance Manager.

Troubleshooting tasksSome troubleshooting tasks in Tivoli Netcool Performance Manager are describedhere.

DataMart process pismgr not getting started after upgradeDataMart process pismgr not getting started after Tivoli Netcool PerformanceManager 1.4.2 upgrade.

Symptoms

After you upgrade to Tivoli Netcool Performance Manager 1.4.2, you might receivethe following error when you start the pismgr DataMart process:


$ pismgr startThu 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, yousee the following error message:“The server could not be contacted. May be the Server or Registry is stopped.”

Resolving the problem1. Log in to the DataMart server as the DataMart software owner (by default,

pvuser).2. Change to the following directory <Datamart_HOME>/bin.

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.

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

CausesTivoli Netcool Performance Manager DataMart supports an Adobe Acrobat PDFhelp system. To view the online help on AIX 7.1, you need to add the acroreadbinary.

Resolving the problem1. 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 indicatesthe Acrobat Reader will not run on AIX 7.1. Click Yes to have Acrobat Readerproceed 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 isthe installation path.

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 expectedSymptomsSometimes when you restart the Tivoli Netcool Performance Manager ChannelName Server (CNS) or Channel Manager (CMGR) component, your real-timecharts no longer work as expected. Real-time charts require a valid reference to thereal-time subscriber object. A restart of these components can cause the ChannelName Server (CNS) to no longer provide a valid reference to the real-timesubscriber 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 theprevious output, the PID is 653.

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

4. Find the PID of the DataChannel CMGR component by using the followingcommand:./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 usingthe 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 followingorder:./cnsw./cmgrwd

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

<WAS_admin_password>


Error: ORA-00001:unique constraint (PV_ADMIN.PK_SEGM)violated

An unique constraint error is generated during inventory and grouping.

SymptomsThe 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 runsinventory grouping. If inventory grouping tries to place the same resource into thegroup, a unique constraint error is generated.

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

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

SymptomsThe 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

CausesYou 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 theresmgr command to insert a resource into a group and then runs inventorygrouping. If inventory grouping tries to place the same resource into the group, aunique constraint error is generated.

Resolving the problemThis error can be addressed with the following suggestions:v Reduce the time period used in the MDE query. If the time range is halved then

the space required should be halved.v Reduce the number of metrics requested. If the original request was for 5

metrics and you can reduce this by 1 metric, it should require approximately20% less space.

v If neither option is possible, then you can increase the size of thePV_LOIS_TEMP tablespace.

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

Symptoms


Some data loss can be observed from the “Expected measures” and “Producedmeasures” in the SNMP collector log message, especially when there is a suddendrop in “Produced measures” when compared with 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.

CausesThis is a thread-related issue that corresponds to insufficient resources to createanother thread, or there is a system-imposed limit on the number of threads to becreated.

Resolving the problemThis resolution is applicable only if the following warning message is displayedfirst to indicate that this is a thread-specific issue as there are many otherconfiguration 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 thecollector.

Note: This decreases the overall performance of the collector.

Concurrency is controlled by the GLOBAL.SNMP.MAXASYNC parameter, which isgiven the default value of 256. The default value can be changed by adding aCustom Datachannel parameter in the TNPM topology. This parameter can beadded using the Topology Editor: GLOBAL.SNMP.MAXASYNC=<value> where <value> isa number less than 256. w

Collectors swapping from idle to running at startupSymptomsThe situation may occur that a collector, upon startup, waits a period of time, thentransitions itself to running state only to be swapped to an idle state by the HighAvailability Manager (HAM).

CausesAt startup the Collector sits in 'Idle' state waiting to determine what it should donext ( if anything ). The HAM (High Availability Manager) should probe theCollector, discover its state, and instruct it to 'start' or to 'stay in idle' or to 'load'

’Start’ leads to running (active collection), ’load’ leads to ready (a sort of hot-sparemode ) and staying in ’idle’ means keep waiting.

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

Resolving the problemUser response:


If you this behaviour a problem, you update either the polling interval of theHAM or the idle timeout of the collector:v Increase the Collector's Idle Timeout by editing DataChannels > Global

DataChannel Properties > Advanced Properties > IDLETIMEOUT, orv Decrease the HAM's probe interval by editing DataChannels > Administrative

Components > High Availibility Managers > <HAM identifier> > Properties >POLL_INTERVAL

Specifying the Database Home directory path in thenon-default DB2 installation

Change in the default value of Database_Home path does not update other requireddirectory paths in the Topology Editor.

SymptomsAfter you install DB2 in a non-default location, you change the default path ofDatabase_Home directory while you add new host in the Topology Editor. However,it does not correctly update the other required directory paths.

For example, following are the directory paths where the non-defaultDatabase_Home directory path is not updated.v Database_Home_Root in Host’s propertiesv Target_Database_Home and DB2_BASE field in Database Configurations'

properties

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

User response:

1. The default DB2_BASE directory path is /opt/db2For example, your DB2 home directory is /opt/db23

2. 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 the Topology editor, see IBM Tivoli Netcool Performance Manager1.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:v Update the value of DB2_BASE in Database Configurations' properties to

/opt/db23

v Update the value of Database_Home_Root in host’s properties to/opt/db23/product

v 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 youchange the default DB2 directory path.


Changing DB_USERNAME for installing UBA Alcatel-Lucent5620 SAM 2.13.0.0

Changing DB_USERNAME from PV_INVENTORY to PV_ADMIN in datachannel properties inxml file that is generated from Topology Editor.

SymptomsWhen you install UBA Alcatel-Lucent 5620 SAM 2.13.0.0 with defaultconfigurations, for SAMIF component DB_USERNAME is PV_INVENTORY. Since in DB2,user name with more than 8 characters cannot have system level access likeworking with sysibm tables, you need to change the user PV_INVENTORY toPV_ADMIN.

Resolving the problemFollowing procedure shows how to change DB_USERNAME for UBA Alcatel-Lucent5620 SAM 2.13.0.0 in xml file.

User response:

1. The default configuration for UBA Alcatel-Lucent 5620 SAM 2.13.0.0 containsDB_USERNAME as PV_INVENTORY.

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

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 reasoncode "3" on table <schema_name>.<table_name>. SQLSTATE=57016

SQL0668N reason code 3 indicates that the table is in the Load Pending state. Aprevious LOAD attempt on this table resulted in failure. No access to the table isallowed until the LOAD operation is restarted or terminated.

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

User response:Select TABSCHEMA, TABNAME, LOAD_STATUS from SYSIBMADM.ADMINTABINFO whereload_status = ’PENDING’ and tabschema = "’<schema_name>’

Restart or terminate the previously failed LOAD operation on this table by issuingLOAD with the RESTART or TERMINATE option. You can use the following queryto 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 whereload_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, seev http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/

com.ibm.db2.luw.messages.sql.doc/doc/msql00668n.htmlv 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 DB2error:TEXT: [IBM][CLI Driver][DB2/LINUXX8664] SQL0438N Application raised error or warning withdiagnostic 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’"

If you find any rows that means the perticular partition is been locked by someapplication. You must restart or terminate the previously locked operation on thistable. by issuing the following commands from the db2 instance user.select* from sysibmadm.LOCKWAITS

Identify the agent id of main application holding lock from columnAGENT_ID_HOLDING_LK kill the culprit application 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


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.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

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

Searching knowledge basesYou can often find solutions to problems by searching IBM knowledge bases. Youcan optimize your results by using available resources, support tools, and searchmethods.

About this task

You can find useful information by searching the information center for TivoliNetcool Performance Manager, but sometimes you need to look beyond theinformation center to answer your questions or resolve problems.

Procedure

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

ISA is a no-charge software serviceability workbench that helps you answerquestions and resolve problems with IBM software products. You can findinstructions for downloading and installing ISA on the ISA website.

v Find the content that you need by using the IBM Support Portal.The IBM Support Portal is a unified, centralized view of all technical supporttools and information for all IBM systems, software, and services. The IBMSupport Portal lets you access the IBM electronic support portfolio from oneplace. You can tailor the pages to focus on the information and resources thatyou need for problem prevention and faster problem resolution. Familiarizeyourself with the IBM Support Portal by viewing the demo videos(https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos)about this tool. These videos introduce you to the IBM Support Portal, exploretroubleshooting and other resources, and demonstrate how you can tailor thepage by moving, adding, and deleting portlets.

v Search for content about Product X by using one of the following additionaltechnical resources:– Tivoli Netcool Performance Manager technotes– Tivoli Netcool Performance Manager Support Website– Tivoli support communities (forums and newsgroups)

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

v 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 toinclude information that is outside the ibm.com domain. However, sometimesyou can find useful problem-solving information about IBM products innewsgroups, forums, and blogs that are not on ibm.com.

Tip: Include “IBM” and the name of the product in your search if you arelooking for information about an IBM product.


http://www.ibm.com/software/support/isa/

https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos

http://www.ibm.com/search/csass/search?q=version%201.3&sn=spe&lang=en&filter=collection:stgsysx,dblue,ic,pubs,devrel1&prod=S153855L88022N79#q%253dtechnotes%2520and%2520apars%2526filter%253d%252bcollection%253astgsysx%252cdblue%252cic%252cpubs%252cdevrel1%2526prod%253dS153855L88022N79%2526sn%253dspe%2526lang%253den%2526sortby%253d%2526o%253d0

http://www-947.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Netcool_Performance_Manager

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Communities.html

Chapter 2. Logs (Wireline Component)

Tivoli Netcool Performance Manager has various logs that can be used to examineprocessing results and problems.

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

Table 1. The Tivoli Netcool Performance Manager logs by component

Component Description

DataChannel DataChannel manages the primary Tivoli Netcool Performance Managerproviso.log log file. This log file collects data from each DataChannelcomponent, and from the SNMP and BCOL collectors. DataChannel also createsthe tnpmlog.log log file that contains all logs of interest to the user.

DataLoad Separate log files capture events about the daemon start-stop sequence, SNMPactivity, and watchdog queries to determine that status of the daemon. Logdata is also written to the 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 TivoliNetcool Performance Manager communications, and database status.

Database The standard database log file.

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

Installation log filesA list of log files created by the Tivoli Netcool Performance Manager WirelineComponents during installation. Where relevant, recommendations regarding thedeletion of log files is provided.

Databasev /opt/Proviso/*

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

v /var/tmp/PvInstall/install.cfg

v /var/tmp/PvInstall/install.log

DataChannel

DataChannel installer logs to stdout and stderr so there are no logs resulting fromthe installation process.

DataViewv $home/DataView_InstallLog.log


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

DataMartv /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:v /tmp/ProvisoConsumer/log.txt

Deployment plan logs:v /tmp/ProvisoConsumer/Plan/logs/[INSTALL_<TIME_STAMP>

Deployer Ant logs:v /tmp/ProvisoConsumer/Plan/MachinePlan_<MACHINE_NAME>/logs

The best cleanup method for installation logs is to remove the/tmp/ProvisoConsumer directory when the system has been running long enough tovalidate all aspects of a working installation. A ProvisoConsumer directory iscreated in the /tmp directory of each server in the installation, not just for theprimary 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 thelog.properties file as follows: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 logsfor individual DataChannel components. The default location of these logs is/DCHOME/log, where DCHOME is the location of DataChannel on your system.

Note: DataChannel component logs are generated only when you enabledual-logging for the component. When enabled, dual-logging writes information toproviso.log and tnpmlog.log, and to the individual log for the DataChannelcomponent. For information about dual-logging, see “DataChannel logsconfiguration” on page 22.

Proviso.logproviso.log is the core Tivoli Netcool Performance Manager log file. It is alwaysrunning and continuously 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 23. At the end ofthe day, a timestamp is added to the file name (for example,2007.08.24_1188000000_proviso.log) and a new proviso.log file is created forcurrent processing.

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

The statistics are analyzed and an hourly system summary is provided per TivoliNetcool Performance Manager component. For example,2013.04.09-08.32.42 UTC UBA.8.200-8664:12997 PERF_INPUT_PROCESSING GYMDC10021ISAM_INVENTORY-sam_inventory_2013-04-09-08-30.csv: processed 3145 records in5.002 sec (37724.9 records/min), rejected 0 records.

This log file contains information about all DataChannel components and SNMPcollectors. The types of events that are logged are determined by the LOG_FILTERsetting, as described in “Topology Editor log settings” on page 23.

tnpmlog.logtnpmlog.log contains a subset of the messages written to the proviso.log file. Thesubset of messages placed in the tnpmlog.log file are only those messages that areof 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 23).

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:v <version and sequence number>: V1:1234

v <time stamp>: 2007.01.16-06.02.03 UTC

v <Component>-PID:T ID: CME.1.1-25201:3456

v <GYMXXXXXSeverity>:Unique ID format, for example GYMDC0412W, which consistsof

Chapter 2. Logs (Wireline Component) 17

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

v Category: DISCARDED_RECORDS

v Message Text: Got 4 duplicate records, Discarded 0, Total of 4 for mid:2206 rid: 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_RECORDSGot 4 duplicate records, Discarded 0, Total of 4 for mid: 2206rid: 200023263 4|4|2006| 200023263

Walkback logsWalkback logs are generated when a Tivoli Netcool Performance Managerapplication encounters serious problems. In most cases, walkback logs areproduced just before the application shuts down because of the error.

These logs are crucial for problem determination by IBM Technical Support. Thename of the file begins with walkback- and includes the DataChannel componentand 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 linesof a walkback log are useful. The following log entry is an example:

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 R2E2Build: Guam.156ORIGINATOR: ’an OracleThreadedConnection( hsvcctx = 245F374 )’PARAMETER: OrderedCollection (an OracleError)TEXT: ORA-01034: ORACLE not available

ORA-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 R2E2Build: Pico.27ORIGINATOR: 'a DB2ThreadedConnection( hsvcctx = 245F374 )'

PARAMETER: OrderedCollection (a DB2 Error)TEXT: DB2 not available

shared memory realm does not existSVR4 Error: 2: No such file or directory

Note: Walkback files must be manually deleted. Due to the DataChannel cronsettings, a process that fails is repeated every 5 minutes. Since a new walkback logis generated upon every failure, the result can be many unneeded files.


DataLoad logsDataLoad logs include the SNMP.log, pvmdmgr.log, and WatchDog.log logs. Thedefault location of these logs is the /DLHOME/log directory, where DLHOME is thelocation of DataLoad on your system.

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

By default, SNMP logs include the following recurring events:v Close hour eventsv Debug level changesv 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 asdescribed in the Configuring and Operating DataMart. On restart, the collectorswitches back to the permanent debug level (which by default is Fatal + Warning +Info messages). The permanent debug level is set through the Topology Editor.Changing the debug level is useful when a specific network device or device groupdoes not respond correctly to SNMP requests.

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

Occasionally, the PVM Collecting daemon is running message is displayed beforethe process is in complete run mode.

WatchDog logsThe daily DataLoad WatchDog.log file contains entries about pings sent to thecollector to ensure that the daemon is still running. The name of this log beginswith the date for which events are records, for example 2007.08.16WatchDog.log.

DataMart logsDataMart does not have a central log. Instead, DataMart information is written tolog files, such as logFile.PVM or TraceInventory.log, that are associated withindividual components or actions, such as Inventory. The default location of theselogs is the /DMHOME/log directory, where DMHOME is the location of DataMart onyour system.

Note: The inventory process does NOT automatically create a log. If inventory isrun as a cron entry, you must redirect the data to a specified log file, otherwise nolog data is stored. To show time stamps in inventory log initiated by cron, youmust 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 containsmessages that sequentially indicate the processing status of an inventory. Thefollowing example shows a typical Discover_Analyze entry in this log.


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

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

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

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

DataView logsDataView does not have a central log. Instead, DataView writes DataView traces tothe Jazz for Service Management.

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

Database log

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

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

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


Diagnostic logDiagnostic logs are not easy to read. These logs log all the logs fromnotification log plus some more error/warning logs. You can use themprimarily 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, whenDIAGSIZE parameter 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,v Diagnostic data directory path DIAGPATH = /opt/db2/sqllib/db2dump/v Current member resolved DIAGPATH = /opt/db2/sqllib/db2dump/v 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 PerformanceManager component, severity code, event ID, and event description.

The following table describes log message elements.

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.


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

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

Table 2. Log message elements. (continued)

Field Description

Component Name of Tivoli Netcool Performance Manager component and its process IDseparated by a dash (-). Names of Tivoli Netcool Performance Managercomponents are defined privately for each subsystem. DataChannel useschannel-based naming conventions (for example, CME.1.1), other subsystemscan develop their own conventions. Some components include both theprocess ID and thread ID separated by a colon (for example,CME.1.1-5638:415).

SeverityCode

Event severity code. For more information, see the description of theLOG_FILTER setting in “Topology Editor log settings” on page 23.

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

Description Description corresponding to the Event ID.

Logging configuration and information utilitiesYou can configure logging behavior or use information utilities to helptroubleshoot Tivoli Netcool Performance Manager components.

DataChannel logs configurationConfiguration options that govern DataChannel logging behavior are set by usingthe Topology Editor and are maintained in the database. Logging behavior can beset at three levels: DataChannel, specific DataChannel components, and allDataChannel components or ‘global'. Logging settings are controlled by the logconfiguration.

Table 3. DataChannel log configuration components.

Level Description

DataChannel Specify logging behavior for DataChannel, including the ChannelManager (CMGR), Channel Name Server (CNS), and ApplicationManager (AMGR). They override any conflicting options set usingGLOBAL. To specify, use the following syntax:

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

DataChannelComponent

Specify logging behavior for DataChannel components (UBA, FTE,CME, LDR, DLDR). They override any conflicting options set usingGLOBAL. To specify, use the 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


Table 3. DataChannel log configuration components. (continued)

Level Description

Global Specify logging behavior for all DataChannel components. To specify,use the following 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 bemade by the Installer. All components must be restarted to apply the changes. Thesettings include enabling/disabling central and local logging and tracing andchanging 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 thefollowing table.

Table 4. Log options in Topology Editor

Option Levels Description

DUAL_LOGGING GLOBALandComponent

Use true or false to turn dual logging on or off.When set to false at the GLOBAL level, only DataChannel logs aregenerated. When set to true at the GLOBAL level, individual logs for allDataChannel components are generated, in addition to the DataChannellog. 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

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=128Note: The syslog daemon must be running locally to have access to thelog host on the network.


Table 4. Log options in Topology Editor (continued)


FILTER or LOG_FILTER ALL The event types to log:

v F = Failure (a hard process error)

v E = Error (process termination or disk space problem)

v W = Warning (frequent messages that require no specific action)

v I = Information only messages

v 1 = Level 1 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

LOG_TRAP_HOST LOG Host where SNMP traps for specific types of log messages are sent.Example: LOG.LOG_TRAP_HOST=localhostNote: The rules file defining the message types must be installed andloaded.

LOG_TRAP_PORT LOG Port used by the host defined in LOG_TRAP_HOST.Example: LOG.LOG_TRAP_PORT=162Note: The rules file defining the message types must be installed andloaded.

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


Table 4. Log options in Topology Editor (continued)


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 locatedin thelog 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 areapplication-specific settings that affect only that application. ALL settings can beused as both global and application-specific settings.

DataView logs configuration


statGet utilitystatGet is a utility that is located at each collector and provides DataLoad statisticslike the statistics that are accessible from the Collector Information Tool GUI.statGet can be run on any local server, and is located in the following defaultlocations:v /opt/dataload/bin/

v /opt/datamart/bin/

Note: For remote systems, you must use the Collector Information Tool. For moreinformation, see the Configuring and Operating DataMart.1. Log into the server that is running Tivoli Netcool Performance Manager SNMP

DataLoad by entering the username and password you specified wheninstalling 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:

SyntaxstatGet [-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:

v objects - Lists all main classes of statistics counters.

v instances - Lists all instances of a specific statistic class.

v counters - Lists all counters names of a specific statisticclass.

v stats - Lists all counters values for a specific class,instance, and so on.

v requests - List all requests configured inside the scheduler.The requests objectType is the default objectType if no -loption is specified.

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

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

[-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 specificSNMP collector. If the flag is undefined, the PVM_SSDADDRESSenvironment variable is used. If the environment variable isalso undefined, the value ‘localhost' is used.

[-P <portNumber>] <portNumber> is the number of the listening port number forthe collector. If the flag is undefined, the PVM_SSDPORTenvironment variable is used. If the environment variable isalso undefined, the value 30023002 is used.

[-T <connectTimeout>] <connectTimeout> is the amount of time permitted toestablish a connection before a timeout. If the flag isundefined, a default value of 20 seconds is used.

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

-? Displays the statGet command reference page.

-version Displays the build version string.

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 ofcounters ‘Targets'.

statGet -l instances -o Targets

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

statGet -l stats -o Targets -i _Total

Get all currently configured requests inDataLoad.

statGet -l requests


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

Default logging levelYou use the configure command to configure the Jazz for Service Managementlogging level for Tivoli Netcool Performance Manager packages or components.

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

Trace logging for DataView


The configure commandConfigures the database connection information and the Dashboard ApplicationServices Hub logging level for the Tivoli Netcool Performance Managerinstallation.

You must restart the application server for your changes to take effect. When youhave restarted the server, the logging level you have selected becomes the defaultlogging 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> -type logging [-level <level>] [-package <package_name>][-module <module_name>]

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

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 DashboardApplication Services Hub. The default user name is smadmin .


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

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

jdbc Configures the JDBC database connection information.

loggingConfigures the Dashboard Application Services Hub logging level forthe Tivoli Netcool Performance Manager installation.

debug Configures 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 levelof detail. A wildcard selects 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 tojdbc:oracle:thin@:host1.company.com:1521:PV:

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.v Use DUAL_LOGGING to write component-specific log files in addition to

proviso.log.v CME “BUILD_TREE” messages indicate whether Formula Requests are deployed

and for how many subelements (Debug Level 2).v UBA “SCANNED_INPUT”, “PERF_ACQUIRE_ALL”, “START_INPUT”, and

“METRIC_STREAM_INFO” messages indicate if metric input is being retrievedand processed.

v UBA PERF_INVFLUSH messages indicate when discovered elements andsubelements are written to the database.

v Use StatGet to obtain SNMP DataLoad information.

Event IDsFor information about Event IDs that are used in Tivoli Netcool PerformanceManager logs, see Error Messages section in this guide..


Chapter 3. Introduction SNMP inventory

An introduction to the Tivoli Netcool Performance Manager SNMP Inventory.

OverviewTivoli Netcool Performance Manager allows the operator to decide how much theTivoli Netcool Performance Manager DataMart will rely upon the OSS Inventorysystem.

The Inventory system can be virtually anything from a full-featured commercialInventory package, to an EMS or Node Manager like HP Open View, to a flat filelike /etc/hosts . The minimum required is a list of the IP addresses of resources tomonitor.

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

Tivoli Netcool Performance Manager supports the following three modes ofelement and sub-element discovery:

Mode Inventory ContainsTivoli 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 thismode, Tivoli Netcool Performance Manager imports a list of elements and thenwalks through the MIB to discover the sub-elements. In the first mode, TivoliNetcool Performance Manager sweeps the network to discover the elements andtheir associated sub-elements.

DiscoveryThe discovery capabilities of Tivoli Netcool Performance Manager include somepowerful and flexible tools that allow you to determine exactly what Tivoli NetcoolPerformance Manager monitors, and how the subelements are labeled andgrouped.

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

Using a formula language, Tivoli Netcool Performance Manager can be configuredto walk through an element's MIBs to discover particular MIBs representing users,tunnels, protocols, service classes or other sub-elements. Particular OIDs can beused to automatically create a label for the subelement.

For example, the subelement label could be a combination of the element name,the interface, the port and 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 Performance Manager allows the operator to create any number ofuser-defined properties.

There are two main differences between metrics and properties. Metrics come froma monitored resource and are used to calculate statistics that are the basis ofperformance reports and alarm thresholds. Metrics are generally numeric valuesthat change frequently, like the number of packets transmitted or a resource'savailability.

Properties, by contrast, are values that change less frequently, such as the CIR(committed information rate) or the location of the element. Properties consist ofmetadata-like identifiers or labels for such things as the customer and/or theservices using a particular sub-element.

The values for properties can be discovered automatically from the monitoredresource, or they can be imported from Inventory, provisioning or from anotherOSS component.

Inventory synchronization and change managementSubelement properties such as the CIR or customer name can change. TivoliNetcool Performance Manager tracks the change and the time of the change, sothat reports are displayed correctly.

For example, utilization may be calculated against CIR. After the CIR is updated,reports must reflect the new value for utilization calculations. But reports thatshow dates prior to the CIR update must use the old CIR value. Tivoli NetcoolPerformance Manager manages this without error.

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

Change management for elementsThe Inventory must track changes so that continuity of meta-data associated withthe elements can be maintained.

Unfortunately, Inventory is not as simple as sweeping a range of IP addresses toidentify the network elements. That is just the beginning of the process. TheInventory must track changes so that continuity of meta-data associated with theelements (such as associations to customers, VPNs and services) can bemaintained. At least one additional challenge remains to keep the elementInventory accurate, as shown with these two problem statements:v IP Address changesv

Problem: If you are tracking a router by its IP address, and you discover a routerat a new IP address, how do you know if it is a new router, or an existing routerwith a changed IP address?Tivoli Netcool Performance Manager solves this problem by associatingadditional properties with each element which provide additional continuity andtrace-ability in the face of IP address changes. These additional properties can be


discovered from the device itself, like SNMP sysName, or gathered externally,like the name resolved from the IP address of the element's managementinterface.

v Name changesv

Problem: If you are tracking a router by its name, and you discover that thename 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 orany other single property. Instead, by tracking a combination of properties,Tivoli Netcool Performance Manager is able to provide continuity to inventoryeven when any of these properties change.

By automatically tracking changes to an element, rather than discovering it as anew element or forcing the operator to manually update the database, TivoliNetcool Performance Manager helps reduce operating costs as follows:v Performance and trend reports for the element show the entire history of the

element, without interruption.v Changes to the element are shown in historical reports so they can be correlated

to problems or changes in performance.v Meta-data, such as location, community string, or other properties remains

associated with the element, saving the operator from having to re-enter this.v Inventory accuracy is improved because the update operation is automatic, not

manual, eliminating errors.v 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 onsubelements, it is important to 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 Manager manages all of this automatically.

There are many reasons why the identifier (in SNMP, the Object Identifier, or OID)might change for a particular subelement. Assuming that the subelement is a portor virtual circuit residing on an interface, some of the changes will be due tofailure and recovery scenarios, or network reconfigurations due to growth:v Adding or removing an interface card can cause the SNMP indexes to shift for

other sub-elements.v The interface the subelement resides upon might fail, forcing the service

associated with the subelement to be moved to another interface.v 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 ismoved to another subelement

Most network changes should be invisible to customers. Their reports shouldreflect the quality of their service, and moves and changes to the network topreserve their service should be invisible to them. This is particularly important forSLA 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.

Chapter 3. Introduction SNMP inventory 33

Throughout the network changes, network operations and engineering staff musthave an accurate view of the actual sub-elements. For troubleshooting and capacityplanning purposes, they should have a historical view of performance and trafficon a particular port, with information on changes that have occurred.

Grouping subelementsProperties can be used to automatically group subelements.

For example, sub-elements can be grouped according to technology, customer,service or site. Groups can be hierarchical, so it is possible to create structures likethe following:v Site/Technology, to see all ATM SVCs in the New York POP.v Customer/Service, to show all of the services a particular customer has

subscribed to.v Technology/Site, to see which sites are generating the most Frame Relay activity.

Subelements can exist in multiple groups simultaneously. For example, asubelement might be part of a network operations group and a particularcustomer's group.

Where to go from hereRelevant information.

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

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


Chapter 4. SNMP inventory troubleshooting

Discusses SNMP Inventory troubleshooting for Tivoli Netcool PerformanceManager.

OverviewThe major phases of SNMP inventory.

The Tivoli Netcool Performance Manager SNMP Inventory consists of thefollowing three major phases, which usually happen sequentially:v SNMP Discovery

Detects all resources on a target network and creates a virtual image of thenetwork.

v SynchronizationCompares the virtual network image generated by the Discovery with therecords in the Tivoli Netcool Performance Manager database that were createdby the previous Inventory run. Any modifications (new, missing, or renamedresources, for example) are then synchronized through the application of variousalgorithms, and the new network image is written to the database.

v GroupingUpdates the grouping structure in the database, which determines the kind ofinformation that is to be collected on each resource, element, sub-element, andso forth.

In almost all cases, Tivoli Netcool Performance Manager SNMP Inventory requiresvirtually no operator intervention.

However, under certain circumstances, problems arise which you will need toaddress. The following sections discuss the more common problems you are likelyto encounter and - where possible -- provide suggestions for remedial actions.

It is strongly advised that you monitor the logs for potential error messages bydoing one of the following:v Running a Discovery from the command line.

If you run a Discovery from the command line, redirect STDER to a log file, asfollows:inventory -noX -action discovery -name lowell >output2>error_log

For a complete list of error messages written to the Tivoli Netcool PerformanceManager log file, see Messages section of this guide. For more information onusing the Tivoli Netcool Performance Manager log file, see See Monitoring theLog File.

v Running a Discovery from the DataMart GUIIf you use the DataMart GUI to initiate a Discovery, error messages will appearon theDataMart GUI > Resource tab > Inventory Tool iconLive Information tab.


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 followingsyntax:numberOfObjectsInInputQueue.numberOfThreadsRunning.numberOfElementsDiscovered

– SubElmt 0.0.0Indicates that progress of discovered sub-elements, using the followingsyntax: numberOfObjectsInInputQueue.numberOfThreadsRunning.numberOfSubElementsDiscovered

If after two minutes there is no change in these messages, the Inventory Tooldisplays a more detailed message like the following:2005/12/09 13:46:57 Current activity @ 2005.12.09-18.46.542005/12/09 13:46:57 Stage: IP done.12005/12/09 13:46:57 Stage: SNMP done.12005/12/09 13:46:57 Stage: Elmt 0.1.02005/12/09 13:46:57 W: R00004/192.168.80.22005/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 to Hang or Never Finishes.

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

Discovery does not startThe following sections offer the most common solutions to problems withDiscovery 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 isreturned: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}

Figure 1. Errors Displayed in the DataMart GUI


To troubleshoot this problem, do the following:

Procedure1. 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 followingcommand:$ dccmd -action status -pattern DISC.*.*

If the Discovery server is not running, the dccmd command returns output likethe 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 server for your deployment (in this example we useDISC.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.*.*

If the Discovery server is running, the dccmd command returns output like thefollowing: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 LineInterface .

Discovery fails because collector stops during discovery

About this task

If the collector stops during a Discovery, several different error messages arelogged. The most common error messages are the following:v Error: Aborted at March 14, 2005 10:21:58 pm

v Error: Connection refused

v Error: Discovery Server : Status of lowell : invalid CLIENTERR [DC1]R00015 Connection refused (-I 682 -D 0 -profil lowell -collectordev19.quallaby.com:3002 -nbGetIfAddress 100 -invFileTxt/opt/datamart/conf/inventory_subelements.txt -vname {} -intcollector 1)


Chapter 4. SNMP inventory troubleshooting 37

Procedure1. Log in as pvuser (or the user name that you specified during installation) on

the system where DataMart is installed.2. (Optional) Ensure that the database and Listener are running. For more

information, see the Tivoli Netcool 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.

4. Click on the Collector Information icon. The Collector Information Toolappears.

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, asfollows (in this example, the collector is dev19.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 2. DataMart GUI

Figure 3. Collector Information Tool


What to do next

ACTION: Restart the collector by entering the following command on the Collectorserver:/opt/dataload/bin/pvmdmgr start

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 notstart because inventory is locked

About this task






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

Figure 4. Stopped Collector


5. Click Live Information. If the profile is locked, you will see a warning messagelike the one displayed in See Inventory Tool.

6. To confirm that the profile is locked, return to the DataMart GUI and click onthe Monitor tab->DataMart Status icon. The DataMart Status Tool appears.

In this example, the Inventory profile lowell is locked by an Inventory processwith a PID of 13458.

7. Determine if the lock is valid and if the process is still running, by entering thefollowing command, replacing LOCK_PROCESS_PID with the PID of thelocking 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 theInventory completes before 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 ofthe toolbar.

Figure 5. Inventory Tool

Figure 6. DataMart Status Tool


The qPing utility has incorrect settingsAs part of Discovery in Inventory Mode 1, Tivoli Netcool Performance Managerscans IP ranges using the DataLoad 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, andexecute permissions are not set correctly on the file:Inventory Tool



the system where the DataLoad server is installed.2. Change your working directory to $PVMHOME/bin ( /opt/dataload/bin by

default), and enter the following command to check the settings on the qPingutility:cd $PVMHOME/binls -l ./qPing

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/qPingchmod 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) allowsthe utility to be executed as root by any UNIX user belonging to the pvusersgroup.

dataload.env gets corruptedThe dataload.env may get corrupted due to many actions being performed such asadding or removing multiple SNMP collectors.

About this task

Even though collectors are present on the host, dataload.env may give faultyrepresentation 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 onthat host. To trigger generation of dataload.env, we need to perform eitheraddition or removal of collector. As it displays NA, we can only add collectors.


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

Default location: /opt/IBM/proviso/topologyEditorDepending on your database go to location /ora/metadata/core/ for oracle orgot to location /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", in host.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" in properties section.If the values are notupdated properly, manually edit it with the correct values.

9. Save topology, and run for Installation. Correct dataload.env is generated.10. Check dataload.env

$ source /opt/dataload/dataLoad.env

Note: Next time if you want to add or remove collector, just confirm whethercorrect values are going into the above mentioned properties. If not, thenrepeat 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 thatoccur during Discovery.

IP addresses are rejectedIf an IP address is rejected during Discovery, errors will be written to the log orwill display on the Information 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:





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 appearswith the Configuration displayed, as shown in See Inventory ToolConfiguration 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 ToolWizard.

c. Click the Next button twice to navigate to the Discovery Tool Wizard, asshown in See Discovery Tool Wizard.

Figure 7. Inventory Tool Configuration Tab

Figure 8. Inventory Tool Wizard


5. As shown in See Discovery Tool Wizard, check to see if the rejected IPaddresses - either individually or within a specified range - have beenintentionally 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 associatedwith it, Tivoli Netcool Performance Manager will "discover" the element multipletimes, reject the duplicates discoveries, and write warning messages to the log.

About this task

See Rejected Duplicate Elements, for example, shows Tivoli Netcool PerformanceManager rejecting three duplicate elements.

This is expected behavior.

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

Figure 9. Discovery Tool Wizard

Figure 10. Rejected Duplicate Elements


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

Procedure1. Invoke the Discovery Tool Wizard (DTW). For instructions on how to invoke

the DTW, see See Invoke the Discovery Tool Wizard by doing the following:.2. Add the duplicated IP addresses to the IP address exclude area of the DTW, as

shown in the following figure:

Elements are not identified during discoveryIf DataLoad did not receive an SNMP answer using the community nameconfigured in the Tivoli Netcool Performance Manager profile, warning messagesare created.

About this task

Warning messages like the following are written to the log and displayed on theLive Information Tab of the 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:

Figure 11. IP address exclude area of the DTW


v The device is not reachable from DataLoad collector (for example, no networkroute).

v The SNMP agent was not started in the device.v Tivoli Netcool Performance Manager has the wrong SNMP community name for

the device.v The device Access List is preventing Tivoli Netcool Performance Manager

DataLoad to act as an SNMP Manager for this device.v The firewall configuration is preventing SNMP traffic with the device.

To troubleshoot this problem, follow these steps:



information, see Installing Tivoli Netcool Performance Manager.3. Change your working directory to DATAMART_ROOT/bin, replacing

DATAMART_ROOT with the root DataMart directory ( /opt/datamart bydefault).

4. Perform an Internet Control Message Protocol (ICMP) query on the device, byentering the following command, replacingIP_ADDRESS_OF_UNIDENTIFIED_DEVICE with the IP address of the unidentifieddevice, 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 unidentifieddevice, 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 enabledand 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 Wizardto add an "alternate" community name to the profile.To change the community name, follow these steps:a. Invoke the Discovery Tool Wizard (DTW). For instructions on how to

invoke the DTW, see See Invoke the Discovery Tool Wizard by doing thefollowing:.

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


Elements skipped because no related subelementsWhen Tivoli Netcool Performance Manager discovers an element but cannotdiscover any related subelements, warning messages are written to the log anddisplayed on the Information Tab of the Inventory 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:


the system where DataChannel is installed.2. Change your working directory to $DC_HOME/log (/opt/datachannel/log, by

default), by entering the following command:cd $DC_HOME/log

3. Enter the following command to search the proviso.log for the Discoveryformula of the skipped element, replacing EL_IP_AD, with the IP address ofthe skipped element:grep DISC proviso.log | grep R00020 | grep ELS_IP_AD | grepCHKDISCOVERY

4. If he grep command returns no output.

Figure 12. Discovery Tool Wizard


If the grep command does not return output, the content of the following filesin the $PVMHOME/conf directory ($PVMHOME is defined as /opt/datamart, bydefault):v $PVMHOME/conf/inventory_elements.txt

v $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 2CHKDISCOVERY 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 2CHKDISCOVERY R00020/192.168.68.173. Family:1213_Device, trydiscoveryFormula Formula (1213_Device - 4851)

2005.03.15-18.58.45 UTC DISC.DEV19.1-13308 2CHKDISCOVERY 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 and monitor the trace, using the DataMart->Metric->Formula Editor, as shown in the following figure:

b. Activate the relevant portion of the device MIB (for example SAA in theCisco router).

Figure 13. Formula Editor


c. In some cases, SNMP attributes do not respond properly, and the Discoveryformula for those devices must be changed. In this event, contact IBMsupport.

Discovery seems to hang or never finishesIf the Discovery server shows no progress for several minutes it has probablyencountered problems with a Discovery formula.

About this task

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

Problems - real or apparent - with Discovery formulas can be the result of thefollowing:v The SNMP agent is slow to respond.v The network latency is very long.v The Discovery formula is not well-suited to the SNMP agent.v Collector performance issues.

When Tivoli Netcool Performance Manager is in such a state one of two thingsresult:v The Discovery formula finally succeeds and the Inventory continues.v 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 ortimes out, do the following:

Procedure1. Determine which Discovery formula is causing the problem by doing the

following:

Figure 14. Discovery formula


a. Log in as pvuser (or the user name that you specified during installation) onthe system where DataChannel is installed.

b. Change your working directory to DATACHANNEL_ROOT/log, replacingDATACHANNEL_ROOT with the root DataMart directory ( /opt/datachannelby default).

c. Enter the following command to search the proviso.log for the Discoveryformula:grep DISC proviso.log | grep R00010 | tail -1

2005.03.15-20.32.16 UTC DISC.PVDEMO2.1-1048 2CHKDISCOVERY 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) onthe system where the DataMart or DataLoad server is installed.

b. Change your working directory to DATAMART_ROOT/log, replacingDATAMART_ROOT with the root DataMart directory ( /opt/datamart bydefault).

c. Enter the following command to find the internal request ID, replacingSERVER_NAME with the name of the Tivoli Netcool Performance ManagerDataMart 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 logwith additional information by doing the following:a. Change your working directory to /opt/dataload/contribs .b. Enter the following command, replacing TASKID with the Internal request

ID you found in See Determine the internal request ID that is stuck bydoing 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 comparesthe virtual network image generated by the Discovery with the records in theTivoli Netcool Performance Manager database that were created by the previousInventory run.

Any modifications (new, missing, or renamed resources, for example) are thensynchronized through the application of various algorithms, and the new networkimage is written to the database.

In order to track elements and sub-elements through subsequent inventories, TivoliNetcool Performance Manager identifies them with a unique, never-changingidentifier, called an invariant.

The default element invariant, for example, is a concatenation of the followingthree attributes:v The MIB II sysName

v The first IP address responding to the ICMP scan (in Inventory mode 1) or theone given in the the mode 2 Inventory file

v 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 hasmoved or changed.

Synchronization Invariant Logic

Element Attributesin Database

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

Defined Defined Defined Two or threeattributes havechanged.

Empty Defined Defined Two attributes havechanged.

Empty Empty Empty The resolved name isdifferent fromresolved name in thedatabase.

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

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


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

The list contains the following types of elements:v Newv Updatedv Burnedv Unchangedv Not Foundv Histo Reject

See Pre-synchronization summary shows the display written to the DataMart >Inventory Tool > Live Information, with this summary information highlighted:

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 three examples.

Figure 15. Pre-synchronization Summary


Identifying burned elementsHow to identify burned elements

In cases where the MIB II sysName, IP address, and physAddress are all defined foran element (the first row in See Synchronization Invariant Logic), Tivoli NetcoolPerformance Manager may encounter a special situation if the MIB II sysName andphyAddress have changed, but the IP address remains unchanged.

In this special case, Tivoli Netcool Performance Manager creates a new elementand writes it to the database. However, since the IP address for "both" elements isthe same, so too is the resolved name, which means that the elements would beseen by Tivoli Netcool Performance Manager as the same element.

To prevent this situation, Tivoli Netcool Performance Manager renames the initialelment with a "Burned" prefix, as shown in “Identifying burned elements”:

When Synchronization completes, a list of burned elements is written to thefollowing 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 statisticsattached to these resources are not continuous in reports.

Preventing burned elementsTivoli Netcool Performance Manager relies quite heavily on the sysName whencalculating invariants. When using sysName you need to prevent burned elements.

About this task

To prevent burned elements, so the following:

Figure 16. Burned Element


Procedure1. 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.4. Minimize any changes to the sysName once they have been set, unless you want

Tivoli Netcool Performance Manager to see the device as new and interrupt thecontinuity of statistics.

Detecting too many new elementsIf there has been extensive configuration changes before an Inventory run (forexample, if two attributes were changed simultaneously on a router), TivoliNetcool Performance Manager will discover and create a new element in thedatabase.

About this task

The consequences are severe:v The element and its sub-elements are duplicated.v The statistics attached to these resources are not continuous in the reports.v 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 tworuns of an Inventory, there is no way to prevent this situation from occurring.

When Synchronization completes, a list of new elements is written to the followingfile. Note that $PVMHOME is defined as /opt/datamart , by default:$PVMHOME/importexport/PROFILE_NAME/synchro/new_e.dat

Procedure1. 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 isdiscovered.

Detecting different elements resolved with the same nameIf the name resolution system (for example, DNS) assigns identical names to the IPaddresses of different devices - a configuration mistake - Tivoli NetcoolPerformance Manager will an error during Synchronization.

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 thefollowing file:PROFILE_HOME_DIRECTORY/PROFILE_NAME/synchro/duplicateElement_e.reject

If you have a duplicateElement_e.reject file, do the following:


Procedure1. From the DataMart server, resolve the name of both conflicting IP addresses, in

order to confirm the identical naming resolution.2. Fix the naming resolution system and start the same Inventory again.

Do not delete incorrectly named elements that define SNMPcommunity namesConfiguring Tivoli Netcool Performance Manager involves associating elementswith their SNMP Community name.

About this task

When initially configuring Tivoli Netcool Performance Manager, you use theSNMP Configuration Tool, as shown in See Configuring SNMP CommunityNames, to associate elements with their SNMP Community name so that TivoliNetcool Performance Manager can read from the devices.

The SNMP Configuration Tool writes this information to the database.

During the next Inventory run, the synchronization process sees the elements thatwere newly entered into the database by the SNMP Configuration Tool as missingall three invariant attributes (see row three in See Synchronization Invariant Logic).

Figure 17. Configuring SNMP Community Names


Tivoli Netcool Performance Manager then attempts to determine if a new elementneeds to be created by comparing the resolved names of the devices, with thefollowing results:v If the name that was entered into the SNMP Configuration Tool was the correct

resolved name of the device, Tivoli Netcool Performance Manager will not createa new element and will instead update the attributes for the existing elementwith the discovered values.

v If the name that was entered into the SNMP Configuration Tool was theincorrect resolved name of the device, Tivoli Netcool Performance Manager willcreate a new element. On subsequent Discoveries, Tivoli Netcool PerformanceManager will rediscover and eventually update this element and ignore theelement with the incorrect resolved name.

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 SNMPCommunity name mapping. If the entry is removed, Tivoli Netcool PerformanceManager will lose the SNMP Community mapping and will not be able to readfrom that resource.

Failed synchronizationPay particular attention to failed elements while monitoring the Synchronizationprocess

About this task

While monitoring the Synchronization process, pay particular attention to failedelements.


Procedure

If Synchronization reports failed elements (greater than 0), contact IBM supportimmediately.

Synchronization (subelements)The subelement invariant is defined in the Discovery Formulas referenced in thefile $PVMHOME/conf/inventory_sub_elements.txt .

Note that $PVMHOME is defined as /opt/datamart by default.

This invariant is usually defined differently per object type (for example, an SAAprobe) and vendor (Cisco, for example).

The logic used to decide if a "newly-discovered" subelement is in fact new,depends on the following:v If the invariant is not defined, the subelement name (usually the concatenation

of the element name and the SNMP instance) is used to determine if a newsubelement should be created or an existing one should be updated.

Any change to the name between two subsequent Discovery runs triggers thecreation of a new subelement.

Figure 18. Failed Elements and the Inventory Tool


An SNMP index (instance) change will trigger the creation of a new subelement(because the SNMP index is part of the name), which will cause reportingdiscontinuity.v If an invariant is defined, the parameter " Enforce Sub-Element Invariant

uniqueness per element " is used, 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 perelement basis; if left unchecked, uniqueness is verified across the entire profile.

Identical subelement invariantIf an invariant is defined for a particular type of subelement (for example, CiscoSAA), Tivoli Netcool Performance Manager will check the uniqueness of thatinvariant during an SNMP Inventory.

About this task

If Tivoli Netcool Performance Manager detects two subelements with the sameinvariant, it displays an error 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 thedatabase.

To resolve this situation, follow these steps:

Procedure1. 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:v The Discovery formula needs to be changed to ensure the uniqueness of

either the element or the profile. This is usually done by concatenating moreOIDs to the invariant.

v The SNMP OID value, used for building the invariant, needs to be changed.For example, if you use the Cisco ifAlias settable OID, its value might not


be unique (among other things, a configuration error may exist due to anon-unique Customer contract number, which should be fixed.

v Discovery should then be re-triggered, so that both subelements can bediscovered.

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.

You should review the $PVMHOME/log/TraceInventory.log file and check for thefollowing:

Large number of subelements not found:

A large mount of "missing" sub-elements (discovered before, but not rediscovered),may be because a large portion of your network is not reachable.

About this task

If the same sub-elements are continually not found during subsequent Inventories,they will eventually be retired. For more information, see “Finding elements andsubelements about to reach their retry limit” on page 65.

Procedure

If your network is reachable, the sub-elements exist, and you are still receivingerror messages, contact IBM support.

Rejected subelements:

The log may report types of rejected subelements.

Procedure

If the log reports any of the following types of rejected sub-elements, contact IBMsupport:v histo rejectv dup reject

Figure 19. TraceInventory.log File


Burned subelements:

Procedure for dealing with burned subelements.

About this task

A burned subelement is determined as follows:v The subelement has an invariant in the database (for example, inv1).v The subelement has a name (for example, name1).v 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 withthe same name.

To prevent this duplication, Tivoli Netcool Performance Manager renames theinitial subelement with a "Burned" prefix, so that each subelement can be stored inthe 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 subelements:

Procedure for dealing with disconnected subelements.

About this task

A disconnected subelement is determined as follows:v The subelement has an invariant in the database (for example, inv1).v The subelement has a name (for example, name1).v 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 physicalresources (ports, for example) to customers.

In this case, the empty invariant is interpreted as a "disconnection" between thecustomer and the resource.

If a subelement is determined to be disconnected, no new subelement is created,and the initial subelement 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 nonearise - it is unlikely that you will encounter problems with grouping.

Monitoring the Tivoli Netcool Performance Manager log fileThe Tivoli Netcool Performance Manager log file is located in theDataChannelInstallROOT/log directory (/opt/datachannel/log, by default) andshould be monitored on a regular basis.

Currently, only DataChannel and DataLoad write to the Tivoli NetcoolPerformance Manager log. Log files for other components can be found in$PVMHOME/log ( /opt/datamart/log, by default) and SILVERSTREAM_HOME/log (/opt/silverstream/log, by default).

You can write a program to do monitor the Tivoli Netcool Performance Managerlog file (recommended) or you can check the Tivoli Netcool Performance Managerlog file by hand, using the grep command.

For example, the following command checks the Tivoli Netcool PerformanceManager log file for a fatal loader 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 PerformanceManager log, see Messages section.

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.v If its Element is burnedv 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 StateMissingCount

200000431 alm00142061.elt01 <04> 200000450 alm00142061.elt01.seinv04I:01:04 on 0



During a subsequent Discovery the following occurs:v The SE with Invariant I:01:05 is not foundv The SE with Invariant I:01:06 is found, but at Instance <05>


Result:v The SE with Invariant I:01:05 is marked missing because it is not in the

Discoveryv 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 Instancev The SE with Invariant I:01:06 is updated (Instance, Name, Label, etc.), but retains

the same dbIndex and Invariant


200000431 alm00142061.elt01 <04> 200000450 alm00142061.elt01.seinv04 I:01:04 on 0


200000431 alm00142061.elt01 Disconnected_200000449_<05>200000448Disconnected_200000449_alm00142061.elt01.seinv05

I:01:05 off 1

In theory, a Disconnected resource could come back; the Invariant is the uniqueidentifier to indicate the return of the SE. The Disconnected resource attempting toreturn would also have to have a different Instance in order to return. ElementName and Instance are required to be unique across all subelements.

Scenario 2 - instance shift causes burnInitial Discovery finds three subelements without Invariant and three subelementswith Invariant.


200000432 alm00142061.elt02 <01> 200000437 alm00142061.elt02.seinv01 on 0






During a subsequent Discovery the following occurs:v The SE that was at Instance <03> is not found in Discoveryv The SE with Invariant I:01:06 is found, but at Instance <03>

Result:v The SE that was at Instance <03> is marked missing because it is not present in

Discoveryv 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 Instancev The SE with Invariant I:01:06 is updated (Instance, Name, Label, etc.), but retains

the same dbIndex and Invariant









200000432 alm00142061.elt02 Burned_200000435_<03>200000435 Burned_200000435_alm00142061.elt02.se03off 1

Burned resources cannot come back, there is no Invariant to uniquely identify theSE in Discovery as that which was Burned. If the Burned resource attempted tocome back without Invariant and with the same Instance, Inventory would rejectboth because of a duplication on Element Name and Instance that cannot beresolved.

Where to go from hereRelevant information

For information on periodic administrative tasks to perform, see Chapter 3,“Introduction SNMP inventory,” on page 31


Chapter 5. SNMP inventory management

Discusses SNMP inventory troubleshooting for Tivoli Netcool PerformanceManager.

Regular monitoringMonitoring actions have to be performed regularly to keep the SNMP Inventoryprocess of Tivoli Netcool Performance Manager performing optimally.

If your SNMP Inventory is triggered every day, we recommend performing thesemonitoring actions at least once a week.

If your SNMP Inventory is triggered several times a day (for example, every sixhours), we recommend performing 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 retrylimit

When elements and subelements reach their retry limit, they are retired from theInventory, which means that Tivoli Netcool Performance Manager stops collectingon them and removes them from some groups.

About this task

The retry limit is set and managed in the DataMart > Inventory Tool > EditProfile > Synchronization Wizard. The default is three retries and a resource thatis older than seven days, as shown in the following figure. BOTH limits must bemet in order for a subelement to be retired.


To find elements and subelements about to reach their retry limit, do the following:


the system where DataMart 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 retrycounter, using greater than 2 (>2) for the retry count and 3 (the default) tospecify the age of the resource.v 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|_|

v 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|_|

Figure 20. Synchronization Wizard


For more information on the resmgr command, see the Tivoli NetcoolPerformance Manager Command Line Interface Guide.

What to do next

ACTION: If the elements or subelements are in the "off" state, then they will beretired. If they are in the "on" state, but are approaching both their age limit andretry limit, they are about to be retired. The commands in this section search forelements and subelements that are in the "on" state, but will soon be retired.

To address this problem, do the following:1. Fix the connectivity problem so that Tivoli Netcool Performance Manager can

discover the element or subelement about to be retired.2. Check to see if there is a problem with the SNMP community name that is

preventing Tivoli Netcool Performance 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 retiredAbout this task

As explained in “Finding elements and subelements about to reach their retrylimit” on page 65, when an element or subelement exceeds its Inventory Retry andInventory Timeout limits, it is changed to the "off" state and retired from theInventory.

To detect elements and subelements that have been retired, do the following:


the system where DataMart 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.v 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|_|

v 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 NetcoolPerformance Manager Command Line Interface Guide.

Chapter 5. SNMP inventory management 67

What to do next

IBM recommends the following Best Practices when dealing with retired elementsand subelements:v Group them in a special group (for example, the retired group) and periodically

check its content.v 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 the database, so they will not overload the "retired" group, which willbe kept at a manageable size.


Chapter 6. Messages

A list of error and operational messages generated by the Tivoli NetcoolPerformance Manager components.

DataChannel error messagesLists reference format error messages produced by DataChannel. Wheneverpossible, explanations are offered, as well as remedial actions.

GYMDC10000W error_description Restarting becauseof unknown error:

Explanation: An unknown error occurred

User response: Contact technical support

GYMDC10001F

Explanation: Configuration of specified Corba service(i.e. name service, event service) failed at componentstartup.


GYMDC10002F

Explanation: Component startup failure. Incorrectconfiguration or missing components

User response: Verify Netcool/Proviso configurationfile

GYMDC10003F No collectors defined in registrytable

Explanation: Database configuration forcollectors/channel is not specified properly

User response: Check installation for this (sub)channel

GYMDC10004F error_description Shutting down theimage with error:

Explanation: Unhandled fatal runtime exception --application produces walkback file and shuts down

User response: If the condition causing failure istransient, the application will restart automatically andin many cases will continue. If the problem persists,contact technical support


GYMDC10005W end start rid mid Timed Out duringTS query for mid:

Explanation: CME experienced a timeout during atuple storage query

User response: Check connectivity and make sureother components are running

GYMDC10006F end start rid mid app name label TimedOut during tuple query for label

Explanation: PBL is paused pending manualintervention. Contact technical support to fix FRMI bugand have formula -> label data manually corrected

User response: Manually fix the problem and removeSTOP file in the PBL root directory. If problem persists,contact technical support

GYMDC10007W Too many failed acquisitionattempts, giving up on remainder ofinput acquisitions

Explanation: While trying to acquire input files,multiple errors occurred and no further attempts willbe made to acquire files on this poll. Acquisition willresume on the next poll.

User response: Look for messages in the logs thatindicate failures to acquire specific files andtroubleshoot the reasons for the failures. Try andacquire the problematic files manually using FTP orSFTP and check that the expected files and directoriesexist and can be accessed.

GYMDC10008 schema_names Waiting For Data ForSchemas:

GYMDC10009W Stopping plan builder because plansave to db failed

Explanation: The plan builder has been stoppedbecause saving the plan to the database has failed

User response: Review the proviso.log file for anypreviously reported warning messages from the planbuilder

GYMDC10010W specificLabels timeSeriesspecificFormulas There are multiplespecific formulas:

Explanation: You cannot have multiple specificformulas for the same resource doing a specific togeneric conversion where the specific timeseries are indifferent labels because the plan builder does not knowwhich label to assign to the generic timeseries. Theplan builder with pick any of the specific labels toassign to the generic timeseries.

User response: Review all specific formulas for this

generic formula and review all specific formulas forthis resource.

GYMDC10011W timeseries Skipped building inputfor

Explanation: Unable to build input becuasesubelement is inactive, or it has no element or elementscollector is wrong

User response: Check to to see if subelement is activeand has an element and the collector is right

GYMDC10012W requests timeseries There are toomany specific formula requests for

Explanation: There should only be one specificformula request for a timeseries

User response: Figure out why there are more thanone specific timeseries for the same resource andformula. Check requests.

GYMDC10013

GYMDC10014W errorDescription

Explanation: An exception occurred while trying tocontact the SAM server

User response: Check that server is reachable

GYMDC10015W schema_name Not acquiring databecause do directory at max hours for

Explanation: Indicates that the UBA has stoppedacquiring data because the "do" directory has too manyhours worth of data queued up to be processed.

User response: It may not be necessary to doanything. As the UBA processes data and catches up,this situation will correct itself. The amount of dataallowed in the "do" directory is controlled by theFC_MAX_DO_HOURS configuration setting.

GYMDC10016 count Acquired files in

GYMDC10017 count count count period stream_name

GYMDC10019 count_seconds total_count count Found

GYMDC10005W • GYMDC10019


GYMDC10020 count_seconds count Acquired

GYMDC10021I

GYMDC10022 reason period stream_name

GYMDC10023W file name Skip processing

Explanation: The given input file is not beingprocessed because a collector number could not bedetermined.

User response: Double check that the input filenameand contents are not malformed.

GYMDC10024

GYMDC10025

GYMDC10026

GYMDC10027

GYMDC10028I

GYMDC10029

GYMDC10030

GYMDC10031 count count count period stream_name

GYMDC10032 count_seconds total_count count Found

GYMDC10033W error description file name schema nameFailed to acquire

Explanation: The UBA failed to acquire the indicatedfile.

User response: Check the connectivty between theUBA and the file, ftp or sftp server. Connect to the file,ftp or sftp server by hand from the same host and userid as the UBA and make sure the directory and fileindicated in the URI exists.

GYMDC10020 • GYMDC10033W

Chapter 6. Messages 71

GYMDC10034W reason Timezone database failed toload:

Explanation: The timezone database failed to loadfrom the ZoneInfo(TZ) DB on the host.

User response: Double check the installation of theZoneInfo(TZ) database on the host where the problemis occurring.

GYMDC10035W

Explanation: An upstream PvUrl was registered withmissing information

User response: Check the upstream component'sAMGR settings for disk usage server DUS

GYMDC10036W

Explanation: This message is an indication of amisconfiguration or that an upstream component(CME) was not running yet so it had not registereditself yet, or the upstream CME was failing to registeritself because CNS is having problems

User response: 1. Check that CME is properlyconfigured in the system. 2. Check CME is running. 3.Check CNS is running

GYMDC10037W Call to getDurationsForIntervals()expects an array as the first argument

Explanation: The call to getDurationsForIntervals()was invoked with something other than an array forthe first argument

User response: Update ecmascript code

GYMDC10038W Call togetAccumulatedDurationForIntervals()expects an array as the first argument

Explanation: The call togetAccumulatedDurationForIntervals() was invokedwith something other than an array for the firstargument


GYMDC10039W required Needs to be inJMS_FILTER:

Explanation: A required event is missing in the filter

User response: Check the JMS_FILTER

GYMDC10034W • GYMDC10039W


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 first argument

Explanation: The call togetAccumulatedDurationForTuples() was invoked withsomething other than an array for the first argument


GYMDC10043W periodStart Call togetAccumulatedDurationForTuples()expects a positive integer as the secondargument. Invalid argment:

Explanation: The call togetAccumulatedDurationForTuples() was invoked withsomething other than an integer for the secondargument


GYMDC10044W periodEnd Call togetAccumulatedDurationForTuples()expects a positive integer as the thirdargument. Invalid argment:

Explanation: The call togetAccumulatedDurationForTuples() was invoked withsomething other than an integer for the third argument


GYMDC10045W Call to getIntervalsForTuples()expects an array as the first argument

Explanation: The call to getIntervalsForTuples() wasinvoked with something other than an array for thefirst argument




GYMDC10046W periodStart Call togetIntervalsForTuples() expects apositive integer as the second argument.Invalid argment:

Explanation: The call to getIntervalsForTuples() wasinvoked with something other than an integer for thesecond argument


GYMDC10047W periodEnd Call togetIntervalsForTuples() expects apositive integer as the thjrd argument.Invalid argment:

Explanation: The call to getIntervalsForTuples() wasinvoked with something other than an integer for thethird argument


GYMDC10048W count

Explanation: Lists number of calculation errors for ametric in an hour

User response: Review the formula code for potentialdefects

GYMDC10049W timestamp node name tuples or heartbeatDiscarded out of sequence

Explanation: Tuples or data were produced that wereout of sequence.

User response: Verify that the system resumesprocessing normally and 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 physical connectivity between the processesinvolved in the request.

GYMDC10052W incoming_record existing_recordtime_series Record types don't match forTS

Explanation: There is a mismatch between existingand new recomputed values during the operator stateupgrade




GYMDC10053W recomputed existing time_seriesRecomp wrapper should have original:TS



GYMDC10054W incoming existing time_series Valuesdon't match for TS



GYMDC10055W host The host address is theloopback interface,

Explanation: This messages indicates that a processwill be unable to communicate with processes locatedon other hosts. Objects the affected process will beadvertising themselves to other processes using theloopback address, and as such, processes on other hostswill fail to be able to communicate with objects thisprocess.

User response: Check the /etc/hosts file for an entrythat corresponding 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 theapplication has attempted to use some SLA relatedfeatures such as RCM or the PBL COL_FORMULASfeature

User response: Enable SLA features

GYMDC10057

GYMDC10058

GYMDC10059

GYMDC10060W error_description Reason:

Explanation: An error occurred while contacting theCMGR

User response: Check connectivity between CME andCMGR



GYMDC10061I nodes Nodes Found:

GYMDC10062W error_description Reason:

Explanation: RCM cannot contact CMGR to obtainCME labels

User response: Check that CMGR is running andcheck connectivity between RCM and CMGR

GYMDC10063I labels CME Labels Found:

GYMDC10064W incoming existing time_series RecompValues don't match: TS



GYMDC10065 outputFilename Merging multiple BOFsto:

GYMDC10066 bofFilename Sorting BOF:

GYMDC10067W currentHour time unitOfWorkDiscover deactivated for unit of work:

Explanation: Discovery was deactivated for this unitof work

User response: None

GYMDC10068W value attribute subelement Notdiscovered:

Explanation: The subelement/attribute/value was notdiscovered

User response: Check configuration or try again

GYMDC10069W value attribute element Notdiscovered:

Explanation: The element/attribute/value was notdiscovered


GYMDC10070W value attribute resource Notdiscovered:

Explanation: The resource/attribute/value was notdiscovered


GYMDC10061I • GYMDC10070W


GYMDC10071

GYMDC10072W errorDescription Error whileconnecting to the database:

Explanation: An error occurred while connecting tothe database

User response: Check database is accessible and thatusername and password are correct

GYMDC10100W error detail port host response Failed toprocess response:

Explanation: Unexpected response to 3002 request(request to SNMP Collector)

User response: If problem persists, contact technicalsupport

GYMDC10101W response Lost response:

Explanation: Unexpected response to 3002 request(request to SNMP Collector)


GYMDC10102W result process id Killed sqlldr pid=

Explanation: Piped merge did not complete, LDR killsOracle SQL loader


GYMDC10103W result process id Killing stuck sqlldrpid=

Explanation: An instance of stuck Oracle SQL loaderwas found before starting piped merge. LDR kills stuckinstance


GYMDC10104F

Explanation: Oracle error encountered duringdatabase load. The actual error message is displayed


GYMDC10071 • GYMDC10104F


GYMDC10105F

Explanation: Oracle SQL loader task is not found

GYMDC10106F

Explanation: Attempt to load end-of-period datafailed. Loading is stopped pending manual intervention

User response: Fix the problem and remove STOP filein the loaded (or daily loader) root directory. If problempersists, contact technical support

GYMDC10107W error details stored procedure name

Explanation: Storage procedure invocation failed

User response: Check that database is running andaccessible. If problem persists, contact technical support

GYMDC10108W filename Unable to get next metricrecord from

Explanation: Failure to read record from one of theinput files

User response: If problem persists, call technicalsupport

GYMDC10109W file Recovery file

Explanation: Recovery file does not exist

User response: None

GYMDC10110W errorDescription sqlStatement A SQLerror has occurred for the SQLstatement: (

Explanation: Non-fatal SQL error

User response: Fix the database privileges and ensurethe database is working properly

GYMDC10111W directory error message Error:

Explanation: An error occured while trying to get diskconsumption for a disk usage server root directory

User response: Try to run the du command manuallyon the same directory to see what error occurs


Explanation: Naming server cannot be accessed orfailed to look up object in the naming service

User response: Start CNS or check network

GYMDC10105F • GYMDC10112W


GYMDC10113W errorMessage

Explanation: Channel component failed to registerwith Corba Naming Service

User response: Start CNS, check network and checkthat port isn't in use


Explanation: Failed to start Corba for channelcomponent

User response: Check configuration


Explanation: Failed to stop Corba for channelcomponent


GYMDC10117W No metadata resources loaded fromdatabase.

Explanation: Metadata load did not load anyresources

User response: Make sure inventory has run

GYMDC10118F

Explanation: Piped merge did not complete, LDR killsOracle SQL loader


GYMDC10119W record Out of order record:

Explanation: Out of order record in BOF file

User response: Call technical support

GYMDC10120W log_contents result_descriptionerror_description General SFTP error:

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




GYMDC10122W count The failure limit of

Explanation: FTP failed to transfer file after severalretries


GYMDC10123W directory Unable to change remoteworking dir:

Explanation: FTP failed to change to specifieddirectory


GYMDC10124W error description uri Unable to getremote file

Explanation: There was a failure when attempting toretrieve a file using FTP.


GYMDC10125W localDirPath Unable to make localdir:

Explanation: FTP failed to create specified directory


GYMDC10126W directory Unable to remove remotedirectory:

Explanation: FTP failed to remove specified directory


GYMDC10127W remoteURI Unable to remove remotefile:

Explanation: FTP failed to remove specified file


GYMDC10128W file Unable to remove remote closehour file:

Explanation: Unable to remove remote close our file


GYMDC10129W

Explanation: Missing input source definition referredto in xlog command.




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 Failed renamingfile from:

Explanation: FTP failed to rename specified file


GYMDC10133W There is more than one top-levelstream operator specified

Explanation: The structure of the UBA operators isinvalid. There is more than one operator that has nooutput operators. Operators without any outputs arecalled root operators and are the ones that actually emitmetrics.

User response: Contact technical support for helpwith a possible tech pack bug.

GYMDC10134W timestamp file name File

Explanation: A file needs to be reprocessed after arestart of the UBA.

User response: No action is necessary

GYMDC10135W error formula id calculate Error during

Explanation: An error occured during the calculate()method

User response: Check formula syntax, check formulaarguments, protect access to tuple lists

GYMDC10136W error formula value Invalid formularesult

Explanation: An error occurred while producing aformula result

User response: Check formula code, check formulaarguments, especially returned value



GYMDC10137W message tuple

Explanation: A bad tuple was encountered.

User response: Check for iFixes for the tech pack thatcorrect the issue.

GYMDC10138W

Explanation: The TIME_GRANULARITY settingdefines what one period of time is. This data filecontains data for more than one period of time.


GYMDC10139F slelabel Can't load, SLE

Explanation: Can't load, SLE is already running

GYMDC10140W

Explanation: An error ocurred while trying toestablish the local timezone. We will use the defaultseconds from GMT

User response: Contact techical support

GYMDC10141F

Explanation: Attempt to load recomputed data failed.Loading is stopped pending manual intervention

User response: Fix the problem and remove STOP filein the recomp root directory. If problem persists,contact technical support

GYMDC10142F

Explanation: Attempt to recover recomputation failed.Running is stopped pending manual intervention

User response: Fix the problem and remove STOP filein the recomp root directory. If problem persists,contact technical support

GYMDC10143W slelabel Can't unload, SLE

Explanation: Can't unload, SLE is not currentlyrunning

User response: Do not try to move an SLE that is notrunning



GYMDC10144W cmelabel slelabel Can't start SLE

Explanation: Can't start SLE, current CME is notowner of the filesystem


GYMDC10145W

Explanation: Failed looking up PvURL for directoryfrom AMGR

User response: Ensure AMGR,CMGR are running andcheck the DUS seciton of the AMGR config

GYMDC10146I Tenuring of load sets turned offbecause too much work

GYMDC10147W errorDescription Log initializationerror:

Explanation: Proceedable error during initialization oflogger

User response: Check error message, verify andchange configuration

GYMDC10148W destinationPvURL sourcePvUrlerrorDescription Error:

Explanation: An error occurred while acquiring aninput file

User response: Make sure that no manual file deletesare hapening and that file permissions are set properlyon the source file

GYMDC10149W

Explanation: An error occurred while collecting inputfiles from inputDirPvURL. Upstream CMEs publishtheir outputDirPvURL so that downstream LDRs canuse these as a inputDirPvURL. LDR looks up theoutputDirPvURL for each of itsINPUT_COMPONENTS in the configuration.

User response: 1. Review the error shown in this logmessage and make sure that the inputDirPvUrl is valid.2. Check the configuration settings for disk usageserver (DUS). 3. Try to do a file copy or ftp/sftp getfrom this inputDirPvURL to make sure that it isaccessible



GYMDC10150W error detail application name Failedtesting for running application:

Explanation: AMGR received an error while trying tocheck if an application is running

User response: Check system status

GYMDC10151W

Explanation: AMGR received an error while trying tokill an application


GYMDC10152W

Explanation: AMGR received an error while trying tostart an application


GYMDC10153W

Explanation: AMGR received an error while trying toget the status of an application


GYMDC10154W

Explanation: AMGR received an error while trying tostop an application


GYMDC10155W

Explanation: AMGR failed to kill the specifiedapplication


GYMDC10156F

GYMDC10157W directory error message Error:

Explanation: An error occured while trying to get diskfree space for a disk usage server root directory

User response: Check that libproviso.so is availableand has proper permissions



GYMDC10160W Collector unknown for realtime

Explanation: Collector specified in real-time dataservices request is not found

User response: Make sure collector is running. Checkconfiguration

GYMDC10161W errorDescription Failed to write datato the subscriber:

Explanation: There was a failure to deliver real-timesubsription data to subscriber

User response: Problem should correct itself

GYMDC10162W

Explanation: The subscription request is invalid dueto bad resource or incorrect formula in the request

User response: Make sure the resource and metric arecorrectly defined in the database for the realtime chartthat fails its subscription request

GYMDC10163W

Explanation: Unable to find SNMP formula for ageneric id

User response: Check request's formula to make suregeneric formula exists

GYMDC10164W router id Router Id

Explanation: Attempt to use a Cisco SAA routerfeature with a non SAA router.

User response: Check router configuration to ensurethat SAA is enabled

GYMDC10165W attribute name Missing mandatoryattribute:

Explanation: A mandatory attribute is missing from aprobe.

User response: Check the health of DataView.

GYMDC10166W Collector unavailable for realtime

Explanation: Collector specified in real-time dataservices request is not available

User response: Make sure collector is running. Checkconnectivity and configuration



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 byCMGR/DataView with invalid arguments.

User response: Contact technical support.

GYMDC10169W target_name target_id SNMP Timeoutor invalid community string on targetId:

Explanation: SNMP Timeout or invalid communitystring on target Id

User response: Check network connectivity andSNMP configuration

GYMDC10170W description

Explanation: An error occurred while monitoringprobes


GYMDC10171W subelement id No subelement withid:

Explanation: A CORBA client to the SAA probemonitor issued a request with an invalid subelement id

User response: Resync collector or restart collector

GYMDC10172W error description subelement id Errorresyncing probes for router

Explanation: An error occurred while attempting toresync the probes on a router.

User response: Check network connectivity, reviewSNMP configuration for that router

GYMDC10173I probe index subelement id Probe:

Explanation: A monitored probe was redeployed on arouter to synchronize its settings with those stored inProviso.

GYMDC10167W • GYMDC10173I


GYMDC10174W Unknown collector error

Explanation: An unknown error has occurred.


GYMDC10175W type name Undefined probe type:

Explanation: Probe type is unknown or unsupported

User response: Review imported configuration inDataView and check supported probe types indocumentation

GYMDC10176W subelement id probe index Unknownprobe at index '

Explanation: Unable to modify probe because ofinvalid index.

User response: Review imported configuration inDataView.

GYMDC10177W name subelement id Router

Explanation: Probe type is unknown or unsupported

User response: Review imported configuration inDataView and check supported probe types indocumentation

GYMDC10178I subelement id Router

Explanation: A router reboot was detected.

User response: No action necessary.

GYMDC10179I subelement id Resyncing probes onrouter

Explanation: Probes in a router are being resyncedwith the probe settings stored in Proviso.


GYMDC10180W error description subelement id Errortrying to detect reboot of router

Explanation: An error occurred while attempting todetect if a router was rebooted.

User response: Review the error described in themessage



GYMDC10181W This collector is currently inactive

Explanation: A collector client sent a probeconfiguration message to an inactive collector.


GYMDC10182W description Failed to load probemonitor configuration from thedatabase:

Explanation: Failed to load the probe monitorconfiguration from the database.

User response: Investigate connectivity with thedatabase

GYMDC10183W The server is too busy to acceptnew probe monitoring requests.

Explanation: Too many probe monitoring requests arecurrently active. Rejecting further requests.

User response: DataView Client should retryautomatically. No action required.

GYMDC10184W The router is too busy to acceptnew probe monitoring requests.

Explanation: Too many probe monitoring requests arecurrently active for the given router. Rejecting furtherrequests.


GYMDC10185I subelement id Router

Explanation: A router check can not be completed atthat time


GYMDC10186W name attribute name Unsupportedattribute '

Explanation: An unknown attribute was sent forprobe type

User response: If the attribute is a user specifiedattribute they should review the router documentation.

GYMDC10187I max_time subelement id Target Id

Explanation: Collector is busy. Client should retry.




GYMDC10188W subelement id probe index Unable tomodify 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 dateand should be removed.

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

Explanation: Problem when accessing BOF file


GYMDC10205W lineErrorMessage A metadata erroroccurred -

Explanation: The metadata was requested without avalid name.

User response: Analyze input files or contact technicalsupport

GYMDC10206W formatType

Explanation: The parser field description attempted tospecify an incorrect value type


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 directoryto remote inventory directory (FTP error)

User response: Check connectivity and configuration

GYMDC10209W errorMessage ftpServer Unable toconnect to ftp site

Explanation: Bulk collector failed to connect to remoteinventory directory (FTP error)


GYMDC10211W ftpResult localFilename Unable to sendinventory file

Explanation: Bulk collector failed sending file


GYMDC10212W ftpResult filename Unable to renameinventory file

Explanation: Bulk collector failed rename file inremote inventory directory (FTP error)


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 identifiedwith specified file


GYMDC10215W line Unexpected input in data file.Offending line is:

Explanation: Unexpected input in data file --offending line shown




GYMDC10216W errorDescription file messageMalformed timestamp encounteredwhile processing file.

Explanation: Malformed timestamp encountered whileprocessing file


GYMDC10217W file message The format typedetection algorithms fail to detect thisfile.

Explanation: The format type detection algorithms failto detect this file

User response: Analyze input files and contacttechnical support

GYMDC10218W file errorDescription Internal error:

Explanation: Internal error while processing file


GYMDC10219W schemaName No schema named

Explanation: Error while processing specified file(invalid schema name)


GYMDC10220W

Explanation: Error while processing input data file


GYMDC10301W A communications error occurredbetween channel manager, applicationmanager and application.

Explanation: A communications error occurred

User response: Check connectivity between CMGR,AMGR and application 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 commandline interface and the channel manager



GYMDC10304W

Explanation: Inable to reach application

User response: Check connectivity

GYMDC10305W

Explanation: Getting labels failed during nearreal-time query

User response: Check connectivity to database.

GYMDC10306W error_description application_nameFailed getting metric records from:

Explanation: CMGR received an error while trying toget metric records from an application

User response: Check connectivity between CMGRhost and application host

GYMDC10307W error_string application_name Failedtesting for running application:

Explanation: CMGR received an error while trying totest if an application is running already

User response: Check system status and connectivitybetween CMGR host and application host

GYMDC10308W

Explanation: CMGR received an error while trying tokill an application


GYMDC10309W

Explanation: CMGR received an error while trying tostart an application


GYMDC10310W

Explanation: CMGR received an error while trying toget the status of an application




GYMDC10311W

Explanation: CMGR received an error while trying tostop an application


GYMDC10312W Abandoned request because clientdisconnected prematurely

Explanation: Abandoned request because clientdisconnected prematurely


GYMDC10313W hostname application name Noconfigured component matches name:

Explanation: No component matches the given name,application and host patterns.

User response: Check the name, application and hostpatterns.

GYMDC10314W

Explanation: CMGR received an error while trying tocontact an application


GYMDC10315W

Explanation: No configured CME matches the givenCME name

User response: Add an entry to configuration for theCME in question and bounce CMGR, then start thatCME.

GYMDC10316W

Explanation: SLE is already assigned to another CME


GYMDC10317W

Explanation: SLE has not been assigned to any CME




GYMDC10318W

Explanation: Currently do not support moving SLEsacross file systems.


GYMDC10400W file name count error description A fileread error:

Explanation: An error occurred while trying to readand process tuples in a file.

User response: Check the input file.

GYMDC10401W error detail metric record Metric record

Explanation: CME was sent data that is either notcovered by requests or is in an invalid format

User response: Check input data

GYMDC10402W metric id count

Explanation: Lists the number of bad records in inputfile by metric id

User response: Review requests and resource groupsfor requests

GYMDC10404W class Bad

Explanation: lasthour file is corrupted


GYMDC10405W gerneric id resource request Badrequest:

Explanation: If it is an SNMP generic formula, thecollector already sends us metrics with generic formulaID, so the generic formula should exist

User response: Check request's formula to make suregeneric formula exists

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 ofcompile error




GYMDC10408W debugInfo errorDescriptionformulaClassName An error occured whilerunning building output metric recordfor formula:

Explanation: Formula refers to invalid input binding


GYMDC10409W debug info errorDescriptionformulaName formulaClassName An erroroccured while running calculation forformula:

Explanation: An error occurred while computingformula value


GYMDC10410W errorDescription className Compilererror for Smalltalk formula:

Explanation: Error compiling formula


GYMDC10411W errorDescription rid gid mid rid mid Anerror occured during thresholdprocessing of a metric record (mid=

Explanation: A failure has occurred in thresholdprocessing

User response: Send exception details to support team

GYMDC10412W timeseries id total count discarded countduplicate count Got

Explanation: CME discovered and discarded duplicaterecords when flushing them to disk

User response: Check for duplicate data being sent toCME. Contact technical support

GYMDC10413W Error sending trap, resetting SNMPengine

Explanation: Error occured during sending trap


GYMDC10414W total count discarded count duplicatecount Got

Explanation: CME found duplicate records or somerecords were discarded because of invariant change

User response: Check system configuration. In case ofinvariant change the system should handle itautomatically



GYMDC10415W filename filename Configuration file

Explanation: The configuration file is newer than thestate file.

User response: Check system configuration.

GYMDC10416W errorDescription rid gid mid An erroroccured when attempting to send a trapfor (mid=

Explanation: An error occurred when creating orsending a trap PDU


GYMDC10417W rid gid mid Mid/Gid/Rid =

Explanation: Reset Baseline state due to missingBaseline History in DB

User response: Check that LDR is loading OK

GYMDC10418W error_details destination_URIsource_URI Failed to copy

Explanation: An error occured during an attempt tocopy a file

User response: Review the error details. Check filepermissions. Attempt to copy the source URI to thedesitnation URI manually to see what error occurs.

GYMDC10419W error_description uri Failed to delete

Explanation: An error occured during an attempt todelete a file

User response: Review the error details. Check filepermissions. Attempt to delete the source URImanually to see what error occurs.

GYMDC10420W error_description destination_URIsource_URI Failed to link

Explanation: An error occured during an attempt tolink one URI to another

User response: Review the error details. Check filepermissions. Attempt to link the URIs manually to seewhat error occurs.

GYMDC10421W error_description destination_URIsource_URI Failed to move

Explanation: An error occured during an attempt tomove a file

User response: Review the error details. Check filepermissions. Attempt to move (rename) the source URIto the desitnation URI manually to see what erroroccurs.



GYMDC10422W error_message souce_code_uri URI:

Explanation: A syntax error was detecting whilecompiling ECMAScript code.

User response: Check the syntax in the indicated fileand 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 tocheck file information for a URI using ls command.

GYMDC10424W destination_size destination_URIsource_size source_URI Copied file sizedoes not match source (source:

Explanation: After a copy the file sizes do not match

User response: Manually copy the source URI to somedesintation on the same partition and/or differentpartition as the destination to see if they are the samefile size.

GYMDC10425W uri_list Failed to copy file, giving up(

Explanation: Retried too many times to copy a file

User response: Check file permissions. Review theerror details Attempt to manually copy a URI to seewhat error occurs.

GYMDC10426W error detail formula resource requestBuild error on request:

Explanation: An error has occurred during the treebuild


GYMDC10427W

Explanation: Bad input: can't resolve <input kind>tsId: <id> from: <db row>


GYMDC10428W input time series time series sequencenumber No argument with s/n

Explanation: When attempting to update a formulainput, no argument with the indicated sequencenumber was found.




GYMDC10429W row time_series No complex formulafor:

Explanation: No complex formula for: <id>


GYMDC10430W tupleContainer timestamp Metrics withtimestamps starting at

Explanation: Metrics have already been received forthis time. Duplicate data will be ignored.

User response: If the tuple container is from acollector, check if that collector is actually producingduplicate data by using bofDump on the output filesthat it produces

GYMDC10431W label Data from label

Explanation: Data from label <label> is not used here


GYMDC10432W error description Failed to write BOFfile because of

Explanation: Failed to write tuples to disk.

User response: Double check disk space andpermissions.

GYMDC10433F error_description row Error buildingtime series from:

Explanation: Error building time series from: {dbrow}, reason: {a reson}

User response: Contact Proviso support

GYMDC10434F error_description row Error buildinginput from:

Explanation: 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 arecord.

User response: Take steps to correct the problembased on the information given in the error description.



GYMDC10437W time_series No formula for:

Explanation: RCM cannot locate the formula for atimeseries

User response: Check plan consistency and thatformula exists for timeseries

GYMDC10439W Problem contacting tuple storage,will retry every 60 seconds.

Explanation: RCM cannot contact tuple storage

User response: Check connectivity between RCM andCMEs

GYMDC10440W error description Error running tuplequery (will retry in 60 seconds):

Explanation: The recomputation engine has a problemquerying other components or the database.

User response: Ensure all CMEs, FTEs and thedatabase are running.

GYMDC10441W A timeout occured while fetchingthe results of a tuple query. The querywill be retried.

Explanation: A timeout occurred while queryingtuples.


GYMDC10442W reason label Remote query of label

Explanation: An attempt to query a remote process fordata failed.

User response: Ensure all components are running.

GYMDC10443W

Explanation: A file needs to be partially reprocessedafter a restart of the UBA in order to finish processingthe file.

User response: No action is necessary.

GYMDC10444W operator schedule modifier Failed toapply repeat modifier

Explanation: The system failed to interpret the repeatmodifier specified in a formula or in a subelementproperty.

User response: Check the subelement property usedfor the repeat modifier and make sure the correctsyntax was used. Also verify that the calendar used inthe formula is compatible with the property.



GYMDC10445W time_series modifier Failed to applytimezone repeat modifier

Explanation: Failed to apply a timezone modifierbased on a subelement property.

User response: Check subelement property value usedfor the timezone modifier.

GYMDC10446W operator calendar name Invalidcalendar/duration:

Explanation: An invalid reference to a calendar orduration was encountered in a formula.

User response: Double check the calendar name orduration specified in the formula and make sure it isdefined using the DataMart calendar manager.

GYMDC10447W timestamp name

Explanation: An aggregator in a UBA failed to recoverits state from disk.

User response: Check for data loss and determinewhether someone may have inadvertently manipulatedthe UBA's state files.

GYMDC10448W timestamp timestamp name

Explanation: An aggregator in a UBA failed to recoverits state from disk. The UBA will attempt to use olderaggregator state instead.

User response: Check for data loss and determinewhether someone may have inadvertently manipulatedthe UBA's state files.

GYMDC10501W

Explanation: The definition for the profile cannot befound in the database. Current execution is aborted

User response: Refresh or bounce the GUI, to resyncthe content

GYMDC10502W

Explanation: The file inventory_element.txt is missingfor executing the profile

User response: Check suggested path, and addcorresponding file to that location



GYMDC10503W

Explanation: The file inventory_subelement.txt ismissing for executing the profile


GYMDC10504W

Explanation: A formula specified in filesinventory_element.txt or inventory_subelement.txt isunknown in the database

User response: Check database and file for formulaspelling

GYMDC10505W

Explanation: One of the configuration parameter forthe profile has an invalid value


GYMDC10506W probe componentName CNS returnedincomplete list of targets for:

Explanation: All component names were not foundwhen looking them up in CNS

User response: Check that all components are running

GYMDC10507W id Invalid id:

Explanation: Inconsistent data was found whileserializing or deserializing timeseries and input data

User response: Check that the formula and resourcefor this input both exist in the database

GYMDC10508W tuple error description operator name

Explanation: An error occurred while trying toprocess an outgoing tuple.

User response: Check for an iFix to the tech packrunning on this UBA that corrects this issue.

GYMDC10509W probe errorDescription Error

Explanation: An error occurred while trying toexecute a monitoring probe

User response: Check script and review error message



GYMDC10510W

Explanation: One input file, specified by the profile ismissing

User response: Check the file name and path, eitherfix the profile of the file name

GYMDC10511W

Explanation: The file inventory_element.txt is missingfor executing the profile


GYMDC10512W

Explanation: The file inventory_subelement.txt ismissing for executing the profile


GYMDC10519W ipAddress tag

Explanation: This IP address is out of range, or hasbeen explicitely excluded within the profile

User response: No action required

GYMDC10520W errorDescription tag

Explanation: The ping sweep did not execute properlyon the collector machine

User response: Check qPing files permissions on thecollector machine

GYMDC10521W finalList count tag

Explanation: A subset of IP address(es) has beenforced on the command line used to start the discovery.The set of IP address(es) the inventory is going to workon is the intersection between the set defined by theprofile (mode 1 or 2), and the forced set. This filterusually takes place during partial re-discoverytriggerred by invariant change detection mechanism.


GYMDC10522W errorDescription tag IP DISC did notexecute properly on the collectormachine:

Explanation: An error occured when the IP DISC didnot execute properly on the collector machine




GYMDC10549W ipAddresses tag

Explanation: This is a warning message about IPaddresses that have not been discovered

User response: Check snmp configuration andconnectivity

GYMDC10559W element element invariant tag

Explanation: An element with the same characteristicshas already been discovered during this execution. Thetwo elements have been identified as true duplicate,and second instance is ignored


GYMDC10579W errorDescription tag

Explanation: A network related error has occurred


GYMDC10590W

Explanation: Ther was an error when trying to writeto a file.

User response: Check the disk utilization and theprocess' permissions to access this file and directory.

GYMDC10591W

Explanation: A retriable database error occurred

User response: This message should go away after itretries. If it does not, contact technical support.

GYMDC10592W additionalInfo errorDescriptionsqlStatement Statement (

Explanation: Bulk database insert or update failed

User response: Review the error description and theadditional information

GYMDC10593I

GYMDC10594W errorDescription domainManager Initialload for

Explanation: Loading initial metadata from databasefailed. Will retry.

User response: If message persists, check thatdatabase is working properly and check connectivity



GYMDC10600W

Explanation: Re-Inventory request failed

User response: Check connectivity, system status

GYMDC10601W error details application name Failed toregister

Explanation: Registering application version failedwith an error

User response: Check connectivity and check databasestatus

GYMDC10602W maxRetries profileName ipAddressFailed to run inventory for:

Explanation: Re-Inventory request failed

User response: Check inventory command line in logfile, dc.cdf, priviliges of datachannel user

GYMDC10603W line Unexpected line in stored QCFdata:

Explanation: Bad data was encountered in the QCIFstate journal files.

User response: Inspect files and/or run full 5620dump and verify the integrity of the file system used tostore QCIF's state.

GYMDC10604W formula name Relation

Explanation: Relation specified in design file is notdefined in the system

User response: Check design file for proper relationname or add relation description (entry inFRML_DESC)

GYMDC10605W property name Property

Explanation: Property specified in 5620 design file isnot defined in the system.

User response: Check design file for proper propertyname or add property description (entry inFRML_DESC).

GYMDC10606W error_description Flush aborted due to

Explanation: A serious error occurred while savingdata in the database. Flush aborted

User response: Check database connectivity or contacttechnical support



GYMDC10607W processName errorDescription 5620Error:

Explanation: A Corba exception was triggered onmessage send to 5620

User response: Alert operator of potential problemwith the primary device

GYMDC10608W processName errorDescription qc_serverConnection to

Explanation: Attemp to connect to device failed

User response: Alert operator of potential problemwith one of the 5620 devices

GYMDC10609W qc_server Switching from

Explanation: Switching from specified device to thebackup device has started


GYMDC10610W errorDescription eventChannelIORFailed to reuse stored event channelreference:

Explanation: Attempt to reuse stored QC eventchannel reference failed

User response: No action required. Application willcreate a new event channel automatically

GYMDC10611W Successfully reused stored sessionreference

Explanation: Attempt to reuse stored QC sessionreference failed

User response: No action required. Application willcreate a new session automatically.

GYMDC10612W 5620 is out of sync, some eventshave been lost!

Explanation: Event buffer on 5620 has been flushed,queued events are lost

User response: Consider running manual full dump toresync

GYMDC10613W Element is not specified for

Explanation: An element is not specified for asubelement. Subelement will be skipped




GYMDC10614W anOid Object with oid

Explanation: An error occurred during the QCgetAttributes call


GYMDC10615W reason file_name Error reading eventsjournal file

Explanation: An error occurred while reading theevents journal file


GYMDC10616F

GYMDC10617W errorDescription anObject Erroradapting object

Explanation: An error occurred while adapting anobject

User response: Check script and refer to errordescription in the message

GYMDC10618W Device is unavailable (Failed toresolve QCF_System or QC_network)

Explanation: QCF device is unavailable

User response: Check that QCF device available andreachable

GYMDC10619W reason

Explanation: A problem was encountered whileattempting a primary device switchover

User response: Check primary device to make sure itis available

GYMDC10620W oid Failed to refetch object or eventat

Explanation: Unable to refetch object or event withoid

User response: Check that object with oid exists

GYMDC10621W object errorDescription Error

Explanation: An error occurred while processingobject

User response: Review message for error details



GYMDC10622W object id Auto-inserted missing nodeat

Explanation: QCIF auto created a missing node in thepath of a 5620 object identifier.

User response: Force a full inventory dump.

GYMDC10623W port host dbEnvironment Switchingfrom database:

Explanation: Switching from specified device to thebackup device started


GYMDC10624W errorDescription filename Error loading

Explanation: An error occurred while trying to load ascript file

User response: Check script file

GYMDC10625W anOid Oid

Explanation: An error occurred during the QCgetAttributes call


GYMDC10626W oid Failed to set attributes for oid:

Explanation: Error during QC getAttributes call


GYMDC10628W

Explanation: The directory defined in the dynamiclibrary path is missing

User response: Remove the missing directory from thedynamic library path

GYMDC10629W

Explanation: RCM cannot locate the timeseries id for arecomputation action

User response: Check plan consistency

GYMDC10630

GYMDC10622W • GYMDC10630


GYMDC10631W

Explanation: RCM has received a bad recomputationrecord

User response: Check input data to make sure RCM isfed recomputation records only

GYMDC10632W

Explanation: RCM has received a duplicaterecomputation record

User response: Check input data to make sure RCM isnot fed any duplicate recomputation records

GYMDC10633 error description uri Failed to deletefile:

Explanation: Failed to delete SAM export file.

User response: Check that the process has properpermission to delete the indicated file.

GYMDC10634W relation name Relation

Explanation: A UBA script tried to create a relation forwhich the relation name is not defined.

User response: Reinstall the tech pack

GYMDC10635W 5620 Error: Failed to send userName

Explanation: An error occurred while gettinguserName

User response: Alert operator of potential problemwith the primary device

GYMDC10636W property name Property

Explanation: Property refers to non-existent formula

User response: Check property in database

GYMDC10637W errorDescription database Connectionto

Explanation: An exception occurred while attemptingto login to Informix

User response: Check that Informix is available

GYMDC10638W subelementName Owning element notspecifed for subelement

Explanation: No owning element specified forsubelement

User response: Review script



GYMDC10639W resource relationFormula No relationmember is specified for relation:

Explanation: No relation member was specified forrelation / resources


GYMDC10640W subeleement2 subelement1relationFormula No relation index isspecified for relation

Explanation: No relation index was specified forrelation / member


GYMDC10641W relation subelementName Nosubelement named

Explanation: No subelement was found for relation


GYMDC10642W

Explanation: An inventory object that the UBA isbeing requested to create has a conflict with anotherinventory object already present in the system.

User response: Make sure the UBA is processing datafor the most current inventory in the database that isassigned to its collector number.

GYMDC10643W current seconds resync seconds Resynctime (

Explanation: The timestamp on a record is earlier thanthe current processing time of the UBA. Records shouldbe emitted in timestamp order by the tech pack.

User response: Double check the validity of databeing fed into the UBA and investigate a possible techpack bug.

GYMDC10644W Failed to connect to SAM service.

Explanation: Unable to connect to SAM service

User response: Check primary SAM serviceavailability

GYMDC10645W errorDescription Error connecting toevent channel:

Explanation: An error was encounterd while trying toconnect to the QCF event channel

User response: Check that QCF device available andreachable



GYMDC10646W errorDescription event Errorprocessing event

Explanation: An error occurred while processing anevent

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 serveravailability

GYMDC10648W errorDescription object Error writingid map entry for

Explanation: An internal error occurred that causedthe idmap entries not to be written

User response: Check file permissions. Contacttechical support

GYMDC10649W Check for primary cwm serveravailability

Explanation: A problem was encountered. Attemptinga primary device switchover

User response: Check primary device to make sure itis available

GYMDC10650W error detail

Explanation: Attempt to purge files in done directoryfailed

User response: Check file permissions and userprivileges

GYMDC10651W Successfully switched back toprimary cwm server

Explanation: A problem was encountered with theprimary device. Successfully switched back to primarycwm server.


GYMDC10652W Successfully switched back toprimary SAM server

Explanation: Switched back to primary SAM server




GYMDC10653W uri Switching from SAM SOAPservice:

Explanation: About to switch from primary SAMSOAP server to alternate service

User response: Check primary SAM SOAP serveravailability

GYMDC10654W Domain model is not configured inecmascript environment

Explanation: The domain model is not configured inthe ecmascript environment


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 noavailable colletor to fail over to

User response: Investigate cause of failovers andreview configuration and log message

GYMDC10704W limit percent stat_name collectorCollector

Explanation: Collector is not suitable for failoverbecause a statistic is over the theshold

User response: Check network connectivity and CPUutilization

GYMDC10705W errorDescription port host Lostconnection to collector

Explanation: Connection to the collector was lost

User response: Check connectivity and that collectoris still running

GYMDC10706W list Redundant collectors detected:

Explanation: Redundant collectors were detected

User response: Check that GRACE_PERIODconfiguration setting is longer than your currentcollector startup time



GYMDC10707W collector Collector

Explanation: Collector is not in HA mode

User response: Check that collector is configured to bein HA mode

GYMDC10708W collector Unable to communicatewith collector

Explanation: Unable to communicate with collector

User response: Check network connectivity and checkthat collector is running

GYMDC10709W message error_description client Client

Explanation: Encountered an error when sendingmessage to collector

User response: Check network connectivity

GYMDC10710W relation_id Missing relation formulawith id

Explanation: Relation refers to a non-existent formula

User response: Check that relation refers to a formulathat exists. If it does, contact technical support.

GYMDC10711W resyncAction relationFormulasubelementId Missing endpointsubelement with id

Explanation: Relation refers to a non-existentsubelement

User response: Check that relation refers to existingsubelements. If it does, contact technical support.

GYMDC10712W file name schema name Unknownschema:

Explanation: An input descriptor was encounteredthat is associated with an unknown input schema. Theinput descriptor will be ignored and discarded.

User response: If the file needs to be processed, itmay be necessary to re-stage the file in the inputdirectory, otherwise no action is necessary and thewarning was likely due to renaming 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 profile Preloadingconfiguration

GYMDC10757I collector duration Extending timeoutby

GYMDC10758I collector Disabling expiration forcollector

GYMDC10759I profile collector Re-registering collector

GYMDC10760I profile collector Pausing collector

GYMDC10800W y x Received trap number

Explanation: Received trap out of sequence


GYMDC10801W y x n Unable to recover

Explanation: Received trap out of sequence onrecovery


GYMDC10802W port host Failed to get sysUpTimefrom RTM Service Agent at

Explanation: Failed to get sysUpTime from RTMService Agent

User response: Check communications, RTM server

GYMDC10803F

GYMDC10804F Both RTM event channels cannot usethe same local port.

GYMDC10752I • GYMDC10804F


GYMDC10805F

GYMDC10806F

GYMDC10807W endpointDbKey Invalid deleteenpoint:

Explanation: Ignoring delete of an enpoint

User response: Check resources should be loaded inmemory

GYMDC10808W errorDescription trap Error processingtrap

Explanation: Handling PDU failed


GYMDC10809W errorDescription port host Errorrenewing registration with service agent

Explanation: An error occured while renewingregistration


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 whilewriting out inventory. Subelement will be skipped


GYMDC10812W pdu errorDescription Trap processingerror:

Explanation: An error was encountered whileprocessing a trap

User response: Review message for error information

GYMDC10850I port host Registering with RTMService Agent at

GYMDC10805F • GYMDC10850I


GYMDC10851I port host Unregistering with RTMService Agent at

GYMDC10852 port host Renewing registration withRTM Service Agent at

GYMDC10853 trap pdu Received trap

GYMDC10854I port host Starting resync with RTMService Agent at

GYMDC10855I port host trapnumber Recovered trapnumber

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 on port

GYMDC10861I username database Starting Glorpsession for database

GYMDC10862I Successfully connected to cwm trapserver

GYMDC10863I last trap number trap number IncomingRTM trap number (

GYMDC10864 port host Registration renewed withRTM Service Agent at

GYMDC10865W port host Failed to renew registrationwith RTM Service Agent at

Explanation: Unable to renew registration with RTMService Agent

User response: Check registration configuration

GYMDC10851I • GYMDC10865W


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 andthat configuration is valid

GYMDC10900W value key Failed to convert:

Explanation: Failed to convert key value pair fromconfiguration


GYMDC10901W error detail Error:

Explanation: An error has occurred during the linkingof formula dependencies


GYMDC10902 error description Bad PDU received

Explanation: A bad PDU was received.

User response: Verify the correct operation of othersystems with which the affected component iscommunicating.

GYMDC10903W errorDescription Error locating andloading Mibs :

Explanation: An error was encountered while locatingand loding Mibs

User response: Check mibs location and review thiserror message

GYMDC10904W errorDescription A command erroroccurred:

Explanation: A request failed


GYMDC10905W object_type object_name Failed toadapt

Explanation: There was an error in trying to emiteither an element or a subelement created by a techpack.

User response: Verify that the input data is correct.Contact your system administrator or technical supportif the input data looks correct and you are unable toresolve the issue.



GYMDC11016W file name Attempt to inject tuples,but one or more files is missing or inthe wrong location:

Explanation: An attempt was made to inject tupleswith a tuple container that has missing or invalid files.

User response: Contact your Proviso systemadministrator.

GYMDC11017W error_description time label Failed toacquire tuples (label:

Explanation: Failed to acquire files from an up streamcomponent.

User response: Double check that the process canaccess the output directory of the up stream componentover the file system, ftp or stfp (depending on thesystem configuration).

GYMDC11018W node_name Name server (CNS)lookup failed for node

Explanation: An attempt to lookup a tuplecommunications node failed.

User response: Make sure the CNS, FTEs and CMEsare running.

GYMDC11019W error_description node_name Acommuncations error occurred withnode

Explanation: An attempt to communicate with a tuplenode failed.

User response: Make sure the FTEs and CMEs arerunning and check their logs for any warning or fatalmessages.

GYMDC12347W symbol Error inFormulaOperator>>update:with: as aresult of responding to

Explanation: An error occured while handling internalevent notification


GYMDC12349W arguments size inputs Something iswrong with inputs:

Explanation: Something is wrong with the number ofinputs because it does not match what was expectedbased on the formula

User response: Check the formula arguments to makesure they are valid properties/formulas/calendars



GYMDC12350W argument operator id Operator

Explanation: The formula specifies an argument butthere is no input for that argument which means thesubelement could be missing an expected relation,property or calendar

User response: Check that the necessary relations,properties and calendars exist

GYMDC12351W formula operator id argument Can'tbuild input for argument

Explanation: Unable to build input because argumentformula is missing

User response: Check to see if argument formula wasdeleted manually

GYMDC12352W error label Failed while contactingthe plan builder to see if a resync isrequired for

Explanation: CME has failed to contact the PBL to seeif there are plan changes within the current hour. CMEcontacting PBL is an optimization. Since it failed, CMEwill simply do a database resync of plan changes forthe current hour.

User response: Check PBL and make sure it isrunning well

GYMDC12356W

Explanation: Pending xlog commands are replayed onrestart to complete transactions. A failure occuredduring this replay

User response: Review the error description andensure necessary resources like the database areavailable. Contact support

GYMDC12357W metric description problem description

Explanation: An attempt was made to create a metricwith invalid state.

User response: Verify the data being fed to the UBAfor accuracy and check the tech pack script for bugs.

GYMDC12358W Unable to produce a record becausethere is no adaptor to process it

Explanation: There is no adaptor to handle metricrecords that are emitted by the script.

User response: Double check the UBA settings and thescript. Make sure the correct version of the tech packscript is configured. Check for any iFixes for the techpack that would correct the issue.



GYMDC12360W error description Failed whilecontacting the plan builder:

Explanation: The UBA failed to contact the planbuilder while trying to inform it about unexpectedmetrics that it is seeing.

User response: Check network connectivity and makesure the channel management components are running.

GYMDL39001W seconds tag

Explanation: A profile is not progressing and will beaborted

User response: Check profile

GYMDL39002 problem description Full inventory dumpis being retried due to the followingreason:

Explanation: A full dump of inventory objects had anerror and is being retried.

User response: Initiate another full dump.

GYMDL39201 error_msg record_number Record #

Explanation: An error was encountered during recordprocessing. The specific error is reported in the logmessage. This message does not necessarily indicate aproblem.

User response: Investigate the reason for the error todetermine whether or not it's a normal condition or alegitimate problem.

GYMDL39205W string Unknown timezone:

Explanation: The configured timezone could not befound in the zoneinfo (tz) database.

User response: Double check the TIMEZONEconfiguration setting and verify that it is in thezoneinfo (tz) database on the host where the UBA isrunning and change the configuration as necessary.

GYMDL39206W license_name License(

Explanation: The shared library that the UBA uses forODBC connectivity does not have correct OEMlicensing information.


GYMDC12360W • GYMDL39206W


GYMDL39207 timezone_used timezone_requestedTimezone requested:

GYMDL39208W No Adaptors deployed

Explanation: No adaptors were specified in the designfile (or no design file was found).

User response: Double check DESIGNFILE andINSTANCES settings in the configuration file.

GYMDC39209W Processing paused because outputat maximum

Explanation: The output directory or tuple storagequeue contains more than the maximum allowednumber of hours of data waiting to be picked up by adownstream component

User response: Start downstream component(s)

GYMDL39209W file name No availability files foundfor metric file

Explanation: The BLB failed to find any availabilitymetric files from the CWMIF that correspond with theother metric files coming from the input URI.

User response: Check the status of the CWMIF andmake sure it is running. Check the logs for CWMIFwarnings or fatal messages and take the correctiveaction suggested for those messages.

GYMDL39210W uri schema name Late input:

Explanation: No input files have been found at theindicated URI for a significant period of time(configurable via the LATELIMITSECONDS setting).

User response: Double check the input URI settingsfor the UBA and make sure the UBA process can accessthe file system, ftp server or sftp server indicated bythe URI (be sure to check using the same unix user idthat the UBA process runs under).

GYMDC39211I Processing unpaused because nolonger at max output

GYMDL39211W file name No availability files foundfor metric file

Explanation: The BLB failed to find any availabilitymetric files from the QCIF that correspond with theother metric files coming from the input URI.

User response: Check the status of the QCIF andmake sure it is running. Check the logs for QCIFwarnings or fatal messages and take the correctiveaction suggested for those messages.

GYMDL39207 • GYMDL39211W


GYMDC39212W timestamp uri schema name Input hastimestamp in future:

Explanation: An input has a timestamp from thefuture relative to the current system time (in UTC). TheUBA will not process an input whose timestamp is inthe future until the system clock catches up with thatinput's timestamp.

User response: Make sure "date -u" reports the correctUTC time and make sure the timestamps on the filesbeing fed to the UBA are in UTC.

GYMDL39212W bytes bytes uri File size is too smallfor uri:

Explanation: The size of the acquired file is smallerthan the configured limit and will not be processed.

User response: Check that the MINFILESIZEconfiguration setting is set appropriately then check thesystem that produces the data for the UBA forproblems.

GYMDL39213W error description

Explanation: An unexpected error occured whileprocessing an input.

User response: No specific advise is available.

GYMDL39214W file name Input file

Explanation: An input descriptor for the given inputfile name was not found in the input descriptorrepository. As a consequence, the indicated file will notbe processed. Since the data file will not be processed,data loss will likely result.

User response: Try and identify how the descriptorrepository may have been deleted or corrupted andtake steps to prevent it from happening in the future.

GYMDL39215W file name Alcatel MR file

Explanation: A file expected to be located in the dodirectory is missing. The input descriptor for the filewill be deleted and the file will not be processed.

User response: Determine why the file in the dodirectory was deleted and take steps to ensure it doesnot happen again in the future. If the file needs to beprocessed, find another copy of the file and re-stage itin the input directory.

GYMDC39212W • GYMDL39215W


GYMDL39217W message uri There was an errorcommunicating with the SAM interface

Explanation: An error occurred in the SAM JMScommunication protocol


GYMDL39218 process id The SAM JMScommunication process has started (pid:

Explanation: The SAM JMS communication processhas stopped.

User response: No action required.

GYMDL39219 process id The SAM JMScommunication process has stopped(pid:

Explanation: The SAM JMS communication processhas stopped.


GYMDL39220W process id The SAM JMScommunication process is hung (pid:

Explanation: A request to stop the JMS process hasbeen issued, but the process is still running


GYMDL39221W problem description Full inventorydump was unable to complete due tothe following reason:

Explanation: A full dump of inventory objects wasinterrupted.

User response: Initiate another full dump.

GYMDL39222I The SAM JMS connection has beenestablished (a keep-alive message wasreceived)

Explanation: The SAM JMS connection has beenestablished.


GYMDL39223W The SAM JMS connection is stale,the JMS process will be restarted.

Explanation: The SAM JMS keep-alive timeout hasbeen exceeded, the JMS process will be restarted.

User response: Check SAM server availability.

GYMDL39217W • GYMDL39223W


GYMDL39224W errorDescription Error processing JMSevent:

Explanation: An error occurred while processing aJMS event.

User response: Contact the system administrator.

GYMDL39225W file_name Error parsing

Explanation: There was an error while trying to parsea CWM bulk statistics file.

User response: Use the CWM statsreader utility toanalyze the file and check for problems.

GYMDL39226W child description Unable to createchild/parent relationship for::

Explanation: A parent and child have the same idwhich is not allowed

User response: Correct invalid group to group entries

GYMDL39801 Starting Inventory transfer andsynchronization

GYMDL39802 code Inventory transfer andsynchronization completed with statuscode=

GYMDL39805 URI schema Start processing input:

Explanation: The adaptor is starting to process thenamed file

User response: None. If this message does not occur itcan be an indicator that a file was not present, or thatthe file glob configuration did not find a matching file

GYMDL39806 uri input_name Completed processinginput:

Explanation: The adaptor completed processing of thenamed input

User response: If records were rejected, this couldindicate a malformed file, file with missing fields(specified in an object adaptor and with no "defaultvalue" or problem with adaptor configuration

GYMDL39224W • GYMDL39806


GYMDL39807 acquired_count ignored_count found_counttime schema Scanned input:

Explanation: The UBA scanned remote URIs for aninput and found n1, n2 were ignored byparseRemoteURI and n3 were already present in the door done directory

GYMDL39809I URI Ignoring input - error parsingURI for timestamp info:

GYMDL39810I acceptable_count saw_count hour Anincorrect number of files was processedfor hour

GYMDL39811W timestamp limit The threshold forinput files containing record errors (

Explanation: The number of files allowed to have oneor more record processing errors in a given hour hasbeen exceeded. The limit is configured with theERRORFILELIMIT setting.

User response: Check the system that is feeding datainto the UBA and double check that theERRORFILELIMIT setting isn't set too low.

GYMDL39812W uri error description Unable to retrievea list of URIs for

Explanation: An error occured while the UBA wasattempting to retrieve a list of files for the indicatedinput URI.

User response: Double check the input URI settingand verify that the file, ftp or sftp server is runningand configured correctly. Attempt to connect to the file,ftp or sftp server by hand from the same host anduserid as the UBA. Verify that the directory indicatedin the input URI exists.

GYMDL42000 timeslot SAM metric export is about tobe issued for timeslot:

Explanation: A SOAP request for SAM to exportmetric data is about to be issued.


GYMDL42001 timeslot SAM metric export has beenrequested for time slot:

Explanation: An export request has been sent to SAM.


GYMDL39807 • GYMDL42001


GYMDL42002W detailed_error_msg timeslot SAMmetric export request failed for timeslot:

Explanation: A SOAP request for SAM to exportmetric data has failed. This can be caused by temporary

loss of connectivity with SAM.

User response: If this message persists, checkconnectivity with the 5620 SAM system.

DataLoad error messagesDescribes reference format error messages produced by DataLoad. Wheneverpossible, explanations are offered, as well as remedial actions.

GYMDL30002F A time bomb function has fired,check previous error DL30138 fordetails. The process will exit, and berestarted by the watchdog process.

Explanation: Some operations are required tocomplete within a given time frame. This messageindicates that a particular operation didn't completewithin the hardcoded maximum time.

System action: The process will exit, and be restartedautomatically by it's watchdog process.

Programmer response: If the issue repeats itself, thiscould be related to a database problem, with a SQLquery that never ends. Look for specific error or tracefiles for the SQL client.

GYMDL30004F Start command failed.

Explanation: The attempt to restart the pvmd processby the watchdog has failed. Unless HAM is deployed,and has switched collections to a different host,collections for that particular profile will NOT happen.This problem must be fixed immediately.

User response: Search in the log for the previousinformation message with ID DL31088. This messagewill indicate the arguments used to attempt to restartthe pvmd process. Inspect each of the arguments. Trythe command on a shell, look for errors on the console,or in the log/pvmd.log, or log/pvmdmgr.log files.

Programmer response: The wrong arguments are inthe start command line, unable to find path forbinaries, or the dataload environment is not present.

GYMDL30005F cmd Error: Unable to kill processwith command '

Explanation: The watchdog is unable to terminate afailing pvmd process using the specified command.Either the process was already terminated by the timethe watchdog issues that command, or the process cannot be terminated because of permission issues.

User response: Check process list on the machine withps. Try the kill command from a shell, using samecredentials as the watchdog process.

GYMDL42002W • GYMDL30005F


GYMDL30006F SNMPv3 cryptography support cannot be loaded. Aborting.

Explanation: The configuration explicitly requires fullSNMP v3 support with encryption, but thecryptographic library can not be located or loaded.

System action: The process will exit, and all furtherattempts to restart the process without changing theconfiguration will fail with the same error.

User response: Either install the cryptographic library,and make sure the library is in the standard searchpath, and accessible for the current user, or edit thecollector configuration to allow startup of the processwithout the cryptography library.

GYMDL30007F function Call to unimplementedcryptography function '

Explanation: The system is configured to useadvanced encryption, but the OpenSSL library beingused does not implement the encryption type.

System action: The process will exit, and be restartedby the watchdog process. Any further attempt to reusethe same problematic encryption mechanism will causethe same error.

User response: Verify the correct version of theOpenSSL library is in the library search path.

Programmer response: Check version and accessibilityof the libcrypto.

GYMDL30100W Fail to checkout new MIBs fromdatabase, using local cache forcollections.

Explanation: Database is not reachable, or is down atthe time. Compiled MIB files are stored in the database,and cached on the collector file system. Updated MIBfiles are downloaded at collector startup, and everytime a reload MIBs message is received.

User response: This is not a serious issue as long asMIB files are still cached on the collector file system.Collector will complete downloading MIBs, once thedatabase connection is restored.

GYMDL30101W reason Server is shutting downbecause of '

Explanation: The administrator user has issued thecommand: pvmdmgr stop. Otherwise an error occurredduring the startup phase of the collector.

System action: The pvmd process is stopping. Allcollections will stop on that host.

User response: Nothing to do if administrativecommand. Otherwise, check the reason field.

GYMDL30006F • GYMDL30101W


GYMDL30102W time name pid Process #

Explanation: Process pvmd is down (crashed), oroverloaded. The watchdog is monitoring the pvmdprocess, and expects periodic heartbeat messages fromthe collector. This error indicates an absence ofheartbeat message for an extended period of time.

System action: The watchdog will terminate thatinstance of the pvmd (if still running), and start a newinstance.

User response: Nothing to do. Verify that the newprocess is properly running.

GYMDL30106W mibfile name Unknown or missingstructure definition for type '

Explanation: There was an error in the original sourcefile for the MIB, or some dependencies were missing atthe time of the compilation.

User response: Re-compile the original MIB, check forand fix eventual errors.

GYMDL30107W err host Host '

Explanation: This error occurs when a SNMP sessioncan not be initialized with the specified target. Thereason and internal error code are printed. This isusually caused by incorrect SNMP V3 credentials.

User response: Check error description, check SNMPcredentials.

GYMDL30108W tnsentry login Unable to connect todatabase using '

Explanation: Incorrect user/password specified,incorrect database environment specified, or the listeneris down on the database server.

User response: Verify database user/passwordinformation. Verify database environmentconfiguration. Verify the database listener is operating.

GYMDL30112W msg

Explanation: The parsing or the execution of theformula failed because of an unrecognized token, aninvalid number of arguments for a function, or anunexpected value for an argument. The messageindicates the exact location of the problem.

User response: If the error indicates a syntax error inthe formula, correct the offending function or argumentin the formula definition, and bounce the collector. Ifthe error indicates a runtime error with a particularvalue for an argument, and the error is occurringrepetitively, check the formula logic, and if the value isa valid input, extend the formula to handle it. Thenbounce the collector.



GYMDL30113W correctmib originalmib id Formula ID#

Explanation: There used to be an issue with theformula Editor, that would produce syntacticallyincorrect content for the dependent MIBs. Formulassaved at that time may have that problem.

System action: System will automatically convert theconfiguration to a valid entry and proceed.

User response: Edit, and save again the formula usingthe formula editor to regenerate the MIB attachments,and prevent the message to reappear.

GYMDL30114W Collector is unable to reconnect todatabase.

Explanation: Database is down, listener process isdown, network between collector and database isdown.

System action: Collector will make periodical attemptsto reconnect to the database if the connection isinterrupted.

User response: Check database status. Let the collectorreconnect by itself when the database is available again.

GYMDL30115W miblist oid Oid '

Explanation: A particular OID used in the formulaexpression has not been found in any of the Mibsassociated with the formula. The formula can not beexecuted as is, and will not produce any result.

User response: Check that the particular mib file ispresent in the mibs/oid directory on the collectormachine. Edit and save the formula to force theformulaEditor to regenerate the list of associated Mibs.

Programmer response: Check if alm00206651 issueapplies.

GYMDL30116W filename Empty or missing MIB file '

Explanation: A Mib file, required by a formula is notfound on the local filesystem. The formula can not beexecuted as is, and will not produce any result.

User response: Issue a confReload pvmMibscommand, check if the Mib file is copied. Try torecompile the source Mib file.



GYMDL30117W duration port host fromto Socket

Explanation: There has been no traffic on a TCPconnection to the collector for a long time. Idleconnections are automatically stopped, and associatedresources are freed.

Programmer response: The duration is controlled bythis configuration setting:TUNING.IDLESOCKETTIMEOUT

GYMDL30118W message key Item #

Explanation: An inconsistency has been detected inthe model. The detail is part of the message.Inconsistencies can occur when several modificationsare performed by various modules, and resyncmessages are not systematically sent to the collectorsfollowing the modifications.

System action: The collector will perform a fullreload, instead of an incremental reload, of the modelin order to catchup with all past changes, and retrievea consistent model.

Programmer response: One type of inconsistency canbe created by the grouping tool, where subElements aremarked as subelement.state='off', but are still part of agroup with a relation content.state='on'.

GYMDL30119W Unable to register current moduleversion in database.

Explanation: The collector failed to update it's versioninformation in the component version tables.

User response: Check SQL credentials used by thecollector to access the database.

GYMDL30120W lang NLS_LANG is not defined, andshould be set toNLS_LANG=AMERICAN_AMERICA.

Explanation: The environment variable NLS_LANG isused by the database client to encode/decode stringinformation. The configuration of the client must matchthe one of the database.

User response: Edit file dataLoad.env, and setNLS_LANG to the recommended value. Source theenvironment again, and bounce the collector.



GYMDL30121W desc id state System overflow.Attempting to reactivate a

Explanation: The scheduler has detected that aperiodic task is still running from it's previousexecution. In order to avoid overload of the system, thecurrent execution of the task is cancelled.

System action: Collector will skip one execution of thetask

User response: If the message is repeated throughoutthe day, this is a sign of a serious performanceproblem, where the collector is overloaded. Loadshould be reduced, by either splitting collections withanother collector, removing some requests, or whenpossible optimizing collection formulas.

Programmer response: See troubleshooting tips fromhttp://w3.tap.ibm.com/w3ki/x/p9MJ

GYMDL30122W msg

Explanation: An explicit error PDU has been returnedby the SNMP agent, in place of the expected answerPDU.

System action: The collector will correct it'sconfiguration accordingly, and when possible reissue avalid PDU to the device. In that case there will be nodata loss.

Programmer response: If message'usmStatsNotInTimeWindows' is repeated abundantlyin the log, this could be a sign that several devicesshare the same SNMP V3 engine ID. This can beinvestigated with the tool `dialogTest2SNMPV3CacheDump all`. Conflicting engine ID is aninvalid situation, and represent a performance problemfor 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 calendarthat has no more execution dates. The request willnever be activated.

User response: Inspect the calendar definition, and thepurpose of the request. either fix the calendar, or deletethe request.

Programmer response: Collection calendars are notsupported thru the requestEditor GUI. The only way toassign a collection calendar is thru resmgr. This featurewill be deprecated soon, and should not berecommended/deployed.



GYMDL30129W entry Missing

Explanation: A mandatory configuration entry ismissing, and there is no acceptable default value.

User response: Check shell environment, sourcedataLoad.env is absent, and bounce the collector. Checkconfiguration entries using Topology Editor.

GYMDL30130W key log error

Explanation: When a configuration error is found onan agent, then all collections that have been alreadyqueued for that agent and are using the exact sameconfiguration parameters, are immediately aborted andwill report the same failure.

User response: Check nature of failure. Adjust SNMPconfiguration, or agent's configuration.

GYMDL30131W errmsg Select function error:

Explanation: This is an internal error of the SNMPlistening thread.

User response: Contact IBM support if the errorhappens again after a collector restart.

GYMDL30132W errortext version hostname Host '

Explanation: This is an internal error. A probe PDUfor the version check has not been sent properly. Theversion check will be limited or will fail.

User response: This error may happen while thecollector is shutting down, and can be ignored in thatsituation.

GYMDL30133W hostname Host '

Explanation: The collector failed to determine witch ofSNMP V1 or V2c should be used for that target. Agentor device is down, or community has changed and hasnot been updated in Proviso SNMP configuration table.

User response: Check device is alive with a ping (ifsupported by the device). Check SNMP communitystring. Check permissions on agent/firewall, for UDPtraffic on port 161, between the collector and thedevice.

GYMDL30134W shortdescr id error Error:

Explanation: The task has encountered an unexpectederror and has generated an exception.

System action: This task will be removed from theScheduler in order to avoid further errors.

User response: Check error message for probablecause.



GYMDL30135W

sqlpvdescrpvcodeoradescroracode

Explanation: A SQL error has occurred.

User response: If the error is a connection problem, check database and access credentials. If error is aSQL order, check database logs for database related problems.

GYMDL30135W sqlpvdescrpvcodedbdescr sqlcode

Explanation: A SQL error has occurred.

User response: If the error is a connection problem, check database and access credentials. If error is aSQL order, check database logs for database related problems.

GYMDL30136W Database connection is down, model has only been partially retrieved from files.

Explanation: The model has been retrieved from saved files rather that from database.

Programmer response: This mode is only available as an explicit load option from the command line,when -usedatabase no is used.

GYMDL30137W Unable to Start, unknown Channel or Collector number.

Explanation: An order to start collection has been received, but the Channel and Collector number hasnot been specified.

System action: Start order will be ignored.

GYMDL30138W modulename duration Failure to reset internal timeout since

Explanation: An operation that is required to complete in a given time has reached it's timeout.

System action: Operation will be aborted.

GYMDL30139W msgtype oid packetdump Sequencing error:

Explanation: A loop has been detected in a device's SNMP response. The same OID has been returnedtwice during the same table scan.

System action: Table scan is automatically aborted, to prevent infinite loop situation.

User response: Per SNMP standard, table scan should never loop. Check vendor of SNMP device, checkpatches for SNMP device operating system.

GYMDL30140W jobdecr errindex Agent error, invalid errorIndex=

Explanation: The SNMP response PDU does not contain a valid error index value, possibly due to acorrupted data packet.

System action: The first response variable will be used as the error index in an attempt to processes thepacket.



GYMDL30142W threshold One or several bandwidth limitations are at or near capacity (check list inprevious DL31020 messages). This is a likely cause for lost collections, and current threadavail (

Explanation: Collections may be lost because at least one collection is consuming excessive bandwidth.

User response: If a specific target from the DL31020 messages is consistently causing the excessivebandwidth, consider disabling the target.

GYMDL30143W method deletion of a still registered 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 by default.

GYMDL30145W msg Unable to invoke callback with:

Explanation: Unable to invoke callback because one or more key parameters is null.

User response: If manually invoking a system command via the UI, check input values. Otherwisecontact IBM support.

Programmer response: Investigate the system for possible configuration issues.

GYMDL30146W phase Phase '

Explanation: The specified phase of the configuration dump operation has failed.

System action: The tool will continue to the next phase to try and process as much information aspossible.

User response: Ensure the specified output directory is not in read only mode and the output device isnot out of space. Also ensurethe database configuration is correct and the database is active.

GYMDL30148W oraerror function Call to '

Explanation: The database library can not be loaded, the library does not contain an expected ocifunction, or the database proxy is unreachable.

User response: Check the log for previous DL30150 or DL30213 errors to determine the exact cause ofthe failure.

GYMDL30150W Can't connect the oraProxy in the host application (or oraProxy is not properlyinitialized), attempting to load the Oracle library instead.

Explanation: The system is unable to contact the database proxy. Either the proxy is not available or isnot configured properly.

System action: The system will attempt to load the database library instead to directly query thedatabase.

Programmer response: This may indicate a configuration and/or installation issue if not expected.



GYMDL30151W function Call to '

Explanation: The specified function is not supported via the database proxy.

User response: Ensure the command is started with the appropriate options. The -useOraProxy switchshould be used to disable the use of the database proxy.

Programmer response: Ensure the system is configured and/or installed properly as this may be anindicator of a configuration issue.

GYMDL30160W filename Load failed. Library file '

Explanation: The OpenSSL library filename specified in the message was not found via the standardlibrary search path in the environment.

User response: Ensure the OpenSSL library file is in the standard library search path for the application,or update the search path toinclude the location of the file listed in the message.

GYMDL30161W prev current prev devname RFC1213LIB, Non compliance detected for device '

Explanation: The system detected a time difference of less than 1 second between the current changevalue and the last change value with no other status change for the device. This could indicate anon-compliance device or a potential device failure.

System action: The system will continue after adjusting to use the previous change time.

User response: If this message occurs regularly, but is not expected, the device should be investigatedfor potential problems.

GYMDL30162W Configuration validation failed.

Explanation: At least one configuration entry is not valid. Check the log for other messages providingmore details as to which entry is incorrect.

User response: If the configuration was recently edited, make corrections based on the other messagesin the log and rerun the previous command.

GYMDL30163W Unable to Start, process is currently shutting down.

Explanation: The current process is already started, or is still in the process of shutting down.

User response: Verify the process is not already started. If recently requested the process to stop, wait ashort time before attempting to start the process.

GYMDL30164W state Currently

Explanation: The process is in the specified state. It can not be started while in that state.

User response: If recently requested the process to stop, wait a few moments before attempting to startthe process.



GYMDL30165W Unable to Start with a different configuration, use Stop first.

Explanation: Attempting to start with a different channel number or collector number without stoppingthe existing process.

User response: Use the current channel number and collector number to start the process, or stop theprocess first.

GYMDL30166W Unable to Start, improper configuration, or invalid database connection.

Explanation: Unable to start the process. Either the specified channel and collector number are incorrect,or the database connection is incorrect.

User response: Ensure the channel and collector number are valid. Also ensure the database isoperational and configured properly.

GYMDL30167W Unable to Stop, process is already shutting down.

Explanation: The process is already being shutdown. Unable to issue a stop command at this time.

User response: Wait a few moments and verify the process has stopped.


Explanation: The process is in the specified state. It can not be stopped while in that state.

User response: If recently requested the process to start, wait a few moments before attempting to stopthe process.

GYMDL30169W Can't Stop from other that Ready or Running states.

Explanation: The process is not in a ready or running state. It can only be stopped while in one of thosetwo states.

GYMDL30170W Unable to Load, unknown Channel or Collector number.

Explanation: Unable to load the configuration for the collector because the channel or collector numberis not known by the system.

User response: Ensure the channel and collector number are valid. Attempt the load operation after anycorrections are made.

GYMDL30171W Unable to Load, process is currently shutting down.

Explanation: The process is already being shutdown. Unable to issue a load command at this time.

User response: Wait a few moments and verify the process has stopped. Then issue command to loadthe configuration.


Explanation: The process is in the specified state. New configuration can not be loaded while in thatstate.

User response: If recently requested the process to stop, wait a few moments before attempting to loadnew configuration.



GYMDL30173W Can't Load from Ready or Running state.

Explanation: The process is in a ready or running state. New configuration can not be loaded while inone of those two states.

User response: Try stopping the process before loading new configuration.

GYMDL30174W Unable to Load, improper configuration, or invalid database connection.

Explanation: Unable to load new configuration. Either the specified channel and collector number areincorrect, or the database connection is incorrect.

User response: Ensure the channel and collector number are valid. Also ensure the database isoperational and configured properly.

GYMDL30175W Unable to Pause, process is currently shutting down.

Explanation: The process is already being shutdown. Unable to issue a pause command at this time.

User response: Wait a few moments and verify the process has stopped.

GYMDL30176W Can't Pause from Idle or Ready state.

Explanation: The process already in an idle or ready state. Unable to pause the process while in one ofthose two states.

GYMDL30177W Database connection is down, model can not be retrieved.

Explanation: The model could not be retrieved from the database.

User response: Verify the database is operational.

GYMDL30178W port invalid values for TUNING.SERVICEPORT=

Explanation: The service port must be between 1025 and 65535.

User response: Correct the service port value and try the command again.

GYMDL30179W dir entry Entry '

Explanation: The directory configuration specified in the entry does not exist in the file system or is nota directory.

User response: Either create the directory specified, or update the configuration to a valid value.

GYMDL30180W Missing DATAMANAGER.FILENAMINGVALIDITY,DATAMANAGER.HEARTBEAT_FREQUENCY orDATAMANAGER.TIME_GRANULARITY configuration.

Explanation: Some configuration settings related to BOF file production are missing.

System action: Collector will fail initialization and quit.

User response: Use Topology Editor to configure the missing configuration entries.



GYMDL30181W fnv hbf DATAMANAGER.HEARTBEAT_FREQUENCY (=

Explanation: Incompatible values have been detected between configuration settings.


User response: Use Topology Editor to reconfigure the invalid configuration entries.

GYMDL30182W hbf tg DATAMANAGER.TIME_GRANULARITY (=

Explanation: Incompatible values have been detected between configuration settings.



GYMDL30183W WATCHMGR.MANAGERPORT can not be NULL

Explanation: An invalid value has been detected for the watchdog process management port. The portcan not be empty.



GYMDL30184W collectornumber channelnumber invalid values for TUNING.CHANNELNUMBER=

Explanation: Invalid values have been detected for collector and collector's channel number.


User response: Use Topology Editor to reconfigure the invalid configuration entries. Redeploy thecollector files. Ensure that the local dataLoad.env has been updated.

Programmer response: The local dataLoad.env contains the DL_CHANNEL_NUMBER andDL_COLLECTOR_NUMBER environment variable. The Deployer does not refresh that file unless the'upgrade' mode is selected. Usually the file has to be manually edited, even if the topology has beencorrected.

GYMDL30185W Configuration incomplete.

Explanation: Some configuration entry is missing or invalid. Usually the exact error is displayed in aprecedent message.


User response: Locate missing or invalid entry. Use Topology Editor to reconfigure the invalidconfiguration entries.

GYMDL30186W msgtype oid oid packetdump Sequencing error:

Explanation: An OID out of order has been detected in a table scan result. The SNMP protocol specifiesthat OIDs should be returned in a strictly ascending order.

System action: The table scan will be aborted. The response set could be incomplete.

User response: Investigate with device's vendor if a patch is available to correct this behavior.

Programmer response: Some devices like Huawei are known to return results in non strictly ascendingorder. If you can confirm that there is no risk of infinite loop, it is possible to temporarly reconfigure thecollector to ignore out of order 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 host or unable to create a socket object.

User response: Verify the host is accurate. This information may be provided via configuration or thecommand line. Also check to verifyoperating system limits have not been exceeded.

GYMDL30190W reason port host Connect to

Explanation: Unable to establish a connection to the specified host and port.

User response: Verify the port specified via configuration or the command line is correct.

Programmer response: It is possible the listener at the host and port is not active. Verify all dependentprocesses are running.

GYMDL30191W maxsize socket Socket

Explanation: The system is attempting to send data bigger than the maximum output buffer.

System action: The system will truncate the message to the maximum output buffer size and continueto send the message.

Programmer response: If this regularly occurs it could cause secondary problems where message data isincomplete.

GYMDL30192W socket Socket

Explanation: Unable to send data to the target system because the remote buffer is full and the numberof retries was exhausted.

System action: The message will not be sent to the target system.

Programmer response: This could be an indication that the target process is overloaded or unresponsive.

GYMDL30194W field Error, empty '

Explanation: The specified field is not specified when doing discovery operations via qPing.

User response: Specify a value for the missing field and retry the qPing command.

GYMDL30195W port host Can't contact pvmd process at

Explanation: Unable to establish a connection to the pvmd process running on the specified host andport.

User response: Verify the pvmd process is running. Verify the host and port 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 any necessary corrections.



GYMDL30197W ip Incorrect address

Explanation: The specified IP address is not valid.

User response: Correct the IP address in the discovery configuration or specified on the command linewhen invoking qPing.

GYMDL30198W command reason CreateProcess failed. Reason:

Explanation: Unable to run the specified command for the provided reason.

User response: Verify the specified command is executable. Correct any issues listed by the reason listedin the message.

Programmer response: Verify the operating system resources are not exhausted. Some may becorrectable by adjusting the operating system configuration.

GYMDL30199W cmd Unable to kill process using command `

Explanation: The system failed to terminate a running process using the specified command.

User response: Verify the process listed in the command is still running. If not, then the process mayhave ended before the command was issued.If the process is still running, then additional DL30198messages will provide details on why the command failed.

GYMDL30200W filename Unable to open file '

Explanation: A configuration file has been specified on the command line, but that file can not belocated or read.

User response: Check command line. Check file path. Check file permissions.

Programmer response: Using configuration files has been obsoleted in Proviso 4.4.3 with theintroduction of the Topology editor and the central database configuration. This option is only present inthe code to support debugging and internal Unit test scenarios.

GYMDL30204W duration Exit process timeout (more than

Explanation: A time boxed operation has reached it's limit. The operation will be aborted, and theprocess will exit.

GYMDL30205W facilityname No configuration records have been retrieved from REG$DCCONFIG forDCCONFIG.GLOBAL nor DCCONFIG.

Explanation: The database table that contains the module's configuration is empty.

User response: Run Topology Editor to save the topology in the database.

GYMDL30206W Unable to read DCCONFIG registry.

Explanation: The database table that contains the module's configuration can not be read.

User response: Check database connectivity from the collector machine. Check database connectionconfiguration.



GYMDL30208W tnsentry login Unable to connect to database using bootstrap connection '

Explanation: The connection to the database can not be established with the provided user, passwordand TNS ID.

User response: Check user, password and TNS ID in dataLoad.env. Check database connectivity withdatabase tools.

GYMDL30208W Unable to connect to database using bootstrap connection '

Explanation: The connection to the database can not be established with the provided user, passwordand Database name.

User response: Check user, password and Database name in dataLoad.env. Check database connectivitywith DB2 tools.

GYMDL30209W dir

Explanation: The ORACLE_HOME environment variable does not point to a valid directory, or does notcontain the expected lib32 or lib64 sub directories.

User response: Check ORACLE_HOME in dataLoad.env and check Oracle install on that machine.

GYMDL30209W dir

Explanation: The DATABASE_HOME environment variable does not point to a valid directory, or doesnot contain the expected lib32 or lib64 sub directories.

User response: Check DATABASE_HOME in dataLoad.env and check DB2 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 the configuration entry.

GYMDL30211W limit entry configuration entry '

Explanation: The value of a configuration entry exceeds the maximum expected size for suchconfiguration.

User response: Run Topology Editor to change the value for the configuration entry.

GYMDL30212W value entry configuration entry '

Explanation: The password listed is not obfuscated properly or is corrupt.

User response: Run Topology Editor to update the password for the listed entry.



GYMDL30213W libname Can't load the Oracle library '

Explanation: The expected Oracle client library file can not be loaded, or does not provide the expectedOCI calls.

User response: Check ORACLE_HOME and dynamic library path in dataLoad.env. Check permissionsfor TNPM user on the Oracle files. Check version of Oracle.

GYMDL30214W oraerr Can't 'Disconnect', reason '

Explanation: The database library is no longer available, yet there is an existing connection to thedatabase.

System action: In most cases the system is shutting down and will proceed to shutdown ignoring thiserror.

Programmer response: If occurring during a shutdown, this could be an indicator of a sequencingproblem inside the collector. If it occurs at another time something caused the library to be unloadedprior to the connection being closed.

GYMDL30215W path name

Explanation: The directory path specified does not exist, is not writable, or is not a directory.

User response: Validate all directories in the path are not read-only and are directories.

GYMDL30216W sql phase

Explanation: The specified query failed to complete in the database possibly due to the database beingunavailable.

User response: Verify the database is operational.

Programmer response: If a proxy is used to query data verify the $DL_LOG_HOME/tmp directory usedto hold query results exists and is writable.If the query consistently fails, then it is possible some sort ofconfiguration issue is causing the problem within the database. Verify the query can be successfullycompleted outside of the collector and expected results are returned.

GYMDL30217W Unable to use command to stop process.

Explanation: The command to stop the watch dog process failed to run.

User response: Check the log for DL30198 errors which will provide more details on why the commandfailed.

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 DL30005 and DL30198 messages in the logfor details on why the 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 run and try again with the properargument.

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 a smalltalk command from thecollector.

GYMDL30222W command taskid hexaddr Unable to invoke callback=

Explanation: Unable to invoke the call back routine because it is null, the task id is 0, or the commandis not specified or is null.

Programmer response: Investigate configuration or install issues that may lead to incomplete data beingused to try and invoke the SmallTalk interface.

GYMDL30224W num fid Formula #

Explanation: The formula listed has a different data type than the formula associated with the savealias.

System action: The alias is ignored and formula processing will continue checking other possible savealias values.

GYMDL30225W num fid Formula #

Explanation: The formula listed uses a formula ID that does not exist.

System action: The alias is ignored and formula processing will continue checking other possible savealias values.

GYMDL30226W dbnum num fid Formula #

Explanation: The formula is already associated with a save alias in the database. The new save alias isnot the same value.

System action: The new save alias is ignored and the formula will be associated with the save aliasalready in the database.

GYMDL30227W dblang systlang Values for NLS_LANG differs between the system (

Explanation: The environment variable NLS_LANG is used by the database client to encode/decodestring information. The configuration of the client must match the one of the database.

User response: Edit file dataLoad.env, and set NLS_LANG to the database value. Source theenvironment again, and bounce the collector.



GYMDL30228W ERROR, remote connection is down, removing task

Explanation: The collector was unable to transmit results to the remote client.

User response: Ensure all processes are active that depend on collector results.

GYMDL30229W id name Unable to compile/install formula '

Explanation: There was an error processing the expression of the listed formula or the formula wasunable to be parsed.

User response: If the formula was recently edited, verify the formula is correct.

GYMDL30230W Execution failed due to invalid SNMP symbols in formula expression

Explanation: Unable to process the SNMP symbols for the formula.

User response: If the formula was recently edited, verify the formula is correct.

GYMDL30231W Initialization failed due to syntax problem in OIDs list.

Explanation: Failed to parse the OID list associated with the formula.

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.


GYMDL30233W Unable to start WatchDog process, Aborting WatchDog thread.

Explanation: Unable to start the watch dog process for the collector.

User response: Check the log for other DL30198 errors which should provide more information as towhy the process failed to start.

GYMDL30234W Unable to communicate with WatchDog process, Aborting WatchDog thread.

Explanation: The collector is unable to communicate with the watch dog process.

User response: Check the log for other DL30189 and DL30190 errors which may explain why thecommunication failed.

GYMDL30235W gid seid Can't get Elmt or Instance info for SubElmt#

Explanation: The sub-element listed is missing an association with an element or is missing instanceinfo. The sub-element is used in collections and becauseof the missing information, will cause missingresults.

System action: The sub-element will be skipped due to the missing information. Since it is used in acollection it will cause missing results.

User response: Try running discovery again which could fix the model either by retiring all connectedobjects, or by recreating the missing ones.



GYMDL30236W gid seid Can't get Elmt or Instance info for SubElmt#

Explanation: The sub-element listed is missing an association with an element or is missing instanceinfo.

System action: The sub-element will be skipped due to the missing information.


GYMDL30237W seid Can't get Elmt info for SubElmt#

Explanation: The sub-element listed is missing an association with an element. The sub-element is usedin collections and becauseof the missing information, will cause missing results.

System action: The sub-element will be skipped due to the missing information. Since it is used in acollection it will cause missing results.


GYMDL30238W port host servicename Incomplete definition for

Explanation: Either the service name is not known to the collector, or the request is incomplete orcorrupted.

System action: System will ignore the request and continue normal operations.

User response: Attempt to re-issue the request or re-run the command line tool issuing the request thatfailed if known.

Programmer response: If this happens often, there could be a compatibility issue from the componentrunning on the specified host/port or with the command line script issuing the request.

GYMDL30239W ip name Reboot detected on device '

Explanation: The collector detected that the named device at the listed IP address was rebooted. Adevice reboot may result in dataloss if a collection was attempted during the reboot cycle.

User response: Ensure the device is operating normally if the reboot was not expected.

GYMDL30241W Unable to initialize DataBaseAccess Library.

Explanation: Failed to initialize the database access library.

Programmer response: This is likely a very rare occurrence. If it does occur it likely means operatingsystem resource limits have been hit.

GYMDL30242W errno Unable to determine max open files per process. errno=

Explanation: Unable to obtain the max number of open files from the operating system.

User response: Check to ensure the number of open files is set via the ulimit command.

Programmer response: This is a rare failure. Ensure the collector binary is valid and ensure the ulimit isnot being changed prior to the binary starting.



GYMDL30243W syst est Max open files (estimated) of

Explanation: The max number of open files required by the collector configuration exceeds themaximum value set for the operating system.

User response: Ensure the operating system maximum is set to a reasonable value. If not, adjust theoperating system value. Otherwise usethe topology editor to adjust the configuration settings listed in themessage. Note, the collector requires 8 additional open files in addition to thetotal for the configurationsettings.

GYMDL30244W syst est Max simultaneous threads value of

Explanation: The number of threads required by the collector is greater than the maximum number ofthreads allowed by the operating system.

User response: Ensure the operating system maximum is set to a reasonable value. If not, adjust theoperating system value. Otherwise usethe topology editor to adjust the configuration setting listed in themessage. Note, the collector requires 12 additional threads in addition to theconfiguration setting value.

GYMDL30245W max_value Scheduler quota exceeded. Unable to create more than

Explanation: More jobs have been requested to be scheduled than is allowed by the currentconfiguration.

User response: If more jobs are desired, adjust the listed configuration variable.

Programmer response: If the schedule limit is already quite large, this could be indicating that severaljobs are consuming too much time or the collector is overloaded.

GYMDL30246W reason port call Socket

Explanation: The specified operating system call did not complete successfully using the port listed.

System action: In the case of calls to select() and accept(), the collector will try to reset the socket andcontinue if successful.

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 should list the port that is havingproblems. Ensure the port is not used by another process.

GYMDL30248W max_value Too many clients at the same time, no more than

Explanation: More clients have established connections to the collector than the collector will handle.

User response: Ensure the clients are operating normally. If not, restart or stop the client. Ensure thecollector is operating normally. If not, restart the collector.



GYMDL30249W manager request Undefined error when applying request

Explanation: An error occurred within the model hierarchy while trying to apply the request.

System action: The system will ignore the request and continue normal operations.


GYMDL30250W file Filesystem '

Explanation: The file system that would host the listed file is out of space.

User response: Clean out any unnecessary files from the file system to create free space.

GYMDL30251W err field host Host '

Explanation: The SNMP V3 read community syntax is not correct for the listed host.

User response: Edit the read community value for the specified host to correct the problem.

GYMDL30253W cmd Unable to start external Watchdog process using '

Explanation: Failed to start the watch dog process with the listed command.

User response: Check the log for other DL30198 errors which should provide more information as towhy the command failed to run.

GYMDL30254W Aborting WatchDog thread.

Explanation: The watch dog thread detected an unknown state. The thread will stop immediately.

Programmer response: This is a very rare occurrence. If occurs regularly, it is recommendeddevelopment become involved.

GYMDL30255W entry host Host '

Explanation: The SNMP V3 parameter in the listed entry is empty for the specified host.

User response: Correct the SNMP V3 authentication for the host to the proper format.

GYMDL30256W line key host Host '

Explanation: The SNMP V3 parameter value for the listed key is empty for the specified host.


GYMDL30257W line key host Host '

Explanation: Incorrect SNMP V3 parameter specified for the listed host.




GYMDL30258W param host Host '

Explanation: The mandatory parameter listed is missing for the SNMP V3 entry for the specified host.


GYMDL30259W val host Host '

Explanation: An unknown access mode was provided for the SNMP V3 authentication for the specifiedhost.

User response: Correct the SNMP V3 authentication for the host to use a valid access mode.

GYMDL30261W name Host '

Explanation: The mandatory parameter SecurityName was not listed for the SNMP V3 authenticationfor the specified host.

User response: Correct the SNMP V3 authentication for the host to provide the SecurityNameparameter.

GYMDL30262W host Host '

Explanation: Unable to generate a security authentication key based on the SNMP V3 authenticationinformation for the specified host.

User response: Verify the SNMP V3 authentication for the host is correct. If so check for DL30007 errorswhich may indicate a secondary error.


Explanation: The mandatory parameter PrivPasswd was not listed for the SNMP V3 authentication forthe specified host.

User response: Correct the SNMP V3 authentication for the host to provide the PrivPasswd parameter.


Explanation: Unable to generate a security privacy key based on the SNMP V3 authenticationinformation for the specified host.

User response: Verify the SNMP V3 authentication for the host is correct. If so check for DL30007 errorswhich may indicate a secondary error.

GYMDL30265W hostname line file Insert of empty session in list in

Explanation: The collector is processing an incorrect SNMP session for a job associated with thespecified host.

Programmer response: Contact development with the error and message to determine futher diagnosticsteps.



GYMDL30266W msg

Explanation: The parsing or the execution of the formula failed because of an unrecognized token, aninvalid number of arguments for a function, or an unexpected value for an argument. The messageindicates the exact location of the problem.

User response: If the error indicates a syntax error in the formula, correct the offending function orargument in the formula definition, and bounce the collector.If the error indicates a runtime error with aparticular value for an argument, and the error is occurring repetitively, check the formula logic, and ifthe value is a valid input, extend the formula to handle it. Then bounce the collector.

GYMDL30271W number elapsedtime unknowntime downtime uptime curlastchange curstate curcoltimecurrentuptime prevlastchange prevstate prevcoltime prevuptime name RFC1213LIB, discardedifAvailability result for SubElement '

Explanation: The collector discarded the ifAvailability result for the listed sub-element because one ormore data items are 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 investigatedfor potential problems.

GYMDL30272W Some new inconsistencies have been detected, a full model reload is attempted.

Explanation: The collector detected inconsistencies in the model.

System action: The collector will request a full reload of the model to try and correct the inconsistencies.

User response: If the problem persists, try running discovery again which could fix the model either byretiring all connected 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, and bounce the collector.

GYMDL30274W Formula HostNeeds / DataType is not defined, probably invalid ID.

Explanation: The formula host needs, or data type is not specified. Possibly the formula is using anunknown or incorrect ID.

User response: If formula was edited recently, verify the formula specification is correct.

GYMDL30275W Formula expression is not defined, probably invalid ID.

Explanation: The formula expression is not specified. Possibly the formula is using an unknown orincorrect ID.

User response: If formula was edited recently, verify the formula specification is correct.



GYMDL30276W error cmd OraProxy command '

Explanation: The specified command failed with an error when running via the database proxy.

Programmer response: The proxy either is not operational, the file system is full, or there is a problemwith the query.

GYMDL30277W curid OraProxy expected result file for cursor '

Explanation: Unable to find the specified cursor file either because the file does not exist, or the cursorid was not processed correctly.

User response: Ensure directory $DL_LOG_HOME/tmp exists, is writable, and the file system is not outof space.

GYMDL30278W rid mid Invalid Metric Record with NaN Value Found (MetricId: '

Explanation: Found a record with a not a number value, but is expected a valid floating point number.

System action: The metric will not be saved because the system can not process these values.

GYMDL30279W formulaPath Missing or non-readable formula file '

Explanation: The specified formula file does not exist or is not readable.

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 while executing command '

Explanation: The collector was not able to run the command specified.

User response: Verify the specified command is executable from the command line.


GYMDL30282W SNMPv3 support is limited to Auth(None,MD5) x Priv(None).

Explanation: SNMPv3 cryptography support can not be loaded. Collections requiring advancedencryption support may result in lost collections.

System action: The system will start with limited encryption support. Uses of advanced encryptionsupport will result in DL30007 messages.

User response: Either install the cryptographic library, and make sure the library is in the standardsearch path, and accessible for the current user.



GYMDL30283W filename Load failed. Found file '

Explanation: The OpenSSL library filename specified in the message was found via the standard librarysearch path, however does not implement all required functions.

User response: Ensure the proper version of the OpenSSL library file is found first in the standardlibrary search path for the application.

GYMDL30284W hostname Unable to resolve IP address for '

Explanation: The system is unable to determine the IP address for the specified host name.

User response: Ensure the host name is spelled correctly. If it is correct it may need to be fully qualifiedwith a domain. Also verify the name is what is stored in DNS or the local hosts file.

GYMDL30285W scriptPath Command '

Explanation: The specified command returned unexpected results.

Programmer response: Verify the command returns valid results when run from the command line.

GYMDL30286W The configuration contains IPv6 address(es). IPv6 is not currently supported on thismachine.

GYMDL30287W SNMPJob jodescr can not start in a dedicated thread. Internal error is ' err

Explanation: Incomplete SNMPv3 metric collection Some data loss can be observed from the “Expectedmeasures” and “Produced measures” in the SNMP collector log message, especially when there is asudden drop in “Produced measures” when compared with 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>

This is a thread-related issue that corresponds to insufficient resources to create another thread, or there isa system-imposed limit on the number of threads to be created. The attached workaround is applicableonly if the following warning message is displayed first to indicate that this is a thread-specific issue asthere 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 erroris ’<2s:err>’.

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

Note: This decreases the overall performance of the collector.Concurrency is controlled by the GLOBAL.SNMP.MAXASYNC parameter, which is given the defaultvalue of 256. The default value can be changed by adding a Custom Datachannel parameter in the TNPMtopology. This parameter can be added using 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 logging level for the specified taskId orchannel Id.

GYMDL31003I version Version:

Explanation: A message indicating the current version number of the collector.

GYMDL31004I reason terminating collector because of

Explanation: The collector is being stopped due to the specified reason.

GYMDL31005I schema tns login Connected to DB '

Explanation: Message indicating the collector successfully connected to the database and the schemaversion being used.

GYMDL31006I err

Explanation: A message indicating any errors that occurred during an SNMP set request.

User response: If the errors are consistent then this may indicate the request is incorrect or is notsupported 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 DL31095 messages. Other causes are badformatting or the type refers to an SNMP trap.

GYMDL31009I data fid Formula #

Explanation: The specified formula has been marked as complex and may cause performance problems.

GYMDL31010I Collector is now reconnected to database.

Explanation: The collector detected the database connection was lost and was successfully able toreconnect.

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 state and can not be scheduled.

GYMDL31001I • GYMDL31012I


GYMDL31014I msg

Explanation: This is a status message indicating the current action being 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 of how many tasks were synchronized outof the total number of tasks is also provided.

GYMDL31017I jobdescr Performance warning: Job

Explanation: The specified job consistently does not return results for the number of PDUs associatedwith it. It may cause performance problems within the collector.

User response: Consider disabling or correcting the job if performance problems are occurring. Othermessages associated with the job may indicate a cause.

GYMDL31018I descr id returnedcode Task returned TASK_RESULT_ZOMBIE (

Explanation: The specified task is no longer operational. Deleting the task.

GYMDL31019I capacity_percent quota usage number capacity_percent target_percent quota estimated usagecollMeasuredKbps:

Explanation: The bandwidth for the collector was adjusted. The new values are listed.

GYMDL31020I usedcapacity quota usage name BandwidthLimiter:

Explanation: The collector output the current performance summary for the specified bandwidth limiter.

GYMDL31021I port Listener started on TCP port

Explanation: The listener was successfully started on the specified port and is ready to acceptconnections.

GYMDL31022I requests mibs metric segrpmbr segrp se prop elmt Elmt:

Explanation: A message indicating the model counts for each type of object.

GYMDL31023I Starting full model reload.

Explanation: The collector has started a full model reload operation.

GYMDL31024I Starting incremental model reload.

Explanation: The collector has started an incremental model reload operation.



GYMDL31051I phase Phase '

Explanation: The specified phase of the configuration dump operation has succeeded.

GYMDL31052I level Set global log generation level to '

Explanation: The logging threshold was updated to the new level indicated in the message.

GYMDL31053I sql cnxid Err CnxId=

Explanation: An error occurred accessing the database, see log for other messages. This message isshowing the context id and SQL that was issued when the error occurred. This message is controlled bythe DIAG.SQL.SHOWSELECT configuration setting.

GYMDL31054I sql curid cnxid OK CnxId=

Explanation: The last SQL command was successful. This message is showing the context id and SQLthat was issued. This message is controlled by the DIAG.SQL.SHOWSELECT configuration setting.

GYMDL31055I curid Error in CurId=

Explanation: This message indicates no result set was generated due to an error in the last databaseoperation. This message is controlled by the DIAG.SQL.SHOWRESULTSET configuration setting.

GYMDL31056I result curid OK CurId=

Explanation: This message is displaying the result of the last database operation. This message iscontrolled by the DIAG.SQL.SHOWRESULTSET configuration setting.

GYMDL31057I dstcollnum srccollnum eltname Marking element cache as dirty, element

Explanation: The element listed is being marked dirty because it is being moved to anothercollector.This message is controlled by the DIAG.DBUPDATE.COLLECTORCHANGE configurationsetting.

GYMDL31058I Process successfully stopped. returned code = 0

Explanation: The process indicated by message DL31091 has successfully been stopped.

GYMDL31059I name EmptyTask:

Explanation: Message indicating the task is being cleared or emptied because it was completed, deletedor stopped.This message is controlled by the DIAG.SCHED.EMPTYTASK configuration setting.

GYMDL31060I rid mid taskid index Refusing to stop task (index=

Explanation: Refusing to stop the specified task because it is used in the model.This message iscontrolled by the DIAG.SCHED.STOPINMODEL and DIAG.SCHED.STOPCHECKMODEL configurationsettings.



GYMDL31061I taskid index Allowing task (index=

Explanation: The system is allowing the specified task to be stopped because it is not used in themodel.This message is controlled by the DIAG.SCHED.STOPOUTOFMODEL andDIAG.SCHED.STOPCHECKMODEL configuration settings.

GYMDL31062I hour Create CLOSE_HOUR file for hour

Explanation: The system created the CLOSE_HOUR file for the specified hour.

GYMDL31063I hour Skip CLOSE_HOUR file for hour

Explanation: The system is skipping creating the CLOSE_HOUR file because requests are currentlydisabled.

GYMDL31064I memused dbavail quotaavail uptime overflowrisk threadavail itemscount hour Hour:

Explanation: A message outputting collector statistics for the last hour.

GYMDL31065I inpdutot outpdutot inpdudisc outpdudisc snmpsuccess resptime hour Hour:


GYMDL31066I prodmeas expmeas requests metrics ses hour Hour:


GYMDL31067I err SNMPJob failed to complete with error: '

Explanation: An SNMP job failed with the specified error. This message is controlled by theDIAG.FORMULA.SNMPJOBFAILURES configuration setting.

GYMDL31068I now timeout lastclose NEXT_HOUR_TIMEOUT detected. Last closed hour=

Explanation: The system detected the hour timeout and is starting to create a new close hour file.

GYMDL31069I taskid Scheduler task

Explanation: The system has detected a task that needs to be synchronized.This message is controlled bythe DIAG.CMPLXCACHE.RESYNCINSERTION, DIAG.LIBCACHE.RESYNCINSERTION, andDIAG.LITECACHE.RESYNCINSERTION configuration settings.

GYMDL31070I taskid Registering synchronization on scheduler task

Explanation: The system has detected a task that needs to be synchronized, however the task hasalready been registered for deletion.This message is controlled by theDIAG.CMPLXCACHE.RESYNCDELETE, DIAG.LIBCACHE.RESYNCDELETE, andDIAG.LITECACHE.RESYNCDELETE configuration settings.



GYMDL31071I taskid Scheduler task

Explanation: The system has detected a task that needs to be deleted.This message is controlled by theDIAG.CMPLXCACHE.DELETEINSERTION, DIAG.LIBCACHE.DELETEINSERTION, andDIAG.LITECACHE.DELETEINSERTION configuration settings.

GYMDL31072I taskid Registering deletion on scheduler task

Explanation: The system has detected a task that needs to be deleted, however it is already registered tobe synchronized.This message is controlled by the DIAG.CMPLXCACHE.DELETERESYNC,DIAG.LIBCACHE.DELETERESYNC, and DIAG.LITECACHE.DELETERESYNC configuration settings.

GYMDL31077I Altering return value from ZOMBIE to VALID.

Explanation: Resetting the result from ZOMBIE to VALID per configuration setting.This functionalityand message is controlled by the DIAG.FORMLITE.EXECUTERETURNVALUE configuration setting.

GYMDL31078I form InitMetric (in cache) returned an error for:

Explanation: The system detected an error initializing a cached metric.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 not currently in the cache.This message iscontrolled by the DIAG.FORMLITE.RESETFORM configuration setting.

GYMDL31084I Disable SNMP log generation

Explanation: The system is disabling SNMP log generation based on the new debug level.

GYMDL31085I Disable DBDriver log generation

Explanation: The system is disabling DBDriver log generation based on the new debug level.

GYMDL31086I level Set DBDriver log generation level to

Explanation: The system is enabling DBDriver log generation to the specified level.

GYMDL31087I Start command successfully executed. Returned code = 0

Explanation: The command listed in the previous DL31088 message started successfully.

GYMDL31088I cmd name Starting new process '

Explanation: The system is about to attempt to start a new process using the specified command.

GYMDL31089I name pid Killing process #

Explanation: The system is about to terminate the specified process, using a kill signal.



GYMDL31090I pid Process #

Explanation: The process requested to be stopped does not currently exist.

System action: The system is skipping the attempt to stop the process and attempt to start it again.

GYMDL31091I cmd name pid Stopping process #

Explanation: The system is about to attempt to stop the process using 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 a file.

GYMDL31094I descr level Set SNMP log generation level to

Explanation: The system is enabling SNMP log generation to the specified level.

GYMDL31095I line access Unknown Access Type '

Explanation: Found an unknown access type processing MIBs from a 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 was synchronized.

GYMDL31099I error [BUILD_RESULTS_FORMLITE] SNMPJob failed to complete with error

Explanation: The SNMP job failed to complete with the specified error.This message is controlled by theDIAG.FORMULA.SNMPJOBFAILURES configuration setting.

GYMDL31100I mib type missing type '

Explanation: The system was unable to find the type specified in the file listed. It was able to find analternate definition in another file.

GYMDL31101I Altering closure return value from ZOMBIE to VALID.

Explanation: Resetting the result from ZOMBIE to VALID per configuration setting.This functionalityand message is controlled by the DIAG.FORMLITE.EXECUTECLOSURERETURNVALUE configurationsetting.



GYMDL31102I Altering return value (was 0:failure) changed to 1:success.

Explanation: Updating the return value to success from failure per configuration setting.Thisfunctionality and message is controlled by the DIAG.FORMLITE.RESETFORMRETURNVALUEconfiguration setting.

GYMDL31103I curdevuptime curlastchange curstatus curvalidcoltime curdevuptime prevlastchange prevstatusprevvalidcoltime prevdevuptime sename RFC1213LIB, invalid lastChange timestamp forSubElement '

Explanation: The system discovered an incorrect timestamp for the specified sub-element. The system isforcing the last change 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 commandline.

GYMDL31106I Internal, task must be TASK_ACTIVE, TASK_ASLEEP or TASK_ZOMBIE to bevalidated

Explanation: The task does not have an expected status and is being marked as failed.

GYMDL31107I taskid Empty'ing TaskId #

Explanation: Clearing task because the status is zombie.

GYMDL31108I indexsize storagesize StatManager storage=

Explanation: Current memory usage by the statistic manager.This message is controlled by theDEBUG.LOGMEMUSE configuration setting.

GYMDL31109I efficiency jobdescr SNMPJob

Explanation: The system is stopping an expensive SNMP job before it runs.This message andfunctionality is controlled by the SNMP.ABORTEXPENSIVEJOBS configuration setting.

GYMDL31111I Process successfully killed.

Explanation: The process mentioned in the previous DL31089 message was successfully killed.

GYMDL31112I versioncode versionstring name Library '

Explanation: The SSL library was successfully loaded. The file name and version are provided.

GYMDL31113I name Library '

Explanation: The open SSL library listed was not used as directed by configuration.This message andfunctionality is controlled by the TUNING.USE_OPENSSL configuration setting.



GYMDL31114I Full SNMPv3 support Auth(None,MD5,SHA-1) x Priv(None,DES,AES) is available.

Explanation: The open SSL library was loaded providing full SNMP V3 support.

GYMDL31115I name Library '

Explanation: The open SSL library was removed from the collector. Partial encryption support now ineffect 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 inorder to resume normal operations. The severity code indicator is identified by acharacter at the end of the message ID. They are as follows:v ‘E' – Error

Typically, errors describe events that represent an unrecoverable error within aserver that affect its ability to service some requests, but not all operations areaffected.

v ‘W – WarningTypically, warnings represent recoverable errors.

v I - InformationalTypically, informational messages represent events like normal conditions, eventssupplied to clarify operations, e.g. state transitions, operational changes.

Note: In this guide informational messages are not documented as they are selfexplanatory and do not require any user action.

GYMVB0002E Settings have not been saved.

Explanation: See message.

User response: Try again. Contact the systemadministrator if this problem persists.

GYMVB0003W No settings are currently enabled forconfiguration.


GYMVB0004E A valid email address is required.Type a valid email address.

User response: See message.

GYMVB0005E Unable to set your email address atpresent.


User response: Contact the system administrator ifthis problem persists.

GYMDL31114I • GYMVB0005E


GYMVB0006E The email address has beensuccessfully set.


GYMVB0008E Changes could not be saved.


Administrator response: Check the network anddatabase connectivity.

GYMVB0009E A valid email address is required.


User response: Type a valid email address.

GYMVB0010E A valid number is required.


User response: Type the number by using the digits 0through 9 only.

GYMVB0011E The time format is not valid.


User response: Type the time in 24-hour notationformat (HH:mm:ss).

GYMVB0012E Changes were not applied. Thefollowing DataView server is alreadyconfigured:PDF Server


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.

GYMVB0006E • GYMVB0012E


GYMB0013E Unable to load user.


GYMB0015E Changes could not be applied.



GYMVB0017E Changes could not be applied.



GYMVB00018E Unable to load profile.


GYMVB0019E A valid number is required.


User response: Type the number by using the digits 0through 9 only.

GYMVB0020W Missing the required information todisplay the threshold violation data.


GYMVB0021E An error occurred while obtainingand rendering data.


System action: Event representing the setting of a setof context parameters.Event representing the setting of a report runtimeparameter.Event representing the successful generation of areport.

GYMVB9000E The following DataView server isalready configured:<server name>


GYMB0013E • GYMVB9000E


GYMVB90001E A value is required for this text field.<text field name>


GYMVB9010E Unable to open workspace. Pleaseensure that the workspace definition isvalid.

Explanation: You might encounter this error, whenyou try to open a previously saved workspace.Typically, you encounter this error if the workspace isinvalid.

User response: Contact the system administrator ifthis problem persists.

GYMVC0000E DataView is not installed in eWas!

Explanation: The tool executed by you is unable tolocate an installed version of Dataview in the eWasapplication server.

System action: The tool will print the above messageto inform you that Dataview is not installed.

User response: You must contact a systemadministrator.

GYMVC0002E Can not connect to eWAS/TIP.

Explanation: The tool was not able to connect to theapplication eWas sevrer.

System action: The tool prints the message to informyou that the application server is not running.

User response: You must contact an administrator orstart up the application server.

GYMVC0003E Can not locate the'legacyDataview.war' file!

Explanation: The tool cannot find the legacyDataviewwar file that it requires 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 thelocation of the DataView context root in the eWasapplication server.

System action: DataView is not correctly installed.

User response: You must contact the administrator.

GYMVB90001E • GYMVC0005E


GYMVC0006E Action not specified or supported.Available actions are:

Explanation: You tried to use the configure tool toexecute an action that is not supported by the tool.

System action: The system will print the abovemessage followed by the supported actions.

User response: You must execute the configure toolwith one of the supported actions that is displayed.

GYMVC0007E Command not specified or supported.Available commands are:

Explanation: You passed no value or an invalid valuefor the type parameter.

System action: The system will print the abovemessage followed by the supported type of commandsfor the configure tool.

User response: You must execute the configure tool bypassing one of the supported commands that is justdisplayed as the value 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 jdbcbut did not provide any valid values for that type ofcommand.

System action: The system will print the abovemessage to show what parameters are expected whenexecuting a command of type jdbc.

User response: You must execute the tool by passingone or more of the supported jdbc parameters that isdisplayed.

GYMVC0010E Logging level not specified orsupported. Available levels are:

Explanation: You executed a command of typelogging but did not provide a valid values for that typeof command.

System action: The system will print the abovemessage followed by the valid values it accepts for thelevel parameter.

User response: You must execute the tool by passingone of the valid values for the level parameter.

GYMVC0006E • GYMVC0010E


GYMVC0011E Debug state not specified orsupported. Available states are.

Explanation: You executed the configure tool with aninvalid value for the Debug parameter.

System action: The system will print the abovemessage followed by the valid values it accepts for theDebug parameter.

User response: You must run the command again bygiving a valid value that is displayed.

GYMVC0049E Invalid JDBC home

Explanation: The location passed for the <driverhome>parameter is incorrect as the tool could not locate thejar files it needs.

User response: You must check the location andprovide the correct location.

GYMVC0050E Unsupported database type {0}

Explanation: The tool is unable to connect to the urlprovided in the <jdbcurl> parameter

System action: The above message is displayedfollowed by the invalid url.

User response: You must check the database url andprovide a valid one.

GYMVC0064E Error occurred: {0}

Explanation: This is a reused message to inform thatthe migrate tool encountered an error.

User response: You must examine the error messageto determine what to do next.

GYMVC0076E Unable to connect to SilverStream at:{0}

Explanation: The migrate tool is unable to connect tothe Silverstream server with the information passed bythe user in the <ssurl>,<ssuser>, and <sspassword>parameters.

System action: The system prints the message abovefollowed by the <ssurl> value.

User response: You must check if the Silverstreamserver is running and also that you passed the correctconnection info.



GYMVC0090E Unknown Host: {0}

Explanation: The client could not connect to the hostthat you passed in the host parameter.

System action: The system displays the messagefollowed by the host parameter.

User response: You must check that the host isrunning. Correct host info if necessary and try again.

GYMVC0091E Unable to connect to DataView at: {0}

Explanation: There is a problem connecting to theDataView server.

System action: The system displays the messagefollowed by url the tool attempted to connect by usingall the parameters provided.

User response: You must check that the check theDataView server is running.

GYMVC0092E Authentication Failure.

Explanation: There is a problem authenticating to thehost.

System action:

User response: Check your given user and passwordcredentials.

GYMVC0094E Wrong context: {0}

Explanation: There is a problem with the context infosupplied by you.

System action:

User response: Check the context you supplied isvalid.

GYMVC0095E Wrong Protocol: {0}

Explanation: The protocol supplied you is incorrect orinvalid.

User response: Supply a valid protocol.

GYMVC0096E Wrong Port: {0}

Explanation: The port number supplied by you isincorrect.

User response: Supply a valid port.



GYMVC0100E Wrong Directory

Explanation: The directory supplied by you isincorrect.

User response: Supply a valid directory.

GYMVC0101E Wrong Port: {0}

Explanation: The port number supplied by you isincorrect.

User response: Supply a valid port.

GYMVC0102E Wrong context: {0}

Explanation: There is a problem with the context infosupplied by you.

System action:

User response: Check the context you supplied isvalid.

GYMVC0103E Wrong Protocol: {0}

Explanation: The protocol supplied you is incorrect orinvalid.

User response: Supply a valid protocol.

GYMVC0105E Unknown Host: {0}

Explanation: The client could not connect to the hostthat you passed in the host parameter.

System action: The system displays the messagefollowed by the host parameter.

User response: You must check that the host isrunning. Correct host info if necessary and try again.

GYMVC0106E Unable to connect to DataView at: {0}

Explanation: There is a problem connecting to theDataView server.

System action: The system displays the messagefollowed by url the tool attempted to connect by usingall the parameters provided.

User response: You must check that the check theDataView server is running.



GYMVC0110W No files found matching pattern: {0}

Explanation: The export tool did not find any filesmatching the pattern provided by you.

System action: The export tool did not export anyfiles.

User response: You need to consider if you passed theright file extension.

GYMVD0001E Unable to dynamically generate SQL

Explanation: The system is unable to create the SQLused to retrieve the requested information from thedatabase.

System action: The system is unable to retrieve therequested information from the database. You will benotified of the error and no data will be returned.

User response: You must ensure that the requiredparameter values are supplied to the API and that theprovided values are valid.

GYMVD0001W User has not been granted access togroup: User = {0}, Group = {1}

Explanation: You made an API request that is notgranted access to information pertaining to thespecified group.

System action: The system will not process the APIrequest and no data will be returned.

User response: You must ensure that the specifiedgroup has access granted or contact the administratorto obtain access to this specific group.

GYMVD0002E Unable to retrieve information fromthe data source

Explanation: The system is unable to connect to orread from the data source containing the requestedinformation.

System action: The system is unable to retrieve therequested information. You will be notified of the errorand no data will be returned.

Administrator response: The administrator mustverify that the network connectivity between theapplication and database servers is valid and that thedatabase is running. Check the application server logfile for error messages that may indicate a problemconfiguring the data source.

GYMVC0110W • GYMVD0002E


GYMVD0002W Time period does not align withaggregation period; Dailypre-aggregated data will be used

Explanation: A request is made to retrieve thepre-aggregated data from the database, but thespecified start/end times do not align with theaggregation periods.

System action: The system will process the request byusing the daily pre-aggregated data that best fits withinthe time period specified by you.

User response: To avoid this situation, you mustensure that the start and end times specified for theAPI request align with the aggregation periodsconfigured within the system.

GYMVD0003E Specified entity name(s) are notunique: {0}

Explanation: The name(s) provided as API parametersare not uniquely identify specific entities.

System action: The system is unable to uniquelyidentify the entity for which information is requested.You will be notified of the error and no data will bereturned.

Administrator response: The administrator mustdetermine where the similarly named entities residewithin the database and assign unique names.

GYMVD0003W Monthly dates do not align withaggregation period; Dailypre-aggregated data will be used

Explanation: A request is made to retrieve themonthly pre-aggregated data from the database, but thespecified start/end times do not align with theaggregation periods.

System action: The system will process the request byusing the daily pre-aggregated data that best fits withinthe time period specified by you. Using the dailyaggregated data is less efficient than using the monthlyaggregated data.

User response: For best performance, you must ensurethat the start and end times specified for the APIrequest align with the aggregation periods configuredwithin the system.

GYMVD0002W • GYMVD0003W


GYMVD0004E Unable to determine numericidentifier(s) for entity name(s)

Explanation: The system is unable to locate the namedentities in the database.

System action: The system is unable to retrieve therequested information from the database for the namedentity. No data will be returned for that entity.

User response: You must ensure that the entityname(s) provided as API parameters are valid and thatthose entities exist.

GYMVD0004W Weekly dates do not align withaggregation period; Dailypre-aggregated data will be used

Explanation: A request is made to retrieve the weeklypre-aggregated data from the database, but thespecified start/end times do not align with theaggregation periods.

System action: The system will process the request byusing the daily pre-aggregated data that best fits withinthe time period specified by you. Using the dailyaggregated data is less efficient than using the weeklyaggregated data.

User response: For best performance, you must ensurethat the start and end times specified for the APIrequest align with the aggregation periods configuredwithin the system.

GYMVD0005W Unable to retrieve registry value {0}

Explanation: The API request is not able to retrievefrom the registry the value corresponding to thespecified registry key.

System action: The system will attempt to process therequest as appropriate without the registry value.

Administrator response: The administrator mustexamine the server logs for warning or error messagesthat may indicate a problem reading from the registryor verify that the registry entry exists.

GYMVD0006E Unable to identify named property:{0}

Explanation: The system is unable to locate the namedproperty in the database.

System action: The system is unable to retrieve therequested information from the database for the namedproperty. No data will be returned for that property.

User response: You must ensure that the propertyname provided as an API parameter is valid and thatthe property exists.

GYMVD0004E • GYMVD0006E


GYMVD0006W Unable to retrieve registry value {0};Default value of {1} will be used

Explanation: The API request is not able to retrievefrom the registry the value corresponding to thespecified registry key. The specified default value willbe used.

System action: The system will attempt to process therequest by using the default value.

Administrator response: The administrator mustexamine the server logs for warning or error messagesthat may indicate a problem reading from the registryor verify that the registry entry exists.

GYMVD0007E Unable to identify named user: {0}

Explanation: The system is unable to locate the nameduser in the database.

System action: The system is unable to retrieve therequested information from the database for the nameduser. No data will be returned for that user.

User response: You must ensure that the user nameprovided as an API parameter is valid and that theuser exists.

GYMVD0007W Unable to initialize the CORBA ORB

Explanation: The system is unable to initialize and/orconfigure the communication between the DataViewand DataChannel components necessary to supportnear-real time metric data or probe configuration.

System action: Near-real time metric data is notincluded in the API response and the user will beunable to configure probes.

Administrator response: The administrator mustexamine the server logs for warning or error messagesthat may indicate the reason for the initializationfailure.

GYMVD0008E Invalid time period: start time = {0},end time = {1}

Explanation: The system is unable to retrieve therequested information because the specified time periodis not valid.

System action: The system is unable to retrieve therequested information from the database for thespecified time period. No data will be returned to theuser.

User response: You must ensure that the start and endtime are valid and that the start time precedes the endtime.

GYMVD0006W • GYMVD0008E


GYMVD0008W Unable to establish connection tonear-real time service

Explanation: The system is unable to initialize and/orconfigure the communication between the DataViewand DataChannel components necessary to supportnear-real time metric data functionality.

System action: Near-real time metric data will not beincluded in the API response

User response: The administrator must examine theserver logs for warning or error messages that mayindicate networking problems. The DataChannel logsshould also be examined to determine whether CORBAconnections are being accepted.

GYMVD0008W


Chapter 7. Contacting IBM support

IBM Support provides assistance with product defects, answering FAQs, andperforming rediscovery.

Before you begin

After trying to find your answer or solution by using other self-help options suchas technical notes, you can contact IBM Support. Before contacting IBM Support,your company must have an active IBM maintenance contract, and you must beauthorized to submit problems to IBM. For information about the types ofavailable 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 theSoftware Support Handbook.

2. Gather diagnostic information.3. Submit the problem to IBM Support in one of the following ways:v Using IBM Support Assistant (ISA):v Online through the IBM Support Portal: You can open, update, and view all

your Service Requests from the Service Request portlet on the ServiceRequest page.

v By phone: For the phone number to call in your country, see the Directory ofworldwide contacts web page.

Results

If the problem that you submit is for a software defect or for missing or inaccuratedocumentation, IBM Support creates an Authorized Program Analysis Report(APAR). The APAR describes the problem in detail. Whenever possible, IBMSupport provides a workaround that you can implement until the APAR isresolved and a fix is delivered. IBM publishes resolved APARs on the IBM Supportwebsite daily, so that other users who experience the same problem can benefitfrom the same resolution.

Exchanging information with IBMTo diagnose or identify a problem, you might need to provide IBM Support withdata and information from your system. In other cases, IBM Support mightprovide you with tools or utilities to use for problem determination.


http://www14.software.ibm.com/webapp/set2/sas/f/handbook/offerings.html

http://www14.software.ibm.com/webapp/set2/sas/f/handbook/getsupport.html

http://www.ibm.com/software/support/

http://www.ibm.com/planetwide/

http://www.ibm.com/planetwide/

Sending information to IBM SupportTo reduce the time that it takes to resolve your problem, you can send trace anddiagnostic information to IBM 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 datamanually or automatically:v Collect the data manually.v 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:v IBM Support Assistantv The Service Request toolv Standard data upload methods: FTP, HTTPv Secure data upload methods: FTPS, SFTP, HTTPSv EmailAll of these data exchange methods are explained on the IBM Support site.


http://www.ibm.com/software/support/isa/

http://www.ibm.com/support/servicerequest

http://www-01.ibm.com/software/support/exchangeinfo.html

Notices

This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license 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 Intellectual Property Department in your country or sendinquiries, 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 THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/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 forconvenience only and do not in any manner serve as an endorsement of those


websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

The performance data discussed herein is presented as derived under specificoperating conditions. Actual results may vary.

The client examples cited are presented for illustrative purposes only. Actualperformance results may vary depending on specific configurations and operatingconditions.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

Statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to actual people or business enterprises is entirelycoincidental.

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms 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 mustinclude a copyright notice as 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 ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Notices 175

http://www.ibm.com/legal/us/en/copytrade.shtml

Java and all Java-based trademarks and logosare trademarks or registered trademarks ofOracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.


IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Notices 177

IBM®

Printed in USA

with ibm corp. · chapter 1. t roubleshooting t ivoli netcool performance manager y ou can use this...

Documents