FIX: Error 602 when you run a stored procedure repeatedly in SQL Server 2012 or SQL Server 2014

Symptoms
Assume that you use Microsoft SQL Server 2012 or SQL Server 2014. When you repeatedly run a stored procedure that retrieves data from a temporary table in a single session, you receive the following error message:
Error: 602, Severity: 21, State: 30.Could not find an entry for table or index with partition ID <partition ID> in database <database name>. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.

Note This issue is more likely to occur on a system that has many CPUs, for example, a computer that has 20 CPUs.
Resolution
The issue was first fixed in the following cumulative update of SQL Server: Recommendation: Install the latest cumulative update for SQL Server
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 3080209 - Last Review: 10/19/2015 18:53:00 - Revision: 2.0

Microsoft SQL Server 2012 Service Pack 2, Microsoft SQL Server 2014 Service Pack 1, Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Standard

  • kbqfe kbsurveynew kbfix kbexpertiseadvanced KB3080209
Feedback
in database " error occurs when you run a stored procedure repeatedly in SQL Server 2012 or SQL Server 2014." />
in database " error occurs when you run a stored procedure repeatedly in SQL Server 2012 or SQL Server 2014." />