7.2.1 Problems relating to the collection and management of performance data
This subsection describes how to correct errors related to the collection and management of performance data in Performance Management. For details about how to correct other types of errors, see the JP1/Performance Management User's Guide.
- Organization of this subsection
(1) Performance data is not collected after PFM - RM for Microsoft SQL Server startup
Take the following action:
-
Check the startup status of the monitored host.
-
If PFM - RM for Microsoft SQL Server and the monitoring target communicate across a firewall, check the port number to route traffic through the firewall.
-
Check the startup status of the Microsoft SQL Server and start it if it is inactive.
-
Check the monitoring target settings.
-
Execute the jpcconf target setup command to specify the correct value for each item.
-
Check the instance environment settings.
Execute the jpcconf inst setup command to specify the correct value for each item.
-
When PFM - RM for Microsoft SQL Server communicates with Microsoft SQL Server in the following configurations, check if a 64-bit alias is specified by using SQL Server Client Network Utility on the PFM - RM host or any other tool.
-
TCP/IP is enabled in the protocol settings and a non-default Microsoft SQL Server port number is specified.
-
The named pipe protocol is enabled.
In PFM - RM for Microsoft SQL Server version 11-50 or later, specify a 64-bit alias by using SQL Server Client Network Utility on the PFM - RM host or any other tool.
In version 11-10 or earlier, you need to specify a 32-bit alias, but in version 11-50 or later, the settings have been changed. For this reason, special attention is required for upgrading version 11-10 or earlier.
For details about alias setting, see 2.1.4(2)(e) Notes when a non-default Microsoft SQL Server port number or the named pipe protocol is used to connect with Microsoft SQL Server or 3.3.1(5) Notes when a non-default Microsoft SQL Server port number or the named pipe protocol is used to connect with Microsoft SQL Server.
-
-
If the monitored Microsoft SQL Server is set to encrypt communications, check that the DRIVER_NAME is correctly specified. For details, see the description about DRIVER_NAME in 2.1.4(2)(b) Set the monitoring target.
For details about the jpcconf agent setup command, see the chapter on the commands in the manual JP1/Performance Management Reference.