It may take a long time after the jpcspm start (jpcstart) command is executed or a service is started using the Service icon before the service actually starts. If the startup takes a long time because of any of the causes listed below, the time it takes for the service startup is shortened during subsequent service startup operations.
- If you start a service in stand-alone mode, service startup may take a long time.
- If a service is started by restarting the system without specifying that the service be automatically stopped when the system is stopped, the Store database index may be rebuilt. In this case, service startup may take a long time.
- When the service is started after a new agent is added, the Store database index is created only during the initial startup. As a result, service startup may take a long time.
- If the Store service cannot be terminated normally because of a power failure, for example, the Store database index is rebuilt during a restart, and as a result, service startup may take a long time.
Immediately after a Performance Management program service has been stopped, if the port number that was used by this service is used by another program to start a service, communication may not be correctly executed. To avoid this condition, specify one of the following:
- Specify fixed port numbers for assignment to the services of the Performance Management program.
Assign fixed port numbers for the individual services of the Performance Management program. For details about how to specify port numbers, see the chapter explaining installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Specify the TCP_TIMEWAIT value
Set the connection wait time to the default in the TCP_TIMEWAIT value. Use the following default value:
- In Windows Server 2003, Windows Server 2008, and Windows Server 2012: 2 minutes
If the disk used by the Store database does not have sufficient free space, storing of data in the Store database is halted. In this case, the message The disk capacity is insufficient. is issued and the Master Store service or Agent Store service stops.
When this message is issued, take one of the following steps:
- Allocate sufficient disk capacity
Estimate the disk space requirement for the Store database, and change the Store database storage destination to a disk that has sufficient capacity. For details about how to estimate the disk space requirement for the Store database, see A. Estimating System Requirements. For details about how to change the Store database storage destination, see 4.7 Changing the operation of PFM - Agent for Platform.
- Change the saving conditions for the Store database
Change the saving conditions for the Store database and adjust the upper limit for the data volume in the Store database. For details about how to change the saving conditions for the Store database, see the chapter explaining management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide.
If the Master Store service or Agent Store service still does not start even after one of these steps has been taken, an unrecoverable logical conflict has occurred in the Store database. In this case, first restore the Store database from backup data and then start the Master Store service or Agent Store service. If there is no available backup data, first initialize the Store database and then start the Master Store service or Agent Store service. To initialize the Store database, delete all of the following files, which are located in the Store database destination directory:
- Files with the extension .DB
- Files with the extension .IDX
For details about the Store database destination directory, see the chapter explaining installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.