SQL Severity 22 alert.

  • Early this morning we got a SQL Severity 22 alert.

    We have a SQL Server Enterprise environment (2 node windows cluster). There's 1 default and 3 named instances. One of the named instances has SQL 2008 R2 - this is the one with the alert (others instances have SQL 2008). Each of the instances has the MAXDOP set to 6 (24 cores on the node). OS: Windows Server 2008 enterprise (service pack 2).

    Description was "Could not open File Control Bank (FCB) for invalid file ID 0 in database 'tempdb'. Verify the file location. Execute DBCC CHECKDB."

    Googling this did not provide a lot of information. Aside from the recommendation to run a DBCC CheckDB, does anyone have any experience with this?

    Any comments / recommendations would be appreciated. Thanks.

  • This is a memory issue. We'll either re-seat the memory or replace it.

    Thank you.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply