I've been doing this IT work for quite sometime now. In the past we worked with Dec equipment and local area vax clusters and RDB. No we work mostly with Sql Server and some Oracle, but locking and blocking locks can still be issues.
On the older lavc we could have a lock on a server that blocked a lock on another server, so we had to be sure that we looked in multiple areas for locking and blocking. On rac, link servers, linked instances etc we need to be aware that blocking can be occurring on servers other than the one we are currently working on or looking at. So we need to be looking and aware of what could be impacting the application.
How are we aware that a remote lock might be causing us some trouble. Well first we would want to understand what the application is doing, is it making a remote call? If it is not then we would focus on our current server and look for resource issues there. If it does make remote calls, we would still first look at our current server and resource issues there but if they appear to be okay but our process does not appear to be making any progress we would want to look at the resources on the remote server and see how things look there. We could very well have a remote locking block occurring that needs to be addressed. Other resource issues can always come into play as well.
Good luck, keep dba'ng and looking for resources.
Mark
No comments:
Post a Comment