December 3, 2010 at 2:52 am
Helllo ,
I have had these errors when I ran DBCC CheckDB command after investigation I noticed that minimum memory was set to zero and maximum memory was not configured for SQL server ..
I am suspecting that might have caused error in DBCC results?
Errorlog:
2010-11-22 15:08:05.59 spid62 Error: 823, Severity: 24, State: 2.
2010-11-22 15:08:05.59 spid62 The operating system returned error 38(error not found) to SQL Server during a read at offset 0x00000147c90000 in file 'G:\Data\xyz79_10.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2
2010-11-26 15:42:30.04 spid77 Error: 824, Severity: 24, State: 2.
2010-11-26 15:42:30.04 spid77 SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:4800942; actual 79:6619251). It occurred during a read of page (1:4800942) in database ID 5 at offset 0x0000092835c000 in file 'G:\Data\xyz79.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2010-11-26 15:42:30.09 spid77 Error: 3314, Severity: 21, State: 4.
2010-11-26 15:42:30.09 spid77 During undoing of a logged operation in database 'xyz79', an error occurred at log record ID (127413:159892:117). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
2010-11-26 15:42:30.12 spid77 Error: 9001, Severity: 21, State: 5.
2010-11-26 15:42:30.12 spid77 The log for database 'xyz79' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Thanks in advance
Ta
December 3, 2010 at 3:01 am
This error has nothing to do with the configuration of the instance.
The data file has corruption in it. Please look out for the last good backup for this database. Also engage the Storage team to look into the underlying storage problems.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
December 3, 2010 at 3:31 am
Thanks but if the SQL server is not configured for the memory then it will end up utilizing all the available memory without leaving anything to Operating System?
December 3, 2010 at 4:42 am
Please go through this article.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
December 3, 2010 at 8:25 am
Thanks Pradeep
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply