No catalog entry found for partition ID (MSSQL 2005)

  • DR_DBA

    SSChasing Mays

    Points: 626

    I've seen few posts regarding this error msg but none that have yet helped me. This error has happened a few times in our environment at seemingly random times, necessitating a restart of the DB service. SQL logs the error as:

    Date 9/13/2009 1:06:36 AM

    Log SQL Server (Archive #1 - 9/13/2009 1:09:00 AM)

    Source spid57

    Message

    No catalog entry found for partition ID xxx in database yyy. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.

    In the Windows Event Viewer:

    Source:MSSQLSERVER

    Time: 1:06:36 AM

    Category: (2)

    Type: Error

    EventID: 608

    Description:

    No catalog entry found for partition ID xxx in database yyy. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.

    The following SQL statement returns no results:

    SELECT OBJECT_NAME([object_id])

    FROM sys.partitions

    WHERE partition_id = xxx

    The SQL log does provide the SpID...is it possible to identify the process that ran into this problem? Are there additional things I can look at to try and determine where/what is causing this problem.

    Further Note: I do not have any jobs scheduled for this time and DBCC returns no errors

    TIA

  • Paul Randal

    One Orange Chip

    Points: 29438

    Is this a user database or tempdb?

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • DR_DBA

    SSChasing Mays

    Points: 626

    This is a user database

  • Paul Randal

    One Orange Chip

    Points: 29438

    There's a known bug with this on tempdb (see http://www.sqlservercentral.com/Forums/Topic770808-149-1.aspx). Could be the same thing. I'll ping Product Support.

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • DR_DBA

    SSChasing Mays

    Points: 626

    I saw that thread and couldn't confirm that it was the same issue. I'll keep my eyes on it for your response. Thanks Paul.

  • Paul Randal

    One Orange Chip

    Points: 29438

    Ok - that bug is tempdb only it seems.

    Can you run DBCC CHECKDB (yourdb) WITH ALL_ERRORMSGS, NO_INFOMSGS and post any results?

    [Edit: Hmm - see that you don't get DBCC errors - in that case it must be a bug and you'll need to call into Product Support to help you out].

    Thanks

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • Alfredo Giotti

    Ten Centuries

    Points: 1106

    Hello. I know this is an old post, however, I just experienced this same issue with Microsoft SQL Server 2012 (SP1) - 11.0.3381.0 (X64) Standard Edition. I am still digging to determine if this is a bug.

    Error: 608, Severity: 16, State: 1.

    2014-03-27 19:50:01.250 spid57 No catalog entry found for partition ID 5908827923301924864 in database 2. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.

    Ran CHECKDB, found no corruption

  • Paul Randal

    One Orange Chip

    Points: 29438

    Did you call Product Support yet? What did they say?

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • Alfredo Giotti

    Ten Centuries

    Points: 1106

    Hello Mr. Randal,

    Thanks for replying so quickly. We are in the process of opening a case.

  • Alfredo Giotti

    Ten Centuries

    Points: 1106

    Mr. Randal,

    MSFT called back to inform us that we may have a TEMPDB corruption. However, I told them running the consistency checker displays no corruption, therefore, their corruption team will be contacting me shortly. Will keep you posted.

  • Alfredo Giotti

    Ten Centuries

    Points: 1106

    Hello Mr. Randal,

    Finally got a response from premier support below is their final statements.

    Cause

    As per our research this is a known issue only occurs on SQL SERVER 2012 Instances when you attempt to query certain DMV’s from a connection using NOLOCK hint or with read uncommitted Isolation level, when other connections are creating and dropping temporary tables. The error message is specific to the transaction which was trying to query the DMVs in READ UNCOMMITED or NOLOCK hint and will not have any impact on other user queries or data that is using TEMPDB database.

    Impact

    These errors are not going to cause any impact on the SQL server.

    Workaround

    You can use READ COMMITTED isolation level as workaround to this problem.

  • Toby Harman

    SSCarpal Tunnel

    Points: 4126

    Just ran into this issue over the weekend on a user database (ID 16). We're running SQL Server 2012 (11.0.3128)

    Fairly comfortable that we don't have corruption as I have run the DBCC CHECKDB and no issues are returned.

    Given that Microsoft have released a patch for this when it occurs in tempdb, I'm going to put this one down to the extensive use of NOLOCK hints used by our developers in the application code.

    I may finally have something more than "Your queries will return inconsistent results." to beat the developers over the head with!

  • JueWe

    SSC Enthusiast

    Points: 166

    *** wrong forum, sorry ***

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

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