H. Upgrade Procedure and Notes on Upgrading

To upgrade PFM - Agent for Platform to a newer version, install the newer version by overwriting the older version. For details about installation operations, see 4. Installation and Setup in UNIX.

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 older version. If you uninstall it, performance data and other data created with the older version are also deleted, and as a result, the newer version will not work.

• When a newer version of PFM - Agent for Platform program is installed by overwriting an older version, the following items are automatically updated:

  • Store database file of the Agent Store service

  • ini file

• When the PFM - Agent for Platform program 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.

• When PFM-Agent for Platform version 07-50 or earlier has already been installed, and an overwrite installation of PFM-Agent for Platform 08-00 or later is performed, some records are no longer supported. When you perform the upgrade installation, the following messages about this change are displayed by the PP installer:

  In the Performance Management - Agent Option for Platform that you are attempting to install, there is a limit on supported records.

  For details, please see the "Release Notes."

  For more information about the records that are no longer supported, please see M. Version Changes.

• If an overwrite installation from version 07-50 or earlier is performed, unsupported records are shown in both the Detail Records and Interval Records displayed in the properties of the PFM - Web Console's Agent Collector service, as well as in Retention displayed in the properties of the Agent Store service.

  You can change the properties of these records, but you cannot edit them, nor store them in the Agent Store database. To prevent unsupported records from being shown in Detail Records and Interval Records, you must copy the jpcagt.ini.model file that is in the in /opt/jp1pc/agtu/agent directory to jpcagt.ini, and reset the properties.

  Similarly, to prevent unsupported records from being shown in Retention, you must copy the jpcsto.ini.model file that is in the in /opt/jp1pc/agtu/store directory to jpcsto.ini, and reset the properties.

  The procedure for the above is as follows:

  1. Stop the service by using the jpcspm stop -key agtu command.

  2. Copy the jpcagt.ini.model file to jpcagt.ini.

  3. Copy the jpcsto.ini.model file to jpcsto.ini.

  4. Start the service by using the jpcspm start -key agtu command.

  5. Reset the property for each record by using PFM - Web Console, because the most recent settings are assumed as the default settings.

• In Linux 8 or CentOS 8, when you upgrade PFM - Agent for Platform to version 12-50 or later, you may need to review the ALL Container Collection for Process property setting. For details, see 2.3.21(5)(b) Notes on the Podman host environment.

To Page Top