7.2 Troubleshooting procedures

Problems relating to the start and setup of services

• A Performance Management program service does not start.

• The Oracle Database does not stop.

7.2.1

• There is a delay from the time the start request is issued until the service starts.

• Communication fails when another program starts a service immediately after a Performance Management program service is stopped.

• The following message is output and the Master Store or Remote Monitor Store service stops: The disk capacity is insufficient.

• The PFM - RM Remote Monitor Collector service does not start.

See the chapter that explains troubleshooting in the JP1/Performance Management User's Guide.

Problems relating to command execution

• The name of an inactive service is output when you execute the jpctool service list command.

• The data output by the jpctool db dump command is not the Store data you specified.

Problems relating to report definitions

• During a certain period, the collected data is not shown in the historical report.

Problems relating to alarm definitions

• A program defined in an action does not operate correctly.

• Alarm events are not displayed.

• Although the alarm threshold has been exceeded, the color of the alarm icon shown in the Alarm Status window of the Agents tree remains green.

Problems relating to collection and management of performance data

• The PFM - RM for Oracle Store database remains large despite setting a short data retention period.

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

• Performance data is not collected after PFM - RM for Oracle startup.

7.2.2