Thursday, March 22, 2012

Error: 5180 - Could not open FCB for invalid file ID #

When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
databases we get following errors:
- spid333 Error: 5180, Severity: 22, State: 1
- spid333 Could not open FCB for invalid file ID <#> in database '<dbname>'.
Is there anyone here that has a hint on what is causing this.This error stated that the file was dropped or the database was corrupted.
- Please run DBCC SHRINKDATABASE again.
- If the error shows up again, please run DBCC CHECKDB to see if the
database is corrupted.
- If the database is not corrupted, then probably there is a bug in shrink
code, you can contact PSS for further assistant.
--
Stephen Jiang
Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tor Lynge Olsen" <TorLyngeOlsen@.discussions.microsoft.com> wrote in message
news:A5E9AA7C-6A4D-4527-A9EC-687A15216E91@.microsoft.com...
> When we do a DBCC SHRINKDATABASE <dbname>, 5 on one of our high volume
> databases we get following errors:
> - spid333 Error: 5180, Severity: 22, State: 1
> - spid333 Could not open FCB for invalid file ID <#> in database
'<dbname>'.
> Is there anyone here that has a hint on what is causing this.
>

No comments:

Post a Comment