March 11, 2013 at 8:54 am
Hi folks
came 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
March 11, 2013 at 1:52 pm
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
March 11, 2013 at 2:51 pm
Hi opc.three
Well, i started to back up all the databases since i did not get any backups since sat. I am using SSMS and if the DBCC CHECKDB fails on any database, the backups do not run, since i do that first.
I know, pretty poor. I am going to have to address this, but anyway i was backing up existing databases and started getting the same problem on two other databases. I found this error also
"A system assertion check has failed. "
Not good according to Gail. Lots of dump files and "BugCheck Dump" files. Not good also.
Anyway as I was doing a check on the third database, the server crashed.
After it came back up and I started the services, I ran a check again on the bad databases.
To my surprise, all the databases that showed a problem, passed the check and I was able to get full backups. So I am not sure what the cause is at this time.
I am trying to get an Admin to get me a ticket with MS to see if they can shed some light on issues we had.
Thanks
Jim
March 11, 2013 at 4:13 pm
Gail looked to be offline so I jumped in. Hopefully she'll drop by and help shed some additional light on the situation.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 11, 2013 at 5:27 pm
Does that particular database have an database snapshot currently defined? Just a guess here.
March 12, 2013 at 9:00 am
Could be an issue with the DBCC snapshot.. the only thing I could remember was this post a while ago:
http://www.sqlservercentral.com/Forums/Topic450261-146-2.aspx#bm477512
Would make sense if your DBCC came back after a server restart after a crash
March 12, 2013 at 9:16 am
Thanks kyleheath33
from what I was told from a sysadmin
this sql server is a virtual machine on vmware
i do not know that much abour vmware
anyway apparently, the vmware console or master pink screened and took down all the clients
of which my server is one, so thus the crash yesterday
that does not explain why i was getting corruption notices starting on last sat though unless that master was going south at that time.
Jim
March 12, 2013 at 9:31 am
From my post I meant that it would make sense for the DBCC to come back clean after a reboot as the SQL restart (server crash) would have cleared the hidden previous snapshot which was causing the issue, this is all just suggestion and would keep going with the MS ticket.
March 12, 2013 at 11:49 am
Hi Lynn
i am not using snapshots that I am aware of
Jim
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply