Mu MSDB database is in suspect mode. Anyone have any info to help get it out. It tells me that it cannot find the path specified for the backups, yet the path exists and there is more than enough disk space even though it says that there is not? I am confused. First time getting this error and doesn't make sense why.
Thanks!
Hi,
I have mssql 2005 installed and i see that MSDB database is marked as suspect. I almost tried all the steps which are submitted in the forums.
1) I shut down the server, navigating to the directory 'd:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn' and doing the following: start sqlservr.exe -c -T3608
2) renamed the damaged msdb files (msdbdata.mdf and msdblog.ldf in the 'd:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData' directory)
3) Run the instmsdb.sql script in the 'd:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall' directory
--x---
When I executed third step it returned me below error:
Msg 926, Level 14, State 1, Line 63
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
Please advice me.
Dear Experts,
I'm using sql server 2005, and now i'm trying to restore with one backup. then i'm getting error saying that MSDB database in suspect mode.
how to make the DB to the normal mode....
please help me in this regard
Vinod
Even you learn 1%, Learn it with 100% confidence.
how to put sql server database in suspect mode intensely and  get it out from suspect mode to normal mode.
  i am using SQL server 2008 R2
I'm running Win2000/SQL2000 on a Compaq CL380 Cluster Server. After a powerdown to do a physical move, the MSDB is now marked SUSPECT. I have tried the stored procedure SP_RESETSTATUS, a DBCC consistency check, and also have restored the database from backup. The database still shows MSDB is suspect. What can I do? We can't get a good backup as long as it is still this way as it depends on the SQL Agent.
View 1 Replies View RelatedHi all,
I have a big problem with a Database on SQL-Server7.0 running on windows 2000 advanced server. The msdb database is marked suspect. I have tried a few suggestions in the SQL BOL but no luck.
Can anyone help please!
We have a new installation on Friday which was running fine. Unfortunately today, the msdb is marked suspect. Do I uninstall and reload SQL server or change the status. We only have a training data on the server presently. Does anybody has any other suggestions? Please help. Thanks for your assistance.
View 4 Replies View RelatedI've got trouble -- somehow my msdb is corrupt and is marked as "suspect". I cannot open it up or it is apparently devoid of any table, etc.
It's on my SQLExpress instance and I'm willing to blow the entire server away -- since this server has been used as a sandbox for personal use.
Can I simply re-install SQLExpress?
Dear Experts,
in one of our servers, the MSDB database is in suspect mode, and i've used the command sp_resetstatus
and i restarted the service also but still it is in suspect mode.
how can i change that to normal state?
it is asking to check the errorlog.
Vinod
Even you learn 1%, Learn it with 100% confidence.
My msdb database is marked as suspect. This means that my maintenance plandoesn't work. I'm a novice when it comes to sql server so now I'm wonderingif anyone could give a hint on how to fix the suspect msdb database? Doesthis database contain any vital information? What could be the reason thatthis database become suspect?Appreciate any suggestions in this matter.Thanks!--mvhHallgeir
View 2 Replies View RelatedA client improperly shutdown a PC running MSDE and it corrupted the MSDB database which contained several DTS packages. I have tried fixing the problem on my own but have exhausted all the simple options like restarting SQL Server.
I googled the problem and found the following SQL script:
USE MasterGO-- Determine the original database statusSELECT [Name], DBID, StatusFROM master.dbo.sysdatabasesGO-- Enable system changessp_configure 'allow updates',1GORECONFIGURE WITH OVERRIDEGO-- Update the database statusUPDATE master.dbo.sysdatabasesSET Status = 24WHERE [Name] = 'msdb'GO-- Disable system changessp_configure 'allow updates',0GORECONFIGURE WITH OVERRIDEGO-- Determine the final database statusSELECT [Name], DBID, StatusFROM master.dbo.sysdatabasesGO
I ran it and and it generated the log file below. I restarted MS SQL but the database was still marked as suspect (as I would expect from the log file).
Any help in interpreting and recovering from this problem would be greatly appreciated.
Thank,
MickeyBob
Log file:
2007-07-09 15:47:39.39 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)2007-07-09 15:47:39.39 server Copyright (C) 1988-2002 Microsoft Corporation.2007-07-09 15:47:39.39 server All rights reserved.2007-07-09 15:47:39.39 server Server Process ID is 2324.2007-07-09 15:47:39.39 server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQLLOGERRORLOG'.2007-07-09 15:47:39.40 server SQL Server is starting at priority class 'normal'(2 CPUs detected).2007-07-09 15:47:39.84 server SQL Server configured for thread mode processing.2007-07-09 15:47:39.84 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.2007-07-09 15:47:39.89 spid3 Starting up database 'master'.2007-07-09 15:47:40.01 server Using 'SSNETLIB.DLL' version '8.0.766'.2007-07-09 15:47:40.01 spid5 Starting up database 'model'.2007-07-09 15:47:40.01 server SQL server listening on Shared Memory.2007-07-09 15:47:40.01 server SQL Server is ready for client connections2007-07-09 15:47:40.04 spid3 Server name is 'BALEHANDLING'.2007-07-09 15:47:40.04 spid3 Skipping startup of clean database id 52007-07-09 15:47:40.04 spid3 Skipping startup of clean database id 62007-07-09 15:47:40.04 spid3 Starting up database 'msdb'.2007-07-09 15:47:40.23 spid5 Clearing tempdb database.2007-07-09 15:47:41.18 spid5 Starting up database 'tempdb'.2007-07-09 15:47:55.56 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.2007-07-09 15:48:01.60 spid3 Analysis of database 'msdb' (4) is 100% complete (approximately 0 more seconds)2007-07-09 15:48:01.62 spid3 Recovery of database 'msdb' (4) is 0% complete (approximately 9 more seconds) (Phase 2 of 3).2007-07-09 15:48:43.95 spid3 Recovery of database 'msdb' (4) is 40% complete (approximately 5 more seconds) (Phase 2 of 3).2007-07-09 15:48:43.96 spid3 7678 transactions rolled forward in database 'msdb' (4).2007-07-09 15:48:43.96 spid3 Recovery of database 'msdb' (4) is 40% complete (approximately 5 more seconds) (Phase 3 of 3).2007-07-09 15:48:44.01 spid3 Using 'dbghelp.dll' version '4.0.5'*Dump thread - spid = 3, PSS = 0x42c2c098, EC = 0x42c2c3c0*Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQLlogSQLDump0030.txt* ********************************************************************************* BEGIN STACK DUMP:* 07/09/07 15:48:44 spid 3** ** ** MODULE BASE END SIZE* sqlservr 00400000 00B2CFFF 0072d000* ntdll 7C900000 7C9AFFFF 000b0000* kernel32 7C800000 7C8F3FFF 000f4000* ADVAPI32 77DD0000 77E6AFFF 0009b000* RPCRT4 77E70000 77F00FFF 00091000* USER32 77D40000 77DCFFFF 00090000* GDI32 77F10000 77F56FFF 00047000* OPENDS60 41060000 41065FFF 00006000* MSVCRT 77C10000 77C67FFF 00058000* UMS 41070000 4107CFFF 0000d000* SQLSORT 42AE0000 42B6FFFF 00090000* MSVCIRT 002A0000 002B0FFF 00011000* sqlevn70 41080000 41086FFF 00007000* NETAPI32 024F0000 02543FFF 00054000* SSNETLIB 00DC0000 00DD4FFF 00015000* WSOCK32 00DF0000 00DF8FFF 00009000* WS2_32 00E00000 00E16FFF 00017000* WS2HELP 00E20000 00E27FFF 00008000* SSNMPN70 02CD0000 02CD5FFF 00006000* security 02FD0000 02FD3FFF 00004000* SECUR32 02FE0000 02FF0FFF 00011000* VERSION 030C0000 030C7FFF 00008000* SSmsLPCn 03000000 03006FFF 00007000* ntdsapi 030A0000 030B2FFF 00013000* DNSAPI 030D0000 030F6FFF 00027000* WLDAP32 03100000 0312BFFF 0002c000* msv1_0 03330000 03352FFF 00023000* iphlpapi 03360000 03378FFF 00019000* OLE32 03390000 034CBFFF 0013c000* xpsp2res 034D0000 03794FFF 002c5000* CLBCATQ 037A0000 0381EFFF 0007f000* OLEAUT32 03820000 038ABFFF 0008c000* COMRes 038B0000 03974FFF 000c5000* sqloledb 03990000 03A10FFF 00081000* MSDART 03A20000 03A44FFF 00025000* COMCTL32 03A50000 03AE9FFF 0009a000* comdlg32 03AF0000 03B38FFF 00049000* SHLWAPI 03B40000 03BB5FFF 00076000* SHELL32 03BC0000 043D4FFF 00815000* MSDATL3 043E0000 043F6FFF 00017000* comctl32 044C0000 045C2FFF 00103000* oledb32 04810000 04886FFF 00077000* OLEDB32R 04480000 04490FFF 00011000* xpstar 04890000 048D6FFF 00047000* SQLRESLD 04420000 04426FFF 00007000* SQLSVC 048E0000 048F6FFF 00017000* ODBC32 04900000 0493CFFF 0003d000* odbcbcp 044A0000 044A5FFF 00006000* W95SCM 04940000 0494BFFF 0000c000* SQLUNIRL 04950000 0497CFFF 0002d000* WINSPOOL 04980000 049A5FFF 00026000* SHFOLDER 049B0000 049B8FFF 00009000* odbcint 04B00000 04B16FFF 00017000* clusapi 04B20000 04B30FFF 00011000* resutils 04B40000 04B51FFF 00012000* USERENV 04B60000 04C12FFF 000b3000* NDDEAPI 04C30000 04C37FFF 00008000* SQLSVC 04C40000 04C45FFF 00006000* xpstar 04C50000 04C58FFF 00009000* dbghelp 04CA0000 04D54FFF 000b5000** Edi: 42C2C3C0: 42C2C098 42C2CB30 42C2CB30 42C2CD20 42C2CD20 42C2C030 * Esi: 00000000: * Eax: 00000000: * Ebx: 42C2C098: 01000003 00000000 00000000 00000000 00000000 00000000 * Ecx: 0294B43C: 00000000 0001003F 00000000 00000000 00000000 00000000 * Edx: 7C90EB94: 24A48DC3 00000000 0024648D 90909090 24548D90 C32ECD08 * Eip: 0087A90E: 4D830088 75FFFFFC 0875FF0C E8E04D8B 0000002D 64F04D8B * Ebp: 0294B420: 0294BC40 0087C41F 42C2C098 0294BDA4 0294C016 77C3F931 * SegCs: 0000001B: * EFlags: 00010246: 006C0069 00730065 0053005C 00650069 0065006D 0073006E * Esp: 0294B3F4: 42C2C3C0 00000000 42C2C098 0294B43C 42C2C000 0294B3F4 * SegSs: 00000023: * ******************************************************************************** -------------------------------------------------------------------------------* Short Stack Dump* 0087A90E Module(sqlservr+0047A90E) (GetOSErrString+00003BDB)* 0087C41F Module(sqlservr+0047C41F) (GetOSErrString+000056EC)* 00931097 Module(sqlservr+00531097) (CDStream:umpBytesHex+000A9840)* 007FC8A6 Module(sqlservr+003FC8A6) (CDStream:perator=+00005B0E)* 00403B44 Module(sqlservr+00003B44)* 004416A7 Module(sqlservr+000416A7)* 0040F1E5 Module(sqlservr+0000F1E5)* 0040FF2B Module(sqlservr+0000FF2B)* 0040FE45 Module(sqlservr+0000FE45)* 00436DD6 Module(sqlservr+00036DD6)* 0043683C Module(sqlservr+0003683C)* 0040FD6F Module(sqlservr+0000FD6F)* 0040FB39 Module(sqlservr+0000FB39)* 008607CA Module(sqlservr+004607CA) (CDStream:perator=+00069A32)* 0086C203 Module(sqlservr+0046C203) (CDStream:perator=+0007546B)* 004401D7 Module(sqlservr+000401D7)* 0085EA07 Module(sqlservr+0045EA07) (CDStream:perator=+00067C6F)* 0050C003 Module(sqlservr+0010C003)* 005100FF Module(sqlservr+001100FF)* 0050F152 Module(sqlservr+0010F152)* 00519C2D Module(sqlservr+00119C2D)* 00829863 Module(sqlservr+00429863) (CDStream:perator=+00032ACB)* 005196A1 Module(sqlservr+001196A1)* 00518066 Module(sqlservr+00118066)* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)* 542868FF Module(UNKNOWN+00000000)* -------------------------------------------------------------------------------2007-07-09 15:48:44.06 spid3 SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed Assertion = 'm_offBeginVar < m_SizeRec'.2007-07-09 15:48:44.06 spid3 Location: recbase.cpp:1378Expression: m_offBeginVar < m_SizeRecSPID: 3Process ID: 23242007-07-09 15:48:44.06 spid3 Error: 3624, Severity: 20, State: 1.2007-07-09 15:48:44.06 spid3 Error: 3314, Severity: 21, State: 32007-07-09 15:48:44.06 spid3 Error while undoing logged operation in database 'msdb'. Error at log record ID (97997:269:86)..2007-07-09 15:48:44.09 spid3 Using 'dbghelp.dll' version '4.0.5'*Dump thread - spid = 3, PSS = 0x42c2c098, EC = 0x42c2c3c0*Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQLlogSQLDump0031.txt* ********************************************************************************* BEGIN STACK DUMP:* 07/09/07 15:48:44 spid 3** ** ** MODULE BASE END SIZE* sqlservr 00400000 00B2CFFF 0072d000* ntdll 7C900000 7C9AFFFF 000b0000* kernel32 7C800000 7C8F3FFF 000f4000* ADVAPI32 77DD0000 77E6AFFF 0009b000* RPCRT4 77E70000 77F00FFF 00091000* USER32 77D40000 77DCFFFF 00090000* GDI32 77F10000 77F56FFF 00047000* OPENDS60 41060000 41065FFF 00006000* MSVCRT 77C10000 77C67FFF 00058000* UMS 41070000 4107CFFF 0000d000* SQLSORT 42AE0000 42B6FFFF 00090000* MSVCIRT 002A0000 002B0FFF 00011000* sqlevn70 41080000 41086FFF 00007000* NETAPI32 024F0000 02543FFF 00054000* SSNETLIB 00DC0000 00DD4FFF 00015000* WSOCK32 00DF0000 00DF8FFF 00009000* WS2_32 00E00000 00E16FFF 00017000* WS2HELP 00E20000 00E27FFF 00008000* SSNMPN70 02CD0000 02CD5FFF 00006000* security 02FD0000 02FD3FFF 00004000* SECUR32 02FE0000 02FF0FFF 00011000* VERSION 030C0000 030C7FFF 00008000* SSmsLPCn 03000000 03006FFF 00007000* ntdsapi 030A0000 030B2FFF 00013000* DNSAPI 030D0000 030F6FFF 00027000* WLDAP32 03100000 0312BFFF 0002c000* msv1_0 03330000 03352FFF 00023000* iphlpapi 03360000 03378FFF 00019000* OLE32 03390000 034CBFFF 0013c000* xpsp2res 034D0000 03794FFF 002c5000* CLBCATQ 037A0000 0381EFFF 0007f000* OLEAUT32 03820000 038ABFFF 0008c000* COMRes 038B0000 03974FFF 000c5000* sqloledb 03990000 03A10FFF 00081000* MSDART 03A20000 03A44FFF 00025000* COMCTL32 03A50000 03AE9FFF 0009a000* comdlg32 03AF0000 03B38FFF 00049000* SHLWAPI 03B40000 03BB5FFF 00076000* SHELL32 03BC0000 043D4FFF 00815000* MSDATL3 043E0000 043F6FFF 00017000* comctl32 044C0000 045C2FFF 00103000* oledb32 04810000 04886FFF 00077000* OLEDB32R 04480000 04490FFF 00011000* xpstar 04890000 048D6FFF 00047000* SQLRESLD 04420000 04426FFF 00007000* SQLSVC 048E0000 048F6FFF 00017000* ODBC32 04900000 0493CFFF 0003d000* odbcbcp 044A0000 044A5FFF 00006000* W95SCM 04940000 0494BFFF 0000c000* SQLUNIRL 04950000 0497CFFF 0002d000* WINSPOOL 04980000 049A5FFF 00026000* SHFOLDER 049B0000 049B8FFF 00009000* odbcint 04B00000 04B16FFF 00017000* clusapi 04B20000 04B30FFF 00011000* resutils 04B40000 04B51FFF 00012000* USERENV 04B60000 04C12FFF 000b3000* NDDEAPI 04C30000 04C37FFF 00008000* SQLSVC 04C40000 04C45FFF 00006000* xpstar 04C50000 04C58FFF 00009000* dbghelp 04CA0000 04D54FFF 000b5000** Edi: 42C2C3C0: 42C2C098 42C2C3C4 42C2C3C4 42C2CD20 42C2CB30 42C2C030 * Esi: 00000000: * Eax: 00000000: * Ebx: 42C2C098: 01000003 00000000 00000000 00000000 00000000 00000000 * Ecx: 02946B44: 00000000 0001003F 00000000 00000000 00000000 00000000 * Edx: 7C90EB94: 24A48DC3 00000000 0024648D 90909090 24548D90 C32ECD08 * Eip: 0087A90E: 4D830088 75FFFFFC 0875FF0C E8E04D8B 0000002D 64F04D8B * Ebp: 02946B28: 02947348 0087C41F 42C2C098 029474AC 02947735 77C3F931 * SegCs: 0000001B: * EFlags: 00010246: 006C0069 00730065 0053005C 00650069 0065006D 0073006E * Esp: 02946AFC: 42C2C3C0 00000000 42C2C098 02946B44 42C2C000 02946AFC * SegSs: 00000023: * ******************************************************************************** -------------------------------------------------------------------------------* Short Stack Dump* 0087A90E Module(sqlservr+0047A90E) (GetOSErrString+00003BDB)* 0087C41F Module(sqlservr+0047C41F) (GetOSErrString+000056EC)* 00931097 Module(sqlservr+00531097) (CDStream:umpBytesHex+000A9840)* 0085C09D Module(sqlservr+0045C09D) (CDStream:perator=+00065305)* 0050A016 Module(sqlservr+0010A016)* 008D048F Module(sqlservr+004D048F) (CDStream:umpBytesHex+00048C38)* 0085D84B Module(sqlservr+0045D84B) (CDStream:perator=+00066AB3)* 005100FF Module(sqlservr+001100FF)* 0050F152 Module(sqlservr+0010F152)* 00519C2D Module(sqlservr+00119C2D)* 00829863 Module(sqlservr+00429863) (CDStream:perator=+00032ACB)* 005196A1 Module(sqlservr+001196A1)* 00518066 Module(sqlservr+00118066)* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)* 542868FF Module(UNKNOWN+00000000)* -------------------------------------------------------------------------------2007-07-09 15:48:44.14 spid3 SQL Server Assertion: File: <logscan.cpp>, line=3063 Failed Assertion = '(m_lastLSN == NullLSN) || (m_lastLSN > m_curLSN)'.2007-07-09 15:48:44.14 spid3 Location: logscan.cpp:3063Expression: (m_lastLSN == NullLSN) || (m_lastLSN > m_curLSN)SPID: 3Process ID: 23242007-07-09 15:48:44.14 spid3 Using 'dbghelp.dll' version '4.0.5'*Dump thread - spid = 3, PSS = 0x42c2c098, EC = 0x42c2c3c0*Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQLlogSQLDump0032.txt* ********************************************************************************* BEGIN STACK DUMP:* 07/09/07 15:48:44 spid 3** ** ** MODULE BASE END SIZE* sqlservr 00400000 00B2CFFF 0072d000* ntdll 7C900000 7C9AFFFF 000b0000* kernel32 7C800000 7C8F3FFF 000f4000* ADVAPI32 77DD0000 77E6AFFF 0009b000* RPCRT4 77E70000 77F00FFF 00091000* USER32 77D40000 77DCFFFF 00090000* GDI32 77F10000 77F56FFF 00047000* OPENDS60 41060000 41065FFF 00006000* MSVCRT 77C10000 77C67FFF 00058000* UMS 41070000 4107CFFF 0000d000* SQLSORT 42AE0000 42B6FFFF 00090000* MSVCIRT 002A0000 002B0FFF 00011000* sqlevn70 41080000 41086FFF 00007000* NETAPI32 024F0000 02543FFF 00054000* SSNETLIB 00DC0000 00DD4FFF 00015000* WSOCK32 00DF0000 00DF8FFF 00009000* WS2_32 00E00000 00E16FFF 00017000* WS2HELP 00E20000 00E27FFF 00008000* SSNMPN70 02CD0000 02CD5FFF 00006000* security 02FD0000 02FD3FFF 00004000* SECUR32 02FE0000 02FF0FFF 00011000* VERSION 030C0000 030C7FFF 00008000* SSmsLPCn 03000000 03006FFF 00007000* ntdsapi 030A0000 030B2FFF 00013000* DNSAPI 030D0000 030F6FFF 00027000* WLDAP32 03100000 0312BFFF 0002c000* msv1_0 03330000 03352FFF 00023000* iphlpapi 03360000 03378FFF 00019000* OLE32 03390000 034CBFFF 0013c000* xpsp2res 034D0000 03794FFF 002c5000* CLBCATQ 037A0000 0381EFFF 0007f000* OLEAUT32 03820000 038ABFFF 0008c000* COMRes 038B0000 03974FFF 000c5000* sqloledb 03990000 03A10FFF 00081000* MSDART 03A20000 03A44FFF 00025000* COMCTL32 03A50000 03AE9FFF 0009a000* comdlg32 03AF0000 03B38FFF 00049000* SHLWAPI 03B40000 03BB5FFF 00076000* SHELL32 03BC0000 043D4FFF 00815000* MSDATL3 043E0000 043F6FFF 00017000* comctl32 044C0000 045C2FFF 00103000* oledb32 04810000 04886FFF 00077000* OLEDB32R 04480000 04490FFF 00011000* xpstar 04890000 048D6FFF 00047000* SQLRESLD 04420000 04426FFF 00007000* SQLSVC 048E0000 048F6FFF 00017000* ODBC32 04900000 0493CFFF 0003d000* odbcbcp 044A0000 044A5FFF 00006000* W95SCM 04940000 0494BFFF 0000c000* SQLUNIRL 04950000 0497CFFF 0002d000* WINSPOOL 04980000 049A5FFF 00026000* SHFOLDER 049B0000 049B8FFF 00009000* odbcint 04B00000 04B16FFF 00017000* clusapi 04B20000 04B30FFF 00011000* resutils 04B40000 04B51FFF 00012000* USERENV 04B60000 04C12FFF 000b3000* NDDEAPI 04C30000 04C37FFF 00008000* SQLSVC 04C40000 04C45FFF 00006000* xpstar 04C50000 04C58FFF 00009000* dbghelp 04CA0000 04D54FFF 000b5000** Edi: 42C2C3C0: 42C2C098 42C2C3C4 42C2C3C4 42C2CD20 42C2CB30 42C2C030 * Esi: 00000000: * Eax: 00000000: * Ebx: 42C2C098: 01000003 00000000 00000000 00000000 00000000 00000000 * Ecx: 029468EC: 00000000 0001003F 00000000 00000000 00000000 00000000 * Edx: 7C90EB94: 24A48DC3 00000000 0024648D 90909090 24548D90 C32ECD08 * Eip: 0087A90E: 4D830088 75FFFFFC 0875FF0C E8E04D8B 0000002D 64F04D8B * Ebp: 029468D0: 029470F0 0087C41F 42C2C098 02947254 029474D9 77C3F931 * SegCs: 0000001B: * EFlags: 00010246: 006C0069 00730065 0053005C 00650069 0065006D 0073006E * Esp: 029468A4: 42C2C3C0 00000000 42C2C098 029468EC 42C2C000 029468A4 * SegSs: 00000023: * ******************************************************************************** -------------------------------------------------------------------------------* Short Stack Dump* 0087A90E Module(sqlservr+0047A90E) (GetOSErrString+00003BDB)* 0087C41F Module(sqlservr+0047C41F) (GetOSErrString+000056EC)* 00931097 Module(sqlservr+00531097) (CDStream:umpBytesHex+000A9840)* 0085C2C1 Module(sqlservr+0045C2C1) (CDStream:perator=+00065529)* 0050A17A Module(sqlservr+0010A17A)* 0050A0BF Module(sqlservr+0010A0BF)* 0050A016 Module(sqlservr+0010A016)* 008D048F Module(sqlservr+004D048F) (CDStream:umpBytesHex+00048C38)* 0085D84B Module(sqlservr+0045D84B) (CDStream:perator=+00066AB3)* 005100FF Module(sqlservr+001100FF)* 0050F152 Module(sqlservr+0010F152)* 00519C2D Module(sqlservr+00119C2D)* 00829863 Module(sqlservr+00429863) (CDStream:perator=+00032ACB)* 005196A1 Module(sqlservr+001196A1)* 00518066 Module(sqlservr+00118066)* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)* 542868FF Module(UNKNOWN+00000000)* -------------------------------------------------------------------------------2007-07-09 15:48:44.17 spid3 SQL Server Assertion: File: <logscan.cpp>, line=3282 Failed Assertion = 'm_lastLSN == NullLSN || startLSN < m_lastLSN'.2007-07-09 15:48:44.17 spid3 Location: logscan.cpp:3282Expression: m_lastLSN == NullLSN || startLSN < m_lastLSNSPID: 3Process ID: 23242007-07-09 15:48:44.20 spid3 Error: 9004, Severity: 23, State: 72007-07-09 15:48:44.20 spid3 An error occurred while processing the log for database 'msdb'..2007-07-09 15:48:44.20 spid3 Error: 3414, Severity: 21, State: 12007-07-09 15:48:44.20 spid3 Database 'msdb' (database ID 4) could not recover. Contact Technical Support..2007-07-09 15:48:44.20 spid3 Recovery complete.2007-07-09 15:48:44.20 spid3 SQL global counter collection task is created.2007-07-09 15:49:21.09 spid51 Starting up database 'Baling'.2007-07-09 15:49:21.18 spid51 Starting up database 'WWAlmDb'.2007-07-09 15:49:21.29 spid51 Starting up database 'Baling'.2007-07-09 15:49:21.39 spid51 Starting up database 'WWAlmDb'.2007-07-09 15:51:11.90 spid53 Starting up database 'Baling'.2007-07-09 15:51:11.96 spid53 Starting up database 'WWAlmDb'.2007-07-09 15:51:33.82 spid52 Error: 15457, Severity: 0, State: 12007-07-09 15:51:33.82 spid52 Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..2007-07-09 15:51:33.89 spid52 Error: 15457, Severity: 0, State: 12007-07-09 15:51:33.89 spid52 Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
We found an interesting 'issue' in one of our productive user database:
The output of msdb..suspect_pages table:
db_idfile_idpage_idevent_typeerror_countlast_update
16 2 22 32015.06.12 10:40
16 2 3 3 3 2015.06.12 10:40
16 2 6 3 3 2015.06.12 10:40
16 2 7 3 3 2015.06.12 10:40
16 2 1 3 3 2015.06.12 10:40
The problem is, that this user database only has one data file and file_id 2 is the log file.I understand that the event_type shows checksum and torn page error but in the log file? DBCC CHECKDB shows no errors and the database is part of an AOAG in synchronized state.We have log backups in every 15 minutes.
can anyone tell me what would casuse this error:
2001-09-12 21:21:01.11 kernel udopen: Operating system error 32(The process cannot access the file because it is being used by another process.) during the creation/opening of physical device C:MSSQL7dataReporting.mdf.
2001-09-12 21:21:01.11 kernel FCB::Open failed: Could not open device C:MSSQL7dataReporting.mdf for virtual device number (VDN) 1.
What other things would cause the Reporting.mdf to be locked so the SQL server could not open it?
I have a database in suspect mode. There is no backup of this database.
I've followed the troubleshooting and it isn't working out.
There are 3 steps:
1. execute sp_resetstatus
2. use alter database to add data file or log file to the database
3. stop and restart SQL Server
4. free disk space and rerun recovery
I've tried to make it, but the step # 2 haven't worked.
Then I tried step 3, however the database is still in suspect mode.
What should I do?
Is there something I am missing?
Thanks,
Fábio
Hi
my database went into suspect mode. i tried to reset the status database by "sp_resetstatus abc". It is giving the message
"Prior to updating sysdatabases entry for database 'cr2db', mode = 0 and status = 260 (status suspect_bit = 256).
For row in sysdatabases for database 'cr2db', the status bit 256 was forced off and mode was forced to 0.
Warning: You must recover this database prior to access."
please let me if you have any solution to this problem.
thank you in advance
ricky
Hi,
Could anyone please tell me steps to recover the database from the suspect
mode. The backup I got is very old. Can it be recovered without the backup.
Thanks in advance
John Jayaseelan
Hi,
When i tried to restore database from the Network m/c ...upto 60% of the restoration process went well,But after that i got message saying that
" Communication link failure " then database went in to LOAD/SUSPECT mode,
This happend in Active/Active Cluster environment and at the same point of time Fail over occured and resources moved to other node.
i tried by running SP_RESETSTATUS stored procedure to change the status of the Database ,But no use...
Then i deleted the Database and recreated and restored.. because it was a test server...BUT if it happens in Production what to do?????.....
Is there anyway to over come such situations...
Thanks in advance
Mar R
Database is in suspect mode and I cant get it out. Customer does not have a backup.........
getting Errors starting
Analysis of database 'SBM01' (7) is 100% complete (approximately 0 more seconds)
ex_raise2: Exception raised, major=79, minor=87, severity=22, attempting to create symptom dump
Error: 7987, Severity: 22, State: 1
A possible database consistency problem has been detected on database 'SBM01'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database 'SBM01'.
ex_raise2: Exception raised, major=79, minor=87, severity=25, attempting to create symptom dump
Using 'dbghelp.dll' version '4.0.5'
*Dump thread - spid = 51, PSS = 0x19b591e0, EC = 0x19b59510
*
* User initiated stack dump. This is not a server exception dump.
Error: 3314, Severity: 21, State: 3
Error while undoing logged operation in database 'SBM01'. Error at log record ID (222:9976:477)..
Error: 9004, Severity: 23, State: 2
An error occurred while processing the log for database 'SBM01'..
Error: 3414, Severity: 21, State: 1
Database 'SBM01' (database ID 7) could not recover. Contact Technical Support..
In SQL 2005 when a database is in suspect mode there is no obvious way to tell (via SSMS). In SQL 2000 the word "suspect" was displayed (via Enterprise Manager) next to the database, and the respective database icon was grayed out. Why was this behavior changed for SQL 2005? From a disaster recovery standpoint, it is very important to see immediately if a database is in suspect mode.
View 9 Replies View RelatedIn the work I came up against a situation when the working database at the end of day went to the Suspect Mode.And the archive was in many hours before. To transfer it in normal mode, until isn't made repaired base it was impossible. DBCC checkdb also refused to run because the database is in this mode.
View 7 Replies View RelatedRajiv Parekh writes "Since last few weeks on Startup of System few Databases moves to SUSPECT MODE.
This probelm is not daily but atleast 0nce in week.The day is is not fixed. Have Unistalled SQL & again Reinstalled, but the problem continues.
Please inform my Why this problem & what is the Solution."
hi all,
one of my sql database went in suspect mode can any one advice why it has happened is it the problem with sql server . This has happend for the second time in 4 months .
thanks and regards
jk
As I know the database should be restored from backup and logs reapplied. That’s the first and generally recommended approach any time a DB is suspect, whether it’s from log or data file corruption.But if I have no backups then we follow below steps ( after Googling I found these steps on most of the websites ):
1.EXEC sp_resetstatus ‘yourDBname’;
2.ALTER DATABASE yourDBname SET EMERGENCY
3.DBCC checkdb(’yourDBname’)
4.ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE
5.DBCC CheckDB (’yourDBname’, REPAIR_ALLOW_DATA_LOSS)
6.ALTER DATABASE yourDBname SET MULTI_USER
Now my question is,Â
1. If after executing DBCC CHECKDB at 3rd step, it shows inconsistency.Then I will execute SET SINGLE USER WITH ROLLBACK & if after executing DBCC CHECKDB at 3rd step, no errors found. Then what will be the steps?
2. When we execute DBCC CHECKDB (' DBNAME ', REPAIR_ALLOW_DATA_LOSS) how can we recover lost data during process.As far as I know some data will loss and if it will happen then business will get suffered.
3. Why run DBCC CHECKDB() WITH REPAIR_ALLOW_DATA_LOSS if there are no consistency errors in the database?
I Want to test for Automatic switch between primary and secondary.
How do i do it ?
or
I need this for some purpose : How to set suspect mode for a database ?
Hi,
One of my DB got into SUSPECT mode.
I tried "sp_resetstatus" procedure. But it says, the following mesg,
"
Prior to updating sysdatabases entry for database 'DELPHI3', mode = 0 and status = 1077936141 (status suspect_bit = 0).
No row in sysdatabases was updated because mode and status are already correctly reset. No error and no changes made.
".
Can anybody please help me how to make this into normal status.
tks in advance,
vasu
Hi,
One of my most used databases has been marked by the Server as SUSPECT. No, i was not trying to recover the Db. The story goes like this..
We are using MTS for a VB, SQL distributed application. One of the MTS transactions was blocking a lot of my other transactions. I tried to kill that transaction to avail nothing. I stopped the SQL Server and restarted it again ( as suggested in BOL, coz the transaction was open and was awaiting command, so server restart was the only way-BOL )
When the server came back up, and i tried to restore the db, it said that the database has been marked suspect. When i tried dbcc dbrecover, it said, could not recover because it could not connect to MSDTC to check the completion status of the transaction xxxx. sp_resetstaus did not help as well.
I do not have a usable backup of that db.
Help. This very urgent.
Deepak.
Hi,
All the databases on one of the server went to the suspect mode as somehow the login for database owner was dropped from the existing domain and moved to the other domain by mistake. When the server was restarted, there are permission denied (OS error 5 ) and device activation errors and databases are in suspect.
We added the dbowner account back to the original domain admin group and resterted the server, still we are seeing device activation errors on all the user databases.
Is there anyway to change th edbowner of te supect database? We ned to do this immediately. Any help will be appreciated.
Hi there,
I need urgent help regarding a database that has been
marked as suspect.
I need to get the data from the database!!
I have a copy of the structure of the database but I need to get cerain very recent data from the database.
I have tried bcp and it doesn't work.
The backup that I have won't sufice
If a database is marked as suspect, Will it recover?>
And if so how long will it take.
If it won't recover is there any other way of getting the data,
Thanks in advance,
Fin
After a weekend upgrade from 6.5 to 7.0 that failed during the import step on user tables because of bad data, we are now left with none of our scheduled tasks. I figured I would go back to the 6.5 msdb database, grab the list of tasks and recreate them in 7.0. Nice theory until I went to add them to msdb and got the error message 207: invalid column name "category_id," "netsend_address," "last_netsend_date, and "last_netsend_time."
Upon investigation, I noticed that we are missing those fields from our sysoperators table in msdb. I fear other tables or columns are missing too. Going back to 6.5 is not an option. Is there a way to get a good msdb or reupgrade only one database (msdb) without interferring with existing databases on that server? Our production database is humming along fine, but I'd like to have a good msdb to support it.
Thanks for any help you can provide.
Hi, I need to your urgent help please...
My Event log is full of I/O Bad Page Id error meaages on MSDB database.
Here is Output of CHECKDB
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:7845). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:7853). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:7854). The PageId in the page header = (0:0).
DBCC results for 'MSDB'.
CHECKDB found 0 allocation errors and 3 consistency errors not associated with any single object.
DBCC results for 'sysobjects'.
There are 533 rows in 9 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 307 rows in 16 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 3755 rows in 125 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 495 rows in 176 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 221 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 14 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 3097 rows in 18 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 33 rows in 1 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 18099105, index ID 0: Page (1:7845) could not be processed. See other errors for details.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'sysdbmaintplan_history.UQ__sysdbmaintplan_h__41EDCAC5' (ID 1090102924) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:7463:0) with values (sequence_id = 8296 and plan_id = 91AF9917-3C72-4FD2-BE43-98601416395E and ? = 24) points to the data row identified by ().
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediaset' (ID 2037582297). Missing or invalid key in index 'backupmediasetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7775:89) identified by (RID = (1:7775:89) media_set_id = 36388) has index values (media_uuid = 00000000-0000-0000-0000-000000000000 and media_set_id = NULL).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediaset' (ID 2037582297). Missing or invalid key in index 'backupmediasetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7775:90) identified by (RID = (1:7775:90) media_set_id = 36389) has index values (media_uuid = 00000000-0000-0000-0000-000000000000 and media_set_id = NULL).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediaset' (ID 2037582297). Missing or invalid key in index 'backupmediasetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7775:91) identified by (RID = (1:7775:91) media_set_id = 36390) has index values (media_uuid = 00000000-0000-0000-0000-000000000000 and media_set_id = NULL).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediaset' (ID 2037582297). Missing or invalid key in index 'backupmediasetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7775:92) identified by (RID = (1:7775:92) media_set_id = 36391) has index values (media_uuid = 00000000-0000-0000-0000-000000000000 and media_set_id = NULL).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediaset' (ID 2037582297). Missing or invalid key in index 'backupmediasetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7775:93) identified by (RID = (1:7775:93) media_set_id = 36392) has index values (media_uuid = 00000000-0000-0000-0000-000000000000 and media_set_id = NULL).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediaset' (ID 2037582297). Missing or invalid key in index 'backupmediasetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7775:94) identified by (RID = (1:7775:94) media_set_id = 36393) has index values (media_uuid = 00000000-0000-0000-0000-000000000000 and media_set_id = NULL).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediaset' (ID 2037582297). Missing or invalid key in index 'backupmediasetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7775:95) identified by (RID = (1:7775:95) media_set_id = 36394) has index values (media_uuid = 00000000-0000-0000-0000-000000000000 and media_set_id = NULL).
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediaset' (ID 2037582297). Missing or invalid key in index 'backupmediasetuuid' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:7775:96) identified by (RID = (1:7775:96) media_set_id = 36395) has index values (media_uuid = 00000000-0000-0000-0000-000000000000 and media_set_id = NULL).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:1768:128) with values (media_family_id = 3988F04C-0000-0000-0000-000000000000 and media_set_id = 36415 and family_sequence_number = 2.121996171E-314) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:1773:225) with values (media_family_id = 8936C309-0000-0000-0000-000000000000 and media_set_id = 36406 and family_sequence_number = 2.121996171E-314) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2080:143) with values (media_family_id = 3B7D0AD5-0000-0000-0000-000000000000 and media_set_id = 36419 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2081:47) with values (media_family_id = 61D32A3C-0000-0000-0000-000000000000 and media_set_id = 36417 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2081:234) with values (media_family_id = 6B23A43D-0000-0000-0000-000000000000 and media_set_id = 36402 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2082:148) with values (media_family_id = EBB5DD1C-0000-0000-0000-000000000000 and media_set_id = 36388 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2083:204) with values (media_family_id = 3C2E9566-0000-0000-0000-000000000000 and media_set_id = 36420 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2084:69) with values (media_family_id = 70907EEB-0000-0000-0000-000000000000 and media_set_id = 36401 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2085:1) with values (media_family_id = 2555E654-0000-0000-0000-000000000000 and media_set_id = 36413 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2087:141) with values (media_family_id = 93BAD469-0000-0000-0000-000000000000 and media_set_id = 36390 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2679:137) with values (media_family_id = A0682005-0000-0000-0000-000000000000 and media_set_id = 36397 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2776:82) with values (media_family_id = 6F12D425-0000-0000-0000-000000000000 and media_set_id = 36400 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2780:50) with values (media_family_id = 2C18BBCC-0000-0000-0000-000000000000 and media_set_id = 36412 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2782:159) with values (media_family_id = 79EDB994-0000-0000-0000-000000000000 and media_set_id = 36416 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2888:89) with values (media_family_id = D448D2F8-0000-0000-0000-000000000000 and media_set_id = 36410 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2889:75) with values (media_family_id = 992EE014-0000-0000-0000-000000000000 and media_set_id = 36404 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2892:32) with values (media_family_id = C2B9073E-0000-0000-0000-000000000000 and media_set_id = 36405 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:2894:23) with values (media_family_id = 9B6D7F6A-0000-0000-0000-000000000000 and media_set_id = 36418 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3058:51) with values (media_family_id = 5726FBA4-0000-0000-0000-000000000000 and media_set_id = 36392 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3058:111) with values (media_family_id = 592F85A5-0000-0000-0000-000000000000 and media_set_id = 36422 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3637:228) with values (media_family_id = 288E49BA-0000-0000-0000-000000000000 and media_set_id = 36411 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3639:85) with values (media_family_id = B79996BD-0000-0000-0000-000000000000 and media_set_id = 36409 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3909:156) with values (media_family_id = 3AC0F52D-0000-0000-0000-000000000000 and media_set_id = 36421 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:4197:259) with values (media_family_id = ECD92D25-0000-0000-0000-000000000000 and media_set_id = 36393 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:5194:26) with values (media_family_id = 337B262B-0000-0000-0000-000000000000 and media_set_id = 36423 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:5194:153) with values (media_family_id = 798F202C-0000-0000-0000-000000000000 and media_set_id = 36396 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:5198:17) with values (media_family_id = FDA6B08F-0000-0000-0000-000000000000 and media_set_id = 36424 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:5547:46) with values (media_family_id = 263071E9-0000-0000-0000-000000000000 and media_set_id = 36408 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:5942:173) with values (media_family_id = 64B33C73-0000-0000-0000-000000000000 and media_set_id = 36414 and family_sequence_number = 3.799364817E-321) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:6207:50) with values (media_family_id = E86E9ED5-0000-0000-0000-000000000000 and media_set_id = 36398 and family_sequence_number = 3.799364817E-321) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:6667:71) with values (media_family_id = B066F284-0000-0000-0000-000000000000 and media_set_id = 36407 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:6671:80) with values (media_family_id = 015B0CB8-0000-0000-0000-000000000000 and media_set_id = 36389 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:7578:97) with values (media_family_id = 79657275-0000-0000-0000-000000000000 and media_set_id = 36394 and family_sequence_number = 5.092789936E-313) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:7579:142) with values (media_family_id = 61DFE89F-0000-0000-0000-000000000000 and media_set_id = 36391 and family_sequence_number = 5.092789936E-313) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'msdb', index 'backupmediafamily.backupmediafamilyuuid' (ID 2069582411) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:7738:43) with values (media_family_id = D9722AE3-0000-0000-0000-000000000000 and media_set_id = 36403 and family_sequence_number = 9.778156605E-311) points to the data row identified by ().
Server: Msg 8934, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. The high key value on page (1:1630) (level 0) is not less than the low key value in the parent (0:1), slot 0 of the next page (1:1815).
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. Page (1:1681) is missing a reference from previous page (1:1815). Possible chain linkage problem.
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. The previous link (1:2231) on page (1:1815) does not match the previous page (1:1630) that the parent (1:1490), slot 164 expects for this page.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. B-tree chain linkage mismatch. (1:1630)->next = (1:1815), but (1:1815)->Prev = (1:2231).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2117582582, index ID 0: Page (1:7853) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2117582582, index ID 0: Page (1:7854) could not be processed. See other errors for details.
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 2117582582, index ID 2. The previous link (1:6317) on page (1:1593) does not match the previous page (1:4450) that the parent (1:82), slot 105 expects for this page.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2117582582, index ID 2. Parent node for page (1:6317) was not encountered.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'sysjobschedules'.
There are 19 rows in 1 pages for object 'sysjobschedules'.
DBCC results for 'RTblIfaceMem'.
There are 1189 rows in 9 pages for object 'RTblIfaceMem'.
DBCC results for 'backupfile'.
There are 37551 rows in 1008 pages for object 'backupfile'.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupfile' (object ID 18099105).
DBCC results for 'syscategories'.
There are 19 rows in 1 pages for object 'syscategories'.
DBCC results for 'systargetservers'.
There are 0 rows in 0 pages for object 'systargetservers'.
DBCC results for 'RTblWorkspaceItems'.
There are 0 rows in 0 pages for object 'RTblWorkspaceItems'.
DBCC results for 'restorehistory'.
There are 28 rows in 1 pages for object 'restorehistory'.
DBCC results for 'systargetservergroups'.
There are 0 rows in 0 pages for object 'systargetservergroups'.
DBCC results for 'DTA_input'.
There are 1 rows in 1 pages for object 'DTA_input'.
DBCC results for 'RTblDatabaseVersion'.
There are 1 rows in 1 pages for object 'RTblDatabaseVersion'.
DBCC results for 'systargetservergroupmembers'.
There are 0 rows in 0 pages for object 'systargetservergroupmembers'.
DBCC results for 'sysalerts'.
There are 16 rows in 1 pages for object 'sysalerts'.
DBCC results for 'RTblDTSProps'.
There are 0 rows in 0 pages for object 'RTblDTSProps'.
DBCC results for 'RTblVersionAdminInfo'.
There are 2333 rows in 30 pages for object 'RTblVersionAdminInfo'.
DBCC results for 'restorefile'.
There are 56 rows in 2 pages for object 'restorefile'.
DBCC results for 'sysoperators'.
There are 0 rows in 0 pages for object 'sysoperators'.
DBCC results for 'sysnotifications'.
There are 0 rows in 0 pages for object 'sysnotifications'.
DBCC results for 'RTblParameterDef'.
There are 136 rows in 1 pages for object 'RTblParameterDef'.
DBCC results for 'restorefilegroup'.
There are 28 rows in 1 pages for object 'restorefilegroup'.
DBCC results for 'systaskids'.
There are 0 rows in 0 pages for object 'systaskids'.
DBCC results for 'syscachedcredentials'.
There are 0 rows in 1 pages for object 'syscachedcredentials'.
DBCC results for 'RTblIfaceHier'.
There are 3349 rows in 18 pages for object 'RTblIfaceHier'.
DBCC results for 'logmarkhistory'.
There are 0 rows in 0 pages for object 'logmarkhistory'.
DBCC results for 'DTA_progress'.
There are 3 rows in 1 pages for object 'DTA_progress'.
DBCC results for 'RTblNamedObj'.
There are 2196 rows in 22 pages for object 'RTblNamedObj'.
DBCC results for 'sysdtscategories'.
There are 3 rows in 1 pages for object 'sysdtscategories'.
DBCC results for 'sysdtspackages'.
There are 91 rows in 2 pages for object 'sysdtspackages'.
DBCC results for 'DTA_output'.
There are 1 rows in 1 pages for object 'DTA_output'.
DBCC results for 'DTA_tuninglog'.
There are 117 rows in 2 pages for object 'DTA_tuninglog'.
DBCC results for 'DTA_reports_database'.
There are 1 rows in 1 pages for object 'DTA_reports_database'.
DBCC results for 'DTA_reports_partitionfunction'.
There are 0 rows in 0 pages for object 'DTA_reports_partitionfunction'.
DBCC results for 'MSdistpublishers'.
There are 0 rows in 1 pages for object 'MSdistpublishers'.
DBCC results for 'MSdistributiondbs'.
There are 1 rows in 1 pages for object 'MSdistributiondbs'.
DBCC results for 'RTblTypeInfo'.
There are 0 rows in 0 pages for object 'RTblTypeInfo'.
DBCC results for 'MSdistributor'.
There are 1 rows in 1 pages for object 'MSdistributor'.
DBCC results for 'DTA_reports_partitionscheme'.
There are 0 rows in 0 pages for object 'DTA_reports_partitionscheme'.
DBCC results for 'sysreplicationalerts'.
There are 2 rows in 1 pages for object 'sysreplicationalerts'.
DBCC results for 'MSagent_profiles'.
There are 15 rows in 1 pages for object 'MSagent_profiles'.
DBCC results for 'sysdtspackagelog'.
There are 0 rows in 0 pages for object 'sysdtspackagelog'.
DBCC results for 'MSagent_parameters'.
There are 228 rows in 2 pages for object 'MSagent_parameters'.
DBCC results for 'DTA_reports_table'.
There are 116 rows in 1 pages for object 'DTA_reports_table'.
DBCC results for 'RTblScriptDefs'.
There are 0 rows in 0 pages for object 'RTblScriptDefs'.
DBCC results for 'MSdatatype_mappings'.
There are 185 rows in 2 pages for object 'MSdatatype_mappings'.
DBCC results for 'RTblOLPProps'.
There are 0 rows in 0 pages for object 'RTblOLPProps'.
DBCC results for 'sysdtssteplog'.
There are 0 rows in 0 pages for object 'sysdtssteplog'.
DBCC results for 'RTblEnumerationDef'.
There are 0 rows in 0 pages for object 'RTblEnumerationDef'.
DBCC results for 'DTA_reports_tableview'.
There are 0 rows in 0 pages for object 'DTA_reports_tableview'.
DBCC results for 'sysdtstasklog'.
There are 0 rows in 0 pages for object 'sysdtstasklog'.
DBCC results for 'DTA_reports_query'.
There are 2 rows in 1 pages for object 'DTA_reports_query'.
DBCC results for 'RTblSumInfo'.
There are 0 rows in 0 pages for object 'RTblSumInfo'.
DBCC results for 'RTblMDSProps'.
There are 0 rows in 0 pages for object 'RTblMDSProps'.
DBCC results for 'DTA_reports_querytable'.
There are 4 rows in 1 pages for object 'DTA_reports_querytable'.
DBCC results for 'RTblEnumerationValueDef'.
There are 0 rows in 0 pages for object 'RTblEnumerationValueDef'.
DBCC results for 'DTA_reports_querydatabase'.
There are 2 rows in 1 pages for object 'DTA_reports_querydatabase'.
DBCC results for 'RTblUMLProps'.
There are 0 rows in 0 pages for object 'RTblUMLProps'.
DBCC results for 'DTA_reports_index'.
There are 145 rows in 2 pages for object 'DTA_reports_index'.
DBCC results for 'sysdbmaintplans'.
There are 1 rows in 1 pages for object 'sysdbmaintplans'.
DBCC results for 'DTA_reports_queryindex'.
There are 16 rows in 1 pages for object 'DTA_reports_queryindex'.
DBCC results for 'DTA_reports_column'.
There are 73 rows in 1 pages for object 'DTA_reports_column'.
DBCC results for 'sysdbmaintplan_jobs'.
There are 0 rows in 1 pages for object 'sysdbmaintplan_jobs'.
DBCC results for 'DTA_reports_indexcolumn'.
There are 24 rows in 1 pages for object 'DTA_reports_indexcolumn'.
DBCC results for 'RTblUMXProps'.
There are 0 rows in 0 pages for object 'RTblUMXProps'.
DBCC results for 'sysdbmaintplan_databases'.
There are 0 rows in 1 pages for object 'sysdbmaintplan_databases'.
DBCC results for 'RTblSIMProps'.
There are 0 rows in 0 pages for object 'RTblSIMProps'.
DBCC results for 'sysdbmaintplan_history'.
There are 0 rows in 1 pages for object 'sysdbmaintplan_history'.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'sysdbmaintplan_history' (object ID 1090102924).
DBCC results for 'DTA_reports_querycolumn'.
There are 22 rows in 1 pages for object 'DTA_reports_querycolumn'.
DBCC results for 'RTblGENProps'.
There are 0 rows in 0 pages for object 'RTblGENProps'.
DBCC results for 'RTblDTMProps'.
There are 0 rows in 0 pages for object 'RTblDTMProps'.
DBCC results for 'log_shipping_primaries'.
There are 0 rows in 0 pages for object 'log_shipping_primaries'.
DBCC results for 'log_shipping_secondaries'.
There are 0 rows in 0 pages for object 'log_shipping_secondaries'.
DBCC results for 'RTblDBMProps'.
There are 0 rows in 0 pages for object 'RTblDBMProps'.
DBCC results for 'RTblEQMProps'.
There are 0 rows in 0 pages for object 'RTblEQMProps'.
DBCC results for 'mswebtasks'.
There are 0 rows in 0 pages for object 'mswebtasks'.
DBCC results for 'RTblVersions'.
There are 2333 rows in 27 pages for object 'RTblVersions'.
DBCC results for 'RTblDBXProps'.
There are 0 rows in 0 pages for object 'RTblDBXProps'.
DBCC results for 'RTblRelships'.
There are 6922 rows in 146 pages for object 'RTblRelships'.
DBCC results for 'RTblSites'.
There are 44 rows in 1 pages for object 'RTblSites'.
DBCC results for 'RTblProps'.
There are 393 rows in 3 pages for object 'RTblProps'.
DBCC results for 'RTblRelshipProps'.
There are 28 rows in 1 pages for object 'RTblRelshipProps'.
DBCC results for 'RTblPropDefs'.
There are 797 rows in 10 pages for object 'RTblPropDefs'.
DBCC results for 'RTblRelColDefs'.
There are 320 rows in 4 pages for object 'RTblRelColDefs'.
DBCC results for 'RTblIfaceDefs'.
There are 453 rows in 5 pages for object 'RTblIfaceDefs'.
DBCC results for 'backupmediaset'.
There are 34167 rows in 384 pages for object 'backupmediaset'.
CHECKDB found 0 allocation errors and 8 consistency errors in table 'backupmediaset' (object ID 2037582297).
DBCC results for 'sqlagent_info'.
There are 0 rows in 0 pages for object 'sqlagent_info'.
DBCC results for 'RTblClassDefs'.
There are 537 rows in 5 pages for object 'RTblClassDefs'.
DBCC results for 'sysdownloadlist'.
There are 0 rows in 0 pages for object 'sysdownloadlist'.
DBCC results for 'backupmediafamily'.
There are 34129 rows in 667 pages for object 'backupmediafamily'.
CHECKDB found 0 allocation errors and 35 consistency errors in table 'backupmediafamily' (object ID 2069582411).
DBCC results for 'sysjobhistory'.
There are 895 rows in 197 pages for object 'sysjobhistory'.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'sysjobhistory' (object ID 2073058421).
DBCC results for 'sysjobs'.
There are 20 rows in 1 pages for object 'sysjobs'.
DBCC results for 'RTblTFMProps'.
There are 0 rows in 0 pages for object 'RTblTFMProps'.
DBCC results for 'RTblRelshipDefs'.
There are 144 rows in 1 pages for object 'RTblRelshipDefs'.
DBCC results for 'backupset'.
There are 36070 rows in 1673 pages for object 'backupset'.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'backupset' (object ID 2117582582).
DBCC results for 'sysjobservers'.
There are 20 rows in 1 pages for object 'sysjobservers'.
DBCC results for 'RTblTypeLibs'.
There are 17 rows in 1 pages for object 'RTblTypeLibs'.
DBCC results for 'sysjobsteps'.
There are 28 rows in 9 pages for object 'sysjobsteps'.
DBCC results for 'RTblClassExtension'.
There are 69 rows in 1 pages for object 'RTblClassExtension'.
CHECKDB found 0 allocation errors and 56 consistency errors in database 'msdb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (msdb ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Please let me know the followings, as I never found issues with MSDB database before... I read that this database only keep track of your SQL Server agent jobs so at wrost I will end up loosing all my Maitenance plans? or will I loose something else
1. Should I restore MSDB backup up takes 3 days ago?
2. Or should I repair it with data loss? will it effect any Database entries?
SKR
Any idea what this error is?
error 911: could not locate entry in sysdatabases for database 'msdb'. No entry found with that name
Thanks.
Sa
Hi experts,
I was trying to restore a "mdf" (MSDE) database for a HP OpenView product, unfortunately at the initial state of restoration, i got the following error messages:
Database 'openview' cannot be opened. It has been marked SUSPECT by recovery.
See the SQL Server errorlog for more information.
Any valuable suggestions on how to set/change the current "SUSPECT" mode so that the 'openview' database can be opened?
Many thanks,
Cheng
Hi
I want to suspect database
stop server first
I try to rename C:Program Files (x86)Microsoft SQL ServerMSSQL.1MSSQLDatamsdbdata.mdf to msdbdata.sav
and then start the server
use command to check:
SELECT status & 256 FROM master.dbo.sysdatabases WHERE name = database_name
if the result is 256,it means the msdb is suspect,but the result is 0,it same as the normal status
do you know how to set database suspect with this way, or do you know other way to suspect databse.
absolutely,I could re-back my server noraml with your way
Thanks