Comments on: HW enqueue contention with LOB

By: leosanil

leosanil — Wed, 02 Jul 2008 14:42:22 +0000

Yes, even with the fix in 10.2.0.4 we still have to set the event. Without setting the event the fix will not be in effect.

Your understanding w.r.t level is correct. It would be hard to suggest an optimal value for the level. I suggest you start with a small value which is close to the average size of your LOB data in a row.

By: eckes

eckes — Fri, 20 Jun 2008 15:56:44 +0000

Fix in 10.2.0.4 means, you still have to set the event? If I dont set one, it will not show any better wait times?

What will be a good number?

I guess if I have typically Lobs with n Chunks, setting the Value to “2*n” means that the number of requests to that lock will be cut in half. So I can control the number of wait events, however I have to be aware that the times the lock is taken for a single reclaim will be longer (but less often)?

What would be the Syntax to set that event? Does it need context and level like trace events?

ALTER SYSTEM SET Event=’44951, level 64′ SCOPE BOTH;

or something?

By: leosanil

leosanil — Thu, 22 May 2008 13:21:04 +0000

Yes, bug# 6376915 is fixed in 10.2.0.4.

For windows this bug is fixed in 10.2.0.3.0 Patch 15 available in 32-Bit Patch 6637235 and 64-Bit (x64) Patch 6637236.

By: eckes

eckes — Sat, 10 May 2008 02:01:00 +0000

I wonder why 6376915 is not available as a patch for windows. Also it looks like the fix is part of 10.2.0.4, but that is not available for win64… strange.