PDF TNPM Troubleshooting

IBM Tivoli Netcool Performance Manager 1.3.
2
Wireline Component
Document Revision R2E2
Troubleshooting Guide
Note
Before using this information and the product it supports, read the information in Notices on page 177.
Copyright IBM Corporation 2011, 2013.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Chapter 1. Troubleshooting Tivoli
Netcool Performance Manager . . . . . 1
Troubleshooting a problem . . . . . . . . . 1
Troubleshooting checklist for Tivoli Netcool
Performance Manager . . . . . . . . . . . 3
Known problems and solutions . . . . . . . . 3
Troubleshooting tasks . . . . . . . . . . . 3
Real-time charts do not work as expected. . . . 3
Error: ORA-00001:unique constraint
(PV_ADMIN.PK_SEGM) violated . . . . . . 4
MDE memory constraint . . . . . . . . . 5
Incomplete SNMPv3 metric collection . . . . . 5
After upgrading Tivoli Common Reporting, it is
not possible to log into Tivoli Integrated Portal . . 6
Collectors swapping from idle to running at
startup . . . . . . . . . . . . . . . 6
Searching knowledge bases . . . . . . . . . 7
Chapter 2. Logs (Wireline Component) . 9
Overview . . . . . . . . . . . . . . . 9
Logs by component . . . . . . . . . . . . 9
Installation log files . . . . . . . . . . . 9
DataChannel logs . . . . . . . . . . . 11
DataLoad logs . . . . . . . . . . . . 12
DataMart logs . . . . . . . . . . . . 13
DataView logs . . . . . . . . . . . . 14
Database log . . . . . . . . . . . . . 14
Logs messages format . . . . . . . . . . . 14
Logging configuration and information utilities . . 15
DataChannel logs configuration . . . . . . 15
DataView logs configuration. . . . . . . . 18
statGet utility. . . . . . . . . . . . . 18
Configuring trace and logging . . . . . . . . 19
Default logging level . . . . . . . . . . 20
Trace logging for DataView . . . . . . . . 20
The configure command . . . . . . . . . 20
Troubleshooting . . . . . . . . . . . . . 22
Event IDs . . . . . . . . . . . . . . . 22
Chapter 3. Contacting IBM support . . 23
Exchanging information with IBM. . . . . . . 23
Sending information to IBM Support . . . . . 24
Chapter 4. Introduction SNMP
Inventory. . . . . . . . . . . . . . 25
Overview . . . . . . . . . . . . . . . 25
Discovery . . . . . . . . . . . . . . . 25
Metrics and Properties. . . . . . . . . . 26
Inventory Synchronization and Change
Management . . . . . . . . . . . . . . 26
Change Management for Elements . . . . . 26
Change Management for Sub-Elements . . . . 27
Grouping Sub-Elements . . . . . . . . . . 28
Where to Go From Here . . . . . . . . . . 28
Chapter 5. SNMP inventory
troubleshooting . . . . . . . . . . . 29
Overview . . . . . . . . . . . . . . . 29
Discovery Troubleshooting . . . . . . . . . 31
Discovery Does Not Start . . . . . . . . . 31
Discovery Starts But Issues Warning Messages. . 37
Discovery Seems to Hang or Never Finishes . . 45
Synchronization Troubleshooting . . . . . . . 47
Synchronization (Elements) . . . . . . . . 47
Synchronization (Sub-elements). . . . . . . 53
Grouping Troubleshooting . . . . . . . . . 57
Monitoring the Tivoli Netcool Performance Manager
Log File . . . . . . . . . . . . . . . 57
Tivoli Netcool Performance Manager Log Messages 57
Burned subelements . . . . . . . . . . . 57
Scenario 1 - Instance Shift Causes Disconnect . . 57
Scenario 2 - Instance Shift Causes Burn . . . . 58
Where to Go From Here . . . . . . . . . . 59
Chapter 6. SNMP inventory
management . . . . . . . . . . . . 61
Regular monitoring. . . . . . . . . . . . 61
Routine SNMP inventory management tasks . . . 61
Finding Elements and subelements about to
reach their retry limit . . . . . . . . . . 61
Finding Elements and Sub-elements That Have
Been Retired . . . . . . . . . . . . . 63
Where to go from here . . . . . . . . . . 64
Chapter 7. Messages. . . . . . . . . 65
DataChannel error messages. . . . . . . . . 65
DataLoad error messages . . . . . . . . . 121
DataView operational messages . . . . . . . 163
Notices . . . . . . . . . . . . . . 177
Copyright IBM Corp. 2011, 2013 iii
iv IBM Tivoli Netcool Performance Manager: Troubleshooting Guide
Chapter 1. Troubleshooting Tivoli Netcool Performance
Manager
You can use this troubleshooting and support information to troubleshoot
problems with Tivoli Netcool Performance Manager.
This information assumes a working installation of Tivoli Netcool Performance
Manager. For installation or upgrade problems, refer to the installation and
upgrade information.
Troubleshooting a problem
Troubleshooting is a systematic approach to solving a problem. The goal of
troubleshooting is to determine why something does not work as expected and
how to resolve the problem.
The first step in the troubleshooting process is to describe the problem completely.
Problem descriptions help you and the IBM technical-support representative know
where to start to find the cause of the problem. This step includes asking yourself
basic 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 the
problem? This question might seem straightforward; however, you can break it
down into several more-focused questions that create a more descriptive picture of
the 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 the
most important steps in resolving a problem. Many layers of technology can exist
between the reporting and failing components. Networks, disks, and drivers are
only a few of the components to consider when you are investigating problems.
The following questions help you to focus on where the problem occurs to isolate
the problem layer:
Copyright IBM Corp. 2011, 2013 1
v Is the problem specific to one platform or operating system, or is it common
across 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 that
layer. Part of identifying where a problem originates is understanding the
environment in which it exists. Take some time to completely describe the problem
environment, including the operating system and version, all corresponding
software and versions, and hardware information. Confirm that you are running
within an environment that is a supported configuration; many problems can be
traced back to incompatible levels of software that are not intended to run together
or have not been fully tested together.
When does the problem occur?
Develop a detailed timeline of events leading up to a failure, especially for those
cases that are one-time occurrences. You can most easily develop a timeline by
working 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 and
information. Typically, you need to look only as far as the first suspicious event
that 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 which
to investigate the problem.
Under which conditions does the problem occur?
Knowing which systems and applications are running at the time that a problem
occurs is an important part of troubleshooting. These questions about your
environment 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 in
which the problem occurs and correlate any dependencies. Remember that just
because multiple problems might have occurred around the same time, the
problems are not necessarily related.
Can the problem be reproduced?
From a troubleshooting standpoint, the ideal problem is one that can be
reproduced. Typically, when a problem can be reproduced you have a larger set of
tools 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 of
significant 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 more
flexibility 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 7
You can often find solutions to problems by searching IBM knowledge bases.
You can optimize your results by using available resources, support tools, and
search methods.
Troubleshooting checklist for Tivoli Netcool Performance Manager
By answering a set of questions that are structured into a checklist, you can
sometimes identify the cause of a problem and find a resolution to the problem on
your own.
Answering the following questions can help you to identify the source of a
problem that is occurring 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 product
v Doing administration tasks
v Doing authorization tasks
v Networking
v Using the product
4. What, if any, error messages or error codes were issued?
5. If the checklist does not guide you to a resolution, collect additional diagnostic
data. This data is necessary for an IBM
technical-support representative to
effectively troubleshoot and assist you in resolving the problem.
Known problems and solutions
A list of known problems and their solutions are described here.
For a list of known problems, visit the following Web site:
Known Issues with Tivoli Netcool Performance Manager 1.3 - Wireline Component
Troubleshooting tasks
Some troubleshooting tasks in Tivoli Netcool Performance Manager are described
here.
Real-time charts do not work as expected
Symptoms
Sometimes when you restart the Tivoli Netcool Performance Manager Channel
Name Server (CNS) or Channel Manager (CMGR) component, your real-time
charts no longer work as expected. Real-time charts require a valid reference to the
real-time subscriber object. A restart of these components can cause the Channel
Name Server (CNS) to no longer provide a valid reference to the real-time
subscriber object.
Chapter 1. Troubleshooting Tivoli Netcool Performance Manager 3
Resolving the problem
To 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_visual
You can see an output like the following:
pvuser 653 648 0 Apr 14 ?
129:46 /opt/datachannel/bin/CNS_visual
-nologo /opt/datachannel/bin/dc.im -a CNS -f /o
Note: The PID is the first number after your login ID. For example, in the
previous output, the PID 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 following
command:
./findvisual | grep CMGR_visual
5. Stop CMGR by using the following command:
kill -9 CMGR_pid
6. On the DataView host, stop the Tivoli Integrated Portal server by using the
following command:
stopServer server1 -user tip_user -password tip_password
7. On the DataChannel host, change to the $DCHOME/bin directory. For example:
cd /opt/datachannel/bin
8. Restart CNS and CMGR by running the following commands in the following
order:
./cnsw
./cmgrw
9. On the DataView host, restart the Tivoli Integrated Portal server by using the
following command:
startServer server1 -user tip_user -password tip_password
Error: ORA-00001:unique constraint (PV_ADMIN.PK_SEGM)
violated
An unique constraint error is generated during inventory and grouping.
Symptoms
The following message is received in inventory and grouping output:
-Error: ORA-00001:unique constraint (PV_ADMIN.PK_SEGM) violated
-Reason: a static group membership link exists between a sub-elements and a group
Causes
A user uses the resmgr command to insert a resource into a group and then runs
inventory grouping. If inventory grouping tries to place the same resource into the
group, a unique constraint error is generated.
Using the resmgr command, delete the grouping link.
MDE memory constraint
An unique constraint error is generated when running an MDE query.
Symptoms
The following message is received you ttempt to run MDE query:
GYMVD0002E: Unable to retrieve information from the data source" error.
or
Mon Feb 1 08:53:51 2010
ORA-1652: unable to extend temp segment by 64 in tablespace PV_LOIS_TEMP
Causes
You are constrained by the available space in PV_LOIS_TEMP.
This is a TEMP tablespace that is shared across all MDE sessions. A user uses the
resmgr command to insert a resource into a group and then runs inventory
grouping. If inventory grouping tries to place the same resource into the group, a
unique constraint error is generated.
This 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 approximately
20% less space.
v If neither option is possible, then you can increase the size of the
PV_LOIS_TEMP tablespace.
Incomplete SNMPv3 metric collection
Some data loss can be observed from the Expected measures and Produced
measures in the SNMP collector log message.
Symptoms
Some data loss can be observed from the Expected measures and Produced
measures in the SNMP collector log message, especially when there is a sudden
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>
GYMDL30287W: SNMPJob jobdescr can not start in a dedicated thread. Internal error is err.
Causes
This is a thread-related issue that corresponds to insufficient resources to create
another thread, or there is a system-imposed limit on the number of threads to be
created.
This resolution is applicable only if the following warning message is displayed
first to indicate that this is a thread-specific issue as there are many other
configuration issues that can cause data losses.
DL30287 W SNMPJOB_THREAD_ERR SNMPJob <1s:jobdescr> can not start in a dedicated thread. Internal error is <2s:err>.
If the system resources cannot be increased, decrease the concurrency in the
collector.
Note: This decreases the overall performance of the collector.
Concurrency is controlled by the GLOBAL.SNMP.MAXASYNC parameter, which is
given the default value of 256. The default value can be changed by adding a
Custom Datachannel parameter in the TNPM topology. This parameter can be
added using the Topology Editor: GLOBAL.SNMP.MAXASYNC=<value> where <value> is
a number less than 256.
After upgrading Tivoli Common Reporting, it is not possible to
log into Tivoli Integrated Portal
Symptoms
After upgrading Tivoli Common Reporting, it is not possible to log into Tivoli
Integrated Portal.
After upgrade of Tivoli Common Reporting, if you are experiencing problems
logging into Tivoli Integrated Portal, do the following you need to and :
User response:
1. Clear your Browser cache for the Tivoli Integrated Portal server
For example:
v In Firefox (v3.6):
a. Click Tools > Options > Privacy
b. Remove individual cookies.
c. Search using your Tivoli Integrated Portal server name and remove those
cookies.
2. Restart your browser.
3. log in to Tivoli Integrated Portal.
Collectors swapping from idle to running at startup
Symptoms
The situation may occur that a collector, upon startup, waits a period of time, then
transitions itself to running state only to be swapped to an idle state by the High
Availability Manager (HAM).
Causes
At startup the Collector sits in 'Idle' state waiting to determine what it should do
next ( if anything ). The HAM (High Availability Manager) should probe the
Collector, 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-spare
mode ) and staying in idle means keep waiting.
If a network disconnect occurred between the collector and HAM, the Collector
may have a configuration (channel & collector number) from its previous run state.
The result would be that the collector waits a period of time, then transitions itself
to running state only to be swapped to an idle state by the HAM. The symptom is
a result of the timing of the HAM's probing, and the Collector's idle-timeout.
User response:
If you this behaviour a problem, you update either the polling interval of the
HAM or the idle timeout of the collector:
v Increase the Collector's Idle Timeout by editing DataChannels > Global
DataChannel Properties > Advanced Properties > IDLETIMEOUT, or
v Decrease the HAM's probe interval by editing DataChannels > Administrative
Components > High Availibility Managers > <HAM identifier> > Properties >
POLL_INTERVAL
Searching knowledge bases
You can often find solutions to problems by searching IBM knowledge bases. You
can optimize your results by using available resources, support tools, and search
methods.
About this task
You can find useful information by searching the information center for Tivoli
Netcool Performance Manager, but sometimes you need to look beyond the
information center to answer your questions or resolve problems.
Procedure
To search knowledge bases for information that you need, use one or more of the
following approaches:
v Search for content by using the IBM Support Assistant (ISA).
ISA is a no-charge software serviceability workbench that helps you answer
questions and resolve problems with IBM software products. You can find
instructions 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 support
tools and information for all IBM systems, software, and services. The IBM
Support Portal lets you access the IBM electronic support portfolio from one
place. You can tailor the pages to focus on the information and resources that
you need for problem prevention and faster problem resolution. Familiarize
yourself 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, explore
troubleshooting and other resources, and demonstrate how you can tailor the
page by moving, adding, and deleting portlets.
v Search for content about Product X by using one of the following additional
technical resources:
Tivoli Netcool Performance Manager technotes
Tivoli Netcool Performance Manager Support Website
Tivoli
support communities (forums and newsgroups)

v Search for content by using the IBM masthead search. You can use the IBM
masthead search by typing your search string into the Search field at the top of
any 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 to
include information that is outside the ibm.com domain. However, sometimes
you can find useful problem-solving information about IBM products in
newsgroups, forums, and blogs that are not on ibm.com.
Tip: Include IBM and the name of the product in your search if you are
looking for information about an IBM product.
Chapter 2. Logs (Wireline Component)
Tivoli Netcool Performance Manager has various logs that can be used to examine
processing results and problems.
Overview
The following table provides a high-level description of Tivoli Netcool Performance
Manager logs.
Table 1. The Tivoli Netcool Performance Manager logs by component
Component Description
DataChannel DataChannel manages the primary Tivoli Netcool Performance Manager
proviso.log log file. This log file collects data from each DataChannel
component, and from the SNMP and BCOL collectors. DataChannel also creates
the 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, SNMP
activity, and watchdog queries to determine that status of the daemon. Log
data 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 Tivoli
Netcool Performance Manager communications, and database status.
Database The standard Oracle database log file.
Logs by component
A description of Tivoli Netcool Performance Manager logs organized by
component.
Installation log files
A list of log files created by the Tivoli Netcool Performance Manager Wireline
Components during installation. Where relevant, recommendations regarding the
deletion of log files is provided.
Database
v /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 from
the installation process.
Tivoli Integrated Portal
$home represents the root location for the Tivoli Integrated Portal.
v Install logs
$home/IA-TIPInstall-XX.log
$home/TCR13InstallTrace00.log
$home/TCR13InstallMessage00.log
v Uninstall logs
$home//IA-TIPUninstall-XX.log
There are also logs created for the Deployment Engine, these are not entirely Tivoli
Integrated Portal or Tivoli Common Reporting related.
DataView
v $home/DataView_InstallLog.log
DataLoad
v /tmp/dlSetup_install_`date +%Y.%m.%d`
DataMart
v /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 to
validate all aspects of a working installation. A ProvisoConsumer directory is
created in the /tmp directory of each server in the installation, not just for the
primary host.
Topology Editor logs are located at:
<topology Editor install location>/topologyEditor/topologyEditorTrace.log
Note: A new log file is created each time the Topology Editor is run.
DataChannel logs
The DataChannel logs include proviso.log, tnpmlog.log, walkback logs, and logs
for 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 enable
dual-logging for the component. When enabled, dual-logging writes information to
proviso.log and tnpmlog.log, and to the individual log for the DataChannel
component. For information about dual-logging, see DataChannel logs
configuration on page 15.
Proviso.log
proviso.log is the core Tivoli Netcool Performance Manager log file. It is always
running 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 16. At the end of
the 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 for
current processing.
The key performance indicators of Tivoli Netcool Performance Manager are
derived from Proviso log files.
The statistics are analyzed and an hourly system summary is provided per Tivoli
Netcool Performance Manager component. For example,
2013.04.09-08.32.42 UTC UBA.8.200-8664:12997 PERF_INPUT_PROCESSING GYMDC10021I
SAM_INVENTORY-sam_inventory_2013-04-09-08-30.csv: processed 3145 records in
5.002 sec (37724.9 records/min), rejected 0 records.
This log file contains information about all DataChannel components and SNMP
collectors. The types of events that are logged are determined by the LOG_FILTER
setting, as described in Topology Editor log settings on page 16.
tnpmlog.log
tnpmlog.log contains a subset of the messages written to the proviso.log file. The
subset of messages placed in the tnpmlog.log file are only those messages that are
of interest to the user.
The location of this log is determined by the LOG.LOG.FILE configuration setting
(for more information, see Topology Editor log settings on page 16).
DataChannel log format
The 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 consists
of
Chapter 2. Logs (Wireline Component) 11
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_RECORDS
Got 4 duplicate records, Discarded 0, Total of 4 for mid: 2206
rid: 200023263 4|4|2006| 200023263
Walkback logs
Walkback logs are generated when a Tivoli Netcool Performance Manager
application encounters serious problems. In most cases, walkback logs are
produced just before the application shuts down because of the error.
These logs are crucial for problem determination by IBM Technical Support. The
name of the file begins with walkback- and includes the DataChannel component
and timestamp (for example, walkback-UBA.1.2-18032-2007.08.21-16.51.32.log).
Unless you have advanced knowledge of the DataChannel, only the first few lines
of a walkback log are useful. The following log entry is an example:
EXCEPTION: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
FACILITY_NAME: LDR.1-11827
Release: 4.4.1 R2E2
Build: Guam.156
ORIGINATOR: an OracleThreadedConnection( hsvcctx = 245F374 )
PARAMETER: OrderedCollection (an OracleError)
TEXT: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
Note: Walkback files must be manually deleted. Due to the DataChannel cron
settings, a process that fails is repeated every 5 minutes. Since a new walkback log
is generated upon every failure, the result can be many unneeded files.
DataLoad logs
DataLoad logs include the SNMP.log, pvmdmgr.log, and WatchDog.log logs. The
default location of these logs is the /DLHOME/log directory, where DLHOME is the
location of DataLoad on your system.
SNMP log
The SNMP log file contains detailed messages about all SNMP requests. All SNMP
log files are created with the date in their name. Also, the name of the local SNMP
log file also includes the collector number, for example: 2010.04.27SNMP.1.1.log
By default, SNMP logs include the following recurring events:
v Close hour events
v Debug level changes
v Start and stop messages
Note: Events reported in this log are also reported to the DataChannel log.
Only the current debug level can be set by using the Collector Information Tool as
described in the IBM Tivoli Netcool Performance Manager: DataMart Operation
Guide. On restart, the collector switches back to the permanent debug level (which
by default is Fatal + Warning + Info messages). The permanent debug level is set
through the Topology Editor. Changing the debug level is useful when a specific
network device or device group does not respond correctly to SNMP requests.
Pvmdmgr.log
The pvmdmgr.log file stores events about the start and stop sequence of the
daemon.
Occasionally, the PVM Collecting daemon is running message is displayed before
the process is in complete run mode.
WatchDog logs
The daily DataLoad WatchDog.log file contains entries about pings sent to the
collector to ensure that the daemon is still running. The name of this log begins
with the date for which events are records, for example 2007.08.16WatchDog.log.
DataMart logs
DataMart does not have a central log. Instead, DataMart information is written to
log files, such as logFile.PVM or TraceInventory.log, that are associated with
individual components or actions, such as Inventory. The default location of these
logs is the /DMHOME/log directory, where DMHOME is the location of DataMart on
your system.
Note: The inventory process does NOT automatically create a log. If inventory is
run as a cron entry, you must redirect the data to a specified log file, otherwise no
log data is stored. To show time stamps in inventory log initiated by cron, you
must add the following lines to the dataMart.env file:
PVM_LOG_DATE=1
export PVM_LOG_DATE
TraceInventory.log
This log is created when the SNMP Inventory GUI is used. The log file contains
messages that sequentially indicate the processing status of an inventory. The
following 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 for
each bulk collector profile. The file suffix follows the format .bulk_n, where n is
the number of the collector.
logFile.*
This type of log file records minor events related to GUI or module function and is
generated as required. Examples of this type of log file include
logFile.POLLINVENTORY and logFile.RESMGR.
provisoinfod*.log
This log contains messages about internal communications and is of limited use for
troubleshooting. At the end of each day, a UNIX timestamp is appended to the file
name (for example, provisoinfod1187726401534.log).
NotifyDBSpace*.log file
The NotifyDBSpace*.log file is a daily automatic file containing messages about the
status of the database. At the end of each day, a UNIX timestamp is appended to
the file name (for example, NotifyDBSpace1190102314443.log).
DataView logs
DataView does not have a central log. Instead, DataView writes DataView traces to
the Tivoli Integrated Portal.
Note: DataView log messages and configuration options are covered in the IBM
Tivoli Netcool Performance Manager: DataView User and Administrator Guide,
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.log
directory, where ORACLEHOME is the location of Oracle on your system.
Logs messages format
In general, each log message indicates the date, time, Tivoli Netcool Performance
Manager component, severity code, event ID, and event description.
The following table describes log message elements.
Table 2. Log message elements.
Field Description
Date and
Time
Date and time using the following format:
<year>.<month>.<day>-<hour>.<minute>.<second>
Timezone Always UTC.
Table 2. Log message elements. (continued)
Field Description
Component Name of Tivoli Netcool Performance Manager component and its process ID
separated by a dash (-). Names of Tivoli Netcool Performance Manager
components are defined privately for each subsystem. DataChannel uses
channel-based naming conventions (for example, CME.1.1), other subsystems
can develop their own conventions. Some components include both the
process ID and thread ID separated by a colon (for example,
CME.1.1-5638:415).
Severity
Code
Event severity code. For more information, see the description of the
LOG_FILTER setting in Topology Editor log settings on page 16.
Event ID Event identifier. For more information, see Event IDs on page 22.
Description Description corresponding to the Event ID.
Logging configuration and information utilities
You can configure logging behavior or use information utilities to help
troubleshoot Tivoli Netcool Performance Manager components.
DataChannel logs configuration
Configuration options that govern DataChannel logging behavior are set by using
the Topology Editor and are maintained in the database. Logging behavior can be
set at three levels: DataChannel, specific DataChannel components, and all
DataChannel components or global'. Logging settings are controlled by the log
configuration.
Table 3. DataChannel log configuration components.
Level Description
DataChannel Specify logging behavior for DataChannel, including the Channel
Manager (CMGR), Channel Name Server (CNS), and Application
Manager (AMGR). They override any conflicting options set using
GLOBAL. To specify, use the following syntax:
LOG.<option>=<value>
where
<option> = log configuration option (see XREF)
<value> = value for the configuration option
Example: LOG.ROOT_DIRECTORY=/opt/datachannel
DataChannel
Component
Specify logging behavior for DataChannel components (UBA, FTE,
CME, LDR, DLDR). They override any conflicting options set using
GLOBAL. 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> = Value
Example: 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> = Value
Example: GLOBAL.FC_RETENTION_HOURS=48
Logging configuration changes in Tivoli Netcool Performance Manager can only be
made by the Installer. All components must be restarted to apply the changes. The
settings include enabling/disabling central and local logging and tracing and
changing the log levels for local/remote logging/tracing. This behavior is
consistent with the previous releases.
Topology Editor log settings
Log options that can be specified in the Topology Editor are described in the
following table.
Table 4. Log options in Topology Editor
Option Levels Description
DUAL_LOGGING GLOBAL
and
Component
Use true or false to turn dual logging on or off.
When set to false at the GLOBAL level, only DataChannel logs are
generated. When set to true at the GLOBAL level, individual logs for all
DataChannel components are generated, in addition to the DataChannel
log. Default is false.
Example: UBA.2.500.DUAL_LOGGING=true
LOG_PORT GLOBAL Port number of the log server for common log and trace files.
Example: GLOBAL.LOG_PORT=25000
LOG_SERVER GLOBAL Host name of the log server for common log and trace log files.
Example: GLOBAL.LOG_SERVER=cme4
MAX_LOGS GLOBAL Retention period for local trace files in days.
Example: CME.1.1. MAX_LOGS=7
LOG_PORT GLOBAL Port number to use for logging.
Example: GLOBAL.LOG_PORT=25000
LOG_SERVER GLOBAL Host name of the log server.
Example: GLOBAL.LOG_SERVER=burlington.acme.com
RENDER_MESSAGE_
ARGUMENTS
GLOBAL Example: CME.1.1.RENDER_MESSAGE_ARGUMENTS=false
SYSLOG_FACILITY GLOBAL Enter 128 to set the syslog facility to localhost.
Example: GLOBAL.SYSLOG_FACILITY=128
Note: The syslog daemon must be running locally to have access to the
log 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=localhost
Note: The rules file defining the message types must be installed and
loaded.
LOG_TRAP_PORT LOG Port used by the host defined in LOG_TRAP_HOST.
Example: LOG.LOG_TRAP_PORT=162
Note: The rules file defining the message types must be installed and
loaded.
LOG_TRAPS If set to TRUE, traps sent by the CME as the result of threshold violations
are 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 located
in 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 are
application-specific settings that affect only that application. ALL settings can be
used as both global and application-specific settings.
DataView logs configuration
statGet utility
statGet is a utility that is located at each collector and provides DataLoad statistics
like 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 default
locations:
v ~/opt/dataload/bin/
v ~/opt/datamart/bin/
Note: For remote systems, you must use the Collector Information Tool. For more
information, see the IBM Tivoli Netcool Performance Manager: DataMart
Operation Guide.
Syntax
statGet [-l {objects|instances|counters|stats|requests}] [-o <object>]
[-i <instance>] [-c <counter>] [-D <debugLevel>] [-S <serverName>]
[-P <portNumber>] [-T <connectTimeout>] [-T2 <dialogTimeout>] [-?] [-v]
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 statistic
class.
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 -l
option is specified.
Table 5. Options for statGet utility (continued)
Option Description
[-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 no
debugging, and 6 specifies verbose debugging.
[-S <serverName>] <serverName> is the name of the server that hosts a specific
SNMP collector. If the flag is undefined, the PVM_SSDADDRESS
environment variable is used. If the environment variable is
also undefined, the value localhost' is used.
[-P <portNumber>] <portNumber> is the number of the listening port number for
the collector. If the flag is undefined, the PVM_SSDPORT
environment variable is used. If the environment variable is
also undefined, the value 30023002 is used.
[-T <connectTimeout>] <connectTimeout> is the amount of time permitted to
establish a connection before a timeout. If the flag is
undefined, a default value of 20 seconds is used.
[-T2 <dialogTimeout>] <dialogTimeout> is the amount of time permitted for a
connection response. If the flag is undefined, a default value
of 7200 seconds (2 hours) is used.
-? Displays the statGet command reference page.
-v 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 of
counters Targets'.
statGet -l instances -o Targets
Get values of all statistics counters of class
Targets, for instance _Total'.
statGet -l stats -o Targets -i _Total
Get all currently configured requests in
DataLoad.
statGet -l requests
Configuring trace and logging
The default logging level can be set by using the configure command. You can
manage logs and trace in the Tivoli Integrated Portal from the Websphere
Administrative Console from the Settings > Websphere Administrative Console
option.
Default logging level
You use the configure command to configure the Tivoli Integrated Portal logging
level for Tivoli Netcool Performance Manager packages or components.
You must restart the application server for your changes to take effect. When you
have restarted the server, the logging level you have selected becomes the default
logging level.
Trace logging for DataView
The configure command
Configures the database connection information and the Tivoli Integrated Portal
logging level for the Tivoli Netcool Performance Manager installation.
You must restart the application server for your changes to take effect. When you
have restarted the server, the logging level you have selected becomes the default
logging level.
Location
<tip_location>/products/tnpm/dataview/bin
Syntax
configure.sh -tipuser <tip_username> -tippassword <tip_password> -type jdbc
[-driverhome <driver_home>] [-jdbcurl <jdbc_url>] [-jdbcuser <jdbc_username>]
[-jdbcpassword <jdbc_password>]
configure.sh -tipuser <tip_username> -tippassword <tip_password> -type logging
[-level <level>] [-package <package_name>] [-module <module_name>]
configure.sh -tipuser <tip_username> -tippassword <tip_password> -type debug
[-state <on|off>]
Parameters
<tip_location>
The Tivoli Integrated Portal installation directory, by default
/opt/IBM/tivoli/tipv2.
<tip_username>
A Tivoli Integrated Portal user name for the local Tivoli Integrated Portal.
<tip_password>
The Tivoli Integrated Portal user password for the local Tivoli Integrated
Portal.
<jdbc|logging|debug>
The three types of configuration options.
jdbc Configures the JDBC database connection information.
logging
Configures the Tivoli Integrated Portal logging level for the 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 Tivoli Integrated Portal logging level of detail. A
wildcard selects all of the com.ibm.tivoli.tnpm.dal packages.
configure.sh -tipuser <tip_username> -tippassword <tip_password> logging
-level detail -package com.ibm.tivoli.tnpm.dal.*
The following command sets the JDBC URL to
jdbc:oracle:thin@:host1.company.com:1521:PV:
configure.sh -tipuser <tip_username> -tippassword <tip_password> jdbc
-driverhome "/root/directory/tnpm.dataview" -jdbcurl
jdbc:oracle:thin@:host1.company.com:1521:PV -jdbcuser <jdbc_username>
-jdbcpassword <jdbc_password>
Troubleshooting
You 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 retrieved
and processed.
v UBA PERF_INVFLUSH messages indicate when discovered elements and
subelements are written to the database.
v Use StatGet to obtain SNMP DataLoad information.
Event IDs
For information about Event IDs that are used in Tivoli Netcool Performance
Manager logs, see Error Messages section in this guide..
Chapter 3. Contacting IBM support
IBM Support provides assistance with product defects, answering FAQs, and
performing rediscovery.
Before you begin
After trying to find your answer or solution by using other self-help options such
as technical notes, you can contact IBM Support. Before contacting IBM Support,
your company must have an active IBM maintenance contract, and you must be
authorized to submit problems to IBM. For information about the types of
available support, see the Support portfolio topic in the Software Support Handbook.
Procedure
Complete the following steps to contact IBM Support with a problem:
1. Define the problem, gather background information, and determine the severity
of the problem. For more information, see the Getting IBM support topic in the
Software Support Handbook.
2. Gather diagnostic information.
3. Submit the problem to IBM Support in one of the following ways:
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 Service
Request page.
v By phone: For the phone number to call in your country, see the Directory of
worldwide contacts web page.
Results
If the problem that you submit is for a software defect or for missing or inaccurate
documentation, IBM Support creates an Authorized Program Analysis Report
(APAR). The APAR describes the problem in detail. Whenever possible, IBM
Support provides a workaround that you can implement until the APAR is
resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support
website daily, so that other users who experience the same problem can benefit
from the same resolution.
Exchanging information with IBM
To diagnose or identify a problem, you might need to provide IBM Support with
data and information from your system. In other cases, IBM Support might
provide you with tools or utilities to use for problem determination.
Sending information to IBM Support
To reduce the time that it takes to resolve your problem, you can send trace and
diagnostic 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 data
manually 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 Assistant
v The Service Request tool
v Standard data upload methods: FTP, HTTP
v Secure data upload methods: FTPS, SFTP, HTTPS
v Email
All of these data exchange methods are explained on the IBM Support site.
Chapter 4. Introduction SNMP Inventory
This chapter provides an introduction to the Tivoli Netcool Performance Manager
SNMP Inventory.
Overview
Tivoli Netcool Performance Manager allows the operator to decide how much the
Tivoli Netcool Performance Manager DataMart will rely upon the OSS Inventory
system.
The Inventory system can be virtually anything from a full-featured commercial
Inventory package, to an EMS or Node Manager like HP Open View, to a flat file
like /etc/hosts . The minimum required is a list of the IP addresses of resources to
monitor.
Tivoli Netcool Performance Manager can discover both elements (resources that
have an IP address, such as a router or a switch), and the sub-elements associated
or contained with them, such as an interface or a port.
Tivoli Netcool Performance Manager supports the following three modes of
element and sub-element discovery:
Mode Inventory Contains
Tivoli Netcool Performance
Manager Discovers
1 Nothing Elements, sub-elements
2 Elements Sub-elements
3 Elements, Sub-Elements Nothing
Most Tivoli Netcool Performance Manager deployments are in mode two. In this
mode, Tivoli Netcool Performance Manager imports a list of elements and then
walks through the MIB to discover the sub-elements. In the first mode, Tivoli
Netcool Performance Manager sweeps the network to discover the elements and
their associated sub-elements.
Discovery
Tivoli Netcool Performance Manager's Discovery capabilities include some
powerful and flexible tools that allow you to determine exactly what Tivoli Netcool
Performance Manager will monitor, and how the sub-elements will be labeled and
grouped.
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 configured
to walk through an element's MIBs to discover particular MIBs representing users,
tunnels, protocols, service classes or other sub-elements. Particular OIDs can be
used to automatically create a label for the sub-element.
For example, the sub-element label could be a combination of the element name,
the interface, the port and the customer name, all taken from the MIB.
Metrics and Properties
In 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 of
user-defined properties.
There are two main differences between metrics and properties. Metrics come from
a monitored resource and are used to calculate statistics that are the basis of
performance reports and alarm thresholds. Metrics are generally numeric values
that change frequently, like the number of packets transmitted or a resource's
availability.
Properties, by contrast, are values that change less frequently, such as the CIR
(committed information rate) or the location of the element. Properties consist of
metadata-like identifiers or labels for such things as the customer and/or the
services using a particular sub-element.
The values for properties can be discovered automatically from the monitored
resource, or they can be imported from Inventory, provisioning or from another
OSS component.
Inventory Synchronization and Change Management
Sub-element properties such as the CIR or customer name can change. Tivoli
Netcool Performance Manager tracks the change and the time of the change, so
that reports are displayed correctly.
For example, utilization may be calculated against CIR. After the CIR is updated,
reports must reflect the new value for utilization calculations. But reports that
show dates prior to the CIR update must use the old CIR value. Tivoli Netcool
Performance Manager manages this without error.
If a sub-element is assigned to a new customer, the customer property will change.
If the sub-element is in a particular customer's group, this can cause the
sub-element to move to a new group. This can change the collection, alarm
thresholds and reporting for that sub-element, automatically.
Change Management for Elements
The Inventory must track changes so that continuity of meta-data associated with
the elements can be maintained.
Unfortunately, Inventory is not as simple as sweeping a range of IP addresses to
identify the network elements. That is just the beginning of the process. The
Inventory must track changes so that continuity of meta-data associated with the
elements (such as associations to customers, VPNs and services) can be
maintained. At least one additional challenge remains to keep the element
Inventory accurate, as shown with these two problem statements:
v IP Address changes
v
Problem: If you are tracking a router by its IP address, and you discover a router
at a new IP address, how do you know if it is a new router, or an existing router
with a changed IP address?
Tivoli Netcool Performance Manager solves this problem by associating
additional properties with each element which provide additional continuity and
trace-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 management
interface.
v Name changes
v
Problem: If you are tracking a router by its name, and you discover that the
name has changed, how do you know if it is a new router with that IP address,
or an existing router with a changed name?
Tivoli Netcool Performance Manager does not track elements by their name or
any other single property. Instead, by tracking a combination of properties,
Tivoli Netcool Performance Manager is able to provide continuity to inventory
even when any of these properties change.
By automatically tracking changes to an element, rather than discovering it as a
new element or forcing the operator to manually update the database, Tivoli
Netcool 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 Sub-Elements
In addition to the challenge of detecting and correctly managing changes on
sub-elements, 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 sub-element. Assuming that the sub-element is a port
or virtual circuit residing on an interface, some of the changes will be due to
failure and recovery scenarios, or network reconfigurations due to growth:
v Adding or removing an interface card can cause the SNMP indexes to shift for
other sub-elements.
v The interface the sub-element resides upon might fail, forcing the service
associated with the sub-element to be moved to another interface.
v The service may be moved to a currently unused sub-element.The service may
be moved to a sub-element in use, and the service currently on the sub-element
is moved to another sub-element
Most network changes should be invisible to customers. Their reports should
reflect the quality of their service, and moves and changes to the network to
Chapter 4. Introduction SNMP Inventory 27
preserve their service should be invisible to them. This is particularly important for
SLA reporting. You certainly want to avoid forcing the customer to view two
reports, one for the original NIC and a second report for the replacement NIC.
Throughout the network changes, network operations and engineering staff must
have an accurate view of the actual sub-elements. For troubleshooting and capacity
planning purposes, they should have a historical view of performance and traffic
on a particular port, with information on changes that have occurred.
Grouping Sub-Elements
Properties can be used to automatically group sub-elements.
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 like
the 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.
Sub-elements can exist in multiple groups simultaneously. For example, a
sub-element might be part of a network operations group and a particular
customer's group.
Where to Go From Here
Relevant information.
For information on troubleshooting tasks to perform after a new SNMP Inventory
has been run, see See SNMP Inventory Troubleshooting.
For information on periodic administrative tasks to perform, see See SNMP
Inventory Management.
Chapter 5. SNMP inventory troubleshooting
This section discusses SNMP Inventory troubleshooting for Tivoli Netcool
Performance Manager.
Overview
The major phases of SNMP inventory.
The Tivoli Netcool Performance Manager SNMP Inventory consists of the
following three major phases, which usually happen sequentially:
v SNMP Discovery
Detects all resources on a target network and creates a virtual image of the
network.
v Synchronization
Compares the virtual network image generated by the Discovery with the
records in the Tivoli Netcool Performance Manager database that were created
by the previous Inventory run. Any modifications (new, missing, or renamed
resources, for example) are then synchronized through the application of various
algorithms, and the new network image is written to the database.
v Grouping
Updates the grouping structure in the database, which determines the kind of
information that is to be collected on each resource, element, sub-element, and
so forth.
In almost all cases, Tivoli Netcool Performance Manager's SNMP Inventory
requires virtually no operator intervention.
However, under certain circumstances, problems arise which you will need to
address. The following sections discuss the more common problems you are likely
to encounter and - where possible -- provide suggestions for remedial actions.
It is strongly advised that you monitor the logs for potential error messages by
doing 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, as
follows:
inventory -noX -action discovery -name lowell >output
2>error_log
For a complete list of error messages written to the Tivoli Netcool Performance
Manager log file, see Messages section of this guide. For more information on
using the Tivoli Netcool Performance Manager log file, see See Monitoring the
Log File.
v Running a Discovery from the DataMart GUI
If you use the DataMart GUI to initiate a Discovery, error messages will appear
on the DataMart GUI > Resource tab > Inventory Tool icon > Live 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/ Elmt
0.1.0/ SubElmt 0.0.0]
These messages explain the progress of the discovery as follows:
IP done.1
Indicates that the IP phase of the discovery process has completed.
SNMP done.1
Indicates that the SNMP phase of the discovery process has completed.
Elmt 0.1.0
Indicates that progress of discovered elements, using the following syntax:
numberOfObjectsInInputQueue.numberOfThreadsRunning.numberOfElementsDiscovered
SubElmt 0.0.0
Indicates that progress of discovered sub-elements, using the following
syntax:
numberOfObjectsInInputQueue.numberOfThreadsRunning.numberOfSubElementsDiscovered
If after two minutes there is no change in these messages, the Inventory Tool
displays a more detailed message like the following:
2005/12/09 13:46:57 Current activity @ 2005.12.09-18.46.54
2005/12/09 13:46:57 Stage: IP done.1
2005/12/09 13:46:57 Stage: SNMP done.1
2005/12/09 13:46:57 Stage: Elmt 0.1.0
2005/12/09 13:46:57 W: R00004/192.168.80.2
2005/12/09 13:46:57 Stage: SubElmt 0.0.0
The line that includes the run number and IP address (2005/12/09 13:46:57 W:
R00004/192.168.80.2, for example) can be used to troubleshoot possible problems,
as explained in See Discovery Seems to Hang or Never Finishes.
Figure 1. Errors Displayed in the DataMart GUI
Discovery Troubleshooting
The following sections address the more common problems that arise during
Discovery.
Discovery Does Not Start
The following sections offer the most common solutions to problems with
Discovery not starting.
Discovery Fails Because Discovery Server Does Not Run
What do to if the discovery fails.
About this task
If the Discovery server fails to start, an error message like the following is
returned:
IIOP: couldnt connect to 192.168.68.251:34024: couldnt open
socket: connection refused
Error: StartInventory Failed for Discovery Server :
IDL:omg.org/CORBA/INTF_REPOS:1.0 {minor 0 completion_status
COMPLETED_NO}
To troubleshoot this problem, do the following:
Procedure
1. Log in as pvuser on the system where the channel manager and log server are
installed.
2. Change your working directory to the $DC_HOME/bin directory, by entering
the following command.
Note that $DC_HOME is defined as /opt/datachannel by default.
cd $DC_HOME/bin
3. Verify that the Discovery server is not running by entering the following
command:
$ dccmd -action status -pattern DISC.*.*
If the Discovery server is not running, the dccmd command returns output like
the following:
NUMBER FACILITY HOST STATUS ES DURATION EXTENDED
STATUS
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 use
DISC.DEV19.1 ):
dccmd -action bounce -pattern DISC.DEV19.1
2. Verify that the Discovery server is running by entering the following command:
dccmd -action status -pattern DISC.*.*
If the Discovery server is running, the dccmd command returns output like the
following:
Chapter 5. SNMP inventory troubleshooting 31
NUMBER FACILITY HOST STATUS ES DURATION EXTENDED
STATUS
1 DISC DEV19.QUALLA running 1 running
For more information on using the dccmd command, see the Netcool/Proviso
Command Line Interface Guide .
Discovery Fails Because Collector Stops During Discovery
About this task
If the collector stops during a Discovery, several different error messages are
logged. The most 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 -collector dev19.quallaby.com:3002
-nbGetIfAddress 100 -invFileTxt /opt/datamart/conf/inventory_subelements.txt -vname {}
-intcollector 1)
Procedure
1. 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 Oracle 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.
Figure 2. DataMart GUI
4. Click on the Collector Information icon. The Collector Information Tool
appears.
The Collectors Tab lists all the collectors loaded from the database.
5. Select the collector that you are troubleshooting. You look for the collector
name in the output of the Live Information tab of the Discovery trace, as
follows (in this example, the collector is dev19.quallaby.com):
BeforeDiscovery for lowell : nothing to do
Running 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) (from
profile )
Start Reload formulas on dev19.quallaby.com:3002 ...
Figure 3. Collector Information Tool
What to do next
ACTION: Restart the collector by entering the following command on the Collector
server:
/opt/dataload/bin/pvmdmgr start
Note: The collector cannot be restarted from the GUI.
Discovery does not start because inventory is locked
How to troubleshoot Tivoli Netcool Performance Manager if discovery does not
start because inventory is locked
About this task
Procedure
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 on the Live Information tab. If the profile is locked, you will see a
warning message like the one displayed in See Inventory Tool.
6. To confirm that the profile is locked, return to the DataMart GUI and click on
the Monitor tab->DataMart Status icon. The DataMart Status Tool appears.
In this example, the Inventory profile lowell is locked by an Inventory process
with a PID of 13458.
7. Determine if the lock is valid and if the process is still running, by entering the
following command, replacing LOCK_PROCESS_PID with the PID of the
locking process (13458 in our example):
ps -aef | grep LOCK_PROCESS_PID
What to do next
ACTION: If the process is active, the lock is valid and you should wait until the
Inventory 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 of
the toolbar.
Figure 5. Inventory Tool
Figure 6. DataMart Status Tool
The qPing Utility Has Incorrect Settings
As part of Discovery in Inventory Mode 1, Tivoli Netcool Performance Manager
scans 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, and
execute permissions are not set correctly on the file:
Procedure
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 qPing
utility:
cd $PVMHOME/bin
ls -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/qPing
chmod 6554 $PVMHOME/bin/qPing
chgrp pvusers $PVMHOME/bin/qPing
4. Verify the settings by entering the ls -l command again
Note: The qPing utility and the DataLoad user must belong to the same group
(in our example, pvusers ). The sticky bit setting ("s" in the ls -l line) allows the
utility to be executed as root by any UNIX user belonging to the pvusers
group.
Discovery Starts But Issues Warning Messages
The following sections offer the most common solutions to warning messages that
occur during Discovery.
IP Addresses Are Rejected
If an IP address is rejected during Discovery, errors will be written to the log or
will 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 address
has been excluded.
Warning: IP Address 10.60.64.230 rejected because this IP address
has been excluded.
In most cases, this is not a problem.
To troubleshoot this error message, do the following:
Procedure
The DataMart GUI appears, as shown in See DataMart GUI.
4. Invoke the Discovery Tool Wizard by doing the following:
a. Select the Resource Tab->Inventory Tool icon. The Inventory Tool appears
with the Configuration Tab displayed, as shown in See Inventory Tool
Configuration Tab
b. Highlight a profile and then select Edit > Profile or click on the edit icon
. The Inventory Tool Wizard appears, as shown in See Inventory Tool
Wizard.
Figure 7. Inventory Tool Configuration Tab
c. Click the Next button twice to navigate to the Discovery Tool Wizard, as
shown in See Discovery Tool Wizard.
5. As shown in See Discovery Tool Wizard, check to see if the rejected IP
addresses - either individually or within a specified range - have been
intentionally excluded. If they have not, contact Micromuse support.
Figure 8. Inventory Tool Wizard
Figure 9. Discovery Tool Wizard
Duplicate Elements Are Found
If the same element, a router for example, has more than one IP address associated
with it, Tivoli Netcool Performance Manager will "discover" the element multiple
times, reject the duplicates discoveries, and write warning messages to the log.
About this task
See Rejected Duplicate Elements, for example, shows Tivoli Netcool Performance
Manager 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 and
eliminating duplicate elements.
You may therefore want to exclude the duplicate addresses from the Discovery by
doing the following:
Procedure
1. Invoke the Discovery Tool Wizard (DTW). For instructions on how to invoke
the DTW, see See 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:
Figure 10. Rejected Duplicate Elements
Elements Are Not Identified During Discovery
If DataLoad did not receive an SNMP answer using the community name
configured in the Tivoli Netcool Performance Manager profile, warning messages
are created.
About this task
Warning messages like the following are written to the log and displayed on the
Live Information Tab 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:
v The device is not reachable from DataLoad collector (for example, no network
route).
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.
Figure 11. IP address exclude area of the DTW
To troubleshoot this problem, follow these steps:
Procedure
3. Change your working directory to DATAMART_ROOT/bin, replacing
DATAMART_ROOT with the root DataMart directory ( /opt/datamart by
default).
4. Perform an Internet Control Message Protocol (ICMP) query on the device, by
entering the following command, replacing
IP_ADDRESS_OF_UNIDENTIFIED_DEVICE with the IP address of the
unidentified device, and NAME_OF_COLLECTOR_SERVER_DOING_PING
with the name of the collector server doing the ping:
qPing IP_ADDRESS_OF_UNIDENTIFIED_DEVICE -S
NAME_OF_COLLECTOR_SERVER_DOING_PING
If successful, the qPing command returns the IP address of the unidentified
device, as follows:
$ qPing 192.168.68.33 -S dev19
192.168.68.33:10
5. Connect to the device and verify whether or not the SNMP agent is enabled
and running.
6. Connect to the device and verify the community name.
7. (Optional) You might have to change the community name in Tivoli Netcool
Performance Manager, by using the DataMart->Inventory->Discovery Wizard to
add an "alternate" community name to 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 the
following:.
b. Add an alternate community name in the specified text box.
c. Click the Add button to confirm your choice, as shown in the following
figure:
Elements Skipped Because No Related Sub-Elements
When Tivoli Netcool Performance Manager discovers an element but cannot
discover any related sub-elements, warning messages are written to the log and
displayed 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 dont have related subElements
This is not expected behavior, and should be resolved immediately.
To troubleshoot this problem, follow these steps:
Procedure
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 Discovery
formula of the skipped element, replacing EL_IP_AD, with the IP address of
the skipped element:
grep DISC proviso.log | grep R00020 | grep ELS_IP_AD | grep
CHKDISCOVERY
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 files
in the $PVMHOME/conf directory ( $PVMHOME is defined as /opt/datamart by
default):
v $PVMHOME/conf/inventory_elements.txt
v $PVMHOME/conf/inventory_sub_elements.txt
Contact Micromuse support.
5. If the grep command returns output like the following:
2005.03.15-18.58.28 UTC DISC.DEV19.1-13308 2
CHKDISCOVERY R00020/192.168.68.173. Family:Generic~Agent, try
discoveryFormula Formula (Basic_Element - 7486 string)
2005.03.15-18.58.43 UTC DISC.DEV19.1-13308 2
CHKDISCOVERY R00020/192.168.68.173. Family:1213_Device, try
discoveryFormula Formula (1213_Device - 4851)
2005.03.15-18.58.45 UTC DISC.DEV19.1-13308 2
CHKDISCOVERY R00020/192.168.68.173. Family:IETF_IF, try
discoveryFormula 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 the
Cisco router).
Figure 13. Formula Editor
c. In some cases, SNMP attributes do not respond properly, and the Discovery
formula for those devices must be changed. In this event, contact
Micromuse support.
Discovery Seems to Hang or Never Finishes
If the Discovery server shows no progress for several minutes it has probably
encountered problems with a Discovery formula.
About this task
If the Discovery server shows no progress for several minutes (up to thirty minutes
in some cases), as shown in the following trace log, it has probably encountered
problems with a Discovery formula:
Problems - real or apparent - with Discovery formulas can be the result of the
following:
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 things
result:
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 Micromuse support and provide them with the DATACHANNEL_ROOT/
datachannel/log/[yyyy.mm.dd]SNMP.log
However, before contacting Micromuse support, and before the Discovery finishes
or times out, do the following:
Procedure
1. Determine which Discovery formula is causing the problem by doing the
following:
Figure 14. Discovery formula
a. Log in as pvuser (or the user name that you specified during installation) on
the system where DataChannel is installed.
b. Change your working directory to DATACHANNEL_ROOT/log, replacing
DATACHANNEL_ROOT with the root DataMart directory ( /opt/datachannel
by default).
c. Enter the following command to search the proviso.log for the Discovery
formula:
grep DISC proviso.log | grep R00010 | tail -1
2005.03.15-20.32.16 UTC DISC.PVDEMO2.1-1048 2
CHKDISCOVERY R00010/172.31.0.51. Family:Cisco_CBQoS_Action, try
discoveryFormula Formula (Cisco_CBQoS_Action - 7784)
In this example, the Discovery formula is Cisco_CBQoS_Action.
2. Determine the internal request ID that is stuck by doing the following:
a. Log in as pvuser (or the user name that you specified during installation) on
the system where the DataMart or DataLoad server is installed.
b. Change your working directory to DATAMART_ROOT/log, replacing
DATAMART_ROOT with the root DataMart directory ( /opt/datamart by
default).
c. Enter the following command to find the internal request ID, replacing
SERVER_NAME with the name of the Tivoli Netcool Performance Manager
DataMart server:
statGet -S SERVER_NAME| grep -i once
+ [33] ID 96627,{CAL none (ONCE)(next=2005/03/15 20:32:16)}(P3)
ACTIVE (LastExec):
ServiceForm:(Trgt=(string)172.31.0.51)(Form=(form)Cisco_CBQoS_Action)(Inst=)(RComm=public)
+ [40] ID 96683,{CAL none (ONCE)(next=2005/03/15 20:48:19)}(P1)
ACTIVE (LastExec): ServiceSTAT (LONG)
In this example, the internal request ID is 96627.
Important: If the command returns no output, contact Micromuse support.
3. Enable limited debugging on the collector server in order to populate the log
with additional information by doing the following:
a. Change your working directory to /opt/dataload/contribs .
b. Enter the following command, replacing TASKID with the Internal request
ID you found in See Determine the internal request ID that is stuck by
doing the following:.
dialogTest2 Debug 6.TASKID
Tivoli Netcool Performance Manager outputs a message like the following:
Set debug level to 6 for taskId 96627.
Debug configuration:
> Global Level= 1; Mask=FW
> ID 96627 Level= 6; Mask=FWI1234
WARNING: DO NOT USE THE GLOBAL COLLECTOR DEBUGGER.
Synchronization Troubleshooting
The following sections address the more common problems that arise during
Synchronization.
Synchronization (Elements)
During the synchronization phase, Tivoli Netcool Performance Manager compares
the virtual network image generated by the Discovery with the records in the
Tivoli Netcool Performance Manager database that were created by the previous
Inventory run.
Any modifications (new, missing, or renamed resources, for example) are then
synchronized through the application of various algorithms, and the new network
image is written to the database.
In order to track elements and sub-elements through subsequent inventories, Tivoli
Netcool Performance Manager identifies them with a unique, never-changing
identifier, called an invariant.
The default element invariant, for example, is a concatenation of the following
three attributes:
v The MIB II sysName
v The first IP address responding to the ICMP scan (in Inventory mode 1) or the
one 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 has
moved or changed.
Synchronization Invariant Logic
Element Attributes
in Database
MIB II sysName IP Address physAddress New Element If ...
Defined Defined Defined Two or three
attributes have
changed.
Empty Defined Defined Two attributes have
changed.
Empty Empty Empty The resolved name is
different from
resolved name in the
database.
If an element does not respond to one of these three MIB II attributes, contact
Micromuse support.
To avoid synchronization errors, we strongly recommend that you limit device
configuration changes to one attribute between two runs of an Inventory
(Discovery and Synchronization).
Pre-synchronization Summary
As Tivoli Netcool Performance Manager prepares for synchronization, it compiles a
list of elements
The list contains the following types of elements:
v New
v Updated
v Burned
v Unchanged
v Not Found
v Histo Reject
See Pre-synchronization Summary shows the display written to the
DataMart->Inventory Tool->Live Information tab, with this summary information
highlighted:
The following sections discuss this summary in more detail.
Identifying not found elements
If the Pre-Synchronization summary lists any contact Micromuse support.
Figure 15. Pre-synchronization Summary
An example of not found elements can be found in See Pre-synchronization
Summary, which contains three examples.
Identifying burned elements
How to identify burned elements
In cases where the MIB II sysName, IP address, and physAddress are all defined for
an element (the first row in See Synchronization Invariant Logic), Tivoli Netcool
Performance Manager may encounter a special situation if the MIB II sysName and
phyAddress have changed, but the IP address remains unchanged.
In this special case, Tivoli Netcool Performance Manager creates a new element
and writes it to the database. However, since the IP address for "both" elements is
the same, so too is the resolved name, which means that the elements would be
seen by Tivoli Netcool Performance Manager as the same element.
To prevent this situation, Tivoli Netcool Performance Manager renames the initial
elment with a "Burned" prefix, as shown in See Burned Element:
When Synchronization completes, a list of burned elements is written to the
following file:
PROFILE_HOME/PROFILE_NAME/synchro/e_burned.dat
e_burned.dat file
If you have an e_burned.dat file, contact Micromuse support.
The burned elements and their sub-elements are duplicated, and the statistics
attached to these resources are not continuous in reports.
Preventing Burned Elements
Tivoli Netcool Performance Manager relies quite heavily on the sysName when
calculating invariants. When using sysName you need to prevent burned elements.
Figure 16. Burned Element
About this task
To prevent burned elements, so the following:
Procedure
1. Do NOT change the sysName on a device when the lowest physAddress has also
changed.
2. Ensure that the sysName is defined and not left empty.
3. Ensure that the sysName is defined with a unique value.
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 the
continuity of statistics.
Detecting Too Many New Elements
If there has been extensive configuration changes before an Inventory run (for
example, if two attributes were changed simultaneously on a router), Tivoli
Netcool Performance Manager will discover and create a new element in the
database.
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 two
runs 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 following
file. Note that $PVMHOME is defined as /opt/datamart , by default:
$PVMHOME/importexport/PROFILE_NAME/synchro/new_e.dat
Procedure
1. If you have a new_e.dat file, check to ensure that the number of new elements is
not unexpected.
2. If the number is unexpected, contact Micromuse support.
Note: A large new_e.dat file is to be expected the first time a network is
discovered.
Detecting Different Elements Resolved With the Same Name
If the name resolution system (for example, DNS) assigns identical names to the IP
addresses of different devices - a configuration mistake - Tivoli Netcool
Performance Manager will an error during Synchronization.
About this task
The error will look like the following:
Warning: IP Address 10.48.58.45 rejected
Warning: IP Address 10.60.64.230 rejected
When Synchronization completes, a list of rejected elements is written to the
following file:
PROFILE_HOME_DIRECTORY/PROFILE_NAME/synchro/duplicateElement_e.reject
If you have a duplicateElement_e.reject file, do the following:
Procedure
1. From the DataMart server, resolve the name of both conflicting IP addresses, in
order to confirm the identical naming resolution.
2. Fix the naming resolution system and start the same Inventory again.
Do not delete incorrectly Named Elements That Define SNMP
Community Names
Configuring Tivoli Netcool Performance Manager involves associating elements
with their SNMP Community name.
About this task
When initially configuring Tivoli Netcool Performance Manager, you use the
SNMP Configuration Tool, as shown in See Configuring SNMP Community
Names, to associate elements with their SNMP Community name so that Tivoli
Netcool Performance Manager can read from the devices.
Figure 17. Configuring SNMP Community Names
The SNMP Configuration Tool writes this information to the database.
During the next Inventory run, the synchronization process sees the elements that
were newly entered into the database by the SNMP Configuration Tool as missing
all three invariant attributes (see row three in See Synchronization Invariant Logic).
Tivoli Netcool Performance Manager then attempts to determine if a new element
needs to be created by comparing the resolved names of the devices, with the
following 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 create
a new element and will instead update the attributes for the existing element
with the discovered values.
v If the name that was entered into the SNMP Configuration Tool was the
incorrect resolved name of the device, Tivoli Netcool Performance Manager will
create a new element. On subsequent Discoveries, Tivoli Netcool Performance
Manager will rediscover and eventually update this element and ignore the
element 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 SNMP
Community name mapping. If the entry is removed, Tivoli Netcool Performance
Manager will lose the SNMP Community mapping and will not be able to read
from that resource.
Failed Synchronization
Pay particular attention to failed elements while monitoring the Synchronization
process
About this task
While monitoring the Synchronization process, pay particular attention to failed
elements.
Procedure
If Synchronization reports failed elements (greater than 0), contact Micromuse
support immediately.
Synchronization (Sub-elements)
The sub-element invariant is defined in the Discovery Formulas referenced in the
file $PVMHOME/conf/inventory_sub_elements.txt .
Note that $PVMHOME is defined as /opt/datamart by default.
This invariant is usually defined differently per object type (for example, an SAA
probe) and vendor (Cisco, for example).
The logic used to decide if a "newly-discovered" sub-element is in fact new,
depends on the following:
v If the invariant is not defined, the sub-element name (usually the concatenation
of the element name and the SNMP instance) is used to determine if a new
sub-element should be created or an existing one should be updated.
Any change to the name between two subsequent Discovery runs triggers the
creation of a new sub-element.
Figure 18. Failed Elements and the Inventory Tool
An SNMP index (instance) change will trigger the creation of a new sub-element
(because the SNMP index is part of the name), which will cause reporting
discontinuity.
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 per
element basis; if left unchecked, uniqueness is verified across the entire profile.
Identical Sub-element Invariant
If an invariant is defined for a particular type of sub-element (for example, Cisco
SAA), Tivoli Netcool Performance Manager will check the uniqeness of that
invariant during an SNMP Inventory.
About this task
If Tivoli Netcool Performance Manager detects two sub-elements with the same
invariant, it displays an error message like the following:
Warning: Identical invariant detected for invariant
172.31.0.51-1_CBQoS-172.31.0.51-class-default-Match any -output-1
(172.31.0.51-1,CBQoS<1107><1123> and
172.31.0.51-1,CBQoS<1107><1177>).
Note: When identical invariants are detected, neither sub-element is stored in the
database.
To resolve this situation, follow these steps:
Procedure
1. Use the DataMart->Metric->Mib Browser utility to verify that the two
invariants are in fact identical.
2. If they are identical, the following needs to be done:
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 more
OIDs 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 a
non-unique Customer contract number, which should be fixed.
v
Discovery should then be re-triggered, so that both sub-elements can be
discovered.
3. Contact Micromuse support for assistance in making these changes.
Checking the TraceInventory.log File
Viewing 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 the
following:
Large number of sub-elements 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 See Finding Elements
and Sub-elements About to Reach Their Retry Limit.
Procedure
If your network is reachable, the sub-elements exist, and you are still receiving
error messages, contact Micromuse support.
Rejected Sub-elements:
The log may report types of rejected sub-elements.
Procedure
If the log reports any of the following types of rejected sub-elements, contact
Micromuse support:
v histo reject
v dup reject
Figure 19. TraceInventory.log File
Burned sub-elements:
Procedure for dealing with burned sub-elements.
About this task
A burned sub-element is determined as follows:
v The sub-element has an invariant in the database (for example, inv1).
v The sub-element has a name (for example, name1).
v During an Inventory, a new sub-element is discovered and created with the
same name (for example, name1) and a different invariant for example, inv2).
In this case, two different sub-elements are about to be created in the database
with the same name.
To prevent this duplication, Tivoli Netcool Performance Manager renames the
initial sub-element with a "Burned" prefix, so that each sub-element can be stored
in the database with a unique name.
A list of burned sub-elements is written to the following file:
PROFILE_HOME/PROFILE_NAME/synchro/burned_seinv.dat1
Procedure
If the log reports any burned sub-elements, contact Micromuse support.
Disconnected sub-elements:
Procedure for dealing with disconnected sub-elements.
About this task
A disconnected sub-element is determined as follows:
v The sub-element has an invariant in the database (for example, inv1).
v The sub-element has a name (for example, name1).
v During an Inventory, a sub-element is discovered with the same name (for
example, name1) and an empty invariant.
An empty invariant typically happens when an invariant is used to assign physical
resources (ports, for example) to customers.
In this case, the empty invariant is interpreted as a "disconnection" between the
customer and the resource.
If a sub-element is determined to be disconnected, no new sub-element is created,
and the initial sub-element is marked as disconnected.
A list of disconnected sub-elements is written to the following file:
PROFILE_HOME/PROFILE_NAME/synchro/disconnected_seinv.dat1
Procedure
If the log reports any disconnected sub-elements, contact Micromuse support.
Grouping Troubleshooting
If all problems with Discovery and Synchronization have been solved - or none
arise - it is unlikely that you will encounter problems with Grouping.
Monitoring the Tivoli Netcool Performance Manager Log File
The Tivoli Netcool Performance Manager log file is located in the
DataChannelInstallROOT/log directory (/opt/datachannel/log by default) and should be
monitored on a regular basis.
Currently, only DataChannel and DataLoad write to the Tivoli Netcool
Performance Manager log. Log 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 Manager
log file (recommended) or you can check the Tivoli Netcool Performance Manager
log file by hand, using the grep command.
For example, the following command checks the Tivoli Netcool Performance
Manager log file for a fatal loader error:
grep CMGR proviso.log | grep -w F
982348945 2001.02.16-18.42.25 CMGR F ERROR There was a problem
loading the domain database
Tivoli Netcool Performance Manager Log Messages
For a complete list of log messages written to the Tivoli Netcool Performance
Manager log, see the Troubleshooting Tivoli Netcool Performance Manager Guide.
Burned subelements
Reasons 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 burned
v An SE is not in Discovery and another SE with Invariant is discovered with the
same Element and Instance
Scenario 1 - Instance Shift Causes Disconnect
Initial Discovery finds three sub-elements, all with Invariant.
Elt dbIndex Elt Name Instance SE dbIndex SE Name Invariant State
Missing
Count
200000431 alm00142061.elt01 <04> 200000450 alm00142061.elt01.seinv04 I:01:04 on 0
During a subsequent Discovery the following occurs:
v The SE with Invariant I:01:05 is not found
v 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
Discovery
v The SE with Invariant I:01:05 becomes Disconnected because it is not in
Discovery and another SE was discovered with the same Element and Instance
v The SE with Invariant I:01:06 is updated (Instance, Name, Label, etc.), but retains
the same dbIndex and Invariant
Missing
Count
200000431 alm00142061.elt01 Disconnected_200000449_<05> 200000448
Disconnected_200000449_alm00142061.elt01.seinv05
I:01:05 off 1
In theory, a Disconnected resource could come back; the Invariant is the unique
identifier to indicate the return of the SE. The Disconnected resource attempting to
return would also have to have a different Instance in order to return. Element
Name and Instance are required to be unique across all Sub-elements.
Scenario 2 - Instance Shift Causes Burn
Initial Discovery finds three sub-elements without Invariant and three sub-elements
with Invariant.
Missing
Count
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 Discovery
v 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
Discovery
v The SE that was at Instance <03> is Burned because it is not present in
Discovery and another SE in Discovery has the same Element and Instance
v The SE with Invariant I:01:06 is updated (Instance, Name, Label, etc.), but retains
the same dbIndex and Invariant
Missing
Count
Missing
Count
200000432 alm00142061.elt02 Burned_200000435_<03> 200000435
Burned_200000435_alm00142061.elt02.se03
off 1
Burned resources cannot come back, there is no Invariant to uniquely identify the
SE in Discovery as that which was Burned. If the Burned resource attempted to
come back without Invariant and with the same Instance, Inventory would reject
both because of a duplication on Element Name and Instance that cannot be
resolved.
Where to Go From Here
Relevant information
For information on periodic administrative tasks to perform, see See SNMP
Inventory Management
Chapter 6. SNMP inventory management
This section discusses SNMP Inventory troubleshooting for Tivoli Netcool
Performance Manager.
Regular monitoring
Monitoring actions have to be performed regularly to keep Tivoli Netcool
Performance Manager's SNMP Inventory process performing optimally.
If your SNMP Inventory is triggered every day, we recommend performing these
monitoring actions at least once a week.
If your SNMP Inventory is triggered several times a day (for example, every six
hours), we recommend performing these monitoring actions at least once a day.
Routine SNMP inventory management tasks
The following sections discuss routine SNMP Inventory management tasks:
Finding Elements and subelements about to reach their retry
limit
When elements and sub-elements reach their retry limit, they are retired from the
Inventory, which means that Tivoli Netcool Performance Manager stops collecting
on them and removes them from some groups.
About this task
The retry limit is set and managed in the DataMart > Inventory Tool > Edit
Profile > Synchronization Wizard. The default is three retries and a resource that
is older than seven days, as shown in the following figure. BOTH limits must be
met in order for a sub-element to be retired.
To find elements and sub-elements about to reach their retry limit, do the
following:
Procedure
1. Log in as pvuser (or the user name that you specified during installation) on
the system 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 sub-elements approaching their retry
counter, using greater than 2 (>2) for the retry count and 3 (the default) to
specify the age of the resource.
v Elements:
$PVMHOME/bin/resmgr/-noHead -export elt -colNames "dbIndex origin
name 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 origin
name label elt.profil invariant state missing" -filterRule
"%(elt.profil) not like %bulk% AND %(state)=on AND %(missing)
>2"
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 Netcool
Performance Manager Command Line Interface Guide.
What to do next
ACTION: If the elements or sub-elements are in the "off" state, then they will be
retired. If they are in the "on" state, but are approaching both their age limit and
retry limit, they are about to be retired. The commands in this section search for
elements and sub-elements 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 sub-element 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 Sub-elements That Have Been Retired
About this task
As explained in See Finding Elements and Sub-elements About to Reach Their
Retry Limit, when an element or sub-element exceeds its Inventory Retry and
Inventory Timeout limits, it is changed to the "off" state and retired from the
Inventory.
To detect elements and sub-elements that have been retired, do the following:
Procedure
1. Log in as pvuser (or the user name that you specified during installation) on
the system 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 sub-elements that have been move to the
"off" state.
v Elements:
$PVMHOME/bin/resmgr -noHead -export elt -colNames "dbIndex origin
name profil state missing" -filter "state(off)"
200028920|_|inventory|_|Delete_200028920_192.168.1.5-1|_|lowell|_|off|_|72|_|
v Sub-elements:
$PVMHOME/bin/resmgr -noHead -export se -colNames "dbIndex origin
name state missing" -filter "state(off)"
200000724|_|inventory|_|Delete_200000724_kafka.com-2_If<1>|_|off|_|7|_|
200000880|_|inventory|_|Delete_200000880_192.168.1.84-2_<NULL>|_|off|_|8|_|
200000916|_|inventory|_|Delete_200000916_192.168.1.84-2_If<1>|_|off|_|8|_|
200001205|_|inventory|_|Delete_200001205_192.168.1.84-2_If<2>|_|off|_|8|_|
For more information on the resmgr command, see the Tivoli Netcool
Performance Manager Command Line Interface Guide.
Chapter 6. SNMP inventory management 63
What to do next
ACTION: Micromuse recommends the following Best Practices when dealing with
retired elements and sub-elements:
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 will
be kept at a manageable size.
Where to go from here
Relevant information
For information on troubleshooting tasks to perform after a new SNMP Inventory
has been run, see See SNMP Inventory Troubleshooting.
Chapter 7. Messages
A list of error and operational messages generated by the Tivoli Netcool
Performance Manager components.
DataChannel error messages
This chapter lists reference format error messages produced by DataChannel.
Whenever possible, explanations are offered, as well as remedial actions.
GYMDC10000W error_description Restarting because
of 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 component
startup.
GYMDC10002F
Explanation: Component startup failure. Incorrect
configuration or missing components
User response: Verify Netcool/Proviso configuration
file
GYMDC10003F No collectors defined in registry
table
Explanation: Database configuration for
collectors/channel is not specified properly
User response: Check installation for this (sub)channel
GYMDC10004F error_description Shutting down the
image with error:
Explanation: Unhandled fatal runtime exception --
application produces walkback file and shuts down
User response: If the condition causing failure is
transient, the application will restart automatically and
in many cases will continue. If the problem persists,
contact technical support
GYMDC10005W end start rid mid Timed Out during
TS query for mid:
Explanation: CME experienced a timeout during a
tuple storage query
User response: Check connectivity and make sure
other components are running
GYMDC10006F end start rid mid app name label Timed
Out during tuple query for label
Explanation: PBL is paused pending manual
intervention. Contact technical support to fix FRMI bug
and have formula -> label data manually corrected
User response: Manually fix the problem and remove
STOP file in the PBL root directory. If problem persists,
GYMDC10007W Too many failed acquisition
attempts, giving up on remainder of
input acquisitions
Explanation: While trying to acquire input files,
multiple errors occurred and no further attempts will
be made to acquire files on this poll. Acquisition will
resume on the next poll.
User response: Look for messages in the logs that
indicate failures to acquire specific files and
troubleshoot the reasons for the failures. Try and
acquire the problematic files manually using FTP or
SFTP and check that the expected files and directories
exist and can be accessed.
GYMDC10008 schema_names Waiting For Data For
Schemas:
GYMDC10009W Stopping plan builder because plan
save to db failed
Explanation: The plan builder has been stopped
because saving the plan to the database has failed
User response: Review the proviso.log file for any
previously reported warning messages from the plan
builder
GYMDC10010W specificLabels timeSeries
specificFormulas There are multiple
specific formulas:
Explanation: You cannot have multiple specific
formulas for the same resource doing a specific to
generic conversion where the specific timeseries are in
different labels because the plan builder does not know
which label to assign to the generic timeseries. The
plan builder with pick any of the specific labels to
assign to the generic timeseries.
User response: Review all specific formulas for this
generic formula and review all specific formulas for
this resource.
GYMDC10011W timeseries Skipped building input
for
Explanation: Unable to build input becuase
subelement is inactive, or it has no element or elements
collector is wrong
User response: Check to to see if subelement is active
and has an element and the collector is right
GYMDC10012W requests timeseries There are too
many specific formula requests for
Explanation: There should only be one specific
formula request for a timeseries
User response: Figure out why there are more than
one specific timeseries for the same resource and
formula. Check requests.
GYMDC10013
GYMDC10014W errorDescription
Explanation: An exception occurred while trying to
contact the SAM server
User response: Check that server is reachable
GYMDC10015W schema_name Not acquiring data
because do directory at max hours for
Explanation: Indicates that the UBA has stopped
acquiring data because the "do" directory has too many
hours worth of data queued up to be processed.
User response: It may not be necessary to do
anything. As the UBA processes data and catches up,
this situation will correct itself. The amount of data
allowed in the "do" directory is controlled by the
FC_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 being
processed because a collector number could not be
determined.
User response: Double check that the input filename
and 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 name
Failed to acquire
Explanation: The UBA failed to acquire the indicated
file.
User response: Check the connectivty between the
UBA and the file, ftp or sftp server. Connect to the file,
ftp or sftp server by hand from the same host and user
id as the UBA and make sure the directory and file
indicated in the URI exists.
GYMDC10020 GYMDC10033W
Chapter 7. Messages 67
GYMDC10034W reason Timezone database failed to
load:
Explanation: The timezone database failed to load
from the ZoneInfo(TZ) DB on the host.
User response: Double check the installation of the
ZoneInfo(TZ) database on the host where the problem
is occurring.
GYMDC10035W
Explanation: An upstream PvUrl was registered with
missing information
User response: Check the upstream component's
AMGR settings for disk usage server DUS
GYMDC10036W
Explanation: This message is an indication of a
misconfiguration or that an upstream component
(CME) was not running yet so it had not registered
itself yet, or the upstream CME was failing to register
itself because CNS is having problems
User response: 1. Check that CME is properly
configured 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 for
the first argument
User response: Update ecmascript code
GYMDC10038W Call to
getAccumulatedDurationForIntervals()
Explanation: The call to
getAccumulatedDurationForIntervals() was invoked
with something other than an array for the first
argument
GYMDC10039W required Needs to be in
JMS_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 to
getAccumulatedDurationForTuples()
getAccumulatedDurationForTuples() was invoked with
something other than an array for the first argument
GYMDC10043W periodStart Call to
expects a positive integer as the second
argument. Invalid argment:
something other than an integer for the second
argument
GYMDC10044W periodEnd Call to
expects a positive integer as the third
argument. Invalid argment:
something other than an integer for the third argument
GYMDC10045W Call to getIntervalsForTuples()
Explanation: The call to getIntervalsForTuples() was
invoked with something other than an array for the
first argument
GYMDC10046W periodStart Call to
getIntervalsForTuples() expects a
positive integer as the second argument.
Invalid argment:
invoked with something other than an integer for the
second argument
GYMDC10047W periodEnd Call to
getIntervalsForTuples() expects a
positive integer as the thjrd argument.
Invalid argment:
invoked with something other than an integer for the
third argument
GYMDC10048W count
Explanation: Lists number of calculation errors for a
metric in an hour
User response: Review the formula code for potential
defects
GYMDC10049W timestamp node name tuples or heartbeat
Discarded out of sequence
Explanation: Tuples or data were produced that were
out of sequence.
User response: Verify that the system resumes
processing normally and check for any lost data.
GYMDC10050 status
GYMDC10051W
Explanation: This message is an indication of either a
communications problem, or a failure to process a
request coming from another process.
User response: If the issue does not resolve itself,
check for physical connectivity between the processes
involved in the request.
GYMDC10052W incoming_record existing_record
time_series Record types don't match for
TS
Explanation: There is a mismatch between existing
and new recomputed values during the operator state
upgrade
GYMDC10053W recomputed existing time_series
Recomp wrapper should have original:
TS
upgrade
GYMDC10054W incoming existing time_series Values
don't match for TS
upgrade
GYMDC10055W host The host address is the
loopback interface,
Explanation: This messages indicates that a process
will be unable to communicate with processes located
on other hosts. Objects the affected process will be
advertising themselves to other processes using the
loopback address, and as such, processes on other hosts
will fail to be able to communicate with objects this
process.
User response: Check the /etc/hosts file for an entry
that corresponding to this host name that maps to
127.0.0.1. Also check DNS and host name resolution
configuration.
GYMDC10056 SLA features are disabled
Explanation: SLA features are disabled but the
application has attempted to use some SLA related
features such as RCM or the PBL COL_FORMULAS
feature
User response: Enable SLA features
GYMDC10057
GYMDC10058
GYMDC10059
GYMDC10060W error_description Reason:
Explanation: An error occurred while contacting the
CMGR
User response: Check connectivity between CME and
CMGR
GYMDC10061I nodes Nodes Found:
GYMDC10062W error_description Reason:
Explanation: RCM cannot contact CMGR to obtain
CME labels
User response: Check that CMGR is running and
check connectivity between RCM and CMGR
GYMDC10063I labels CME Labels Found:
GYMDC10064W incoming existing time_series Recomp
Values don't match: TS
upgrade
GYMDC10065 outputFilename Merging multiple BOFs
to:
GYMDC10066 bofFilename Sorting BOF:
GYMDC10067W currentHour time unitOfWork
Discover deactivated for unit of work:
Explanation: Discovery was deactivated for this unit
of work
User response: None
GYMDC10068W value attribute subelement Not
discovered:
Explanation: The subelement/attribute/value was not
discovered
User response: Check configuration or try again
GYMDC10069W value attribute element Not
discovered:
Explanation: The element/attribute/value was not
discovered
GYMDC10070W value attribute resource Not
discovered:
Explanation: The resource/attribute/value was not
discovered
GYMDC10061I GYMDC10070W
GYMDC10071
GYMDC10072W errorDescription Error while
connecting to the database:
Explanation: An error occurred while connecting to
the database
User response: Check database is accessible and that
username and password are correct
GYMDC10100W error detail port host response Failed to
process response:
Explanation: Unexpected response to 3002 request
(request to SNMP Collector)
User response: If problem persists, contact technical
support
GYMDC10101W response Lost response:
Explanation: Unexpected response to 3002 request
(request to SNMP Collector)
support
GYMDC10102W result process id Killed sqlldr pid=
Explanation: Piped merge did not complete, LDR kills
Oracle SQL loader
support
GYMDC10103W result process id Killing stuck sqlldr
pid=
Explanation: An instance of stuck Oracle SQL loader
was found before starting piped merge. LDR kills stuck
instance
support
GYMDC10104F
Explanation: Oracle error encountered during
database load. The actual error message is displayed
support
GYMDC10071 GYMDC10104F
GYMDC10105F
Explanation: Oracle SQL loader task is not found
GYMDC10106F
Explanation: Attempt to load end-of-period data
failed. Loading is stopped pending manual intervention
User response: Fix the problem and remove STOP file
in the loaded (or daily loader) root directory. If problem
persists, contact technical support
GYMDC10107W error details stored procedure name
Explanation: Storage procedure invocation failed
User response: Check that database is running and
accessible. If problem persists, contact technical support
GYMDC10108W filename Unable to get next metric
record from
Explanation: Failure to read record from one of the
input files
User response: If problem persists, call technical
support
GYMDC10109W file Recovery file
Explanation: Recovery file does not exist
User response: None
GYMDC10110W errorDescription sqlStatement A SQL
error has occurred for the SQL
statement: (
Explanation: Non-fatal SQL error
User response: Fix the database privileges and ensure
the database is working properly
GYMDC10111W directory error message Error:
Explanation: An error occured while trying to get disk
consumption for a disk usage server root directory
User response: Try to run the du command manually
on the same directory to see what error occurs
Explanation: Naming server cannot be accessed or
failed to look up object in the naming service
User response: Start CNS or check network
GYMDC10105F GYMDC10112W
GYMDC10113W errorMessage
Explanation: Channel component failed to register
with Corba Naming Service
User response: Start CNS, check network and check
that port isn't in use
Explanation: Failed to start Corba for channel
component
User response: Check configuration
Explanation: Failed to stop Corba for channel
component
GYMDC10117W No metadata resources loaded from
database.
Explanation: Metadata load did not load any
resources
User response: Make sure inventory has run
GYMDC10118F
Explanation: Piped merge did not complete, LDR kills
Oracle SQL loader
support
GYMDC10119W record Out of order record:
Explanation: Out of order record in BOF file
User response: Call technical support
GYMDC10120W log_contents result_description
error_description General SFTP error:
Explanation: General SFTP error
User response: Check datachannel configuration
GYMDC10121W error host Unable to connect to
remote host:
Explanation: FTP failed to connect to specified host
GYMDC10122W count The failure limit of
Explanation: FTP failed to transfer file after several
retries
GYMDC10123W directory Unable to change remote
working dir:
Explanation: FTP failed to change to specified
directory
GYMDC10124W error description uri Unable to get
remote file
Explanation: There was a failure when attempting to
retrieve a file using FTP.
GYMDC10125W localDirPath Unable to make local
dir:
Explanation: FTP failed to create specified directory
GYMDC10126W directory Unable to remove remote
directory:
Explanation: FTP failed to remove specified directory
GYMDC10127W remoteURI Unable to remove remote
file:
Explanation: FTP failed to remove specified file
GYMDC10128W file Unable to remove remote close
hour file:
Explanation: Unable to remove remote close our file
GYMDC10129W
Explanation: Missing input source definition referred
to in xlog command.
GYMDC10130W sqlStatement object SQL insert of
update for
Explanation: Insert or update failed
User response: Check Database connectivity
GYMDC10131I uri error_description
GYMDC10132W new_name old_name Failed renaming
file from:
Explanation: FTP failed to rename specified file
GYMDC10133W There is more than one top-level
stream operator specified
Explanation: The structure of the UBA operators is
invalid. There is more than one operator that has no
output operators. Operators without any outputs are
called root operators and are the ones that actually emit
metrics.
User response: Contact technical support for help
with a possible tech pack bug.
GYMDC10134W timestamp file name File
Explanation: A file needs to be reprocessed after a
restart 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 formula
arguments, protect access to tuple lists
GYMDC10136W error formula value Invalid formula
result
Explanation: An error occurred while producing a
formula result
User response: Check formula code, check formula
arguments, especially returned value
GYMDC10137W message tuple
Explanation: A bad tuple was encountered.
User response: Check for iFixes for the tech pack that
correct the issue.
GYMDC10138W
Explanation: The TIME_GRANULARITY setting
defines what one period of time is. This data file
contains 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 to
establish the local timezone. We will use the default
seconds from GMT
User response: Contact techical support
GYMDC10141F
Explanation: Attempt to load recomputed data failed.
Loading is stopped pending manual intervention
in the recomp root directory. If problem persists,
GYMDC10142F
Explanation: Attempt to recover recomputation failed.
Running is stopped pending manual intervention
in the recomp root directory. If problem persists,
GYMDC10143W slelabel Can't unload, SLE
Explanation: Can't unload, SLE is not currently
running
User response: Do not try to move an SLE that is not
running
GYMDC10144W cmelabel slelabel Can't start SLE
Explanation: Can't start SLE, current CME is not
owner of the filesystem
GYMDC10145W
Explanation: Failed looking up PvURL for directory
from AMGR
User response: Ensure AMGR,CMGR are running and
check the DUS seciton of the AMGR config
GYMDC10146I Tenuring of load sets turned off
because too much work
GYMDC10147W errorDescription Log initialization
error:
Explanation: Proceedable error during initialization of
logger
User response: Check error message, verify and
change configuration
GYMDC10148W destinationPvURL sourcePvUrl
errorDescription Error:
Explanation: An error occurred while acquiring an
input file
User response: Make sure that no manual file deletes
are hapening and that file permissions are set properly
on the source file
GYMDC10149W
Explanation: An error occurred while collecting input
files from inputDirPvURL. Upstream CMEs publish
their outputDirPvURL so that downstream LDRs can
use these as a inputDirPvURL. LDR looks up the
outputDirPvURL for each of its
INPUT_COMPONENTS in the configuration.
User response: 1. Review the error shown in this log
message and make sure that the inputDirPvUrl is valid.
2. Check the configuration settings for disk usage
server (DUS). 3. Try to do a file copy or ftp/sftp get
from this inputDirPvURL to make sure that it is
accessible
GYMDC10150W error detail application name Failed
testing for running application:
Explanation: AMGR received an error while trying to
check if an application is running
User response: Check system status
GYMDC10151W
kill an application
GYMDC10152W
start an application
GYMDC10153W
get the status of an application
GYMDC10154W
stop an application
GYMDC10155W
Explanation: AMGR failed to kill the specified
application
GYMDC10156F
GYMDC10157W directory error message Error:
Explanation: An error occured while trying to get disk
free space for a disk usage server root directory
User response: Check that libproviso.so is available
and has proper permissions
GYMDC10160W Collector unknown for realtime
Explanation: Collector specified in real-time data
services request is not found
User response: Make sure collector is running. Check
configuration
GYMDC10161W errorDescription Failed to write data
to the subscriber:
Explanation: There was a failure to deliver real-time
subsription data to subscriber
User response: Problem should correct itself
GYMDC10162W
Explanation: The subscription request is invalid due
to bad resource or incorrect formula in the request
User response: Make sure the resource and metric are
correctly defined in the database for the realtime chart
that fails its subscription request
GYMDC10163W
Explanation: Unable to find SNMP formula for a
generic id
User response: Check request's formula to make sure
generic formula exists
GYMDC10164W router id Router Id
Explanation: Attempt to use a Cisco SAA router
feature with a non SAA router.
User response: Check router configuration to ensure
that SAA is enabled
GYMDC10165W attribute name Missing mandatory
attribute:
Explanation: A mandatory attribute is missing from a
probe.
User response: Check the health of DataView.
GYMDC10166W Collector unavailable for realtime
Explanation: Collector specified in real-time data
services request is not available
User response: Make sure collector is running. Check
connectivity and configuration
GYMDC10167W target_id Unknown or incomplete
target Id
Explanation: Uknown or incomplete target id
User response: Resync collector or restart collector
GYMDC10168W apiCall Invalid arguments to API
call to
Explanation: The collector library has been called by
CMGR/DataView with invalid arguments.
User response: Contact technical support.
GYMDC10169W target_name target_id SNMP Timeout
or invalid community string on target
Id:
Explanation: SNMP Timeout or invalid community
string on target Id
User response: Check network connectivity and
SNMP configuration
GYMDC10170W description
Explanation: An error occurred while monitoring
probes
GYMDC10171W subelement id No subelement with
id:
Explanation: A CORBA client to the SAA probe
monitor issued a request with an invalid subelement id
User response: Resync collector or restart collector
GYMDC10172W error description subelement id Error
resyncing probes for router
Explanation: An error occurred while attempting to
resync the probes on a router.
User response: Check network connectivity, review
SNMP configuration for that router
GYMDC10173I probe index subelement id Probe:
Explanation: A monitored probe was redeployed on a
router to synchronize its settings with those stored in
Proviso.
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 in
DataView and check supported probe types in
documentation
GYMDC10176W subelement id probe index Unknown
probe at index '
Explanation: Unable to modify probe because of
invalid index.
DataView.
GYMDC10177W name subelement id Router
Explanation: Probe type is unknown or unsupported
DataView and check supported probe types in
documentation
GYMDC10178I subelement id Router
Explanation: A router reboot was detected.
User response: No action necessary.
GYMDC10179I subelement id Resyncing probes on
router
Explanation: Probes in a router are being resynced
with the probe settings stored in Proviso.
GYMDC10180W error description subelement id Error
trying to detect reboot of router
Explanation: An error occurred while attempting to
detect if a router was rebooted.
User response: Review the error described in the
message
GYMDC10181W This collector is currently inactive
Explanation: A collector client sent a probe
configuration message to an inactive collector.
GYMDC10182W description Failed to load probe
monitor configuration from the
database:
Explanation: Failed to load the probe monitor
configuration from the database.
User response: Investigate connectivity with the
database
GYMDC10183W The server is too busy to accept
new probe monitoring requests.
Explanation: Too many probe monitoring requests are
currently active. Rejecting further requests.
User response: DataView Client should retry
automatically. No action required.
GYMDC10184W The router is too busy to accept
new probe monitoring requests.
Explanation: Too many probe monitoring requests are
currently active for the given router. Rejecting further
requests.
GYMDC10185I subelement id Router
Explanation: A router check can not be completed at
that time
GYMDC10186W name attribute name Unsupported
attribute '
Explanation: An unknown attribute was sent for
probe type
User response: If the attribute is a user specified
attribute 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 to
modify probe type at index '
Explanation: Unable to modify probe type.
User response: Use delete/create instead.
GYMDC10189W The probe has expired
Explanation: A probe has reached its expiration date
and should be removed.
User response: Remove the probe.
GYMDC10200W errorMessage Moving file caused
problem:
Explanation: Failed to move (rename) specified file
User response: Check bulk collector configuration
GYMDC10201W errorMessage Moving file to done
caused problem:
Explanation: Failed to move (rename) specified file
User response: Check bulk collector configuration
GYMDC10204W file Saved file
Explanation: Problem when accessing BOF file
support
GYMDC10205W lineErrorMessage A metadata error
occurred -
Explanation: The metadata was requested without a
valid name.
User response: Analyze input files or contact technical
support
GYMDC10206W formatType
Explanation: The parser field description attempted to
specify 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 to
profile directory:
Explanation: Bulk collector failed to change directory
to remote inventory directory (FTP error)
User response: Check connectivity and configuration
GYMDC10209W errorMessage ftpServer Unable to
connect to ftp site
Explanation: Bulk collector failed to connect to remote
inventory directory (FTP error)
GYMDC10211W ftpResult localFilename Unable to send
inventory file
Explanation: Bulk collector failed sending file
GYMDC10212W ftpResult filename Unable to rename
inventory file
Explanation: Bulk collector failed rename file in
remote inventory directory (FTP error)
GYMDC10213W errorDescription line Unexpected
input in data file. Offending line is:
Explanation: Unexpected input in data file --
offending line shown
User response: Check input data file
GYMDC10214W file
Explanation: No valid file format can be identified
with specified file
GYMDC10215W line Unexpected input in data file.
Offending line is:
Explanation: Unexpected input in data file --
offending line shown
GYMDC10216W errorDescription file message
Malformed timestamp encountered
while processing file.
Explanation: Malformed timestamp encountered while
processing file
GYMDC10217W file message The format type
detection algorithms fail to detect this
file.
Explanation: The format type detection algorithms fail
to detect this file
User response: Analyze input files and contact
technical 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 occurred
between channel manager, application
manager 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 error
occurred between command line
interface and the channel manager (
Explanation: A communications error occurred
User response: Check connectivity between command
line interface and the channel manager
GYMDC10304W
Explanation: Inable to reach application
User response: Check connectivity
GYMDC10305W
Explanation: Getting labels failed during near
real-time query
User response: Check connectivity to Oracle
GYMDC10306W error_description application_name
Failed getting metric records from:
Explanation: CMGR received an error while trying to
get metric records from an application
User response: Check connectivity between CMGR
host and application host
GYMDC10307W error_string application_name Failed
testing for running application:
test if an application is running already
User response: Check system status and connectivity
between CMGR host and application host
GYMDC10308W
kill an application
GYMDC10309W
start an application
GYMDC10310W
get the status of an application
GYMDC10311W
stop an application
GYMDC10312W Abandoned request because client
disconnected prematurely
Explanation: Abandoned request because client
disconnected prematurely
GYMDC10313W hostname application name No
configured component matches name:
Explanation: No component matches the given name,
application and host patterns.
User response: Check the name, application and host
patterns.
GYMDC10314W
contact an application
GYMDC10315W
Explanation: No configured CME matches the given
CME name
User response: Add an entry to configuration for the
CME in question and bounce CMGR, then start that
CME.
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 SLEs
across file systems.
GYMDC10400W file name count error description A file
read error:
Explanation: An error occurred while trying to read
and 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 not
covered 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 input
file by metric id
User response: Review requests and resource groups
for requests
GYMDC10404W class Bad
Explanation: lasthour file is corrupted
GYMDC10405W gerneric id resource request Bad
request:
Explanation: If it is an SNMP generic formula, the
collector already sends us metrics with generic formula
ID, so the generic formula should exist
User response: Check request's formula to make sure
generic formula exists
GYMDC10406W mid Metric id is invalid:
Explanation: Formula refers to invalid input binding
User response: Check formula definition
GYMDC10407W errorDescription Formula was
removed because of compile error:
Explanation: Formula could not be loaded because of
compile error
GYMDC10408W debugInfo errorDescription
formulaClassName An error occured while
running building output metric record
for formula:
Explanation: Formula refers to invalid input binding
GYMDC10409W debug info errorDescription
formulaName formulaClassName An error
occured while running calculation for
formula:
Explanation: An error occurred while computing
formula value
GYMDC10410W errorDescription className Compiler
error for Smalltalk formula:
Explanation: Error compiling formula
GYMDC10411W errorDescription rid gid mid rid mid An
error occured during threshold
processing of a metric record (mid=
Explanation: A failure has occurred in threshold
processing
User response: Send exception details to support team
GYMDC10412W timeseries id total count discarded count
duplicate count Got
Explanation: CME discovered and discarded duplicate
records when flushing them to disk
User response: Check for duplicate data being sent to
CME. Contact technical support
GYMDC10413W Error sending trap, resetting SNMP
engine
Explanation: Error occured during sending trap
GYMDC10414W total count discarded count duplicate
count Got
Explanation: CME found duplicate records or some
records were discarded because of invariant change
User response: Check system configuration. In case of
invariant change the system should handle it
automatically
GYMDC10415W filename filename Configuration file
Explanation: The configuration file is newer than the
state file.
User response: Check system configuration.
GYMDC10416W errorDescription rid gid mid An error
occured when attempting to send a trap
for (mid=
Explanation: An error occurred when creating or
sending a trap PDU
GYMDC10417W rid gid mid Mid/Gid/Rid =
Explanation: Reset Baseline state due to missing
Baseline History in DB
User response: Check that LDR is loading OK
GYMDC10418W error_details destination_URI
source_URI Failed to copy
Explanation: An error occured during an attempt to
copy a file
User response: Review the error details. Check file
permissions. Attempt to copy the source URI to the
desitnation URI manually to see what error occurs.
GYMDC10419W error_description uri Failed to delete
delete a file
permissions. Attempt to delete the source URI
manually to see what error occurs.
GYMDC10420W error_description destination_URI
source_URI Failed to link
link one URI to another
permissions. Attempt to link the URIs manually to see
what error occurs.
GYMDC10421W error_description destination_URI
source_URI Failed to move
move a file
permissions. Attempt to move (rename) the source URI
to the desitnation URI manually to see what error
occurs.
GYMDC10422W error_message souce_code_uri URI:
Explanation: A syntax error was detecting while
compiling ECMAScript code.
User response: Check the syntax in the indicated file
and correct it.
GYMDC10423W URI Failed to retrieve file size:
Explanation: Unable to retrieve the file size of a URI
User response: Check file permissions. Attempt to
check file information for a URI using ls command.
GYMDC10424W destination_size destination_URI
source_size source_URI Copied file size
does not match source (source:
Explanation: After a copy the file sizes do not match
User response: Manually copy the source URI to some
desintation on the same partition and/or different
partition as the destination to see if they are the same
file 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 the
error details Attempt to manually copy a URI to see
what error occurs.
GYMDC10426W error detail formula resource request
Build error on request:
Explanation: An error has occurred during the tree
build
GYMDC10427W
Explanation: Bad input: can't resolve <input kind>
tsId: <id> from: <db row>
GYMDC10428W input time series time series sequence
number No argument with s/n
Explanation: When attempting to update a formula
input, no argument with the indicated sequence
number was found.
GYMDC10429W row time_series No complex formula
for:
Explanation: No complex formula for: <id>
GYMDC10430W tupleContainer timestamp Metrics with
timestamps starting at
Explanation: Metrics have already been received for
this time. Duplicate data will be ignored.
User response: If the tuple container is from a
collector, check if that collector is actually producing
duplicate data by using bofDump on the output files
that it produces
GYMDC10431W label Data from label
Explanation: Data from label <label> is not used here
GYMDC10432W error description Failed to write BOF
file because of
Explanation: Failed to write tuples to disk.
User response: Double check disk space and
permissions.
GYMDC10433F error_description row Error building
time series from:
Explanation: Error building time series from: {db
row}, reason: {a reson}
User response: Contact Proviso support
GYMDC10434F error_description row Error building
input from:
Explanation: Error building input from: {db row},
reason: {a reson}
User response: Contact Proviso support
GYMDC10435W error description record Error
processing record
Explanation: An error occurred while processing a
record.
User response: Take steps to correct the problem
based on the information given in the error description.
GYMDC10437W time_series No formula for:
Explanation: RCM cannot locate the formula for a
timeseries
User response: Check plan consistency and that
formula exists for timeseries
GYMDC10439W Problem contacting tuple storage,
will retry every 60 seconds.
Explanation: RCM cannot contact tuple storage
User response: Check connectivity between RCM and
CMEs
GYMDC10440W error description Error running tuple
query (will retry in 60 seconds):
Explanation: The recomputation engine has a problem
querying other components or the database.
User response: Ensure all CMEs, FTEs and the
database are running.
GYMDC10441W A timeout occured while fetching
the results of a tuple query. The query
will be retried.
Explanation: A timeout occurred while querying
tuples.
GYMDC10442W reason label Remote query of label
Explanation: An attempt to query a remote process for
data failed.
User response: Ensure all components are running.
GYMDC10443W
Explanation: A file needs to be partially reprocessed
after a restart of the UBA in order to finish processing
the file.
User response: No action is necessary.
GYMDC10444W operator schedule modifier Failed to
apply repeat modifier
Explanation: The system failed to interpret the repeat
modifier specified in a formula or in a subelement
property.
User response: Check the subelement property used
for the repeat modifier and make sure the correct
syntax was used. Also verify that the calendar used in
the formula is compatible with the property.
GYMDC10445W time_series modifier Failed to apply
timezone repeat modifier
Explanation: Failed to apply a timezone modifier
based on a subelement property.
User response: Check subelement property value used
for the timezone modifier.
GYMDC10446W operator calendar name Invalid
calendar/duration:
Explanation: An invalid reference to a calendar or
duration was encountered in a formula.
User response: Double check the calendar name or
duration specified in the formula and make sure it is
defined using the DataMart calendar manager.
GYMDC10447W timestamp name
Explanation: An aggregator in a UBA failed to recover
its state from disk.
User response: Check for data loss and determine
whether someone may have inadvertently manipulated
the UBA's state files.
GYMDC10448W timestamp timestamp name
Explanation: An aggregator in a UBA failed to recover
its state from disk. The UBA will attempt to use older
aggregator state instead.
User response: Check for data loss and determine
whether someone may have inadvertently manipulated
the UBA's state files.
GYMDC10501W
Explanation: The definition for the profile cannot be
found in the database. Current execution is aborted
User response: Refresh or bounce the GUI, to resync
the content
GYMDC10502W
Explanation: The file inventory_element.txt is missing
for executing the profile
User response: Check suggested path, and add
corresponding file to that location
GYMDC10503W
Explanation: The file inventory_subelement.txt is
missing for executing the profile
GYMDC10504W
Explanation: A formula specified in files
inventory_element.txt or inventory_subelement.txt is
unknown in the database
User response: Check database and file for formula
spelling
GYMDC10505W
Explanation: One of the configuration parameter for
the profile has an invalid value
GYMDC10506W probe componentName CNS returned
incomplete list of targets for:
Explanation: All component names were not found
when looking them up in CNS
User response: Check that all components are running
GYMDC10507W id Invalid id:
Explanation: Inconsistent data was found while
serializing or deserializing timeseries and input data
User response: Check that the formula and resource
for this input both exist in the database
GYMDC10508W tuple error description operator name
Explanation: An error occurred while trying to
process an outgoing tuple.
User response: Check for an iFix to the tech pack
running on this UBA that corrects this issue.
GYMDC10509W probe errorDescription Error
Explanation: An error occurred while trying to
execute a monitoring probe
User response: Check script and review error message
GYMDC10510W
Explanation: One input file, specified by the profile is
missing
User response: Check the file name and path, either
fix the profile of the file name
GYMDC10511W
Explanation: The file inventory_element.txt is missing
for executing the profile
GYMDC10512W
Explanation: The file inventory_subelement.txt is
missing for executing the profile
GYMDC10519W ipAddress tag
Explanation: This IP address is out of range, or has
been explicitely excluded within the profile
User response: No action required
GYMDC10520W errorDescription tag
Explanation: The ping sweep did not execute properly
on the collector machine
User response: Check qPing files permissions on the
collector machine
GYMDC10521W finalList count tag
Explanation: A subset of IP address(es) has been
forced on the command line used to start the discovery.
The set of IP address(es) the inventory is going to work
on is the intersection between the set defined by the
profile (mode 1 or 2), and the forced set. This filter
usually takes place during partial re-discovery
triggerred by invariant change detection mechanism.
GYMDC10522W errorDescription tag IP DISC did not
execute properly on the collector
machine:
Explanation: An error occured when the IP DISC did
not execute properly on the collector machine
GYMDC10549W ipAddresses tag
Explanation: This is a warning message about IP
addresses that have not been discovered
User response: Check snmp configuration and
connectivity
GYMDC10559W element element invariant tag
Explanation: An element with the same characteristics
has already been discovered during this execution. The
two 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 write
to a file.
User response: Check the disk utilization and the
process' permissions to access this file and directory.
GYMDC10591W
Explanation: A retriable database error occurred
User response: This message should go away after it
retries. If it does not, contact technical support.
GYMDC10592W additionalInfo errorDescription
sqlStatement Statement (
Explanation: Bulk database insert or update failed
User response: Review the error description and the
additional information
GYMDC10593I
GYMDC10594W errorDescription domainManager Initial
load for
Explanation: Loading initial metadata from database
failed. Will retry.
User response: If message persists, check that
database is working properly and check connectivity
GYMDC10600W
Explanation: Re-Inventory request failed
User response: Check connectivity, system status
GYMDC10601W error details application name Failed to
register
Explanation: Registering application version failed
with an error
User response: Check connectivity and check Oracle
status
GYMDC10602W maxRetries profileName ipAddress
Failed to run inventory for:
Explanation: Re-Inventory request failed
User response: Check inventory command line in log
file, dc.cdf, priviliges of datachannel user
GYMDC10603W line Unexpected line in stored QCF
data:
Explanation: Bad data was encountered in the QCIF
state journal files.
User response: Inspect files and/or run full 5620
dump and verify the integrity of the file system used to
store QCIF's state.
GYMDC10604W formula name Relation
Explanation: Relation specified in design file is not
defined in the system
User response: Check design file for proper relation
name or add relation description (entry in
FRML_DESC)
GYMDC10605W property name Property
Explanation: Property specified in 5620 design file is
not defined in the system.
User response: Check design file for proper property
name or add property description (entry in
FRML_DESC).
GYMDC10606W error_description Flush aborted due to
Explanation: A serious error occurred while saving
data in the database. Flush aborted
User response: Check database connectivity or contact
technical support
GYMDC10607W processName errorDescription 5620
Error:
Explanation: A Corba exception was triggered on
message send to 5620
User response: Alert operator of potential problem
with the primary device
GYMDC10608W processName errorDescription qc_server
Connection to
Explanation: Attemp to connect to device failed
with one of the 5620 devices
GYMDC10609W qc_server Switching from
Explanation: Switching from specified device to the
backup device has started
GYMDC10610W errorDescription eventChannelIOR
Failed to reuse stored event channel
reference:
Explanation: Attempt to reuse stored QC event
channel reference failed
User response: No action required. Application will
create a new event channel automatically
GYMDC10611W Successfully reused stored session
reference
Explanation: Attempt to reuse stored QC session
reference failed
User response: No action required. Application will
create a new session automatically.
GYMDC10612W 5620 is out of sync, some events
have been lost!
Explanation: Event buffer on 5620 has been flushed,
queued events are lost
User response: Consider running manual full dump to
resync
GYMDC10613W Element is not specified for
Explanation: An element is not specified for a
subelement. Subelement will be skipped
GYMDC10614W anOid Object with oid
Explanation: An error occurred during the QC
getAttributes call
GYMDC10615W reason file_name Error reading events
journal file
Explanation: An error occurred while reading the
events journal file
GYMDC10616F
GYMDC10617W errorDescription anObject Error
adapting object
Explanation: An error occurred while adapting an
object
User response: Check script and refer to error
description in the message
GYMDC10618W Device is unavailable (Failed to
resolve QCF_System or QC_network)
Explanation: QCF device is unavailable
User response: Check that QCF device available and
reachable
GYMDC10619W reason
Explanation: A problem was encountered while
attempting a primary device switchover
User response: Check primary device to make sure it
is available
GYMDC10620W oid Failed to refetch object or event
at
Explanation: Unable to refetch object or event with
oid
User response: Check that object with oid exists
GYMDC10621W object errorDescription Error
Explanation: An error occurred while processing
object
User response: Review message for error details
GYMDC10622W object id Auto-inserted missing node
at
Explanation: QCIF auto created a missing node in the
path of a 5620 object identifier.
User response: Force a full inventory dump.
GYMDC10623W port host dbEnvironment Switching
from database:
Explanation: Switching from specified device to the
backup device started
GYMDC10624W errorDescription filename Error loading
Explanation: An error occurred while trying to load a
script file
User response: Check script file
GYMDC10625W anOid Oid
Explanation: An error occurred during the QC
getAttributes call
GYMDC10626W oid Failed to set attributes for oid:
Explanation: Error during QC getAttributes call
GYMDC10628W
Explanation: The directory defined in the dynamic
library path is missing
User response: Remove the missing directory from the
dynamic library path
GYMDC10629W
Explanation: RCM cannot locate the timeseries id for a
recomputation action
User response: Check plan consistency
GYMDC10630
GYMDC10622W GYMDC10630
GYMDC10631W
Explanation: RCM has received a bad recomputation
record
User response: Check input data to make sure RCM is
fed recomputation records only
GYMDC10632W
Explanation: RCM has received a duplicate
recomputation record
User response: Check input data to make sure RCM is
not fed any duplicate recomputation records
GYMDC10633 error description uri Failed to delete
file:
Explanation: Failed to delete SAM export file.
User response: Check that the process has proper
permission to delete the indicated file.
GYMDC10634W relation name Relation
Explanation: A UBA script tried to create a relation for
which the relation name is not defined.
User response: Reinstall the tech pack
GYMDC10635W 5620 Error: Failed to send userName
Explanation: An error occurred while getting
userName
with the primary device
GYMDC10636W property name Property
Explanation: Property refers to non-existent formula
User response: Check property in database
GYMDC10637W errorDescription database Connection
to
Explanation: An exception occurred while attempting
to login to Informix
User response: Check that Informix is available
GYMDC10638W subelementName Owning element not
specifed for subelement
Explanation: No owning element specified for
subelement
User response: Review script
GYMDC10639W resource relationFormula No relation
member is specified for relation:
Explanation: No relation member was specified for
relation / resources
GYMDC10640W subeleement2 subelement1
relationFormula No relation index is
specified for relation
Explanation: No relation index was specified for
relation / member
GYMDC10641W relation subelementName No
subelement named
Explanation: No subelement was found for relation
GYMDC10642W
Explanation: An inventory object that the UBA is
being requested to create has a conflict with another
inventory object already present in the system.
User response: Make sure the UBA is processing data
for the most current inventory in the database that is
assigned to its collector number.
GYMDC10643W current seconds resync seconds Resync
time (
Explanation: The timestamp on a record is earlier than
the current processing time of the UBA. Records should
be emitted in timestamp order by the tech pack.
User response: Double check the validity of data
being fed into the UBA and investigate a possible tech
pack bug.
GYMDC10644W Failed to connect to SAM service.
Explanation: Unable to connect to SAM service
User response: Check primary SAM service
availability
GYMDC10645W errorDescription Error connecting to
event channel:
Explanation: An error was encounterd while trying to
connect to the QCF event channel
User response: Check that QCF device available and
reachable
GYMDC10646W errorDescription event Error
processing event
Explanation: An error occurred while processing an
event
User response: Review message for error details
GYMDC10647W Check for primary SAM server
availability
Explanation: Reconnecting to primary SAM server
User response: Check for primary SAM server
availability
GYMDC10648W errorDescription object Error writing
id map entry for
Explanation: An internal error occurred that caused
the idmap entries not to be written
User response: Check file permissions. Contact
techical support
GYMDC10649W Check for primary cwm server
availability
Explanation: A problem was encountered. Attempting
a primary device switchover
User response: Check primary device to make sure it
is available
GYMDC10650W error detail
Explanation: Attempt to purge files in done directory
failed
User response: Check file permissions and user
privileges
GYMDC10651W Successfully switched back to
primary cwm server
Explanation: A problem was encountered with the
primary device. Successfully switched back to primary
cwm server.
GYMDC10652W Successfully switched back to
primary SAM server
Explanation: Switched back to primary SAM server
GYMDC10653W uri Switching from SAM SOAP
service:
Explanation: About to switch from primary SAM
SOAP server to alternate service
User response: Check primary SAM SOAP server
availability
GYMDC10654W Domain model is not configured in
ecmascript environment
Explanation: The domain model is not configured in
the 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 no
available colletor to fail over to
User response: Investigate cause of failovers and
review configuration and log message
GYMDC10704W limit percent stat_name collector
Collector
Explanation: Collector is not suitable for failover
because a statistic is over the theshold
User response: Check network connectivity and CPU
utilization
GYMDC10705W errorDescription port host Lost
connection to collector
Explanation: Connection to the collector was lost
User response: Check connectivity and that collector
is still running
GYMDC10706W list Redundant collectors detected:
Explanation: Redundant collectors were detected
User response: Check that GRACE_PERIOD
configuration setting is longer than your current
collector startup time
GYMDC10707W collector Collector
Explanation: Collector is not in HA mode
User response: Check that collector is configured to be
in HA mode
GYMDC10708W collector Unable to communicate
with collector
Explanation: Unable to communicate with collector
User response: Check network connectivity and check
that collector is running
GYMDC10709W message error_description client Client
Explanation: Encountered an error when sending
message to collector
User response: Check network connectivity
GYMDC10710W relation_id Missing relation formula
with id
Explanation: Relation refers to a non-existent formula
User response: Check that relation refers to a formula
that exists. If it does, contact technical support.
GYMDC10711W resyncAction relationFormula
subelementId Missing endpoint
subelement with id
Explanation: Relation refers to a non-existent
subelement
User response: Check that relation refers to existing
subelements. If it does, contact technical support.
GYMDC10712W file name schema name Unknown
schema:
Explanation: An input descriptor was encountered
that is associated with an unknown input schema. The
input descriptor will be ignored and discarded.
User response: If the file needs to be processed, it
may be necessary to re-stage the file in the input
directory, otherwise no action is necessary and the
warning 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 Preloading
configuration
GYMDC10757I collector duration Extending timeout
by
GYMDC10758I collector Disabling expiration for
collector
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 on
recovery
GYMDC10802W port host Failed to get sysUpTime
from RTM Service Agent at
Explanation: Failed to get sysUpTime from RTM
Service Agent
User response: Check communications, RTM server
GYMDC10803F
GYMDC10804F Both RTM event channels cannot use
the same local port.
GYMDC10752I GYMDC10804F
GYMDC10805F
GYMDC10806F
GYMDC10807W endpointDbKey Invalid delete
enpoint:
Explanation: Ignoring delete of an enpoint
User response: Check resources should be loaded in
memory
GYMDC10808W errorDescription trap Error processing
trap
Explanation: Handling PDU failed
GYMDC10809W errorDescription port host Error
renewing registration with service agent
Explanation: An error occured while renewing
registration
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 date
Obsolete date
Explanation: An obsolete date was encountered while
writing out inventory. Subelement will be skipped
GYMDC10812W pdu errorDescription Trap processing
error:
Explanation: An error was encountered while
processing a trap
User response: Review message for error information
GYMDC10850I port host Registering with RTM
Service Agent at
GYMDC10805F GYMDC10850I
GYMDC10851I port host Unregistering with RTM
Service Agent at
GYMDC10852 port host Renewing registration with
RTM Service Agent at
GYMDC10853 trap pdu Received trap
GYMDC10854I port host Starting resync with RTM
Service Agent at
GYMDC10855I port host trapnumber Recovered trap
number
GYMDC10856 pdu Received response:
GYMDC10857I port Starting SNMP listener on port
GYMDC10858I Starting RTM registration renewal
job
GYMDC10859I Stopping RTM registration renewal
job
GYMDC10860I port Stopping SNMP listener on port
GYMDC10861I username database Starting Glorp
session for database
GYMDC10862I Successfully connected to cwm trap
server
GYMDC10863I last trap number trap number Incoming
RTM trap number (
GYMDC10864 port host Registration renewed with
RTM Service Agent at
GYMDC10865W port host Failed to renew registration
with RTM Service Agent at
Explanation: Unable to renew registration with RTM
Service Agent
User response: Check registration configuration
GYMDC10851I GYMDC10865W
GYMDC10866W reason Unable to connect to cwm
trap server because:
Explanation: Unable to connect to CWM trap server
User response: Check that trap server is available and
that configuration is valid
GYMDC10900W value key Failed to convert:
Explanation: Failed to convert key value pair from
configuration
GYMDC10901W error detail Error:
Explanation: An error has occurred during the linking
of formula dependencies
GYMDC10902 error description Bad PDU received
Explanation: A bad PDU was received.
User response: Verify the correct operation of other
systems with which the affected component is
communicating.
GYMDC10903W errorDescription Error locating and
loading Mibs :
Explanation: An error was encountered while locating
and loding Mibs
User response: Check mibs location and review this
error message
GYMDC10904W errorDescription A command error
occurred:
Explanation: A request failed
GYMDC10905W object_type object_name Failed to
adapt
Explanation: There was an error in trying to emit
either an element or a subelement created by a tech
pack.
User response: Verify that the input data is correct.
Contact your system administrator or technical support
if the input data looks correct and you are unable to
resolve the issue.
GYMDC11016W file name Attempt to inject tuples,
but one or more files is missing or in
the wrong location:
Explanation: An attempt was made to inject tuples
with a tuple container that has missing or invalid files.
User response: Contact your Proviso system
administrator.
GYMDC11017W error_description time label Failed to
acquire tuples (label:
Explanation: Failed to acquire files from an up stream
component.
User response: Double check that the process can
access the output directory of the up stream component
over the file system, ftp or stfp (depending on the
system configuration).
GYMDC11018W node_name Name server (CNS)
lookup failed for node
Explanation: An attempt to lookup a tuple
communications node failed.
User response: Make sure the CNS, FTEs and CMEs
are running.
GYMDC11019W error_description node_name A
communcations error occurred with
node
Explanation: An attempt to communicate with a tuple
node failed.
User response: Make sure the FTEs and CMEs are
running and check their logs for any warning or fatal
messages.
GYMDC12347W symbol Error in
FormulaOperator>>update:with: as a
result of responding to
Explanation: An error occured while handling internal
event notification
GYMDC12349W arguments size inputs Something is
wrong with inputs:
Explanation: Something is wrong with the number of
inputs because it does not match what was expected
based on the formula
User response: Check the formula arguments to make
sure they are valid properties/formulas/calendars
GYMDC12350W argument operator id Operator
Explanation: The formula specifies an argument but
there is no input for that argument which means the
subelement 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't
build input for argument
Explanation: Unable to build input because argument
formula is missing
User response: Check to see if argument formula was
deleted manually
GYMDC12352W error label Failed while contacting
the plan builder to see if a resync is
required for
Explanation: CME has failed to contact the PBL to see
if there are plan changes within the current hour. CME
contacting PBL is an optimization. Since it failed, CME
will simply do a database resync of plan changes for
the current hour.
User response: Check PBL and make sure it is
running well
GYMDC12356W
Explanation: Pending xlog commands are replayed on
restart to complete transactions. A failure occured
during this replay
User response: Review the error description and
ensure necessary resources like the database are
available. Contact support
GYMDC12357W metric description problem description
Explanation: An attempt was made to create a metric
with invalid state.
User response: Verify the data being fed to the UBA
for accuracy and check the tech pack script for bugs.
GYMDC12358W Unable to produce a record because
there is no adaptor to process it
Explanation: There is no adaptor to handle metric
records that are emitted by the script.
User response: Double check the UBA settings and the
script. Make sure the correct version of the tech pack
script is configured. Check for any iFixes for the tech
pack that would correct the issue.
GYMDC12360W error description Failed while
contacting the plan builder:
Explanation: The UBA failed to contact the plan
builder while trying to inform it about unexpected
metrics that it is seeing.
User response: Check network connectivity and make
sure the channel management components are running.
GYMDL39001W seconds tag
Explanation: A profile is not progressing and will be
aborted
User response: Check profile
GYMDL39002 problem description Full inventory dump
is being retried due to the following
reason:
Explanation: A full dump of inventory objects had an
error and is being retried.
User response: Initiate another full dump.
GYMDL39201 error_msg record_number Record #
Explanation: An error was encountered during record
processing. The specific error is reported in the log
message. This message does not necessarily indicate a
problem.
User response: Investigate the reason for the error to
determine whether or not it's a normal condition or a
legitimate problem.
GYMDL39205W string Unknown timezone:
Explanation: The configured timezone could not be
found in the zoneinfo (tz) database.
User response: Double check the TIMEZONE
configuration setting and verify that it is in the
zoneinfo (tz) database on the host where the UBA is
running and change the configuration as necessary.
GYMDL39206W license_name License(
Explanation: The shared library that the UBA uses for
ODBC connectivity does not have correct OEM
licensing information.
GYMDC12360W GYMDL39206W
GYMDL39207 timezone_used timezone_requested
Timezone requested:
GYMDL39208W No Adaptors deployed
Explanation: No adaptors were specified in the design
file (or no design file was found).
User response: Double check DESIGNFILE and
INSTANCES settings in the configuration file.
GYMDC39209W Processing paused because output
at maximum
Explanation: The output directory or tuple storage
queue contains more than the maximum allowed
number of hours of data waiting to be picked up by a
downstream component
User response: Start downstream component(s)
GYMDL39209W file name No availability files found
for metric file
Explanation: The BLB failed to find any availability
metric files from the CWMIF that correspond with the
other metric files coming from the input URI.
User response: Check the status of the CWMIF and
make sure it is running. Check the logs for CWMIF
warnings or fatal messages and take the corrective
action suggested for those messages.
GYMDL39210W uri schema name Late input:
Explanation: No input files have been found at the
indicated URI for a significant period of time
(configurable via the LATELIMITSECONDS setting).
User response: Double check the input URI settings
for the UBA and make sure the UBA process can access
the file system, ftp server or sftp server indicated by
the URI (be sure to check using the same unix user id
that the UBA process runs under).
GYMDC39211I Processing unpaused because no
longer at max output
GYMDL39211W file name No availability files found
for metric file
Explanation: The BLB failed to find any availability
metric files from the QCIF that correspond with the
other metric files coming from the input URI.
User response: Check the status of the QCIF and
make sure it is running. Check the logs for QCIF
warnings or fatal messages and take the corrective
action suggested for those messages.
GYMDL39207 GYMDL39211W
GYMDC39212W timestamp uri schema name Input has
timestamp in future:
Explanation: An input has a timestamp from the
future relative to the current system time (in UTC). The
UBA will not process an input whose timestamp is in
the future until the system clock catches up with that
input's timestamp.
User response: Make sure "date -u" reports the correct
UTC time and make sure the timestamps on the files
being fed to the UBA are in UTC.
GYMDL39212W bytes bytes uri File size is too small
for uri:
Explanation: The size of the acquired file is smaller
than the configured limit and will not be processed.
User response: Check that the MINFILESIZE
configuration setting is set appropriately then check the
system that produces the data for the UBA for
problems.
GYMDL39213W error description
Explanation: An unexpected error occured while
processing an input.
User response: No specific advise is available.
GYMDL39214W file name Input file
Explanation: An input descriptor for the given input
file name was not found in the input descriptor
repository. As a consequence, the indicated file will not
be processed. Since the data file will not be processed,
data loss will likely result.
User response: Try and identify how the descriptor
repository may have been deleted or corrupted and
take steps to prevent it from happening in the future.
GYMDL39215W file name Alcatel MR file
Explanation: A file expected to be located in the do
directory is missing. The input descriptor for the file
will be deleted and the file will not be processed.
User response: Determine why the file in the do
directory was deleted and take steps to ensure it does
not happen again in the future. If the file needs to be
processed, find another copy of the file and re-stage it
in the input directory.
GYMDC39212W GYMDL39215W
GYMDL39217W message uri There was an error
communicating with the SAM interface
Explanation: An error occurred in the SAM JMS
communication protocol
GYMDL39218 process id The SAM JMS
communication process has started (pid:
Explanation: The SAM JMS communication process
has stopped.
User response: No action required.
GYMDL39219 process id The SAM JMS
communication process has stopped
(pid:
Explanation: The SAM JMS communication process
has stopped.
GYMDL39220W process id The SAM JMS
communication process is hung (pid:
Explanation: A request to stop the JMS process has
been issued, but the process is still running
GYMDL39221W problem description Full inventory
dump was unable to complete due to
the following reason:
Explanation: A full dump of inventory objects was
interrupted.
User response: Initiate another full dump.
GYMDL39222I The SAM JMS connection has been
established (a keep-alive message was
received)
Explanation: The SAM JMS connection has been
established.
GYMDL39223W The SAM JMS connection is stale,
the JMS process will be restarted.
Explanation: The SAM JMS keep-alive timeout has
been exceeded, the JMS process will be restarted.
User response: Check SAM server availability.
GYMDL39217W GYMDL39223W
GYMDL39224W errorDescription Error processing JMS
event:
Explanation: An error occurred while processing a
JMS event.
User response: Contact the system administrator.
GYMDL39225W file_name Error parsing
Explanation: There was an error while trying to parse
a CWM bulk statistics file.
User response: Use the CWM statsreader utility to
analyze the file and check for problems.
GYMDL39226W child description Unable to create
child/parent relationship for::
Explanation: A parent and child have the same id
which is not allowed
User response: Correct invalid group to group entries
GYMDL39801 Starting Inventory transfer and
synchronization
GYMDL39802 code Inventory transfer and
synchronization completed with status
code=
GYMDL39805 URI schema Start processing input:
Explanation: The adaptor is starting to process the
named file
User response: None. If this message does not occur it
can be an indicator that a file was not present, or that
the file glob configuration did not find a matching file
GYMDL39806 uri input_name Completed processing
input:
Explanation: The adaptor completed processing of the
named input
User response: If records were rejected, this could
indicate a malformed file, file with missing fields
(specified in an object adaptor and with no "default
value" or problem with adaptor configuration
GYMDL39224W GYMDL39806
GYMDL39807 acquired_count ignored_count found_count
time schema Scanned input:
Explanation: The UBA scanned remote URIs for an
input and found n1, n2 were ignored by
parseRemoteURI and n3 were already present in the do
or done directory
GYMDL39809I URI Ignoring input - error parsing
URI for timestamp info:
GYMDL39810I acceptable_count saw_count hour An
incorrect number of files was processed
for hour
GYMDL39811W timestamp limit The threshold for
input files containing record errors (
Explanation: The number of files allowed to have one
or more record processing errors in a given hour has
been exceeded. The limit is configured with the
ERRORFILELIMIT setting.
User response: Check the system that is feeding data
into the UBA and double check that the
ERRORFILELIMIT setting isn't set too low.
GYMDL39812W uri error description Unable to retrieve
a list of URIs for
Explanation: An error occured while the UBA was
attempting to retrieve a list of files for the indicated
input URI.
User response: Double check the input URI setting
and verify that the file, ftp or sftp server is running
and configured correctly. Attempt to connect to the file,
ftp or sftp server by hand from the same host and
userid as the UBA. Verify that the directory indicated
in the input URI exists.
GYMDL42000 timeslot SAM metric export is about to
be issued for timeslot:
Explanation: A SOAP request for SAM to export
metric data is about to be issued.
GYMDL42001 timeslot SAM metric export has been
requested for time slot:
Explanation: An export request has been sent to SAM.
GYMDL39807 GYMDL42001
GYMDL42002W detailed_error_msg timeslot SAM
metric export request failed for timeslot:
Explanation: A SOAP request for SAM to export
metric data has failed. This can be caused by temporary
loss of connectivity with SAM.
User response: If this message persists, check
connectivity with the 5620 SAM system.
DataLoad error messages
This chapter lists reference format error messages produced by DataLoad.
Whenever possible, explanations are offered, as well as remedial actions.
GYMDL30002F A time bomb function has fired,
check previous error DL30138 for
details. The process will exit, and be
restarted by the watchdog process.
Explanation: Some operations are required to
complete within a given time frame. This message
indicates that a particular operation didn't complete
within the hardcoded maximum time.
System action: The process will exit, and be restarted
automatically by it's watchdog process.
Programmer response: If the issue repeats itself, this
could be related to a database problem, with a SQL
query that never ends. Look for specific error or trace
files for the SQL client.
GYMDL30004F Start command failed.
Explanation: The attempt to restart the pvmd process
by 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 previous
information message with ID DL31088. This message
will indicate the arguments used to attempt to restart
the pvmd process. Inspect each of the arguments. Try
the 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 in
the start command line, unable to find path for
binaries, or the dataload environment is not present.
GYMDL30005F cmd Error: Unable to kill process
with command '
Explanation: The watchdog is unable to terminate a
failing pvmd process using the specified command.
Either the process was already terminated by the time
the watchdog issues that command, or the process can
not be terminated because of permission issues.
User response: Check process list on the machine with
ps. Try the kill command from a shell, using same
credentials as the watchdog process.
GYMDL42002W GYMDL30005F
GYMDL30006F SNMPv3 cryptography support can
not be loaded. Aborting.
Explanation: The configuration explicitly requires full
SNMP v3 support with encryption, but the
cryptographic library can not be located or loaded.
System action: The process will exit, and all further
attempts to restart the process without changing the
configuration will fail with the same error.
User response: Either install the cryptographic library,
and make sure the library is in the standard search
path, and accessible for the current user, or edit the
collector configuration to allow startup of the process
without the cryptography library.
GYMDL30007F function Call to unimplemented
cryptography function '
Explanation: The system is configured to use
advanced encryption, but the OpenSSL library being
used does not implement the encryption type.
System action: The process will exit, and be restarted
by the watchdog process. Any further attempt to reuse
the same problematic encryption mechanism will cause
the same error.
User response: Verify the correct version of the
OpenSSL library is in the library search path.
Programmer response: Check version and accessibility
of the libcrypto.
GYMDL30100W Fail to checkout new MIBs from
database, using local cache for
collections.
Explanation: Database is not reachable, or is down at
the time. Compiled MIB files are stored in the database,
and cached on the collector file system. Updated MIB
files are downloaded at collector startup, and every
time a reload MIBs message is received.
User response: This is not a serious issue as long as
MIB files are still cached on the collector file system.
Collector will complete downloading MIBs, once the
database connection is restored.
GYMDL30101W reason Server is shutting down
because of '
Explanation: The administrator user has issued the
command: pvmdmgr stop. Otherwise an error occurred
during the startup phase of the collector.
System action: The pvmd process is stopping. All
collections will stop on that host.
User response: Nothing to do if administrative
command. Otherwise, check the reason field.
GYMDL30006F GYMDL30101W
GYMDL30102W time name pid Process #
Explanation: Process pvmd is down (crashed), or
overloaded. The watchdog is monitoring the pvmd
process, and expects periodic heartbeat messages from
the collector. This error indicates an absence of
heartbeat message for an extended period of time.
System action: The watchdog will terminate that
instance of the pvmd (if still running), and start a new
instance.
User response: Nothing to do. Verify that the new
process is properly running.
GYMDL30106W mibfile name Unknown or missing
structure definition for type '
Explanation: There was an error in the original source
file for the MIB, or some dependencies were missing at
the time of the compilation.
User response: Re-compile the original MIB, check for
and fix eventual errors.
GYMDL30107W err host Host '
Explanation: This error occurs when a SNMP session
can not be initialized with the specified target. The
reason and internal error code are printed. This is
usually caused by incorrect SNMP V3 credentials.
User response: Check error description, check SNMP
credentials.
GYMDL30108W tnsentry login Unable to connect to
database using '
Explanation: Incorrect user/password specified,
incorrect database environment specified, or the listener
is down on the database server.
User response: Verify database user/password
information. Verify database environment
configuration. Verify the database listener is operating.
GYMDL30112W msg
Explanation: The parsing or the execution of the
formula failed because of an unrecognized token, an
invalid number of arguments for a function, or an
unexpected value for an argument. The message
indicates the exact location of the problem.
User response: If the error indicates a syntax error in
the formula, correct the offending function or argument
in the formula definition, and bounce the collector. If
the error indicates a runtime error with a particular
value for an argument, and the error is occurring
repetitively, check the formula logic, and if the value is
a valid input, extend the formula to handle it. Then
bounce the collector.
GYMDL30113W correctmib originalmib id Formula ID#
Explanation: There used to be an issue with the
formula Editor, that would produce syntactically
incorrect content for the dependent MIBs. Formulas
saved at that time may have that problem.
System action: System will automatically convert the
configuration to a valid entry and proceed.
User response: Edit, and save again the formula using
the formula editor to regenerate the MIB attachments,
and prevent the message to reappear.
GYMDL30114W Collector is unable to reconnect to
database.
Explanation: Database is down, listener process is
down, network between collector and database is
down.
System action: Collector will make periodical attempts
to reconnect to the database if the connection is
interrupted.
User response: Check database status. Let the collector
reconnect by itself when the database is available again.
GYMDL30115W miblist oid Oid '
Explanation: A particular OID used in the formula
expression has not been found in any of the Mibs
associated with the formula. The formula can not be
executed as is, and will not produce any result.
User response: Check that the particular mib file is
present in the mibs/oid directory on the collector
machine. Edit and save the formula to force the
formulaEditor to regenerate the list of associated Mibs.
Programmer response: Check if alm00206651 issue
applies.
GYMDL30116W filename Empty or missing MIB file '
Explanation: A Mib file, required by a formula is not
found on the local filesystem. The formula can not be
executed as is, and will not produce any result.
User response: Issue a confReload pvmMibs
command, check if the Mib file is copied. Try to
recompile the source Mib file.
GYMDL30117W duration port host fromto Socket
Explanation: There has been no traffic on a TCP
connection to the collector for a long time. Idle
connections are automatically stopped, and associated
resources are freed.
Programmer response: The duration is controlled by
this configuration setting:
TUNING.IDLESOCKETTIMEOUT
GYMDL30118W message key Item #
Explanation: An inconsistency has been detected in
the model. The detail is part of the message.
Inconsistencies can occur when several modifications
are performed by various modules, and resync
messages are not systematically sent to the collectors
following the modifications.
System action: The collector will perform a full
reload, instead of an incremental reload, of the model
in order to catchup with all past changes, and retrieve
a consistent model.
Programmer response: One type of inconsistency can
be created by the grouping tool, where subElements are
marked as subelement.state='off', but are still part of a
group with a relation content.state='on'.
GYMDL30119W Unable to register current module
version in database.
Explanation: The collector failed to update it's version
information in the component version tables.
User response: Check SQL credentials used by the
collector to access the database.
GYMDL30120W lang NLS_LANG is not defined, and
should be set to
NLS_LANG=AMERICAN_AMERICA.
Explanation: The environment variable NLS_LANG is
used by the database client to encode/decode string
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 recommended value. Source the
environment again, and bounce the collector.
GYMDL30121W desc id state System overflow.
Attempting to reactivate a
Explanation: The scheduler has detected that a
periodic task is still running from it's previous
execution. In order to avoid overload of the system, the
current execution of the task is cancelled.
System action: Collector will skip one execution of the
task
User response: If the message is repeated throughout
the day, this is a sign of a serious performance
problem, where the collector is overloaded. Load
should be reduced, by either splitting collections with
another collector, removing some requests, or when
possible optimizing collection formulas.
Programmer response: See troubleshooting tips from
http://w3.tap.ibm.com/w3ki/x/p9MJ
GYMDL30122W msg
Explanation: An explicit error PDU has been returned
by the SNMP agent, in place of the expected answer
PDU.
System action: The collector will correct it's
configuration accordingly, and when possible reissue a
valid PDU to the device. In that case there will be no
data loss.
Programmer response: If message
'usmStatsNotInTimeWindows' is repeated abundantly
in the log, this could be a sign that several devices
share the same SNMP V3 engine ID. This can be
investigated with the tool `dialogTest2
SNMPV3CacheDump all`. Conflicting engine ID is an
invalid situation, and represent a performance problem
for the collector.
Possible values are: Host '(host)', ERROR:
usmStatsNotInTimeWindows, adjusting values using
device's parameters. Host '(host)', ERROR: returned
REPORT PDU with (something) Host '(host)', ERROR:
returned empty REPORT PDU"; Host '(host)', ERROR :
PDU too big, can't reduce size anymore (already (size))
Host '(host)', ERROR : PDU too big, splitting by half ->
(newsize)
GYMDL30128W reqid calid calname Calendar '
Explanation: A request is deployed using a calendar
that has no more execution dates. The request will
never be activated.
User response: Inspect the calendar definition, and the
purpose of the request. either fix the calendar, or delete
the request.
Programmer response: Collection calendars are not
supported thru the requestEditor GUI. The only way to
assign a collection calendar is thru resmgr. This feature
will be deprecated soon, and should not be
recommended/deployed.
GYMDL30129W entry Missing
Explanation: A mandatory configuration entry is
missing, and there is no acceptable default value.
User response: Check shell environment, source
dataLoad.env is absent, and bounce the collector. Check
configuration entries using Topology Editor.
GYMDL30130W key log error
Explanation: When a configuration error is found on
an agent, then all collections that have been already
queued for that agent and are using the exact same
configuration parameters, are immediately aborted and
will report the same failure.
User response: Check nature of failure. Adjust SNMP
configuration, or agent's configuration.
GYMDL30131W errmsg Select function error:
Explanation: This is an internal error of the SNMP
listening thread.
User response: Contact IBM support if the error
happens again after a collector restart.
GYMDL30132W errortext version hostname Host '
Explanation: This is an internal error. A probe PDU
for the version check has not been sent properly. The
version check will be limited or will fail.
User response: This error may happen while the
collector is shutting down, and can be ignored in that
situation.
GYMDL30133W hostname Host '
Explanation: The collector failed to determine witch of
SNMP V1 or V2c should be used for that target. Agent
or device is down, or community has changed and has
not been updated in Proviso SNMP configuration table.
User response: Check device is alive with a ping (if
supported by the device). Check SNMP community
string. Check permissions on agent/firewall, for UDP
traffic on port 161, between the collector and the
device.
GYMDL30134W shortdescr id error Error:
Explanation: The task has encountered an unexpected
error and has generated an exception.
System action: This task will be removed from the
Scheduler in order to avoid further errors.
User response: Check error message for probable
cause.
GYMDL30135W sql pvdescr pvcode oradescr oracode
Error ORA
Explanation: A SQL error has occurred.
User response: If the error is a connection problem,
check database and access credentials. If error is a SQL
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 has
not 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 returned
twice 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, check
patches 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 a
corrupted data packet.
System action: The first response variable will be used
as the error index in an attempt to processes the packet.
GYMDL30142W threshold One or several bandwidth
limitations are at or near capacity (check
list in previous DL31020 messages). This
is a likely cause for lost collections, and
current thread avail (
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 excessive
bandwidth, 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. Otherwise
contact 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 as
possible.
User response: Ensure the specified output directory
is not in read only mode and the output device is not
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 oci function,
or the database proxy is unreachable.
User response: Check the log for previous DL30150 or
DL30213 errors to determine the exact cause of the
failure.
GYMDL30150W Can't connect the oraProxy in the
host application (or oraProxy is not
properly initialized), attempting to load
the Oracle library instead.
Explanation: The system is unable to contact the
database proxy. Either the proxy is not available or is
not configured properly.
System action: The system will attempt to load the
database library instead to directly query the database.
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 switch
should 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 an
indicator of a configuration issue.
GYMDL30160W filename Load failed. Library file '
Explanation: The OpenSSL library filename specified
in the message was not found via the standard library
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 change value
and the last change value with no other status change
for the device. This could indicate a non-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 investigated for
potential problems.
GYMDL30162W Configuration validation failed.
Explanation: At least one configuration entry is not
valid. Check the log for other messages providing more
details as to which entry is incorrect.
User response: If the configuration was recently
edited, make corrections based on the other messages
in 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 a
short 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 start the
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 stopping
the existing process.
User response: Use the current channel number and
collector number to start the process, or stop the
process 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 is
operational 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.
start, wait a few moments before attempting to stop the
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 those two
states.
GYMDL30170W Unable to Load, unknown Channel
or Collector number.
Explanation: Unable to load the configuration for the
collector because the channel or collector number is not
known by the system.
number are valid. Attempt the load operation after any
corrections are made.
GYMDL30171W Unable to Load, process is currently
shutting down.
Unable to issue a load command at this time.
process has stopped. Then issue command to load the
configuration.
Explanation: The process is in the specified state. New
configuration can not be loaded while in that state.
stop, wait a few moments before attempting to load
new 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 in
one 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 are
incorrect, or the database connection is incorrect.
number are valid. Also ensure the database is
operational and configured properly.
GYMDL30175W Unable to Pause, process is
currently shutting down.
Unable to issue a pause command at this time.
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 of those
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 not a
directory.
User response: Either create the directory specified, or
update the configuration to a valid value.
GYMDL30180W Missing
DATAMANAGER.FILENAMINGVALIDITY,
DATAMANAGER.HEARTBEAT_FREQUENCY
or
DATAMANAGER.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.
quit.
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.
quit.
GYMDL30183W WATCHMGR.MANAGERPORT can
not be NULL
Explanation: An invalid value has been detected for
the watchdog process management port. The port can
not be empty.
quit.
GYMDL30184W collectornumber channelnumber invalid
values for
TUNING.CHANNELNUMBER=
Explanation: Invalid values have been detected for
collector and collector's channel number.
quit.
invalid configuration entries. Redeploy the collector
files. Ensure that the local dataLoad.env has been
updated.
Programmer response: The local dataLoad.env
contains the DL_CHANNEL_NUMBER and
DL_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 been corrected.
GYMDL30185W Configuration incomplete.
Explanation: Some configuration entry is missing or
invalid. Usually the exact error is displayed in a
precedent message.
quit.
User response: Locate missing or invalid entry. Use
Topology Editor to reconfigure the invalid
configuration 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 specifies that
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 ascending order.
If you can confirm that there is no risk of infinite loop,
it is possible to temporarly reconfigure the collector to
ignore out of order OIDs, and proceed with the table
scan. Set entry SNMP.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 the
command 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 dependent
processes 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 continue to
send the message.
Programmer response: If this regularly occurs it could
cause secondary problems where message data is
incomplete.
GYMDL30192W socket Socket
Explanation: Unable to send data to the target system
because the remote buffer is full and the number of
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 and port.
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 line when
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
listed in the message.
Programmer response: Verify the operating system
resources are not exhausted. Some may be correctable
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 may
have ended before the command was issued.If the
process is still running, then additional DL30198
messages 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 be located 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 the introduction of
the Topology editor and the central database
configuration. This option is only present in the 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 the process
will exit.
GYMDL30205W facilityname No configuration records
have been retrieved from
REG$DCCONFIG for
DCCONFIG.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 connection
configuration.
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, password and
TNS ID.
User response: Check user, password and TNS ID in
dataLoad.env. Check database connectivity with Oracle
tools.
GYMDL30209W dir 'DATABASE.ORACLE_HOME=
Explanation: The ORACLE_HOME environment
variable does not point to a valid directory, or does not
contain the expected lib32 or lib64 sub directories.
User response: Check ORACLE_HOME in
dataLoad.env and check Oracle 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 such
configuration.
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 expected
OCI calls.
User response: Check ORACLE_HOME and dynamic
library path in dataLoad.env. Check permissions for
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 the
database.
System action: In most cases the system is shutting
down and will proceed to shutdown ignoring this
error.
Programmer response: If occurring during a
shutdown, this could be an indicator of a sequencing
problem inside the collector. If it occurs at another time
something caused the library to be unloaded prior 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 being
unavailable.
User response: Verify the database is operational.
Programmer response: If a proxy is used to query
data verify the $DL_LOG_HOME/tmp directory used
to hold query results exists and is writable.If the query
consistently fails, then it is possible some sort of
configuration issue is causing the problem within the
database. Verify the query can be successfully
completed 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 command
failed.
GYMDL30218W pid Unable to use kill process #
Explanation: Failed to terminate the process listed in
the message.
User response: If the process is still running, check for
other DL30005 and DL30198 messages in the log for
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 proper argument.
GYMDL30220W Callback didn't return result, timing
out.
Explanation: An expected result did not return in the
time allotted.
Programmer response: This is primarily the result of
trying to execute a smalltalk command from the
collector.
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 command is
not specified or is null.
Programmer response: Investigate configuration or
install issues that may lead to incomplete data being
used 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 save alias.
System action: The alias is ignored and formula
processing will continue checking other possible save
alias 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 save
alias values.
GYMDL30226W dbnum num fid Formula #
Explanation: The formula is already associated with a
save alias in the database. The new save alias is not the
same value.
System action: The new save alias is ignored and the
formula will be associated with the save alias already
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/decode string
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 the
environment 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 was
unable 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 to why 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 the
communication 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 instance info.
The sub-element is used in 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 a
collection it will cause missing results.
User response: Try running discovery again which
could fix the model either by retiring all connected
objects, or by recreating the missing ones.
GYMDL30236W gid seid Can't get Elmt or Instance
info for SubElmt#
association with an element or is missing instance info.
to the missing information.
GYMDL30237W seid Can't get Elmt info for
SubElmt#
association with an element. The sub-element is used in
collections and becauseof the missing information, will
cause missing results.
to the missing information. Since it is used in a
collection 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 or corrupted.
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 that
failed if known.
Programmer response: If this happens often, there
could be a compatibility issue from the component
running 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. A device
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 operating
system 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 is not
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 the maximum
value set for the operating system.
User response: Ensure the operating system maximum
is set to a reasonable value. If not, adjust the operating
system value. Otherwise usethe topology editor to
adjust the configuration settings listed in the message.
Note, the collector requires 8 additional open files in
addition to thetotal for the configuration settings.
GYMDL30244W syst est Max simultaneous threads
value of
Explanation: The number of threads required by the
collector is greater than the maximum number of
threads allowed by the operating system.
User response: Ensure the operating system maximum
is set to a reasonable value. If not, adjust the operating
system value. Otherwise usethe topology editor to
adjust the configuration setting listed in the message.
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 current configuration.
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 several jobs 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 and
continue 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 having problems.
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 the
collector 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 to why 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 recommended development
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 specified host.
for the host to use a valid access mode.
GYMDL30261W name Host '
Explanation: The mandatory parameter SecurityName
was not listed for the SNMP V3 authentication for the
specified host.
for the host to provide the SecurityName parameter.
GYMDL30262W host Host '
Explanation: Unable to generate a security
authentication key based on the SNMP V3
authentication information for the specified host.
User response: Verify the SNMP V3 authentication for
the host is correct. If so check for DL30007 errors which
may indicate a secondary error.
Explanation: The mandatory parameter PrivPasswd
was not listed for the SNMP V3 authentication for the
specified host.
for the host to provide the PrivPasswd parameter.
Explanation: Unable to generate a security privacy
key based on the SNMP V3 authentication information
for the specified host.
User response: Verify the SNMP V3 authentication for
the host is correct. If so check for DL30007 errors which
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 the specified
host.
Programmer response: Contact development with the
error and message to determine futher diagnostic steps.
GYMDL30266W msg
Explanation: The parsing or the execution of the
formula failed because of an unrecognized token, an
invalid number of arguments for a function, or an
unexpected value for an argument. The message
indicates the exact location of the problem.
User response: If the error indicates a syntax error in
the formula, correct the offending function or argument
in the formula definition, and bounce the collector.If the
error indicates a runtime error with a particular value
for an argument, and the error is occurring repetitively,
check the formula logic, and if the value is a valid
input, extend the formula to handle it. Then bounce the
collector.
GYMDL30271W number elapsedtime unknowntime
downtime uptime curlastchange curstate
curcoltime currentuptime prevlastchange
prevstate prevcoltime prevuptime name
RFC1213LIB, discarded ifAvailability
result for SubElement '
Explanation: The collector discarded the ifAvailability
result for the listed sub-element because one or more
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 investigated for
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 by
retiring 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 an
unknown 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 or incorrect
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 problem
with 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 cursor id
was not processed correctly.
User response: Ensure directory $DL_LOG_HOME/
tmp exists, is writable, and the file system is not out of
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 advanced encryption
support may result in lost collections.
System action: The system will start with limited
encryption support. Uses of advanced encryption
support will result in DL30007 messages.
User response: Either install the cryptographic library,
and make sure the library is in the standard search
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 library
search path, however does not implement all required
functions.
User response: Ensure the proper version of the
OpenSSL library file is found first in the standard
library 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 qualified
with 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 this machine.
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 Expected
measures and Produced measures in the SNMP
collector log message, especially when there is a
sudden 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
is a system-imposed limit on the number of threads to
be created. The attached workaround is applicable only
if the following warning message is displayed first to
indicate that this is a thread-specific issue as there are
many other configuration issues that can cause data
losses.
DL30287 W SNMPJOB_THREAD_ERR SNMPJob <1s:jobdescr>
can not start in a dedicated thread. Internal error is
<2s:err>.
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 default value of 256. The default value can be
changed by adding a Custom Datachannel parameter in
the TNPM topology. This parameter can be added
using the Topology Editor:
GLOBAL.SNMP.MAXASYNC=<value> where <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 or
channel 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 schema
version 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 not
supported by the target.
GYMDL31007I file line Ignoring line '
Explanation: The specified line was skipped in the
specified file.
User response: Check the log for related DL31093 or
DL31095 messages. Other causes are bad formatting or
the type refers to an SNMP trap.
GYMDL31001I GYMDL31007I
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 to
reconnect.
GYMDL31011I type arg oid Oid '
Explanation: Failed to decode the specified OID.
GYMDL31012I descr id TaskId #
Explanation: The specified SNMP task is still in the
initialized state and can not be scheduled.
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 out of
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 associated with
it. It may cause performance problems within the
collector.
User response: Consider disabling or correcting the
job if performance problems are occurring. Other
messages 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 usage collMeasuredKbps:
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 accept connections.
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 is
showing the context id and SQL that was issued when
the error occurred. This message is controlled by the
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 SQL that
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 database
operation. 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 is controlled
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 another collector.This
message is controlled by the
DIAG.DBUPDATE.COLLECTORCHANGE
configuration setting.
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, deleted
or 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 is
controlled by the DIAG.SCHED.STOPINMODEL and
DIAG.SCHED.STOPCHECKMODEL configuration
settings.
GYMDL31061I taskid index Allowing task (index=
Explanation: The system is allowing the specified task
to be stopped because it is not used in the model.This
DIAG.SCHED.STOPOUTOFMODEL and
DIAG.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 currently
disabled.
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:
for the last hour.
GYMDL31066I prodmeas expmeas requests metrics ses
hour Hour:
for the last hour.
GYMDL31067I err SNMPJob failed to complete with
error: '
Explanation: An SNMP job failed with the specified
error. This message is controlled by the
DIAG.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 by
the DIAG.CMPLXCACHE.RESYNCINSERTION,
DIAG.LIBCACHE.RESYNCINSERTION, and
DIAG.LITECACHE.RESYNCINSERTION configuration
settings.
GYMDL31070I taskid Registering synchronization on
scheduler task
needs to be synchronized, however the task has already
been registered for deletion.This message is controlled
by the DIAG.CMPLXCACHE.RESYNCDELETE,
DIAG.LIBCACHE.RESYNCDELETE, and
DIAG.LITECACHE.RESYNCDELETE configuration
settings.
GYMDL31071I taskid Scheduler task
needs to be deleted.This message is controlled by the
DIAG.CMPLXCACHE.DELETEINSERTION,
DIAG.LIBCACHE.DELETEINSERTION, and
DIAG.LITECACHE.DELETEINSERTION configuration
settings.
GYMDL31072I taskid Registering deletion on
scheduler task
needs to be deleted, however it is already registered to
be 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 functionality and
DIAG.FORMLITE.EXECUTERETURNVALUE
GYMDL31078I form InitMetric (in cache) returned an
error for:
Explanation: The system detected an error initializing
a cached metric.This message is controlled by the
DIAG.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 is
controlled by the DIAG.FORMLITE.RESETFORM
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 the
DIAG.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 an
alternate 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 functionality and
DIAG.FORMLITE.EXECUTECLOSURERETURNVALUE
GYMDL31102I Altering return value (was 0:failure)
changed to 1:success.
Explanation: Updating the return value to success
from failure per configuration setting.This functionality
and message is controlled by the
DIAG.FORMLITE.RESETFORMRETURNVALUE
GYMDL31103I curdevuptime curlastchange curstatus
curvalidcoltime curdevuptime prevlastchange
prevstatus prevvalidcoltime prevdevuptime
sename RFC1213LIB, invalid lastChange
timestamp for SubElement '
Explanation: The system discovered an incorrect
timestamp for the specified sub-element. The system is
forcing 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 command
line.
GYMDL31106I Internal, task must be
TASK_ACTIVE, TASK_ASLEEP or
TASK_ZOMBIE to be validated
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 the
DEBUG.LOGMEMUSE configuration setting.
GYMDL31109I efficiency jobdescr SNMPJob
Explanation: The system is stopping an expensive
SNMP job before it runs.This message and functionality
is controlled by the SNMP.ABORTEXPENSIVEJOBS
GYMDL31111I Process successfully killed.
Explanation: The process mentioned in the previous
DL31089 message was successfully killed.
GYMDL31111I
GYMDL31112I versioncode versionstring name Library '
Explanation: The SSL library was successfully loaded.
The file name and version are provided.
GYMDL31112I
GYMDL31113I name Library '
Explanation: The open SSL library listed was not used
as directed by configuration.This message and
functionality is controlled by the
TUNING.USE_OPENSSL configuration setting.
GYMDL31113I
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.
GYMDL31114I
GYMDL31115I name Library '
Explanation: The open SSL library was removed from
the collector. Partial encryption support now in effect
for SNMP V3.
DataView operational messages
A list of error messages generated by the DataView component.
The message severity indicates how critical it is for the situation to be resolved in
order to resume normal operations. The severity code indicator is identified by a
character at the end of the message ID. They are as follows:
v E' Error
Typically, errors describe events that represent an unrecoverable error within a
server that affect its ability to service some requests, but not all operations are
affected.
v W Warning
Typically, warnings represent recoverable errors.
v I - Informational
Typically, informational messages represent events like normal conditions, events
supplied to clarify operations, e.g. state transitions, operational changes.
Note: In this guide informational messages are not documented as they are self
explanatory and do not require any user action.
GYMVB0002E Settings have not been saved.
Explanation: See message.
User response: Try again. Contact the system
administrator if this problem persists.
GYMVB0003W No settings are currently enabled for
configuration.
GYMVB0004E A valid email address is required.
Type a valid email address.
User response: See message.
GYMVB0005E Unable to set your email address at
present.
User response: Contact the system administrator if
this problem persists.
GYMDL31115I GYMVB0005E
GYMVB0006E The email address has been
successfully set.
GYMVB0008E Changes could not be saved.
Administrator response: Check the network and
database 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 0
through 9 only.
GYMVB0011E The time format is not valid.
User response: Type the time in 24-hour notation
format (HH:mm:ss).
GYMVB0012E Changes were not applied. The
following DataView server is already
configured:
PDF Server
Administrator response:
1. Configure the settings for the server used to
generate PDF files.
2. After applying these settings, click Export to PDF
that is available in the Defined Resource Views
toolbar for users with privileges to create PDF files.
3. In the PDF Server column, type the fully qualified
URL of the PDF Server.
4. In the Additional URL Parameters column, type
any other parameters that the server requires.
5. Set the email address for the Contact button in the
Defined Resource Views toolbar. Typically, this is
the address of an administrator or customer
support.
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 0
through 9 only.
GYMVB0020W Missing the required information to
display the threshold violation data.
GYMVB0021E An error occurred while obtaining
and rendering data.
System action: Event representing the setting of a set
of context parameters.
Event representing the setting of a report runtime
parameter.
Event representing the successful generation of a
report.
GYMVB9000E The following DataView server is
already configured:
<server name>
GYMB0013E GYMVB9000E
GYMVB90001E A value is required for this text field.
<text field name>
GYMVB9010E Unable to open workspace. Please
ensure that the workspace definition is
valid.
Explanation: You might encounter this error, when
you try to open a previously saved workspace.
Typically, you encounter this error if the workspace is
invalid.
User response: Contact the system administrator if
this problem persists.
GYMVC0000E DataView is not installed in eWas!
Explanation: The tool executed by you is unable to
locate an installed version of Dataview in the eWas
application server.
System action: The tool will print the above message
to inform you that Dataview is not installed.
User response: You must contact a system
administrator.
GYMVC0002E Can not connect to eWAS/TIP.
Explanation: The tool was not able to connect to the
application eWas sevrer.
System action: The tool prints the message to inform
you that the application server is not running.
User response: You must contact an administrator or
start up the application server.
GYMVC0003E Can not locate the
'legacyDataview.war' file!
Explanation: The tool cannot find the legacyDataview
war 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's
current context root!
Explanation: The tool is not able to determine the
location of the DataView context root in the eWas
application 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 to
execute an action that is not supported by the tool.
System action: The system will print the above
message followed by the supported actions.
User response: You must execute the configure tool
with 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 value
for the type parameter.
message followed by the supported type of commands
for the configure tool.
User response: You must execute the configure tool by
passing one of the supported commands that is just
displayed as the value for the type parameter.
GYMVC0009E At least one of the following
parameters is required for the jdbc
command: -jdbcUrl, -jdbcUser, or
-jdbcPassword
Explanation: You executed a command of type jdbc
but did not provide any valid values for that type of
command.
message to show what parameters are expected when
executing a command of type jdbc.
User response: You must execute the tool by passing
one or more of the supported jdbc parameters that is
displayed.
GYMVC0010E Logging level not specified or
supported. Available levels are:
Explanation: You executed a command of type
logging but did not provide a valid values for that type
of command.
message followed by the valid values it accepts for the
level parameter.
User response: You must execute the tool by passing
one of the valid values for the level parameter.
GYMVC0006E GYMVC0010E
GYMVC0011E Debug state not specified or
supported. Available states are.
Explanation: You executed the configure tool with an
invalid value for the Debug parameter.
message followed by the valid values it accepts for the
Debug parameter.
User response: You must run the command again by
giving 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 the
jar files it needs.
User response: You must check the location and
provide the correct location.
GYMVC0050E Unsupported database type {0}
Explanation: The tool is unable to connect to the url
provided in the <jdbcurl> parameter
System action: The above message is displayed
followed by the invalid url.
User response: You must check the database url and
provide a valid one.
GYMVC0064E Error occurred: {0}
Explanation: This is a reused message to inform that
the migrate tool encountered an error.
User response: You must examine the error message
to determine what to do next.
GYMVC0076E Unable to connect to SilverStream at:
{0}
Explanation: The migrate tool is unable to connect to
the Silverstream server with the information passed by
the user in the <ssurl>,<ssuser>, and <sspassword>
parameters.
System action: The system prints the message above
followed by the <ssurl> value.
User response: You must check if the Silverstream
server is running and also that you passed the correct
connection info.
GYMVC0090E Unknown Host: {0}
Explanation: The client could not connect to the host
that you passed in the host parameter.
System action: The system displays the message
followed by the host parameter.
User response: You must check that the host is
running. Correct host info if necessary and try again.
GYMVC0091E Unable to connect to DataView at: {0}
Explanation: There is a problem connecting to the
DataView server.
followed by url the tool attempted to connect by using
all the parameters provided.
User response: You must check that the check the
DataView server is running.
GYMVC0092E Authentication Failure.
Explanation: There is a problem authenticating to the
host.
System action:
User response: Check your given user and password
credentials.
GYMVC0094E Wrong context: {0}
Explanation: There is a problem with the context info
supplied by you.
System action:
User response: Check the context you supplied is
valid.
GYMVC0095E Wrong Protocol: {0}
Explanation: The protocol supplied you is incorrect or
invalid.
User response: Supply a valid protocol.
GYMVC0096E Wrong Port: {0}
Explanation: The port number supplied by you is
incorrect.
User response: Supply a valid port.
GYMVC0100E Wrong Directory
Explanation: The directory supplied by you is
incorrect.
User response: Supply a valid directory.
GYMVC0101E Wrong Port: {0}
Explanation: The port number supplied by you is
incorrect.
User response: Supply a valid port.
GYMVC0102E Wrong context: {0}
Explanation: There is a problem with the context info
supplied by you.
System action:
User response: Check the context you supplied is
valid.
GYMVC0103E Wrong Protocol: {0}
Explanation: The protocol supplied you is incorrect or
invalid.
User response: Supply a valid protocol.
GYMVC0105E Unknown Host: {0}
Explanation: The client could not connect to the host
that you passed in the host parameter.
followed by the host parameter.
User response: You must check that the host is
running. Correct host info if necessary and try again.
GYMVC0106E Unable to connect to DataView at: {0}
Explanation: There is a problem connecting to the
DataView server.
followed by url the tool attempted to connect by using
all the parameters provided.
User response: You must check that the check the
DataView server is running.
GYMVC0110W No files found matching pattern: {0}
Explanation: The export tool did not find any files
matching the pattern provided by you.
System action: The export tool did not export any
files.
User response: You need to consider if you passed the
right file extension.
GYMVD0001E Unable to dynamically generate SQL
Explanation: The system is unable to create the SQL
used to retrieve the requested information from the
database.
System action: The system is unable to retrieve the
requested information from the database. You will be
notified of the error and no data will be returned.
User response: You must ensure that the required
parameter values are supplied to the API and that the
provided values are valid.
GYMVD0001W User has not been granted access to
group: User = {0}, Group = {1}
Explanation: You made an API request that is not
granted access to information pertaining to the
specified group.
System action: The system will not process the API
request and no data will be returned.
User response: You must ensure that the specified
group has access granted or contact the administrator
to obtain access to this specific group.
GYMVD0002E Unable to retrieve information from
the data source
Explanation: The system is unable to connect to or
read from the data source containing the requested
information.
requested information. You will be notified of the error
and no data will be returned.
Administrator response: The administrator must
verify that the network connectivity between the
application and database servers is valid and that the
database is running. Check the application server log
file for error messages that may indicate a problem
configuring the data source.
GYMVC0110W GYMVD0002E
GYMVD0002W Time period does not align with
aggregation period; Daily
pre-aggregated data will be used
Explanation: A request is made to retrieve the
pre-aggregated data from the database, but the
specified start/end times do not align with the
aggregation periods.
System action: The system will process the request by
using the daily pre-aggregated data that best fits within
the time period specified by you.
User response: To avoid this situation, you must
ensure that the start and end times specified for the
API request align with the aggregation periods
configured within the system.
GYMVD0003E Specified entity name(s) are not
unique: {0}
Explanation: The name(s) provided as API parameters
are not uniquely identify specific entities.
System action: The system is unable to uniquely
identify the entity for which information is requested.
You will be notified of the error and no data will be
returned.
determine where the similarly named entities reside
within the database and assign unique names.
GYMVD0003W Monthly dates do not align with
Explanation: A request is made to retrieve the
monthly pre-aggregated data from the database, but the
the time period specified by you. Using the daily
aggregated data is less efficient than using the monthly
aggregated data.
User response: For best performance, you must ensure
that the start and end times specified for the API
request align with the aggregation periods configured
within the system.
GYMVD0002W GYMVD0003W
GYMVD0004E Unable to determine numeric
identifier(s) for entity name(s)
Explanation: The system is unable to locate the named
entities in the database.
requested information from the database for the named
entity. No data will be returned for that entity.
User response: You must ensure that the entity
name(s) provided as API parameters are valid and that
those entities exist.
GYMVD0004W Weekly dates do not align with
Explanation: A request is made to retrieve the weekly
pre-aggregated data from the database, but the
the time period specified by you. Using the daily
aggregated data is less efficient than using the weekly
aggregated data.
User response: For best performance, you must ensure
that the start and end times specified for the API
request align with the aggregation periods configured
within the system.
GYMVD0005W Unable to retrieve registry value {0}
Explanation: The API request is not able to retrieve
from the registry the value corresponding to the
specified registry key.
System action: The system will attempt to process the
request as appropriate without the registry value.
examine the server logs for warning or error messages
that may indicate a problem reading from the registry
or verify that the registry entry exists.
GYMVD0006E Unable to identify named property:
{0}
property in the database.
property. No data will be returned for that property.
User response: You must ensure that the property
name provided as an API parameter is valid and that
the 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 retrieve
from the registry the value corresponding to the
specified registry key. The specified default value will
be used.
System action: The system will attempt to process the
request by using the default value.
that may indicate a problem reading from the registry
or verify that the registry entry exists.
GYMVD0007E Unable to identify named user: {0}
user in the database.
user. No data will be returned for that user.
User response: You must ensure that the user name
provided as an API parameter is valid and that the
user exists.
GYMVD0007W Unable to initialize the CORBA ORB
Explanation: The system is unable to initialize and/or
configure the communication between the DataView
and DataChannel components necessary to support
near-real time metric data or probe configuration.
System action: Near-real time metric data is not
included in the API response and the user will be
unable to configure probes.
that may indicate the reason for the initialization
failure.
GYMVD0008E Invalid time period: start time = {0},
end time = {1}
Explanation: The system is unable to retrieve the
requested information because the specified time period
is not valid.
requested information from the database for the
specified time period. No data will be returned to the
user.
User response: You must ensure that the start and end
time are valid and that the start time precedes the end
time.
GYMVD0006W GYMVD0008E
GYMVD0008W Unable to establish connection to
near-real time service
Explanation: The system is unable to initialize and/or
configure the communication between the DataView
and DataChannel components necessary to support
near-real time metric data functionality.
System action: Near-real time metric data will not be
included in the API response
User response: The administrator must examine the
server logs for warning or error messages that may
indicate networking problems. The DataChannel logs
should also be examined to determine whether CORBA
connections are being accepted.
GYMVD0008W
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law :
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement might not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBM's application programming interfaces.
Each copy or any portion of these sample programs or any derivative work, must
include 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_. All rights
reserved.
If you are viewing this information in softcopy form, the photographs and color
illustrations might not be displayed.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International 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 and
trademark information at www.ibm.com/legal/copytrade.shtml.
Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered
trademarks 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 and
Telecommunications Agency which is now part of the Office of Government
Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of The
Minister for the Cabinet Office, and is registered in the U.S. Patent and Trademark
Office.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Notices 179
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the
United States, other countries, or both and is used under license therefrom.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are
trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Printed in USA

PDF TNPM Troubleshooting

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

PDF TNPM Troubleshooting

Caricato da

Copyright:

Formati disponibili

IBM Tivoli Netcool Performance Manager 1.3.

support communities (forums and newsgroups)

Potrebbero piacerti anche