none
Unable to find index entry in index ID 0, of table 1589580701, in database 'tempdb'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.

    Question

  • environment: clustered

    Microsoft SQL Server 2005 - 9.00.3215.00 (X64)
    Dec  8 2007 17:58:16
    Copyright (c) 1988-2005 Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    Error:
    Unable to find index entry in index ID 0, of table 1589580701, in database 'tempdb'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.

    I see this issue may be addressed in an SP2 Cumulative update.  Does anyone know if it addressed in SQL2005 SP3?
    Or have found another way to address the error?

    Thanks. 

    Monday, August 31, 2009 2:23 PM

Answers

  • Hi MicMicky,

    Unable to find index entry in index ID 0, of table 1589580701, in database 'tempdb'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.

     

    Recently ran into a serious issue with SQL Server issueing the above message under load.  After shutting things down and running check db there was no corruption, but every time a particular stored procedure was executed under load, stack dumps would occur with the above message in the Error Log.

    With the help of Microsoft support we isolate the issue to a particular delete statement that was being executed with a join to another table and a where clause.  The query was performing a hash join and there is some bug that was causing a problem.  Microsoft continues to research the issue, but recommended we use a query hint to force a merge join to resolve the problem.  Testing indicates that the problem has gone away.

    Old Query:

    DELETE FROM {child table}
    FROM {child table} aq, {parent table} a
    WHERE aq.id = a.id
    AND ( a.status_id in (4, 5, 6, 7)
    OR
    type_id = 3
    OR a.match_id =
    AND a.id%@p_in_threads = @p_in_thread_no

    New Query

    DELETE FROM {child table}
    FROM {child table} aq, {parent table} a
    WHERE aq.id = a.id
    AND ( a.status_id in (4, 5, 6, 7)
    OR
    type_id = 3
    OR a.match_id =
    AND a.id%@p_in_threads = @p_in_thread_no
    option (merge join)

     

    Hope this helps…

    Please Vote & “Mark As Answer” if this post is helpful to you.

    Cheers

    Bikash Dash

    MCDBA/MCITP

     

    Monday, August 31, 2009 2:40 PM

All replies

  • Hi MicMicky,

    Unable to find index entry in index ID 0, of table 1589580701, in database 'tempdb'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.

     

    Recently ran into a serious issue with SQL Server issueing the above message under load.  After shutting things down and running check db there was no corruption, but every time a particular stored procedure was executed under load, stack dumps would occur with the above message in the Error Log.

    With the help of Microsoft support we isolate the issue to a particular delete statement that was being executed with a join to another table and a where clause.  The query was performing a hash join and there is some bug that was causing a problem.  Microsoft continues to research the issue, but recommended we use a query hint to force a merge join to resolve the problem.  Testing indicates that the problem has gone away.

    Old Query:

    DELETE FROM {child table}
    FROM {child table} aq, {parent table} a
    WHERE aq.id = a.id
    AND ( a.status_id in (4, 5, 6, 7)
    OR
    type_id = 3
    OR a.match_id =
    AND a.id%@p_in_threads = @p_in_thread_no

    New Query

    DELETE FROM {child table}
    FROM {child table} aq, {parent table} a
    WHERE aq.id = a.id
    AND ( a.status_id in (4, 5, 6, 7)
    OR
    type_id = 3
    OR a.match_id =
    AND a.id%@p_in_threads = @p_in_thread_no
    option (merge join)

     

    Hope this helps…

    Please Vote & “Mark As Answer” if this post is helpful to you.

    Cheers

    Bikash Dash

    MCDBA/MCITP

     

    Monday, August 31, 2009 2:40 PM
  • Hi,

    We had the same issue in an update statement that had a join between 2 tables and a where clause. I deleted the indexes on the table being updated and then rebuild the same indexes. The issue was resolved.

    Thanks!

    Sunday, July 31, 2011 5:40 PM
  • Hi,

    i have the same issue with SQL Server 2016. I cant find these "ghost" table. The server creates very large dump files, i dont know how to fix it.

    Monday, September 25, 2017 2:09 PM