Re: Illustra locking an Index ?

Hi Mark, Don't forget that Illustra uses No-Overwrite storage. That means that EVERY update to a row is, in effect, an 'update' in-place to the system columns of the 'Old' version of the row to tag it as deleted, followed by Insert of the 'New' version of the row (actually appended to the bottom of the table's file). This means that for every update, ALL indexes on that table must be updated to include the 'New' row. All the best, Rob Mark Brodell <brodell@nospam.teleport.com> wrote in article <01bc7dbf$91b958c0$30a43ace@brick.unival.com>... > We have some concurrancy problems in Illustra that we think we have tracked > down to a table/index level lock on an index. The confusing part is that > this is happening when the base table is being updated but the column(s) > being updated are not in the key OR the index. We are therefore confused as > to why we're seeing table level write locks on the index. > > Can anyone shed any light on under what circumstances Illustra 3.3 would > take out a table level lock on an index whose columns weren't being updated > ? > > TIA > > Mark > ( To email remove "nospam" from address. ) >