Error Occurred While Attempting To Drop Work Table With Partition
Kent [MSFT]June 25, 20080 0 0 0 I recently worked with a customer who was seeing the following error in their error log: SQL Server Assertion: File: , line=1069 Failed Assertion = ‘cref == 0'Could not find an entry for table or index with partition ID 491897996509184 in database 2 As you would expect a mini dump was produced at the same time, which detailed the stored procedure that was being run when the assertion occurred. In the case of such errors I would always advise you to contact us here at PSS so that we can analyze the dump and provide an explanation or solution. However this particular case reminded me of an interesting side issue where you can proactively help yourself, before contacting PSS. You should consider running SQL Server Best Practice Analyzer on your server. You can download it from here. We regularly see cases where the running of the tool could have identified known issues in advance. When you run the tool initially, it checks for updates to the tool itself, but more importantly it checks for updated configuration files. For your reference (and if you're nosey like me) you can look at the configuration file it has downloaded here: C:\Program Files (x86)\Microsoft SQL Server 2005 Best Practices Analyzer\EN\SqlBPA.config.XML (removing the x86 from the directory path if you don’t have a 64 bit installation of windows) Within PSS nowadays we add rules to this tool when we find interesting new issues or where we find common causes of problems that our customers experience. If you run the tool regularly you’ll pick up our latest updates, things that we in PSS think are important you should check for, and check for them automatically. A large number of the support cases that I work on contain known issues of configuration and the like which could be avoided or at least highlighted by this tool. The reason that I mention this now is that the tool currently contains a rule for a known issue with a driver from Dell which can cause random data corruptions which show up as assertions and errors similar to the one above. For reference the driver in question is LSI_SAS.SYS where the version is less than 1.21.26.01. If you notice
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error[36, 17, 145] occurred while attempting to drop allocation unit SQL Server > SQL Server Database Engine Question 0 Sign in to vote The following error message has been logging in SQL log 2-3 times during production hours in last 3 weeks . Error [36, https://blogs.msdn.microsoft.com/grahamk/2008/06/25/sql-server-assertions-and-dumps-a-typical-example-and-some-proactive-help/ 17, 145] occurred while attempting to drop allocation unit ID[] belonging to worktable with partition ID [] I have been monitoring Database to find out if any queires ,reports and stored procedure might be throwing this error in SQL log but I could not identify it . Would https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ae0e6f71-ff63-49ee-bcaf-c53fa4dea6e4/error36-17-145-occurred-while-attempting-to-drop-allocation-unit?forum=sqldatabaseengine you please help me How do I start investigation ? What would be impact on database perfomance when this error is occured ? Thanks Daizy Edited by Daizy Desai Thursday, September 27, 2012 7:24 PM Wednesday, September 26, 2012 9:49 PM Reply | Quote Answers 0 Sign in to vote Hi Daizy, Error [%d, %d, %d] occurred while attempting to drop allocation unit ID[] belonging to worktable with partition ID [], please try to install the latest SP(Services Pack) and Cumulative update to see if the problem goes away. The case is similar to you, please refer to: http://social.msdn.microsoft.com/Forums/is/sqldatabaseengine/thread/3c405637-5453-46ea-9e45-83da4055fe50 Please refer to: http://support.microsoft.com/kb/916086 . Regards, Amy PengAmy Peng TechNet Community Support
Marked as answer by Maggie LuoModerator Friday, October 05, 2012 1:16 AM Friday, September 28, 2012 3:10 AM Reply | Quote 0 Sign in to vote Hi, What is
inmy sql server logs and roughly correspond with periods of poor db performance. 03/05/2011 16:02:18,spid431,Unknown,Error [36 17 145] occurred while attempting to drop allocation unit ID 438356380090368 belonging to worktable with partition ID 438356380090368. 03/07/2011 14:42:18,spid333,Unknown,Error http://www.networksteve.com/forum/topic.php/Error_occurred_while_attempting_to_drop_allocation_unit_ID/?TopicId=49033&Posts=2 [36 17 145] occurred while attempting to drop allocation unit ID 438859152752640 belonging to worktable with partition ID 438859152752640. March 8th, 2011 8:22pm Please post the results of SELECT @@VERSION. I would suggest installing the latest SP and Cumulative update to see if the problem goes away. See: http://www.sqlteam.com/article/sql-server-versions Free Windows Admin Tool Kit Click here and download it now March 9th, 2011 7:50pm We had this exact problem when we were on SQL error occurred Server 2005 SP2 early builds when there was high tempdb activity + a mistimed job that updates statistics on a relatively large table in the middle of the day. After talking to Bob Ward at MSFT, it was identified that a resource monitor was trying to free up a cached plan that has a cursor, where it was trying to deallocate a worktable but gets stuck on a latch for an IAM page in tempdb. error occurred while The solution that worked for us was to change the schedule for the update stats job + reduced the load on tempdb. I would suggest you to look at the VirtualFileStats DMV and see the amount of IO you are doing against tempdb when compared to other databases. For us at the time of this issue, our tempdb IO activity was 90% of the total activity on the box. After few optimizations, we got it down to 50-60%. I am NOT sure if this really helps you but wanted to share some notes. March 9th, 2011 8:24pm I am fencing problem in mssql 2012 with enterprise edition.Please any one having suggetion. Please.Please share Free Windows Admin Tool Kit Click here and download it now March 5th, 2015 6:59am It does no good to post a followup question to a very old and answered thread, especially when you have a different environment. Start your own thread and post as much useful information about your environment as you can. There are sticky posts at the top of the forum that provide suggestions. March 5th, 2015 8:42am This topic is archived. No further replies will be accepted. Other recent topics Remote Administration For Windows. Easy remote access of Windows 10, 7, 8, XP, 2008, 2000, and Vista Computers Click here to find out m