January 7, 2010 at 6:41 pm
I have a Windows 2K Server with 4GB Ram, etc.. SQL Server 2003 SP3 with DB's ranging in size from 300mb to 4.2GB (data file size). We had shut the server down for a UPS Replacement and upon powering it back up all but two of the databases came back online (inc. Great Plains Dynamics). The two that will not allow me to login to are the Symantec Backup Exec 11 BEDB database and a custom database (which is the 4.2 GB one). If I try to start the BU Exec services, to launch the BU Exec application, it times out and in the The event log shows the following:
2010-01-07 19:18:17.53 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2010-01-07 19:18:17.53 server Copyright (C) 1988-2002 Microsoft Corporation.
2010-01-07 19:18:17.53 server All rights reserved.
2010-01-07 19:18:17.53 server Server Process ID is 1020.
2010-01-07 19:18:17.53 server Logging SQL Server messages in file 'd:\data\MSSQL\log\ERRORLOG'.
2010-01-07 19:18:17.54 server SQL Server is starting at priority class 'high'(4 CPUs detected).
2010-01-07 19:18:17.64 server SQL Server configured for thread mode processing.
2010-01-07 19:18:17.65 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2010-01-07 19:18:18.10 server Attempting to initialize Distributed Transaction Coordinator.
2010-01-07 19:18:18.64 server Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
2010-01-07 19:18:18.67 spid3 Starting up database 'master'.
2010-01-07 19:18:19.01 spid3 0 transactions rolled back in database 'master' (1).
2010-01-07 19:18:19.01 spid3 Recovery is checkpointing database 'master' (1)
2010-01-07 19:18:19.07 spid5 Starting up database 'model'.
2010-01-07 19:18:19.07 server Using 'SSNETLIB.DLL' version '8.0.766'.
2010-01-07 19:18:19.07 spid3 Server name is 'SQL'.
2010-01-07 19:18:19.09 spid8 Starting up database 'msdb'.
2010-01-07 19:18:19.09 spid9 Starting up database 'pubs'.
2010-01-07 19:18:19.09 spid10 Starting up database 'Northwind'.
2010-01-07 19:18:19.09 spid11 Starting up database 'BEDB'.
2010-01-07 19:18:19.09 spid12 Starting up database 'DYNAMICS'.
2010-01-07 19:18:19.09 spid13 Starting up database 'WAI'.
2010-01-07 19:18:19.10 spid14 Starting up database 'WJI'.
2010-01-07 19:18:19.12 spid15 Starting up database 'WFI'.
2010-01-07 19:18:19.12 spid16 Starting up database 'WNEC'.
2010-01-07 19:18:19.12 spid17 Starting up database 'WS125'.
2010-01-07 19:18:19.12 spid18 Starting up database 'TWO'.
2010-01-07 19:18:19.17 spid19 Starting up database 'TPRO'.
2010-01-07 19:18:19.24 spid20 Starting up database 'WCS'.
2010-01-07 19:18:19.24 spid5 Clearing tempdb database.
2010-01-07 19:18:19.26 server SQL server listening on 192.168.1.111: 1433.
2010-01-07 19:18:19.26 server SQL server listening on 127.0.0.1: 1433.
2010-01-07 19:18:19.31 server SQL server listening on TCP, Shared Memory, Named Pipes.
2010-01-07 19:18:19.31 server SQL Server is ready for client connections
2010-01-07 19:18:19.31 spid13 14 transactions rolled forward in database 'WAI' (9).
2010-01-07 19:18:19.35 spid11 123 transactions rolled forward in database 'BEDB' (7).
2010-01-07 19:18:19.35 spid13 0 transactions rolled back in database 'WAI' (9).
2010-01-07 19:18:19.37 spid13 Recovery is checkpointing database 'WAI' (9)
2010-01-07 19:18:19.37 spid16 15 transactions rolled forward in database 'WNEC' (12).
2010-01-07 19:18:19.42 spid16 0 transactions rolled back in database 'WNEC' (12).
2010-01-07 19:18:19.42 spid11 0 transactions rolled back in database 'BEDB' (7).
2010-01-07 19:18:19.43 spid16 Recovery is checkpointing database 'WNEC' (12)
2010-01-07 19:18:19.43 spid11 Recovery is checkpointing database 'BEDB' (7)
2010-01-07 19:18:19.79 spid12 308 transactions rolled forward in database 'DYNAMICS' (8).
2010-01-07 19:18:19.84 spid12 0 transactions rolled back in database 'DYNAMICS' (8).
2010-01-07 19:18:19.86 spid12 Recovery is checkpointing database 'DYNAMICS' (8)
2010-01-07 19:18:19.96 spid5 Starting up database 'tempdb'.
2010-01-07 19:49:19.45 server Error: 17883, Severity: 1, State: 0
2010-01-07 19:49:19.45 server The Scheduler 0 appears to be hung. SPID 19, ECID 0, UMS Context 0x03BF3B38.
2010-01-07 19:50:19.45 server Error: 17883, Severity: 1, State: 0
If I try to launch Enterprise Manager, it starts up fine and logs in fine, but if I try to expand any of the folders (database, etc.) if freezes... also the 4 CPU Box is idle.. all quiet..
Does anyone have any ideas on what to try to correct this issue?
Thanks ahead of time!
January 8, 2010 at 1:07 am
There are no errors in that list of messages. That's just SQL's startup routine.
Can you open query analyser and try to query one of those databases?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 8, 2010 at 6:48 am
Hi Gail,
When I entered my office this morning, they were all up are running fine, I restarted the Backup Exec Engine and DB and that started fine too.. I have read that SP4 might fix the issue with the hung process.. but one other thing to note.. The servers hard drives where churning for about 15 mins after the SQL Server was up and running.. could there be an issue maybe with caching or something?
January 8, 2010 at 9:09 am
I don't know what the issue could be with, because, as I said, I see nothing wrong with the errorlog, and there's not really enough info here to work with.
Once SQL starts, the disks will work harder than later, as the data cache has to be 'warmed'. That may be a significant increase or it may be unnoticeable. Depends on the app, the database, etc.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 8, 2010 at 9:36 am
There are rollforward messages in there, if they were large transactions, they could have caused some disk activity.
January 8, 2010 at 12:31 pm
you have the infamous 17883 Messages in there which suggest the server was stressed. these could have the effect of making SQL unresponsive.
Did you only have those two occurrences or were there in fact a whole heap of them?
SP4 does not resolve this issue, it just outputs extra info that would help MS troubleshoot it.
---------------------------------------------------------------------
January 8, 2010 at 1:59 pm
There were many up until three hours later.. the discs where not spinning for no more than 1/2 hour of that 3 hours.. and the processors where showing only a 1% utilization...
January 8, 2010 at 2:41 pm
well thats the reason you were having connection problems.
Not a lot you can do now just keep an eye on it see if it becomes a recurring problem.
---------------------------------------------------------------------
January 8, 2010 at 3:31 pm
I just wanted to prove a point and succeeded.. I shut the server down early this afternoon.. same thing happened after I powered back up.. same two DB's.. had to wait 2-3 hours for them to come back online.. maybe the raid write cache is on and not finishing it's writes prior to restart?
January 8, 2010 at 4:09 pm
if you got the 17883s again thats an error, those are not normal messages on a restart. If your sysadmins cannot identify a HW\OS problem I would contact microsoft.
---------------------------------------------------------------------
January 8, 2010 at 5:11 pm
Would applying SP$ goive more info on the issue?
January 9, 2010 at 2:55 am
Is there more to the error log than what you've indicated?
Did you try to query the databases from Query Analyser like I asked?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 9, 2010 at 3:12 am
szymas (1/8/2010)
Would applying SP$ goive more info on the issue?
on this one MS would probably ask you apply SP4. the extra info it gives i think is in the form of memory dumps so you are going to need assistance to intrepet them.
---------------------------------------------------------------------
January 9, 2010 at 9:22 am
by good fortune I have just seen another post with a reference to a link about 17883 and related errors, I think you should read it
http://technet.microsoft.com/en-us/library/cc917684.aspx#_17883%20Detection
---------------------------------------------------------------------
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply