JC-3113 (3/11/2013)
Hi folkscame in today and found this error on one of my databases.
Would appreciate any assistance on this as I have not seen this type of error before
If you could lend me your expertise in this i would greatly appreciate it:
Event Error:
The operating system returned error 87(The parameter is incorrect.)
to SQL Server during a write at offset 0x000001cdc58000 in file 'K:\MSSQL\UserDB\Data\SP04_WSS_Content.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.
Thanks
Jim
use [sp04_wss_content];
dbcc checkdb;
go
Changed database context to 'SP04_WSS_Content'.
Msg 823, Level 24, State 3, Server NSAB-SS80-SQL-N, Line 4
The operating system returned error 87(The parameter is incorrect.) to SQL Server during a write at offset 0x000001cdc58000 in file
'K:\MSSQL\UserDB\Data\SP04_WSS_Content.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.
Msg 1823, Level 16, State 2, Server NSAB-SS80-SQL-N, Line 4
A database snapshot cannot be created because it failed to start.
Msg 7928, Level 16, State 1, Server NSAB-SS80-SQL-N, Line 4
The database snapshot for online checks could not be created.
Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or
alternate streams. Attempting to get exclusive access to run checks offline.
Msg 5030, Level 16, State 12, Server NSAB-SS80-SQL-N, Line 4
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Server NSAB-SS80-SQL-N, Line 4
Error 823 means SQL Server had trouble accessing the database file on disk. If you cannot run CHECKDB it may be a sign of an impending crash of your I/O subsytem. Do you have a current backup of this database. Can you take a new FULL backup of this database? Enlist the help of your hardware team (if you have one) and look for other messages in the Windows Event log and SQL Server Error log denoting issues with the I/O subsystem right away.
From the database side, try restoring a current database backup to another machine and checking for corruption there, i.e. run DBCC CHECKDB(sp04_wss_content) WITH NO_INFOMSGS on the restored copy and post the entire result here.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato