G. Upgrade Procedure and Notes on Upgrading
To upgrade PFM - Agent for Platform to a later version, install the later version by overwriting the earlier version. For details about installation operations, see 4. Installation and Setup in Windows.
For notes about upgrading the Performance Management programs, see the section that presents the notes on upgrading in the chapter and appendix describing installation and setup in the JP1/Performance Management Planning and Configuration Guide.
The following are notes about upgrading PFM - Agent for Platform:
-
When upgrading the PFM - Agent for Platform version, do not uninstall the earlier version. If you uninstall it, performance data and other data created with the earlier version are also deleted, and as a result, the later version will not work.
-
When a later version of PFM - Agent for Platform is installed by overwriting an earlier version, the following items are automatically updated:
-
Store database file of the Agent Store service
-
ini file
-
-
When this product is upgraded, the existing Store database is also automatically upgraded. It may take a few dozen of minutes for the installation to finish, depending on the size of the Store database.
-
The maximum size of Store database files (*.DB and *.IDX) after upgrading is 1.8 GB. However, if a limit is set for the file size or file system by using the ulimit command, then the maximum file size is 90% of that limit, or 1.8 GB, whichever is less. If the size of Store database files exceeds this maximum size, after upgrading, the data that does not fit in the maximum size is deleted, and the message KAVE05834-W is output to the common message log. The data to be deleted is selected by using the following rules:
-
For the PD database or PL database
Data is deleted sequentially, starting with the oldest data.
-
For the PI database
Data is deleted sequentially based on the period by which it is summarized, in the following order: minute, hour, day, week, month, and year. When the summary period is the same, the data is deleted sequentially, starting with the oldest data.
As mentioned above, old data may get deleted. If necessary, output the performance data to a CSV file before upgrading. For details on outputting a CSV file, see the chapter explaining outputting reports in the manual JP1/Performance Management User's Guide.
-
-
When Store databases are upgraded, the data model changes, and therefore the disk usage of the Store databases changes. Based on the new data model, please review, and if necessary change, the collection items and frequency as well as the storage conditions of the Store databases.
-
When an upgrade installation is performed, the Store database is automatically updated. Because of this, free space equal to twice the size of the Store database is temporarily needed on the disk where the database is stored. Therefore, before you perform an upgrade installation, make sure there is sufficient space on the disk where the Store database is stored.