2.9.1 Notes on operating

• Microsoft SQL Server must be installed and started before PFM -RM 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 RM SQLServer, Troubleshooting, Recent Past, and Cache Usage report definitions. Therefore, you need enable collection of PI_SERV records to displaythe associated reports. For details about the records required for usingalarms and reports, see 4. Monitoring Template.

• While PFM - RM 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 - RM for Microsoft SQL Server can be rolled back and its collection can fail.

  If this incident happens, PFM - RM for Microsoft SQL Server fails to collect information temporarily. Yet, after rebuilding the indexes completes, PFM - RM for Microsoft SQL Server can successfully collect information at next interval. Although PFM - RM for Microsoft SQL Server continues to operate, it is recommended that you should stop the service of PFM - RM for Microsoft SQL Server while the Microsoft SQL Server is rebuilding the indexes so that PFM - RM 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 - RM for Microsoft SQL Server cannot collect data until the operation is finalized

• While PFM - RM 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 and the ODBC that PFM - RM for Microsoft SQL Server uses for database queries. If this error occurs, stop the services of all the instances of PFM - RM for Microsoft SQL Server, and then create a new database.

• It may take longer for PFM - RM for Microsoft SQL Server to detect connection failure than the value of the LOGIN_TIMEOUT parameter you specified when you set the monitoring target, if the monitoring target Microsoft SQL Server host stops or is not found on the network due to the network failure or else. This is because Windows TCP/IP configuration decides how many times TCP retries sending the connection requests. You can change the number of retries by adjusting the TcpMaxConnectRetransmissions parameter. If you change the value of TcpMaxConnectRetransmissions, it will affect the whole TCP/IP communication including the connection between PFM - RM for Microsoft SQL Server and the Microsoft SQL Server. When you adjust the TcpMaxConnectRetransmissions parameter, please take into account the behaviour

• Due to the specifications of Microsoft SQL Server, if you specify the host name longer than 15 bytes, PFM - RM for Microsoft SQL Server can sometimes fail to connect to the Microsoft SQL Server. For details, contact Microsoft.

• You cannot monitor the Microsoft SQL Server installed on the Linux.

• When you use the jpcconf target setup 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 target setup command.

• For notes on executing the jpctool service list command for the Remote Monitor Collector service or Remote Monitor Store service, see the chapter that describes commands in the manual JP1/Performance Management Reference.

• If PFM - RM for Microsoft SQL Server fails to start, the RM Store service remains running. Use the jpcspm stop command to terminate the service. Alternatively, make RM Collector service ready to be started, and then use the jpcspm start command to start it. There is no problem if the RM 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.

To Page Top