Experience with setting _kgl_latch_count > 31
From: ca111026 <ca111026_at_gmail.com>
Date: Wed, 19 Aug 2009 01:35:54 -0700 (PDT)
Message-ID: <17c7e53f-cd15-4b2c-9bb5-f0d9ed5e1777_at_b25g2000prb.googlegroups.com>
Would you be able to share real-life experience with setting underscore parameter
_kgl_version_count to value more than 31? This parameter controls number of
child latches for library cache latch.
Date: Wed, 19 Aug 2009 01:35:54 -0700 (PDT)
Message-ID: <17c7e53f-cd15-4b2c-9bb5-f0d9ed5e1777_at_b25g2000prb.googlegroups.com>
Would you be able to share real-life experience with setting underscore parameter
_kgl_version_count to value more than 31? This parameter controls number of
child latches for library cache latch.
It is recommend to increase the value of _kgl_latch_count if instance
experiences issues
with library cache, for example:
http://www.ixora.com.au/q+a/library.htm
However Metalink Note 420308.1 states that as a result of bug 5508574 the instance may hang if the value of parameter is more than 31.
We are looking at increasing value of this parameter for database
running on
server with 24 CPU. Default value of the parameter is 29 (next prime
number after CPU count).
Received on Wed Aug 19 2009 - 03:35:54 CDT