Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

No catalog entry found for partition ID Expand / Collapse
Author
Message
Posted Monday, June 1, 2009 10:56 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 5:03 AM
Points: 2,840, Visits: 3,975
I get this error message when I try to execute a stored procedure.

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

If I run the SQL code inside the SPROC it works fine. I have tried recreating, renaming, different database, everything, always the same response (but different partition ID number).

DBCC CheckDB never shows any issues.


Please Help


-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #727139
Posted Wednesday, August 12, 2009 11:14 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, August 24, 2012 3:34 AM
Points: 10, Visits: 61
I got the same error message when i trying to select one table in the particular database.
Post #769869
Posted Friday, August 14, 2009 11:08 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Saturday, November 22, 2014 7:46 PM
Points: 3,220, Visits: 2,361
I believe that 'Database 2' is tempdb.

Try stopping and restarting SQL Server.




Regards
Rudy Komacsar
Senior Database Administrator

"Ave Caesar! - Morituri te salutamus."
Post #771160
Posted Friday, August 14, 2009 12:05 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:57 AM
Points: 40,418, Visits: 36,869
See - http://www.sqlservercentral.com/Forums/Topic770808-149-1.aspx


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #771196
Posted Friday, April 26, 2013 8:37 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, October 24, 2013 7:29 AM
Points: 109, Visits: 74
On SQL 2005, you will be surprised that reindexing a temporary table can cause this error.
I have tested this on other versions like 2012 and it does not arise.

I guess something is causing some kinda data change on an object which is resident on TempDB while the data is being referenced by a transaction, hence the error.
Post #1447039
Posted Friday, May 24, 2013 12:01 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, March 13, 2014 10:10 AM
Points: 1, Visits: 56
I was surprised when it happened to me, once I removed the index on temporary table that fixed it.



Good find and thanx
Post #1456641
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse