-
タイトル
Blocking sessions appear sooner in the built-in dashboard than a custom dashboard when SQL PI is enabled -
説明
When using a custom dashboard to view blocking the sessions show up almost 2-3 min late and the database properties for some databases are not visible.
-
原因
There are two topologies blocked_history_data > pi_blocked_history and blocked_history_data > blocked_history
The PI blocked history data is stored in the PI repository and is not accessible for reporting.
When using SQL PI, the built-in blocking dashboard will begin using the SQL PI collections for the blocking data instead of the topology in the databases dashboard which uses a collection running in the background and stored in the FMS repository.
The background database agent blocking collection will also be managed by the Administration setting minimal duration (seconds) for collecting a block.
-
対策
Lower the threshold in the admin panel for the blocked history to 30 seconds or lower.- Navigate to the databases dashboard
- Select the database agent
- Select Settings | Administration
- Choose the Locks menu item in the Administration dashboard
- Select the database agent checkbox and click the Edit button
- Change the minimal duration (seconds) for collecting a block
- Click the Set button
- Click the Save Changes button
The topology for the Blocking History data is
All Data[]->DBSS_Data_Model-->clusters[]-->instances[]-->blocked_history_data-->blocked_historyOther options can include
Changing the refresh interval on an custom dashboard (to 20 seconds)Change the collection frequency for blocking for Online and Real time (as described in KB 114612)