Advertisement

08.28.2008 at 07:22AM PDT, ID: 23685554
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.0

getting deadlock with process using the procedure sp_server_info

Asked by IDCSSupport in Sybase Database

I was doing an off hours "ALTER TABLE" and we are getting deadlocks with a ubknown process that is executing the procedure 'sp_server_info'. I need to run these alter statements to change the width on a column. See sample text from one of the deadlocks below:

Deadlock Id 19: Process (Familyid 292 292) (suid 949) was executing a EXECUTE command in the procedure 'objid 4541929'.
SQL Text: exec Sp_SeRvEr_InFo
Deadlock Id 19: Process (Familyid 671, 671) (suid 1) was executing a ALTER TABLE command at line 1.
SQL Text:
Deadlock Id 19: Process (Familyid 0, Spid 671) was waiting for a 'exclusive table' lock on the 'sysindexes' table in database 5 but process (Familyid 292, Spid 292) already held a 'shared table' lock on it.
Deadlock Id 19: Process (Familyid 0, Spid 292) was waiting for a 'shared intent' lock on the 'sysobjects' table in database 5 but process (Familyid 671, Spid 671) already held a 'exclusive table' lock on it.

Deadlock Id 19: Process (Familyid 0, 671) encountered multiple deadlocks.
Deadlock Id 19: Process (Familyid 0, 671) was chosen as the victim. End of deadlock information.
Start Free Trial
 
Keywords: getting deadlock with process using th…
 
Loading Advertisement...
 
[+][-]08.28.2008 at 09:43AM PDT, ID: 22336903

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: Sybase Database
Sign Up Now!
Solution Provided By: grant300
Participating Experts: 1
Solution Grade: B
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628