视频1 视频21 视频41 视频61 视频文章1 视频文章21 视频文章41 视频文章61 推荐1 推荐3 推荐5 推荐7 推荐9 推荐11 推荐13 推荐15 推荐17 推荐19 推荐21 推荐23 推荐25 推荐27 推荐29 推荐31 推荐33 推荐35 推荐37 推荐39 推荐41 推荐43 推荐45 推荐47 推荐49 关键词1 关键词101 关键词201 关键词301 关键词401 关键词501 关键词601 关键词701 关键词801 关键词901 关键词1001 关键词1101 关键词1201 关键词1301 关键词1401 关键词1501 关键词1601 关键词1701 关键词1801 关键词1901 视频扩展1 视频扩展6 视频扩展11 视频扩展16 文章1 文章201 文章401 文章601 文章801 文章1001 资讯1 资讯501 资讯1001 资讯1501 标签1 标签501 标签1001 关键词1 关键词501 关键词1001 关键词1501 专题2001
OracleKernel:Functionkglic&LibraryCacheLatch
2020-11-09 10:04:52 责编:小采
文档


Oracle Kernel : Function kglic & Library Cache Latch 有碰到此类问题的朋友可以一起参考一下本文章。

Oracle Kernel : Function kglic & Library Cache Latch 有碰到此类问题的朋友可以一起参考一下本文章。

以下是关于KGLIC函数的功能简要说明:

代码如下

1. kglic means Kernel Generic Library cache Iterate Chain (AFAIK), it's the function which is executed when you access most X$KGL tables.

2. kglic is the code which goes through the library cache and row cache to answer queries on various dictionary fixed views and tables. This is the function which returns data for the fixed views and tables that scan the sql area. Therefore, it was highly possible that such queries could also be coming from monitoring tools used by DBAs and they are not restricted to the two views specifically mentioned in the bug by Joan. Any monitoring job which looks at v$open_cursor would also use the kglic iterator.

与此相关的BUG,在10g中仍然存在,最后确认客户有较为频繁的查询访问v$sql视图,导致了严重的library cache的竞争。

以下BUG的影响版本为10.2.0.4,10.2.0.5,11.2.0.2 :

代码如下
Bug 9287616 - Accessing [G]V$SQL or [G]V$SQLTEXT_WITH_NEWLINES may be slow / takes a long time / latch contention (Doc ID 9287616.8)

下载本文
显示全文
专题