7.2 Troubleshooting

This section describes troubleshooting related to the use of Performance Management. If a problem occurs when you are using Performance Management, first check whether any of the events explained in this section has occurred.

The table below describes the main problems that can occur in Performance Management.

Table 7‒1: Troubleshooting
Classification	Problem description	Described in
Setup and service startup	A Performance Management program service does not start. It takes a long time for a service to start after a service startup request is issued. When another program begins a service after a Performance Management program service has stopped, communication cannot be established correctly. After an `The disk capacity is insufficient` message is output, the Master Store service or Remote Monitor Store service stops. The Remote Monitor Collector service of PFM - RM does not start.	See the chapter that explains troubleshooting in the JP1/Performance Management User's Guide.
Command execution	When the `jpctool service list` command is executed, a service name that is not active is output. When the `jpctool db dump` command is executed, data that is not from the specified Store database is output.
Report definition	Some time bands are not displayed in the historical report.
Alarm definition	A program defined in the action definition is not running correctly. No alarm event is displayed.
Performance data collection and management	Even though a short data retention period was set, the size of the PFM - RM for Virtual Machine Store database is not reduced. The message `Illegal data was detected in the Store database` is output to the common message log.
Performance data collection and management	Even though PFM - RM for Virtual Machine has started, no performance data is being collected. There is a large time difference between Record Time and Sampling Time.	7.2.1

Organization of this section

To Page Top