Could not open FCB for invalid file Id 0 in database Jde_Prestine and JDE_Production

Subject: Could not open FCB for invalid file Id 0 in database Jde_Prestine
and JDE_Production

Hi all

I am on SQL Server 2000 SP2, with XE SP 22

I am having a serious problem whith Dbcc checkdb, when I run dbcc checkdb
with repair_rebuild option from Query Anaylzer.

My query is

Alter Database: dbName
Set Single_User
Go

dbcc checkdb (Jde_Prestine ,repair_rebuild) (Or JDE_Production)
go

Alter Database: dbName
Set Multi_User
Go

it failed upon execution and message appears.

Server: Msg 5180, Level 22, State 1, Line 2
Could not open FCB for invalid file Id 0 in database 'dbname'
ODBC: Msg 0, Level 16, State 1
Communication Link Failure

Communication Broken

I can not repair the databses,

I could not find any solution of it. I checked Network connectivity it is
ok, Hardware is not failing. I installed another SQL installation and
install Sql 2k SP3a, copy my database JDE_Prestine and JDE_Production
(without Master/msdb) try dbcc checkdb but still got the same problem. I
also upgrade the MDAC to 2.8 latest and got no luck. I use Tcp/ip and remove
name pipe also, but same.

How to repair these database?
Do I have to rebuild Master db first? I think it is also currupted. How to
rebuild Master db (any pros or corns).
Can I copy Master, msdb and model Db to another SQL Server and repair there,
is this possible?
Is there any third party tool/s to repair databases and check the health od
databases?

FCB stands for what?

Please help.

Re: Could not open FCB for invalid file Id 0 in database Jde_Prestine and JDE_Production

Hi there,

FCB stands for File Control Block, the physical file structure used
by SQL to write in and read data from the storage.
I've also suffered from these nasty troubles!
They're always related to disk crashes, controller errors or
NTFS corruption (such as cold reboots or viruses).
Take a look at your RAID and check that there are no orange or
red lights blinking! Try also running a low level diagnostic on your
disk controller (typically booting your server from a Compaq Smartstart
or HP Navigator CDROM).
Be careful, some of these tests do erase your disk contents!
I never saw that these errors could be repaired, you'll have to
replace disks and/or reformat them, and finally restore the most
recent healthy copy of your databases (starting by master and msdb).
Of course, don't use any backup performed after this data corruption.
As a rule of thumb, never rely on DBCC CHECKDB WITH REPAIR
(unless it's just a corrupted index). Most of times, REPAIR will
turn things worse!

Best luck,

Sebastian Sajaroff