![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Job Management Partner 1/Performance Management - Remote Monitor for Platform Description, User's Guide and Reference
This subsection describes how to handle problems that are related to collection and management of Performance Management performance data.
- Organization of this subsection
- (1) The size of the PFM - RM for Platform's Store database is not reduced even though the data retention period was shortened
- (2) The message "Illegal data was detected in the Store database" is output to the common message log
- (3) PFM - RM for Platform was started, but no performance data is being collected
(1) The size of the PFM - RM for Platform's Store database is not reduced even though the data retention period was shortened
If the Store database has reached its maximum size but shortening the data retention period does not reduce the file size, you need to shorten the retention period, back up the Store database, and then restore the database.
For details about how to specify the data retention period, see the chapter that describes management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide. For details about how to back up and restore the Store database, see the chapter that describes backup and restore processing in the Job Management Partner 1/Performance Management User's Guide.
(2) The message "Illegal data was detected in the Store database" is output to the common message log
An inconsistency might have occurred in the Store database due to an unexpected service stop or machine shutdown. Take one of the following actions:
- If you have backed up the Store database, restore it.
- If you have not backed up the Store database, stop the Remote Monitor Store service, delete the corresponding database files (*.DB and *.IDX files), and then restart the service.
(3) PFM - RM for Platform was started, but no performance data is being collected
If the Status field value in the PD record is ERROR, take appropriate action based on the Reason field value.
The following describes the items to be checked for each Reason field value.
(a) Connection failed: Connection to the monitored host failed.
- In Windows
- Is the monitored host running?
- Is the WMI service running on the monitored host?
- Were the settings for the following specified correctly when the monitoring target was set up?#
TargetHost
- Can the name be resolved by the host name (TargetHost) that was specified when the monitoring target was set up?
- Were the following WMI connection setup procedures performed correctly?
- If there is a firewall between PFM - RM for Platform and the monitoring target, is the firewall passage port set appropriately?
- In UNIX
- Is the monitored host running?
- Is the SSH service running on the monitored host?
- Were the following settings specified correctly when the monitoring target was set up?#
- Can the name be resolved by the host name (TargetHost) that was specified when the monitoring target was set up?
- Was the SSH connection setup procedure performed correctly?
- If there is a firewall between PFM - RM for Platform and the monitoring target, is the firewall passage port set appropriately?
- #
- To check the settings, execute the jpcconf target setup command. Alternatively, use PFM - Web Console to check the settings by displaying the Remote Monitor Configuration properties from the Remote Monitor Collector service of PFM - RM for Platform.
(b) Authorization failed: Authorization of the monitored host failed.
- In Windows
- Were the following settings specified correctly when the monitoring target was set up?#
- Were the following WMI connection setup procedures performed correctly?
- #
- To check the settings, execute the jpcconf target setup command. Alternatively, use PFM - Web Console to check the settings by displaying the Remote Monitor Configuration properties from the Remote Monitor Collector service of PFM - RM for Platform.
(c) Value other than Connection failed or Authorization failed
- Collect maintenance data and contact the system administrator.
- In a Windows environment, check the application event log and take appropriate action.
To use PFM - RM for Platform to collect performance data for the records listed below, PFM - RM for Platform must be set up so that objects can be monitored on the performance console.# The table below lists the objects corresponding to each record, the source (service) names that are output to the event log, and the performance extension DLLs.
- #
- You can use Performance to check the object name that corresponds to each record. If there is no corresponding object, specify the settings according to the procedure provided in Microsoft Knowledge Base by Microsoft so that the objects can be monitored.
Table 7-2 Objects corresponding to each record, the source (service) names that are output to the event log, and the performance extension DLLs
No. Category Record name (record ID) Object name Source (service) name that is output to the event log Performance extension DLL 1 Disk Logical Disk Overview (PI_LDSK) LogicalDisk WinMgmt perfdisk.dll 2 Physical Disk Overview (PI_PDSK) PhysicalDisk 3 Network-related Network Interface Overview (PI_NET) Network Interface WinMgmt perfctrs.dll 4 OS in general (such as processors and memory) System Overview (PI) Memory WinMgmt perfos.dll 5 System 6 Processor 7 Processor Overview (PI_CPU) Processor WinMgmt perfos.dll If the name WinMgmt is recorded in the application event log, PFM - RM for Platform might not function correctly or the records corresponding to that source (service) might not be collected. If the application event log contains the events shown in the table below, either reinstall the source (service) or eliminate the cause of the error that is disclosed in Microsoft Knowledge Base, or contact the developer of the source (service) and then repair the environment so that the application event logs are not recorded.
The following table shows examples of application event logs when PFM - RM for Platform is not functioning correctly or the records for the source (service) cannot be collected.
Table 7-3 Examples of application event logs when records are not collected successfully
No. Event ID Source (service) name Event log information 1 37 WinMgmt WMI ADAP 0x0 was unable to read the file-name performance library due to an unknown problem in the library. 2 41 WinMgmt WMI ADAP did not create object index n for the performance library service-name because the value was not found by the 009 subkey. 3 61 WinMgmt WMI ADAP was unable to process the file-name performance library due to a time violation in the open function.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.