SQL Server Performance Forum – Threads Archive
Help on Error: 5180.I am facing this problem with Sql Server 2000 Pro with sp3 installed. I keep encountering this error when i check my event viewer in windows 2000 server.<br /><br />Error: 5180, Severity: 22, State: 1<br />Could not open FCB for invalid file ID 3840 in database ‘dbCallingCard’. <br /><br />0000: 3c 14 00 00 16 00 00 00 <…….<br />0008: 03 00 00 00 44 00 42 00 ….D.B.<br />0010: 00 00 0e 00 00 00 64 00 ……d.<br />0018: 62 00 43 00 61 00 6c 00 b.C.a.l.<br />0020: 6c 00 69 00 6e 00 67 00 l.i.n.g.<br />0028: 43 00 61 00 72 00 64 00 C.a.r.d.<br />0030: 00 00 .. <br /><br />I’ve checked with microsoft support and i’ve confirmed that it’s not the dirty read bug on Text/Image column. <br />This database is runing on a machine with 4 scsi harddisk Raid 5 setup. Few days back, one of the harddisk failed to work and the engineers rebuilt the Raid immediately. Since then, this problem occurs everyday. Anyone has any experience in solving this issue? What is FCB? I couldnt find any information on it. I really do appreciate any help and guidance offered. Thank you. <img src=’/community/emoticons/emotion-1.gif’ alt=’‘ /><br /><br /><br />
REfer to this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;276043] to resolve this issue. _________
Hi Satya, The sql server is already installed with service pack 3 and we dont have text/image column created in the database. Any other possible problems which might lead to this error?
Any issues so far on H/w i.e, Disk I/o errors etc.
How often you schedule DBCC Checks? _________
DBCC checks on weekly basis, we do perform reindexing and index defragment as well. Anyway, i’ve found out that the CALL_ASR05 is corrupted during the raid rebuild process. But weird that when i perform DBCC checks on database and tables, it doesnt show any sign. I’ve solved the problem by copying all records into another temporary table, then drop the corrupted table and then renamed the temporary table to CALL_ASR05. Since the system keep logs of all the transactions to CALL_ASR05, i’ll need to recovers missing records for the table changeover period. Thank you for your attention Satya, i really appreciated it. <img src=’/community/emoticons/emotion-1.gif’ alt=’‘ />
Better to export data (may be DTS or BCP) to another table and delete the corrupted one, then rename the new one to CALL_ASR05. Make sure to keep an eye on SQL error log, maint.jobs logs and event viewer logs regularly. _________