If the Store database has already reached its maximum file capacity when you reduce the data retention period, file size will not decrease. In this case, back up and then restore the Store database after reducing the retention period.

For details about how to set the data retention period, see the chapter on management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide. For details about how to back up and restore the Store database, see the chapter on backup and restoration in the Job Management Partner 1/Performance Management User's Guide.

If a service terminates or the machine shuts down unexpectedly, inconsistencies may appear in the data in the Store database. In this case, take the following action:

• If you have a backup of the Store database, restore the database from the backup.
• If you do not have a backup, stop the Remote Monitor Store service, delete the corresponding database files (*.DB and *.IDX files), and then restart the service.

Take the following action:

• Check the startup status of the monitored host.
• If PFM - RM for Oracle and the monitoring target communicate across a firewall, check the port number to route traffic through the firewall.
• Check the startup status of the Oracle Database and start it if it is inactive.
• Check the monitoring target settings.
• Execute the jpcconf target setup command to specify the correct value for each item. For the detail about jpcconf target setup command, see the chapter on the commands in the manual Job Management Partner 1/Performance Management Reference.
• Check the instance environment settings.
  Execute the jpcconf agent setup command to specify the correct value for each item. For details about the jpcconf agent setup command, see the chapter on the commands in the manual Job Management Partner 1/Performance Management Reference.