Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference

7.2 Troubleshooting

This section explains troubleshooting for Performance Management. If an error occurs while you are using Performance Management, first check whether any of the phenomena explained in this section has occurred.

The table below shows the major errors that may occur in Performance Management.

Table 7-1 Error description

Category Error description Description location

Setting up or starting a service

The Performance Management program service does not start.

It takes a long time between a service startup request and the actual service startup.

When another program begins a service immediately after a Performance Management program service has been stopped, communication cannot be correctly executed.

After the message The disk capacity is insufficient. is issued, the Master Store service or Agent Store service stops.

7.2.1

Executing commands

When the jpctool service list (jpcctrl list) command is executed, a non-active service name is output.

When the jpctool db dump (jpcctrl dump) command is executed, data that is different from the specified Store database is output.

7.2.2

Report definitions

Information for some period of time is not displayed in historical reports.

7.2.3

Alarm definitions

The program defined in action execution does not run correctly.

No alarm event is displayed.

7.2.4

Collecting and managing performance data

Even though the data retention period is set to be short, the size of PFM - Agent's Store database does not decrease.

The message Illegal data was detected in the Store database. is output to the common message log.

7.2.5

Hang-up and abnormal termination

Even though the PFM Agent for Windows service is running, performance information is not collected.

The PFM Agent for Windows service terminates abnormally.

When the PFM Agent for Windows service stops, the KAVE05034-E error message is output.

7.2.6

Organization of this section

7.2.1 Setting up or starting a service

7.2.2 Executing commands

7.2.3 Report definitions

7.2.4 Alarm definitions

7.2.5 Collecting and managing performance data

7.2.6 Hang-up and abnormal termination

7.2.7 Other problems

Category	Error description	Description location
Setting up or starting a service	The Performance Management program service does not start. It takes a long time between a service startup request and the actual service startup. When another program begins a service immediately after a Performance Management program service has been stopped, communication cannot be correctly executed. After the message The disk capacity is insufficient. is issued, the Master Store service or Agent Store service stops.	7.2.1
Executing commands	When the jpctool service list (jpcctrl list) command is executed, a non-active service name is output. When the jpctool db dump (jpcctrl dump) command is executed, data that is different from the specified Store database is output.	7.2.2
Report definitions	Information for some period of time is not displayed in historical reports.	7.2.3
Alarm definitions	The program defined in action execution does not run correctly. No alarm event is displayed.	7.2.4
Collecting and managing performance data	Even though the data retention period is set to be short, the size of PFM - Agent's Store database does not decrease. The message Illegal data was detected in the Store database. is output to the common message log.	7.2.5
Hang-up and abnormal termination	Even though the PFM Agent for Windows service is running, performance information is not collected. The PFM Agent for Windows service terminates abnormally. When the PFM Agent for Windows service stops, the KAVE05034-E error message is output.	7.2.6

[Contents][Back][Next]

[Trademarks]