December 13, 2002 at 2:18 pm
This is a synopsis of a SQL 7.0 failure that I had. Has anyone experienced this?
Backup logs job started On database which also restores logs on stand by server..
Took 1hr :44mins to run before it got cancelled by issueing stop command to SQLServer agent
Started traces to capture data for blocked processes
Started killing blocking processes but couldn't kill any
Issued stopp to SQL Server services. SQL agent stopped but engine was still trying to stop.
Issued hard boot to the system
System came backup SQL Server was started successfully.
December 13, 2002 at 3:28 pm
Why couldnt you kill the processes? Were they system spids? Taking the server down without letting SQL finish checkpointing should definitely be a last resort. One of my servers takes anywhere from 7-10 mins to close down once I issue the stop.
Andy
December 13, 2002 at 3:54 pm
The problem is that I couldn't kill any fo the processes. They were all database spids coming from an application server.
Even after I shutdown all the application servers I could still see them and couldn't kill them.
December 14, 2002 at 6:23 am
Still not sure I understand. When you issued the kill, did the spid begin rollback? Not affected at all? Are you sure the app server didnt immediately reconnect and establish the spid?
Andy
December 16, 2002 at 1:00 pm
The spid did not begin rollback and was not affected at all. We stop all the processes on the app server so it wasn't trying to reconnect.
December 26, 2002 at 9:53 am
Has anyone else seen this problem?
December 28, 2002 at 4:43 pm
I'm running SQL 7.0 SP 4 with latest hot fix I had similar problem yesterday my server became unresponsive. We Couldn't connect to the databases. I ran couple of perfmon counter but they were showing no activity on server. I tried to stop and start services but it got hanged. Helplessly we had to reboot the system. When system came back we checked sql errorlogs which shows error " The Scheduler 0 appears to be hung. PSS 0x44B31128, EC 0x44B312D8, UMS Context 0x0109FBA0" any clue ?
January 1, 2003 at 5:37 pm
Got this through our DBA from Microsoft Support - any similarlity?
Please check KB (BUG: Ghosted Record Cleanup Process May Go Into CPU
Spin Due to an WGID:168
ID: 284938.KB.EN-US) for more details.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;284938
January 2, 2003 at 11:59 pm
Where the spids in as rollback-state ? Then you cannot kill them. I've noticed this in relation with some non-IT-developed access-applications. After these applications where banned to use the production sqlserver this phenomenon nomore occured.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply