How can special lock waits be analyzed?
Pro-active Suggestion is:-
The namesever topology tracks the current state of the database (e.g. existing tables and locations) and is implemented as shared memory. Concurrent accesses to the nameserver topology are synchronized via a file on operating system level:
If there is a bottleneck accessing the /tmp directory (e.g. because it is mounted via NFS) and there are massive topology changes (e.g. due to a high amount of temporary objects), the performance can be significantly impacted. In order to minimize the risk of synchronization delays you have to make sure that /tmp is located on fast, local devices.
Special lock waits are all lock waits that aren't covered by normal thread states and monitoring views. Due to a lack of monitoring data it is particularly hard to analyze them.
Read here How can transactional lock waits be analyzed?
Sign up for STechies
Ask Question From Our Experts
All the site contents are Copyright © www.stechies.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies. The site www.stechies.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity. Information used on this site is at your own risk.
The content on this site may not be reproduced or redistributed without the express written permission of
www.stechies.com or the content authors.