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 RepliesHi 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 RelatedHi,
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.
A 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..
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!
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.
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.
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
Whenever I start my SQL Express 2005 database, I get the following in the logs :
View 10 Replies View RelatedOne of my database (name XYZ) shows suspect status in EM but when i try to dig further by running below query i get only "OK" ( see query)
SELECT [name],status, case status when (status & 32) then 'Loading'
when (status & 32) then 'Loading'
when (status & 64) then 'Pre Recovery'
when (status & 128) then 'Recovering'
when (status & 256) then 'Not recoverd'
when (status & 512) then ' Offline'
when (status & 1024) then ' Single user'
when (status & 1024) then ' Read only'
when (status & 32768) then ' Emergency Mode' else 'OK' end as status
FROM master.dbo.sysdatabases
WHERE [name] NOT IN ('distribution', 'tempdb', 'model','Pubs','Northwind')
also i run this
select * from sysdatabases where databaseproperty(name,N'IsSuspect') <> 1
and here also i get all the database including "XYZ"...i guess if "XYZ" is suspect the resultset should not be including "XYZ"
Why if the EM shows suspect status FOR "XYZ" DATABASE it should come up when i check status column in sysdatabases table?
Hi all,
What does this mean? SUSPECT, in SQL server 7? I dont remember what caused one of my database to be SUSPECTed. Can someone let me informed what causes a database to be SUSPECT and what are its implications and how to make the SUSPECTed database work
Thanx in advance
ozone
I had a database (give it a name A) that was marked suspect. I ran the following query
use master
go
sp_resetstatus <db_name>
I then stopped and restarted SQL Server. This fixed the problem for database A but I got two more that were suspect. After running the same query for both B & C, C got fixed but I still cannot fix B. My question is why did fixing problem A cause a problem for DB B & C?
I tried running the following query on B after the first one failed.
Update sysdatabases set status = -32768 where name='B'
This gave me the following error: Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this.
Could somebody please help me solve this problem?
One of my database mark as suspect and resetstaus did not work. From the SQL server error log i find following message. Any suggestion?
source:kernel
SQL Server Assertion: File: <recovery.c>, line=2687
Failed Assertion = 'seenCkptEnd'.
...
source:spid7
Error: 0, Severity: 19, State: 0
...
source:spid7
Location: recovery.c:2687
Expression: seenCkptEnd
SPID: 7
Process ID: 162
...
source:spid7
SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
....
source:spid7
Error: 3414, Severity: 21, State: 1
Hi all,
I have had problems lately with my standby server,when i am trying to do a load from my production it goes into suspect mode
.the load is just fine as per my error log after
5/10 minutes it goes into suspect mode the error is
"Error 3305,Severity 21,State 1"
"Page 559396 in databse "xyz' read in during runtime or load xact was uninitilised"
"Idxact:Dbid:6 is in IN_LOAD state with the following exception raised:major 43,minor 3,pstat:0X400"
Now i have checkd error 3305 everywhere but no answers..please help
Regards
I have a db in suspect. I want to try to run sp_reset_status and reset the status bit. I believe there is a script that I can run to create sp_reset_status. Where can I find that?
Thanks
Betty Lee
Every once in a while one the DB on SQL Server 2000 goes suspect. I was thinking it was because there was no back up plan. The problem is usually resolved after a simple start and stop of the SQL Server Agents. Anyone have similar situations that could shed some light?
Thanks
Matt
One of my databses is saying suspect beside it can this be fixed
View 1 Replies View RelatedMy database is marked as suspectI am using SQL Server 2000,I ran the command sp_resetstatus it executes succesfully. but still the database is in suspect state.can any one tell me how i recover my data.thanks in advance
View 1 Replies View RelatedIm running SQL 7.0 with a large heavily used 4Gb database. After a while the database is marked suspect. What can be the cause to this ? Please email me and I can send you additional information about hardware and the system.
View 3 Replies View RelatedHi,
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
I wonder if one can give a hint on remove a DB suspect,
Mind you I have used SP_dbremove still did not remove the DB
This is on SQL 7.0 box
Any idea welcomed
Saad
Hi everyone,
I really need help on this, one of my databases is marked suspect. I did tried to execute this command below (scripts):
use master
go
sp_configure 'allow updates',1
go
reconfigure with override
go
update sysdatabases set status=4 where name='security'
go
sp_configure 'allow updates',0
go
reconfigure with override
go
and it release the suspect from the 'Security' database, but it Won't let me access the table,data or nothing. The worse thing is when I stop & start the server again, the database marked suspect again.
Could anybody out the help me on this. Thank in advance, Vu
Hello,
Today we found a suspect database and after consulting this website went and ran sp_resetstatus on one database with success. After which we stopped and started the server and ran dbcc newalloc, dbcc textall, dbcc checkdb on that database. It successfully changed from its suspect status and random queries showed that the data was still intact.
Exactly the same process was run on another database and it failed to move from the suspect status after restarting the server. We then went through books online, which advised to update sysdatabases setting the database's status to 0. This also failed.
HELP PLEASE.
Does anyone know what else to try? This was a development database with no backups. This would save a weeks work. Thanks for you time.
Cheers
Damian
steps to recovery suspect database
Log showed a 614 error and probably is a result of a hardware 0/s problem or ?. The database was not
reloaded before the error.
I was recently was called in to help some people who had a SQL Server database marked as suspect.
I have never had to deal with this situation before. I got the database operational by doing the
following steps. Was there an easier or better way?
Executed statement per BOL procedure to allow updates to system tables.
Removed suspect flag per BOL (BOL says to use sp_resetstatus which I did not find in master or msdb,
however the BOL had the code listed so I typed in the pertinent statement). I do not know what the '^ 256
meant in BOL, I used the status code that the nonsuspect databases had '16400'.
SQL Server would not let me restore into a suspect database so I reset the suspect flag. Could have dropped
the database, however I did not have the information to recreate the database so the restore function would
work.
Put database in single user mode.
restored database.
Removed the ability to update system tables per BOL
Set the database back to multi user mode.
I am using SQL server 6.5 sp3 and NT 4.0 sp4.
My SMS database has been marked suspect.
I do not have a backup.
I have read several articles about trying to us sp_resetstatus.
I can not find this sp on my server.
When I try the following:
UPDATE master..sysdatabases status=256 WHERE name = ('sms')
I get the following back:
Ad-hoc updates to system catalog not enabled. System Adminstrator must recongifure system to allow this.
I have searched Microsoft KB and everywhere I can think of. If anyone can help I would really appreciate it.
I even tried reapplying sp3 and rebooting...this did not help either.
Can someone please tell me how to change the status back to normal.....I think this is a it will take..
thanks in advance,
nathan
I have the original dat files ( 2 seperate log / data) of a database. I have created new devices (same size as originals) and a new database. I replace the new dat files with the originals and the database always comes up as a suspect. I have done this with the other 7 databases on my server and none have similar problems. This database was created different then others using new database and new devices routine rather than creating the devices first. Any Ideas?
Thanks in Advance.
Hi... I have this problem with my database (dunno how this thing happen). Today, 2 of my databases have been marked as 'suspect' (grey color in SQL Enterprise Manager). In ISQL, when I try 2 connect 2 the database (use), the message '
Msg 926, Level 14, State 1
Database 'MYUAT' cannot be opened - it has been marked SUSPECT by recovery. The SA can drop the database with DBCC.'
appeared.
Don't understand Y this occurred...
Thanks in advance for any help...
~Cheers~
my database is in suspect,how to correct it?
thx in adance..
Hi all,
We recently had some kind of error on one of the server's hard drives. The network guys, reinintialized (or something) and were able to bring everything back. However, two of my databases now is "Suspect" and can't be used. Both the MDF & LDF exist, and there are no indications of actual data loss. What can I do with a "suspect" database ? SQL 2K
What should I do to recover these two databases?
Thank you for all your suggestions.