databases are in suspect mode automatically | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

databases are in suspect mode automatically

10 of My databases are in suspect mode automatically.The log file exist and hard disk id fine .What should I do to make them healthy
You should check for root cause by monitoring the logs and keep a schedule of monitor.
You would be able to make database online as per BOL
Resetting the Suspect Status
Microsoft® SQL Server™ 2000 returns error 1105 and sets the status column of sysdatabases to suspect if SQL Server is unable to complete recovery on a database because the disk drive no longer has any free space. Follow these steps to resolve the problem: Execute sp_resetstatus.
Use ALTER DATABASE to add a data file or log file to the database.
Stop and restart SQL Server.
With the extra space provided by the new data file or log file, SQL Server should be able to complete recovery of the database. Free disk space and rerun recovery.
sp_resetstatus turns off the suspect flag on a database, but leaves all other database options intact.
Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
I have done sp_resetstatus already,but again they became suspect.
I checked event viewer and found the following errors
SuperSocket Info: Bind failed on TCP port 1433. Error accepting connection request via Net-Library ‘SSNETLIB’. Execution continuing.. Error: 17059, Severity: 18, State: 0 SqlDumpExceptionHandler: Process 75 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 08/10/05 15:25:58 spid 75
*
* Exception Address = 0497B4FB (RegisterLsp + 0000091B Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000008
* Input Buffer 82 bytes –
* SELECT * FROM Documents ORDER BY doc_file
*
*
* MODULE BASE END SIZE
* sqlservr 00400000 00B2CFFF 0072d000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C47FFF 00048000
* OPENDS60 41060000 41065FFF 00006000
* MSVCRT 77BA0000 77BF9FFF 0005a000
* UMS 41070000 4107CFFF 0000d000
* SQLSORT 42AE0000 42B6FFFF 00090000
* MSVCIRT 60020000 6002FFFF 00010000
* sqlevn70 41080000 41086FFF 00007000
* NETAPI32 02C50000 02CA7FFF 00058000
* ole32 030C0000 031F3FFF 00134000
* XOLEHLP 03200000 03205FFF 00006000
* MSDTCPRX 03210000 03287FFF 00078000
* msvcp60 03290000 032F0FFF 00061000
* MTXCLU 03300000 03318FFF 00019000
* VERSION 03320000 03327FFF 00008000
* WSOCK32 03330000 03338FFF 00009000
* WS2_32 03340000 03356FFF 00017000
* WS2HELP 03360000 03367FFF 00008000
* OLEAUT32 03370000 033FBFFF 0008c000
* CLUSAPI 03440000 03451FFF 00012000
* RESUTILS 03460000 03472FFF 00013000
* USERENV 03480000 03543FFF 000c4000
* secur32 03550000 03562FFF 00013000
* mswsock 03580000 035C0FFF 00041000
* DNSAPI 035D0000 035F8FFF 00029000
* winrnr 03640000 03646FFF 00007000
* WLDAP32 03650000 0367DFFF 0002e000
* rasadhlp 036A0000 036A4FFF 00005000
* SSNMPN70 00C70000 00C75FFF 00006000
* SSNETLIB 00C80000 00C94FFF 00015000
* security 04160000 04163FFF 00004000
* imon 04970000 049B4FFF 00045000
* NTMARTA 049D0000 049F1FFF 00022000
* SAMLIB 04A00000 04A0EFFF 0000f000
* hnetcfg 04A50000 04AA8FFF 00059000
* wshtcpip 04AF0000 04AF7FFF 00008000
* SSmsLPCn 04D80000 04D86FFF 00007000
* ntdsapi 04E20000 04E34FFF 00015000
* rsaenh 05600000 0562EFFF 0002f000
* PSAPI 05630000 0563AFFF 0000b000
* SQLFTQRY 06670000 066A1FFF 00032000
* xpsp2res 10000000 102C4FFF 002c5000
* CLBCatQ 066B0000 06732FFF 00083000
* COMRes 06740000 06805FFF 000c6000
* sqloledb 06830000 068B0FFF 00081000
* MSDART 06940000 06959FFF 0001a000
* MSDATL3 06960000 06974FFF 00015000
* oledb32 06D90000 06E08FFF 00079000
* OLEDB32R 06E10000 06E20FFF 00011000
* msv1_0 06E40000 06E66FFF 00027000
* iphlpapi 06E70000 06E89FFF 0001a000
* xpsqlbot 06EA0000 06EA5FFF 00006000
* dbghelp 074D0000 07584FFF 000b5000
*
* Edi: 073BF030: 00000000 00000000 283BC030 00000000 037363D0 073BF0C0
* Esi: 047F02D0: 00000000 00000000 00000000 00000000 00000000 00000000
* Eax: 00000000:
* Ebx: 047F0300: 00000000 00000000 00000000 00000000 00000000 00000000
* Ecx: 00000000:
* Edx: 7C82ED54: 24A48DC3 00000000 0024648D 0824548D 55C32ECD A48DEC8B
* Eip: 0497B4FB: 74084189 EB1B8B04 8BDB3302 FF856056 740C5A89 EB3F8B04
* Ebp: 00000000:
* SegCs: 0000001B:
* EFlags: 00010206: 0054004E 00500000 00740061 003D0068 003A0043 0050005C
* Esp: 073BEF50: 04A38F00 047F02D0 00000000 00000000 0497B1F9 00000000
* SegSs: 00000023:
* *******************************************************************************
* ——————————————————————————-
* Short Stack Dump
* 0497B4FB Module(imon+0000B4FB) (RegisterLsp+0000091B)
* ——————————————————————–
That seems your server has a serious problem, KBAhttp://support.microsoft.com/default.aspx?scid=kb;en-us;318605 about that error. Check for any virus on the server, disk space issues where the tempdb and other databases are located. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>