SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


DBCC CheckDB CREATE FILE encountered operating system error 1450


DBCC CheckDB CREATE FILE encountered operating system error 1450

Author
Message
phil_mw60
phil_mw60
SSC-Addicted
SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)

Group: General Forum Members
Points: 436 Visits: 62
Hi,

We are running into an issue with a PROD database. The original error was:

"The operating system returned error 1450(error not found) to SQL Server during a write at offset 0x000067819b0000 in file [FILEPATH]. 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). "

When I run dbcc checkdb ('DatabaseName') I get the following error:

"A database snapshot cannot be created because it failed to start.
Msg 5123, Level 16, State 1, Line 1 CREATE FILE encountered operating system error 1450(error not found) while attempting to open or create the physical file 'Path\Filename.mdf:MSSQL_DBCC12'."

I believe this may be because Check DB is trying to create a Snapshot file and encountering an error during the creation of that file.. The MDF for the DB in question is 434GB and there is only 67GB free on the same drive. Could this be due to the amount of free space on the drive?

I was able to run a full backup of the database in question and this completed successfully so it seems like all the pages in the MDF could be successfully read at least.

Has anyone else expeirenced this issue? Any ideas how to resolve? CheckDB for all other DBs in the SQL instance check out ok and a chkdsk doesn't return any errors so maybe it's not a problem with the underlying drive?

Thanks in advance for any ideas.

Phil
GilaMonster
GilaMonster
SSC Guru
SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)

Group: General Forum Members
Points: 951576 Visits: 48920
See http://blogs.msdn.com/b/psssql/archive/2008/07/10/sql-server-reports-operating-system-error-1450-or-1452-or-665-retries.aspx

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


phil_mw60
phil_mw60
SSC-Addicted
SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)

Group: General Forum Members
Points: 436 Visits: 62
Hi Gila,

Thanks for your reply. I found that same article when googling this error. Our server is WS2003 Enterprise Edition x64 edition with 42GB RAM so we don't have the /3GB switch in boot.ini.

The other strange thing is that we don't have any database snapshots configured for this DB. Although I understand that Check DB automatically creates a database snapshot when running in multi-user mode?

In fact, although there was an error mentioned in the output of DBCC CHECKDB there is also the following message:

CHECKDB found 0 allocation errors and 0 consistency errors in database 'DBName'.

Which gives me hope..

Will the following solution require me to place the DB into single user mode?
Run DBCC CHECKDB in OFFLINE mode (WITH TABLOCK)

Sorry for all the Q's, I'm still not 100% sure I understand the issue after reading that article.

I am restoring a previous backup of the DB in question (overwriting the current database files) to see if this resolves the issue. Obviously the data will be slightly outdated.

Many THanks,

Phil
GilaMonster
GilaMonster
SSC Guru
SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)SSC Guru (951K reputation)

Group: General Forum Members
Points: 951576 Visits: 48920
phil_mw60 (11/19/2014)
Although I understand that Check DB automatically creates a database snapshot when running in multi-user mode?


Yes

Will the following solution require me to place the DB into single user mode?
Run DBCC CHECKDB in OFFLINE mode (WITH TABLOCK)


It doesn't *require* single user mode, but you must ensure that no one is using the database at all for the entire duration

I am restoring a previous backup of the DB in question (overwriting the current database files) to see if this resolves the issue. Obviously the data will be slightly outdated.


Highly unlikely to do anything other than lose data (by restoring to an earlier time). As the blog post stated, this is a resource problem.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


phil_mw60
phil_mw60
SSC-Addicted
SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)SSC-Addicted (436 reputation)

Group: General Forum Members
Points: 436 Visits: 62
Hi,

Just a quick update on this situation for anyone who may be interested..

I was able to resolve this issue by restoring a previous backup of the DB in question (using the with replace option).

Although this lead to data loss it was acceptable because we have a process which synchronises data into this DB from another data source, so we were able to load the missing data.

After restoring the DB, DBCC Check DB completed successfully without returning any error messages.

Could this be because the restore effectively moved the MDF to a different part of the disk? This is still cause for concern in the long run but at least the DB is back online again now with no errors.

Thanks,

Phil
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search