17.7.1 Restore procedure for an error related to changes in the configuration

Use the following procedure to restore Performance Management when there is an error related to changes in the configuration.

Organization of this subsection

(1) Stopping services
(2) Checking the consistency of and restoring the service definition information
(3) Checking the consistency of and restoring the performance data and event data
(4) Reconstructing the index file
(5) Starting services
(6) Checking operations

(1) Stopping services

Stop all Performance Management program services.

For details on stopping a service, see 1.3 Stopping services.

To Page Top

(2) Checking the consistency of and restoring the service definition information

Compare the service definition information on the target host and the backed-up service definition information to check for any inconsistencies. Save any files on the target host that are different, and then restore the backed-up service definition information.

For details on the service definition information to be restored, see 9.2 Backing up and restoring definition information.

To Page Top

(3) Checking the consistency of and restoring the performance data and event data

Compare the data model definition files on the target host and the backed-up data model definition files to check for any inconsistencies. Save any files on the target host that are different, and then restore the backed-up data model definition files.

The following table shows the data model definition files that must be compared and restored.

OS	Type	File name
In Windows	PFM - Manager	`installation-folder\mgr\store\*.DAT`
	PFM - Manager	`installation-folder\agt0\store\*.DAT`
	PFM - Agent and PFM - RM	`installation-folder\xxxx`^#1`\store\*.DAT`
	PFM - Agent and PFM - RM	`installation-folder\xxxx`^#1`\store\instance-name`^#2`\*.DAT`
In UNIX	PFM - Manager	`/opt/jp1pc/mgr/store/*.DAT`
	PFM - Manager	`/opt/jp1pc/agt0/store/*.DAT`
	PFM - Agent and PFM - RM	`/opt/jp1pc/xxxx`^#1`/store/*.DAT`
	PFM - Agent and PFM - RM	`/opt/jp1pc/xxxx`^#1`/store/instance-name`^#2`/*.DAT`

#1

xxxx indicates the service key of each PFM - Agent or PFM - RM. For details on service keys of each PFM - Agent or PFM - RM, see the description of the naming rules in an appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

#2

Folders when running in an instance environment. One folder is created for each instance.

Note:

If the Master Store, Agent Store, or Remote Monitor Store service is started when the comparison check reveals an inconsistency, the Store database becomes invalid. In this case, use the following procedure to fix the Store database.

Stop the Master Store, Agent Store, or Remote Monitor Store service.
Delete all of the following files in the installation directory of the Store database.

- Files with the extension .DB

- Files with the extension .IDX
Restore the Store database.

For details on restoring the Store database, see 9.3 Backing up and restoring operation monitoring data.

To Page Top

(4) Reconstructing the index file

Execute the following command to reconstruct the index file of the Store database:

In Windows: installation-folder\bin\jpcmkindex xxxx^#1 [-lhost logical-host-name^#2]
In UNIX: /opt/jp1pc/bin/jpcmkindex xxxx^#1 [-lhost logical-host name^#2]
#1: xxxx indicates the service key of each PFM - Agent or PFM - RM. For details on service keys of each PFM - Agent or PFM - RM, see the description of the naming rules in an appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.
#2: To specify the service of the logical host environment, specify the -lhost option. If this option is omitted, the physical host is temporarily set.

The following table lists the command return values. If the command does not terminate normally, follow the solutions in the table to review the command, and then reconstruct the index file again.

Return value	Command execution result	Solution
0	Terminated normally.	N/A
1	There is an error in the argument setting.	Check, and if necessary, revise the command arguments.
2	You do not have permissions to execute the command.	Check, and if necessary, revise the permissions to execute command.
4	The specified service is not stopped.	Perform the following procedure: Stop the specified service. Delete all of the following files in the installation directory of the Store database. Files with the extension `.DB` Files with the extension `.IDX` Restore the Store database.
5	The specified service is not installed.	Install the specified service.
100	The Performance Management environment is invalid.	Restore the Store database.
102	The specified logical host name is not set up.	Set up the specified logical host name.
230	Execution of an internal command failed.	Check for the following problems: The memory or hard drive size is insufficient The limit on the number of processes has been exceeded Note: If the return value is 230 even after checking and re-executing the command, the Store database must be restored.
255	An index creation error occurred.	Delete all of the following files in the installation directory of the Store database: Files with the extension `.DB` Files with the extension `.IDX`

Legend:: N/A: Not applicable
Note:: For details on restoring the Store database, see 9.3 Backing up and restoring operation monitoring data.

To Page Top

(5) Starting services

Start the Performance Management program services and confirm that the service starts normally.

For details on starting the services, see 1.2 Starting services. Use the jpctool service list command to check the service status. For details on checking the service status, see 1.6 Checking the status of service operations.

To Page Top

(6) Checking operations

Lastly, make sure that the trouble has been resolved. Check whether the following items are normal:

Check whether performance data can be collected

Run Performance Management for more than twice the length of the collection interval for performance data to confirm that performance data can be collected without a problem.

For details on the collection interval of performance data, see 4.1.1 Modifying the recording options for performance data.
Check whether there is a problem with the data in the Store database

Export the data of the Store database to a text file and check whether there is a problem with the data. Use the jpctool db dump command to export the data in the Store database to a text file.

For details on the jpctool db dump command, see the chapter that describes commands in the manual Job Management Partner 1/Performance Management Reference.
Check the report and alarm definitions

Check whether there is a problem with the report or alarm definitions. Use PFM - Web Console to check the report and alarm definitions.

For details on the report definition, see 5. Creation of Reports for Operation Analysis. For details about the alarm definition, see 6. Monitoring Operations with Alarms.

To Page Top