在alert日志中出现如下信息:
Thu Jan 27 14:35:16 2011
Memory Notification: Library Cache Object loaded into SGA
Heap size 3174K exceeds notification threshold (2048K)
Details in trace file /opt/app/oracle/admin/devdb/udump/devdb1_ora_18115.trc
KGL object name :select param, getpdbs1, getpdbs2,
dbms_swrf_report_internal.get_pctdiff(getpdbs1, getpdbs2) dgpds,
getps1, getps2,
dbms_swrf_report_internal.get_pctdiff(getps1, getps2) dgps,
gets1, gets2, getm1, getm2, scans1, scans2, scanm1, scanm2, mods1, mods2,
usage1, usage2
from (select sp1.param param,
sp1.gets/:dbtime*1000000 getpdbs1, sp2.gets/:dbtime2*1000000 getpdbs2,
sp1.gets/:ela getps1, sp2.gets/:ela2 getps2,
sp1.gets gets1, sp2.gets gets2,
sp1.get
Oracle10g中,在load较大的对象进library cache中时,会记录以上警告。在版本10.2.0.1中,这个定义大对象的阈值是2M,这是有隐含参数_kgl_large_heap_warning_threshold指定的,如果系统中需要load很多大对象,又不想在alert中看到太多这类的警告信息,可以修改该参数:
SQL> alter system set "_kgl_large_heap_warning_threshold"=8388608 scope=spfile;
参数值以字节为单位,设置完后需要重启实例才能生效。
从10.2.0.2起,这个参数的默认值被修改为50M.
下面是oracle上的metalink信息:
Memory Notification: Library Cache Object Loaded Into Sga
In 10g we have a new undocumented parameter that sets the KGL heap size warning threshold. This parameter was not present in 10gR1.Warnings are written if heap size exceeds this threshold.
Set _kgl_large_heap_warning_threshold to a reasonable high value or zero to prevent these warning messages. Value needs to be set in bytes.
If you want to set this to 8192 (8192 * 1024) and are using an spfile:
(logged in as "/ as sysdba")
SQL> alter system set "_kgl_large_heap_warning_threshold"=8388608 scope=spfile ;
SQL> shutdown immediate
SQL> startup
SQL> show parameter _kgl_large_heap_warning_threshold
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
_kgl_large_heap_warning_threshold integer 8388608
If using an "old-style" init parameter,
Edit the init parameter file and add
_kgl_large_heap_warning_threshold=8388608
NOTE: The default threshold in 10.2.0.1 is 2M. So these messages could show up frequently in some application environments.
In 10.2.0.2, the threshold was increased to 50MB after regression tests, so this should be a reasonable and recommended value. If you continue to see the these warning messages in the alert log after applying 10.2.0.2 or higher, please contact Oracle Support Services for further investigation of any possible shared pool problems.