November 21, 2011 at 8:32 am
I got following error through dbcc checkdb
An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
DBCC results for ''.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
DBCC results for 'sys.sysrowsetcolumns'.
There are 3377 rows in 40 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
What should I do for next step? Thanks for any suggestions.
November 21, 2011 at 8:35 am
Restore from backup.
If you're in full recovery with log backups, take a tail-log backup first then restore full and all log backups since then. You'll restore with no data loss. If you're running in simple recovery, you'll lose any data since the last full/differential backup.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 21, 2011 at 8:39 am
Thanks for the reply. Here is extra from error log. Any advice on below error log? Thanks in advance.
CImageHelper::Init () Failed load of symbol file with path = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\BINN - Not enough storage is available to process this command.
011-11-21 03:22:48.44 spid91 Stack Signature for the dump is 0x0B3BE262
2011-11-21 03:22:51.18 spid91 External dump process return code 0x20000001.
External dump process returned no errors.
2011-11-21 03:22:51.18 spid91 Error: 5242, Severity: 22, State: 1.
2011-11-21 03:22:51.18 spid91 An inconsistency was detected during an internal operation in database 'KLSite30'(ID:16) on page (1:9014455). Please contact technical support. Reference number 5.
2011-11-21 03:24:55.27 spid91 Using 'dbghelp.dll' version '4.0.5'
2011-11-21 03:24:55.27 spid91 CImageHelper::Init () Failed load of symbol file with path = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\BINN - Not enough storage is available to process this command.
2011-11-21 03:24:55.28 spid91 Using 'dbghelp.dll' version '4.0.5'
2011-11-21 03:24:55.28 spid91 CImageHelper::Init () Failed load of symbol file with path = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\;C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\BINN - Not enough storage is available to process this command.
2011-11-21 03:24:55.28 spid91 ***Symbol load failed - Proceed to dump without any symbols
2011-11-21 03:24:55.28 spid91 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump1842.txt
2011-11-21 03:24:55.28 spid91 SqlDumpExceptionHandler: Process 91 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2011-11-21 03:24:55.28 spid91 * *******************************************************************************
November 21, 2011 at 8:57 am
Is KLSite30 the database you ran the CheckDB on?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 21, 2011 at 9:05 am
Yes. Actually this db is broken already - months ago - I just got this server recently. So I will take care of this later.
Thanks,
November 21, 2011 at 9:15 am
The errors in that DB are the cause of the log errors.
As for 'take care of it later', that DB is not repairable. If you don't have a clean backup, that's going to be a nasty fix.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 21, 2011 at 9:21 am
Thanks! I got it. I will continue getting this error if no action now. I really appreciate your help!!!
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply