Job Management Partner 1/Performance Management User's Guide

4.3.3 When the disk capacity is insufficient

The Store database stops accepting more data when it cannot use sufficient required disk space. If this occurs, a KAVE00105-E message is output, and the Master Store, Agent Store, or Remote Monitor Store service stops.

If you receive the above message, perform one of the following procedures:

• Reserve sufficient disk space
• Reduce the disk space occupied by the Store database

Organization of this subsection

(1) Reserving sufficient disk space

(2) Reducing the disk space occupied by the Store database (Store 1.0 only)

(1) Reserving sufficient disk space

Estimate how much disk space is used by the Store database and change the storage location of the Store database to a disk with enough free space. For details on how to estimate the amount of disk space occupied by the Store database, see the appendix describing system estimation in the appropriate PFM - Agent or PFM - RM manual. For details on how to change the storage location of the Store database for event data, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide. For details on how to change the storage location of the Store database for performance data, see the appropriate PFM - Agent or PFM - RM manual.

(2) Reducing the disk space occupied by the Store database (Store 1.0 only)

First, you must change the current settings to decrease the maximum size of the disk space occupied exclusively by the Store database. To decrease the maximum size of data, you can restrict the number or type of records to be collected by the Agent Collector service, or set shorter retention periods or smaller numbers of stored records to be kept by the Store database. For details on how to change which records are collected by the Agent Collector service, see 4.1.1 Modifying the recording options for performance data. For details on how to change the retention conditions for the Store database, see 4.1.3 Modifying the retention conditions for performance data (in Store 1.0) and 4.2.1 Changing the maximum number of records for event data.

You cannot, however, reduce the disk space occupied exclusively by the Store database only by setting the maximum size of data. To reduce the occupied disk space, perform the following procedures:

• For the Store database of the Agent Store service:
  Follow steps 1-3 below:
  
  1. Delete the performance data for records in the Store database that are no longer needed.
     In the Store database, unnecessary data for a particular record is deleted when new performance data of that record is stored. If you configure the Agent Collector service to no longer collect particular records, the performance data for those records remains in the Store database, and the amount of disk space occupied by the Store database remains the same. Perform the following procedure to delete the performance data of records that are no longer being collected from the Store database. This procedure is not required for the Store database of the Master Store service, or for when you have not configured any records not to be collected by the Agent Collector service.
     The following procedure shows an example of how to delete data of unwanted records from the Store database.
     For example, suppose you are using PFM - Agent for Platform, and want to change the collection settings from Yes for PI_LOGD, Yes for PI_NIND, and Yes for PD_PD to No for PI_LOGD, Yes for PI_NIND, and No for PD_PD
     (1) Set Yes for records that you no longer want collected. Set No for all other records. In this example, set Yes for PI_LOGD and PD_PD, and No for the others.
     (2) Modify the retention conditions as follows:
     - For PD and PL record types, set the maximum number of records to 0.
     - For the PI record type, set the retention period of records to the minimum for each collection period. For example, set Minute for performance data stored in minutes and Hour for performance data stored in hours.
     (3) Store the performance data in the Store database at least once.
     Note 1: For details on the timing when the performance data is stored in the Store database, see the chapter that describes the Performance Management functions in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
     Note 2: Tasks (1) to (3) invalidate the area in the Store database occupied by the records that you no longer want to collect (in this example, PI_LOGD and PD_PD). The invalidated areas can be eliminated from the database file by reorganizing the Store database. Note that you might be unable to invalidate the entire area occupied by the performance data if the record is a PI-type record or a Process Detail (PD) record of PFM - Agent for Platform. For details, see [Notes about the data that cannot be deleted from the Store database even by storing the performance data of the record].
     (4) Set No as the collection setting for all records.
     (5) Set your desired retention conditions of the Store database.
     (6) Set your desired collection configurations.
     
  2. Deleting the extra performance data in the Store database
     If you reduce the number of records kept by the Store database or set shorter retention periods, you will have more performance data in the Store database than the retention conditions allow. This is because the data stored by using previous retention conditions still remains intact. If this is the case then you must perform the following procedure to delete the extra performance data that does not match the new retention conditions. This procedure is only required when you have set shorter retention periods or smaller numbers of stored records to be kept by the Store database.
     (1) Set your desired retention conditions of the Store database.
     (2) In the Store database store, at least once, the performance data of the records for which you modified the retention conditions.
     Note 1: For details on the timing when the performance data is stored in the Store database, see the chapter that describes the Performance Management functions in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
     Note 2: The area of the performance data for a record that no longer matches the retention conditions is invalidated when a new record is stored and performance data in the Store database is increased. The invalidated areas can be eliminated from the database file by reorganizing the Store database. Note that you might be unable to invalidate the entire area occupied by the performance data if the record is a PI-type record or a Process Detail (PD) record of PFM - Agent for Platform. For details, see [Notes about the data that cannot be deleted from the Store database even by storing the performance data of the record].
     
  3. Reorganizing the Store database
     Reorganize the Store database to reduce the disk space occupied exclusively by the Store database. For details on how to reorganize the Store database, see 4.3.4 Checking the size of, and reorganizing, the Store database.
     

  [Notes about the data that cannot be deleted from the Store database even by storing the performance data of the record]

  When the performance data of a record is stored in the Store database, the area of the performance data for a record that does not match the retention conditions is invalidated when the performance data of the record increases in the Store database. There are, however, some records in the Store database where storing additional performance data for them does not increase the size of the data. None of the performance data for these records shall be invalidated. Records of PI record type or of the Process Detail (PD) of the PFM - Agent for Platform fall under this category.

  In the case of the PI record type, in a summary block where new performance data is created by the process of storing performance data, the performance data for that summary block is deleted from the Store database. When new performance data is not created, the data remains in the Store database. Note that the performance data in the summary block of year always remains. For example, suppose that the Store database contains performance data for the PI-LOGD record that was all collected before 16:00:00 on May 23, 2006 (Tuesday), and you store performance data for the PI_LOGD record at 10:00:00 on May 24, 2006 (Wednesday). The performance data in the summary block of year remains in the database. The performance data for May 2006 is consolidated into the performance data in the summary block of month, so no new performance data is created. Accordingly, all the performance data of the PI_LOGD record in the summary block of month remains in the Store database. Similarly, all the performance data in the summary block of week remains in the Store database. For the performance data in the summary block of day, the new performance data for May 24, 2006 is created, so all of the performance data of the PI_LOGD record in the summary block of day is invalidated in the Store database. Similarly, all of the performance data in the summary block of hour and minute is invalidated. Count all the remaining performance data in when you estimate the disk space occupied exclusively by the Store database.

  In case of the Process Detail (PD) record of the PFM - Agent for Platform, when there is no difference between the data last collected and the one that has just been collected, the performance data remains in the Store database. For details on the Process Detail (PD) record of PFM - Agent for Platform, see the chapter explaining records in the manual Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference. Either make differences so that the old performance data will be deleted, or add such space as required for the Process Detail (PD) record to the estimated disk space occupied exclusively by the Store database when you operate the system.

• For the Store database of the Master Store service:
  
  1. Set your desired retention conditions for the Store database.
  2. Store the event data in the Store database at least once.
     Note 1: For details on the timing when the event data is stored in the Store database, see the chapter that describes the Performance Management functions in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
     Note 2: The area of the data that no longer matches the retention conditions is invalidated when event data for the record is stored in the Store database. The invalidated area can be deleted from the database file by reorganizing the Store database.
     
  3. Reorganize the Store database.
     Reorganize the Store database to reduce the disk space occupied exclusively by the Store database. For details on how to reorganize the Store database, see 4.3.4 Checking the size of, and reorganizing, the Store database.
     

If the Master Store service or the Agent Store service does not start even after taking these actions, there might be some unrecoverable logical errors in the Store database. In this case, you must restore the Store database from the backup data, and then restart the Master Store service or the Agent Store service. If you have no backup data, you must initialize the Store database, and then start the Master Store service or the Agent Store service. To initialize the Store database, delete all the files indicated below from the storage directory of the Store database.

• Files with the extension .DB
• Files with the extension .IDX

The default storage directories of the Store database are listed below.

The storage directory of the Store database for performance data:

For details, see each of the PFM - Agent manuals.

The storage directory of the Store database for event data:

• In Windows:
  installation-folder\mgr\store
  
• In UNIX:
  /opt/jp1pc/mgr/store
  

You can change the storage directories of the Store database for event data in the jpcsto.ini file. For details on how to change the storage directories, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.