Could not open FCB for invalid file ID 5120

I was just running a query and got the following error.
Could not open FCB for invalid file ID 5120 in database
<dbname>. Table or database may be corrupted..
Any ideas?Hi,
Execute the DBCC CHECKDB with REPAIR_REBUILD option. If you still have
issues then take a full database backup and you may need to try the option
REPAIR_ALLOW_DATA_LOSS with DBCC CHECKDB.
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:299dc01c465ab$06520cb0$a501280a@.phx.gbl...
> I was just running a query and got the following error.
> Could not open FCB for invalid file ID 5120 in database
> <dbname>. Table or database may be corrupted..
> Any ideas?|||I did this just before I ran the query.
I repaired all of the errors found and then ran the query.
>--Original Message--
>Hi,
>Execute the DBCC CHECKDB with REPAIR_REBUILD option. If
you still have
>issues then take a full database backup and you may need
to try the option
>REPAIR_ALLOW_DATA_LOSS with DBCC CHECKDB.
>
>--
>Thanks
>Hari
>MCDBA
><anonymous@.discussions.microsoft.com> wrote in message
>news:299dc01c465ab$06520cb0$a501280a@.phx.gbl...
>> I was just running a query and got the following error.
>> Could not open FCB for invalid file ID 5120 in database
>> <dbname>. Table or database may be corrupted..
>> Any ideas?
>
>.
>|||If the AUTO SHRINK is enabled on this database, then disable it.
Otherwise do not issue DBCC SHRINKFILE statement while SHRINKDATABASE is working.
Also confirm what is the level of service pack on SQL?
As there is no confirmation of version used, check whether this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;276043 is any help.
"anonymous@.discussions.microsoft.com" wrote:
> I did this just before I ran the query.
> I repaired all of the errors found and then ran the query.
> >--Original Message--
> >Hi,
> >
> >Execute the DBCC CHECKDB with REPAIR_REBUILD option. If
> you still have
> >issues then take a full database backup and you may need
> to try the option
> >REPAIR_ALLOW_DATA_LOSS with DBCC CHECKDB.
> >
> >
> >--
> >Thanks
> >Hari
> >MCDBA
> ><anonymous@.discussions.microsoft.com> wrote in message
> >news:299dc01c465ab$06520cb0$a501280a@.phx.gbl...
> >> I was just running a query and got the following error.
> >>
> >> Could not open FCB for invalid file ID 5120 in database
> >> <dbname>. Table or database may be corrupted..
> >>
> >> Any ideas?
> >
> >
> >.
> >
>|||Can you explain the advice below about shrinkdatabase and shrinkfile? Can
you also explain how autoshrink could cause the invalid FCB message?
Thanks.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"SatyaSKJ" <SatyaSKJ@.discussions.microsoft.com> wrote in message
news:961E7787-C82B-44D3-8653-56D9BCFD3CC2@.microsoft.com...
> If the AUTO SHRINK is enabled on this database, then disable it.
> Otherwise do not issue DBCC SHRINKFILE statement while SHRINKDATABASE is
working.
> Also confirm what is the level of service pack on SQL?
> As there is no confirmation of version used, check whether this KBA
http://support.microsoft.com/default.aspx?scid=kb;EN-US;276043 is any help.
>
> "anonymous@.discussions.microsoft.com" wrote:
> > I did this just before I ran the query.
> > I repaired all of the errors found and then ran the query.
> >
> > >--Original Message--
> > >Hi,
> > >
> > >Execute the DBCC CHECKDB with REPAIR_REBUILD option. If
> > you still have
> > >issues then take a full database backup and you may need
> > to try the option
> > >REPAIR_ALLOW_DATA_LOSS with DBCC CHECKDB.
> > >
> > >
> > >--
> > >Thanks
> > >Hari
> > >MCDBA
> > ><anonymous@.discussions.microsoft.com> wrote in message
> > >news:299dc01c465ab$06520cb0$a501280a@.phx.gbl...
> > >> I was just running a query and got the following error.
> > >>
> > >> Could not open FCB for invalid file ID 5120 in database
> > >> <dbname>. Table or database may be corrupted..
> > >>
> > >> Any ideas?
> > >
> > >
> > >.
> > >
> >|||This is very bad advice.
Microsoft does not recommend you run repair blindly without working out the
root cause of your problem and the consequences of running repair. Running
REPAIR_ALLOW_DATA_LOSS (as its name suggests) deletes data with no heed to
whatever business logic is inherent in your database. Even running
REPAIR_REBUILD without first working out what happened is very foolish and
is just a band-aid until the problem occurs again.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uv3QnuaZEHA.1248@.TK2MSFTNGP11.phx.gbl...
> Hi,
> Execute the DBCC CHECKDB with REPAIR_REBUILD option. If you still have
> issues then take a full database backup and you may need to try the option
> REPAIR_ALLOW_DATA_LOSS with DBCC CHECKDB.
>
> --
> Thanks
> Hari
> MCDBA
> <anonymous@.discussions.microsoft.com> wrote in message
> news:299dc01c465ab$06520cb0$a501280a@.phx.gbl...
> > I was just running a query and got the following error.
> >
> > Could not open FCB for invalid file ID 5120 in database
> > <dbname>. Table or database may be corrupted..
> >
> > Any ideas?
>