July 26, 2011 at 6:26 pm
I'm trying to add new ranges to an existing partition and for several ranges I receive the message:
"LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page"
Other ranges split out just fine.
A little history on what has been done.
The database was torn page detection mode for the page verify, since discovering that I've changed it back to checksum and reindexed all of the tables as well as ran a checkdb which came back with no errors.
I've restored the database from a backup onto a new machine and I'm still getting the error so I don't believe it is a hardware issue. Very few tables have a LOB data type defined and I'm unable to determine which table it is having issues splitting out the data.
The partition range is on a unique identifier data type.
Any help would be great.
July 26, 2011 at 7:47 pm
Hi
What version of SQL are you running?
http://www.sqlskills.com/BLOGS/PAUL/category/LOB-data.aspx
Cheers
Jannie
July 26, 2011 at 9:42 pm
SQL 2008 R2 SP1
July 27, 2011 at 12:06 pm
Found the issue. One table has two indexes in the partition however the table itself was not in the partition. I moved the indexes out of the partition group and the split was able to complete without an more errors.
To find out which table had the issue I had to turn on IO stat and look at what the last table that it successfully touched before the error take it's object id and look for the next table that was greater. Would have been nice for MS to actually say what object it was on when the error occurred vs just outputting the page data.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply