7.2.1 Problems relating to the start and setup of services

This subsection describes how to correct errors related to the start and setup of services.

Organization of this subsection
(1) Performance Management program service does not start
(2) There is a delay from the time the start request is issued until the service starts
(3) Communication fails when a second program starts a service immediately after a Performance Management program service is stopped
(4) The following message is output and the Master Store service or Remote Monitor Store service stops: "The disk capacity is insufficient"
(5) The Oracle Database does not stop
(6) The PFM - RM Remote Monitor Collector service does not start

(1) Performance Management program service does not start

Potential causes and actions to take are as follows:

(2) There is a delay from the time the start request is issued until the service starts

Occasionally, you may experience a delay after executing the jpcspm start command or clicking an icon in the Services window until the service actually starts. If this delay is caused by one of the following, the service will start more quickly next time.

(3) Communication fails when a second program starts a service immediately after a Performance Management program service is stopped

If another program starts a service that uses the same port number as a Performance Management program service that has recently stopped, communication may not be performed correctly. To prevent this from occurring, perform either of the following settings:

(4) The following message is output and the Master Store service or Remote Monitor Store service stops: "The disk capacity is insufficient"

The system will stop recording data in the Store database if there is not enough space on the disk used by the database. In this case, the following message is output and the Master Store or Remote Monitor Store service stops: The disk capacity is insufficient.

If this message appears, take one of the following actions:

If the Master Store service or Remote Monitor Store service still does not start, an unrecoverable logic conflict has occurred in the Store database. In this case, restore the Store database from backup data, and then start the Master Store or Remote Monitor Store service. If no backup data is available, initialize the Store database and then start the Master Store or Remote Monitor Store service. You can initialize the Store database by deleting the following files from the Store database's storage directory:

For details about the storage directory of the Store database, see 2.6.1 Changing the storage location of performance data.

(5) The Oracle Database does not stop

When you attempt to stop the monitored Oracle Database before stopping PFM - RM for Oracle, a normal shutdown may not stop the Oracle Database. In this case, use an immediate shutdown to stop the Oracle Database.

(6) The PFM - RM Remote Monitor Collector service does not start

For the PFM - RM host running in Windows, the Remote Monitor Collector service fails to start when PFM - RM is started, and either of the following messages is output to the Windows event log when Windows is restarted.

Because this failure is due to the Windows service control manager timing out, the failure tends to occur when the communication load with PFM - Manager is high, and too much time is required to receive a response from PFM - Manager. This problem occurs when all the following conditions exist.

You can use either of the following operational techniques to avoid this problem:

#
This is a directory on a shared disk specified when the logical host was created.