4.3.2 Size limits that apply to the Store database
- Organization of this subsection
(1) With Store 2.0
With Store 2.0, data is stored in multiple files, each covering a specific time period. Also, the data for each record type is stored in a different data file. For this reason, a size limit of 2 GB applies to each individual data file, rather than to the total amount of data in the database. Also, you cannot exceed the file size limit imposed by the ulimit command on UNIX systems or other restrictions on the file system.
You can calculate the size of each data file by using an expression to estimate the amount of disk space occupied by the Store database and setting the retention period for historical data to zero. For the expression used to estimate the amount of disk space occupied by the Store database, see the appendix describing the amount of disk space occupied by the Store database (Store version 2.0) for PFM - Agent 08-00 and later in the JP1/Performance Management Planning and Configuration Guide, or an appropriate PFM - Agent manual.
Data for each record type is written to a data file in the Store database that is switched periodically. If the size of the data file reaches the limit within the allotted time period, the KAVE00227-W message is output, and no more data of that record type is written to the database. However, the Agent Store and Remote Monitor Store services continue to run.
When the allotted time period elapses and the data file is switched, the KAVE00228-I message is output and the Agent Store and Remote Monitor Store services resume writing data to the database.
(2) With Store 1.0
The maximum overall file size of the Store database used in Performance Management is 2 GB. Also, you cannot exceed the file size limit imposed by the ulimit command on UNIX systems or other restrictions on the file system.
The Store service stops when the file size of the Store database has reached the limit.# In this case, the KAVE00182-E message is output to the system log (Windows Event Log in Windows or syslog on UNIX systems) and the common message log.
- #
-
If this symptom occurs, the Agent Store service stops, but the Agent Collector service does not stop.
If the file size of the Store database has reached the limit, perform the following steps:
-
Access the Agent Collector properties from PFM - Web Console, and change the settings so that no records are collected.
In this situation, only the Agent Store service stops. The Agent Collector service is still running.
-
Use the jpcspm start command to restart the Agent Store service.
For details on the jpcspm start command, see the chapter on commands in the manual JP1/Performance Management Reference.
-
Back up data.
To do so, use the jpctool db dump or jpcrpt command, or output reports to a file in CSV or HTML format. For details on how to use the jpctool db dump command to back up performance data and event data, see 4.1.4 Exporting performance data and 4.2.2 Exporting event data, respectively.
For details on the jpcrpt command, see the chapter on commands in the manual JP1/Performance Management Reference.
For details on how to output reports to files in CSV of HTML format, see 5.9.1 Exporting reports in CSV or HTML format by using a Web browser.
-
Erase data.
Erase the performance data. For details on how to erase performance data and event data, see 4.1.6 Erasing performance data and 4.2.4 Erasing event data, respectively.
-
Access the Agent Collector properties from PFM - Web Console.
Configure the Agent Collector service to collect records, and then resume operation.