2.10.1 Notes on operating
-
Microsoft SQL Server must be installed and started before PFM - Agent for Microsoft SQL Server is started. Performance data can be collected only when Microsoft SQL Server has been installed, set up, and started.
-
Before using reports and alarms of the monitoring templates, you need to enable collection of the records to be used for reports and alarms. For example, the Cache Usage alarm is associated with the SQL, Troubleshooting, Recent Past, and Cache Usage report definitions. Therefore, you need enable collection of PI_SERV records to display the associated reports. For details about the records required for using alarms and reports, see 4. Monitoring Template.
-
If you attempt to retrieve PD_JH record data in real time from the Microsoft SQL Server database that is currently executing a large number of jobs, data reception might fail with the message KAVE10167-E or KAVE10162-E displayed. If KAVE10167-E or KAVE10162-E is displayed, reduce the number of records to be displayed by using the filter setting or the ranking view.
-
The number of errors to be collected varies as follows depending on whether you are using 10-00-20 or earlier versions or 10-00-21 or later versions to collect historical data of the Errorlog Error Detail (PD_EE) record (or to evaluate the alarm that uses the Errorlog Error Detail (PD_EE) record as the data source):
- <10-00-20 or earlier versions>
-
The number of errors recorded in the Microsoft SQL Server error log after the previous data collection time
- <10-00-21 or later versions>
-
The number of errors recorded in the Microsoft SQL Server error log after the previous data collection time or the value specified for the instance information LIMIT_PD_EE_NUMBER, whichever is smaller
If you upgrade from 10-00-20 or an earlier version to 10-00-21 or a later version, the default value 1000 is set as the instance information LIMIT_PD_EE_NUMBER. For details about the instance information LIMIT_PD_EE_NUMBER, see 2.1.4(2) Setting up an instance environment.
-
While PFM - Agent for Microsoft SQL Server is collecting information, exclusive locks may occur to secure the data integrity due to rebuilding the indexes on the monitoring target Microsoft SQL Server. In this case, the locks will be released if they are considered not to influence the data integrity. Then, the collecting-information request from PFM - Agent for Microsoft SQL Server can be rolled back and its collection can fail.
If this incident happens, PFM - Agent for Microsoft SQL Server fails to collect information temporarily. Yet, after rebuilding the indexes completes, PFM - Agent for Microsoft SQL Server can successfully collect information at next interval. Although PFM - Agent for Microsoft SQL Server continues to operate, it is recommended that you should stop the service of PFM - Agent for Microsoft SQL Server while the Microsoft SQL Server is rebuilding the indexes so that PFM - Agent for Microsoft SQL Server does not fail to collect information.
-
If Microsoft SQL Server creates a table during a transaction and does not finalize an operation, a shared lock is placed on the system table, so, at that time, queries for Microsoft SQL Server fail and PFM - Agent for Microsoft SQL Server cannot collect data until the operation is finalized.
-
While PFM - Agent for Microsoft SQL Server is collecting data, an attempt to create a new database of Microsoft SQL Server may fail if the attempt is made when a shared lock is set on the database. This shared lock is set because of the specifications of the ADO or the ODBC that PFM - Agent for Microsoft SQL Server uses for database queries. If this error occurs, stop the services of all the instances of PFM - Agent for Microsoft SQL Server, and then create a new database.
-
When you use the jpcconf inst setup (jpcinssetup) command to create an instance environment, even if you specify the name of an instance that does not exist in Microsoft SQL Server, the command terminates normally. When you start collecting records thereafter, an error occurs. In that case, check whether the name of the instance is correct and then re-execute the jpcconf inst setup (jpcinssetup) command.
-
For notes on executing the jpctool service list command for the Agent Collector service or Agent Store service, see the chapter that describes commands in the manual JP1/Performance Management Reference.
-
If PFM - Agent for Microsoft SQL Server fails to start, the Agent Store service remains running. Use the jpcspm stop command to terminate the service. Alternatively, make Agent Collector service ready to be started, and then use the jpcspm start command to start it. There is no problem if the Agent Store service remains.
-
When this product is installed for the first time and the Add or Remove Programs dialog box is opened, the icon displayed for the product might switch to another icon immediately after being displayed. This is only a problem with the icon display, and does not affect product operation.