4.7.2 Updating the Store version to 2.0
The Store database comes in two versions, 1.0 and 2.0. The difference between the two versions is the saving format. For details about Store version 2.0, see the chapter that describes the design of the operations monitoring system in the JP1/Performance Management Planning and Configuration Guide.
Store version 2.0 is provided as the default when you perform a new installation of PFM - Agent for Platform version 08-11 or later in an environment with PFM - Base or PFM - Manager version 08-11 or later. In other cases, the Store version remains 1.0. If you want to use Store 2.0, you must use a setup command to update the version to 2.0.
If you have to restore Store 1.0 from Store 2.0, perform unsetup of Store 2.0.
The following table shows the installation conditions, whether Store 2.0 is available for the given conditions, and the procedure for enabling Store 2.0.
|
Installation conditions |
Whether Store 2.0 is available |
Procedure for enabling Store 2.0 |
|
|---|---|---|---|
|
Version of installed PFM - Base or PFM - Manager |
PFM - Agent installation type |
||
|
Earlier than 08-11 |
Overwrite installation |
No |
Update the version of PFM - Base or PFM - Manager to 08-11, and then execute the setup command. Update the version of PFM - Base or PFM - Manager to 08-11 or later, and then execute the setup command. |
|
New installation |
|||
|
08-11 or later |
Overwrite installation |
Available after setup |
Execute the setup command. |
|
New installation |
Yes |
None |
|
- Organization of this subsection
(1) Setup of Store 2.0
-
Estimate the system resources and determine the retention period.
Check whether the system resources that Store 2.0 requires are suitable for the execution environment. The system resources to be considered are the following:
-
Disk capacity
-
Number of files
-
Number of files opened by one process
These can be adjusted by the retention period settings. When you specify the retention period, take into account the resources available in the execution environment. See the Release Notes for details about estimating system resources.
-
-
Review the directory settings.
When the Store version is updated to 2.0, the Agent Store service might fail to start with the same directory settings that were available in Store 1.0. For this reason, you must review the settings of the directories used by the Agent Store service. You can use the jpcconf db define command to view and change the settings of these directories.
The maximum length of the names of the save destination directory, backup destination directory, and other directories used by the Store database in Store 2.0 differs from the maximum length in Store 1.0. In particular, be careful when the directory settings have been changed to use a relative path name in Store 1.0. If the settings have been changed, confirm that the length of the absolute path name for the relative path name is no more than 214 bytes, which is the maximum length for directory names in Store 2.0. If the absolute path name is longer than the maximum, change the settings of each directory used by the Agent Store service before proceeding to the next step.
-
Execute the setup command.
Execute the following command to update the Store version to 2.0:
jpcconf db vrset -ver 2.0 -key UNIX
For details about the jpcconf db vrset command, see the manual JP1/Performance Management Reference.
-
Set the retention period.
Specify the retention period that you determined in step 1. Start the Agent Store service, and then specify the retention period in PFM - Web Console.
(2) Unsetup of Store 2.0
Use the jpcconf db vrset -ver 1.0 command to perform unsetup of Store 2.0. When unsetup is performed, the entire Store database is initialized and the Store version reverts to 1.0.
For details about the jpcconf db vrset command, see the manual JP1/Performance Management Reference.
(3) Notes
(a) When migrating from Store version 1.0 to Store version 2.0
When the Store database is migrated from Store version 1.0 to Store version 2.0, retention period settings for records of the PI record type are carried over. For records of the PD record type, however, the default number of retention days is set for each record regardless of the previously set value (number of retained records), and data collected before the number of retention days is deleted.
For example, in Store version 1.0, when the number of retained records is set to 1,000 for PD records for which Collection Interval is set to 3,600 seconds, 24 PD records are retained in a day. As a result, data for 1,000 ÷ 24 (roughly 42) days is retained. After this Store database has been migrated to Store version 2.0, if the default number of retention days is set to 10, data from 11 or more days before is deleted and can no longer be viewed.
Before migrating to Store version 2.0, check the settings for the number of retained records for records of the PD record type. If data is set to be retained for the default number of retention days or more for Store version 2.0, use the jpctool db dump command to output the data in the database. See the Release Notes for details about the default number of days saved in Store version 2.0.
(b) When returning from Store version 2.0 to Store version 1.0
When unsetup is performed for Store version 2.0, data is initialized. Therefore, before changing the version to Store version 1.0, use the jpctool db dump command to output Store version 2.0 information.