December 22, 2004 at 1:07 pm
Hi everyone,
I have been using this forum for quite sometime to solve my SQL Server problems and it's great. I appreciate all the help I'm getting from you guys and I say just keep it up. You are serving the SQL Server community very well!
Now to my problem. The following error I'm getting on my SQL Server machine. I tried to get the informtion about it on the web but unfortunately couldn't.
"Could not open FCB for invalid file ID 9338 in database 'msdb'"
Just a background about the machine. It's a log shipping machine and is connected to our production server. We have a job agent running on the production server which keeps on every 10mins executes and restores the log on the log shipping machine. The process was performing smoothly till the last night I got this problem started and till now I'm getting this every 10 minutes. I have also tried to restore the logs manually but still getting the same error. Can someone in the forum tell me whats going on...and why I'm getting this error? and how to resolve this problem?
Thanx.
MA
December 23, 2004 at 10:12 am
Wow! Such kind words about the forum and no responses to your query for nearly 22 hours?!?! Well, it seems responses have slowed due to the holiday season. I know absolutely nothing about your error message, but found the following on Microsoft.com:
http://support.microsoft.com/default.aspx?scid=kb;en-us;236568
http://support.microsoft.com/default.aspx?scid=kb;en-us;276043
I found these links by searching on http://www.microsoft.com with the following search string: "Could not open FCB". There are other results as well.
Hope this helps!
Steve
December 23, 2004 at 12:07 pm
RE: Q1 What is FCB for invalid file ID means?? Now to my problem. The following error I'm getting on my SQL Server machine. I tried to get the informtion about it on the web but unfortunately couldn't. "Could not open FCB for invalid file ID 9338 in database 'msdb'"
------
A1 FCB = File Control Block which is something like a file handle (if that is more meaningful); among other thngs it may indicate IO device issues, database corruption (use dbcc checkdb to diagnose for problems), or it may represent a service packed bug e.g(http://support.microsoft.com/kb/278366/EN-US/). HTH
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply