Job Management Partner 1/Performance Management User's Guide

[Contents][Glossary][Index][Back][Next]

14.2 Troubleshooting

This section describes how to conduct troubleshooting while you are using Performance Management. If an error occurs while you are using Performance Management, you should first check to see if any of the events described in this section have occurred.

The following table lists and describes the principal errors that might occur while you are using Performance Management.

Table 14-1 Errors

Classification Error Reference
Setting up and starting service
  • A Performance Management program service does not start.
  • A service takes a long time to start once startup is requested.
  • Immediately after a Performance Management program service is stopped, another program starts service and communication is not performed properly.
  • After the message The disk capacity is insufficient is output, the Master Store service, Agent Store service, or Remote Monitor Store service stops.
 14.2.1
Connecting to agents An error message, such as Cannot connect to an agent is output to PFM - Web Console. 14.2.2
Logging on to PFM - Web Console
  • The specified Performance Management user name is not recognized during logon.
  • Cannot establish a connection from PFM - Web Console to the View Server service.
 14.2.3
Executing commands
  • When the jpctool service list command is executed, the names of services not operating are output.
  • When the jpctool db dump command is executed, the output data does not match the data in the specified Store database.
 14.2.4
Agent management
  • No agent is displayed in the Agents window of PFM - Web Console.
  • The operating status of the server or agent is Unconfirmed or Not Supported.
 14.2.5
Report definition
  • There is a time period not indicated on the history report.
  • A memory shortage can occur with the View Server service when a large number of reports are displayed simultaneously.
 14.2.6
Alarm definition
  • The program defined to be executed by an action does not work properly.
  • No alarm event is displayed.
 14.2.7
Collecting and managing performance data
  • Even if the data storage time is set for a shorter period, the size of the Store database for the Agent Store service and the Remote Monitor Store service does not become smaller.
  • The message Illegal data was detected in the Store database. is output to the common message log.
 14.2.8
Linking with other programs
  • A server request error occurs and no connection is established when linking with an ODBC-compliant program.
  • A status change event is not displayed in the event browser when linking with NNM.
  • No symbol appears in ovw when linking with NNM.
  • JP1 events are not reported when linking with JP1/IM.
  • Monitored PFM - Agent or PFM - RM is not displayed in the monitoring tree window when linking with a monitored object function of JP1/IM.
  • The display color of the monitored object does not change when linking with a monitored object function of JP1/IM.
 14.2.9
Organization of this section
14.2.1 Setting up and starting a service
14.2.2 Connecting to agents
14.2.3 Logging on to PFM - Web Console
14.2.4 Executing commands
14.2.5 Agent management
14.2.6 Report definition
14.2.7 Alarm definition
14.2.8 Collecting and managing performance data
14.2.9 Linking with other programs
14.2.10 Other problems

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.