July 21, 2012 at 1:50 am
Hi....guys...
Getting this error in error log of SQL Server 2000:
2012-07-21 02:08:21.54 spid4 Starting up database 'master'.
2012-07-21 02:08:21.87 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2012-07-21 02:08:21.87 spid5 Starting up database 'model'.
2012-07-21 02:08:21.90 server SQL server listening on Shared Memory.
2012-07-21 02:08:21.90 server SQL Server is ready for client connections
2012-07-21 02:08:21.91 spid4 Server name is 'SERVER\SHAREPOINT'.
2012-07-21 02:08:21.91 spid4 Skipping startup of clean database id 4
2012-07-21 02:08:21.91 spid4 Skipping startup of clean database id 5
2012-07-21 02:08:21.91 spid4 Skipping startup of clean database id 6
2012-07-21 02:08:22.21 spid5 Clearing tempdb database.
2012-07-21 02:08:22.52 spid5 Starting up database 'tempdb'.
2012-07-21 02:08:22.66 spid4 Recovery complete.
2012-07-21 02:08:27.12 spid4 SQL global counter collection task is created.
2012-07-21 03:39:18.32 spid51 Starting up database 'msdb'.
2012-07-21 03:39:18.43 spid51 Error: 823, Severity: 24, State: 2
2012-07-21 03:39:18.43 spid51 I/O error (torn page) detected during read at offset 0x00000000012000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data\MSDBData.mdf'..
Also this error when working thru management studio:
ADDITIONAL INFORMATION:
Cannot show requested dialog. (Microsoft.SqlServer.Express.SqlMgmt)
------------------------------
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)
------------------------------
Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (Microsoft SQL Server, Error: 945)
Reply......thnx
July 21, 2012 at 4:41 am
Restore MSDB from backup.
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
July 21, 2012 at 4:45 am
This definitely looks like database corruption (from the 823 message)
if nothing else works I would suggest that you
1)start up SQL Server from command line in minimum configuration mode (sqlservr -f )
2) and then restore the msdb database from a backup.
it is a system database so you may not have to worry too much unless you have stored DTS packages in MSDB which are being changed or added frequently
.
I would also like to suggest that you wait for additional opinions on this thread from more knowledgeable and experts folks, maybe there is a another and a better way out.
July 21, 2012 at 4:51 am
ok as Gail mentioned you just need to restore MSDB from backup.you can definitely go by that option.
I got it wrong, there is no need to start the server in minimum configuration mode.
July 21, 2012 at 6:02 am
and one additional thing, is the sqlserveragent service running? you may to stop the sqlserveragent service before you restore msdb database, this may only be applicable are refreshing a good MSDB database.
The database in this is suspect so it is unlikely that sqlsereveragent (if it is running) will cause any issues.
July 21, 2012 at 6:33 am
vikrantspatil (7/21/2012)
1)start up SQL Server from command line in minimum configuration mode (sqlservr -f )2) and then restore the msdb database from a backup.
That's not necessary. A suspect MSDB does not stop SQL from starting and a restore of MSDB is just like a user database (just have to make sure SQLAgent is not running)
http://msdn.microsoft.com/en-us/library/ms190749%28v=sql.105%29.aspx
it is a system database so you may not have to worry too much unless you have stored DTS packages in MSDB which are being changed or added frequently
Or jobs, job history, backup history, agent alerts, 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
July 21, 2012 at 7:35 am
got it, Thanks Gail, I stand corrected.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply