-
Title
Historical lock analysis says that no data is available -
Description
When in the historical lock analysis module of Performance Analysis for SQL Server it will show a screen that says no data is available.
"Time Range:N/A Lock information is available up to 1899-12-30 PM 12:00
No Lock activity was observed for the selected time range"
-
Cause
The historical lock analysis retrieves its data from long term repository database, and is having a problem to do so.
Possible causes:
1) The problem in this case is the password of the Agent Administrator user (quest) on the monitored server side was changed but the change is not reflected in the Middleware or Repository configuration files on the Middleware platform.
You have changed the default password for user "quest" and added one more user who is not an Administrator of the Agent.But the Repository on the Middleware is configured to use the default password of user "quest"
The Middleware will continue to work in spite of unsynchronized passwords between Middleware agents and Monitored Host agents but the Repository will not. So we have a situation where the monitored agents passed on the collection data to the Middleware and data is up to date in recent collection but is out-of-sync on the Repository.2) The monitored instance is a node of a cluster. The configuration file is pointing to the physical node of the cluster, instead of the virtual node name, as a result the data sync between the monitored instance and the repository is not in sync.
-
Resolution
RESOLUTION 1:
In the agent administration and then check the status of the repository agent to notice an error.
AgentStatus: A severe problem has been detected. Click on more for more information says the following:
There was a critical problem with the repository.
Start | Programs | Quest Software | Performance Analysis | Agent Administration
Please reconfigure the Repository connection using the agent installer. The reconfiguration will ask for the new password for connecting to monitored host and this will be used in rewriting the Repository config files both on Monitored host and Middleware platform.
Choose" install a performance repository for an existing agent" option during the install.It should pickup that the quest user password that has changed.Please provide the correct password of user "quest" that is current for the agent on the Monitored host.
You will also get a message to override the repository configuration. Click yes.
Once this is done you will have access to the repository again and get historical lock information.,RESOLUTION 2:Re-run the Agent Installation and select that this is a Active/Passive cluster during the installation. Supply the virtual hostname to be monitored, and after installation check whether it fixes the problem. If the issue persists, contact Technical Support with a full support bundle.