客户反应alert.log以下警告一直出现:
KGL object name :create table cjb_3 as select a.xn,a.xq,a.xkkh,a.xh,a.xm,a.kcmc,a.qzxs,a.xf,a.cj,a.zscj,a.jd,a.bz,a.xgsj,a.xgs,a.cxbj,a.pscj,a.qmcj,a.sycj,a.bkcj,a.cxcj,a.kcxz,a.tj,a.tjbz,a.tzf,a.tzfjd,a.kcdm,a.cxxnxq,a.qzcj,a.fxbj,a.jf,a.kcgs,a.xsqr,a.jycj,a.jybkcj,a.bybkcj,a.sfkc,a.ysbkcj,b.cxcj1,b.cxcj2,b.cxcj3,b.cxcj4,b.cxcj5,b.cxcj6,b.cxcj7,b.cxcj8,b.cxcj9,b.cxcj10,b.cxdtcj,b.MjycxcjN,b.MjycxbkcjN from cjb_2 a left join (select xh,substr(xkkh,case when instr(xkkh,'-',1,3)<>0 then instr(xkkh,'-',1,3) else length(xk
KGL object name :create table cjb_2 as select a.*,case when (McjN=zpZ and (cxbj<>'0' and cxbj is not null) and '' is not null ) then '' when (McjN=zpZ and ('' is null) ) then cj when (McjN=bkcjZ and ('' is not null)) then '' when (McjN=bkcjZ and ('' is null)) then bkcj||'' when (McjN=cxcjZ and ('' is null)) then cxcj||'' when (McjN=cxcjZ and ('' is not null)) then '' end McjX ,case when (McjbkN=bkcjZ and bkcj is not null) then bkcj when (McjbkN=cxcjZ and cxcj is not null) then cxcj end McjbkX ,case when (M
Heap size 2814K exceeds notification threshold (2048K)
os:Redhat Linux
Db version: 10gR2 rac
查阅MOS
Symptoms
The following messages are reported in alert.log after 10g Release 2 is installed.
Memory Notification: Library Cache Object loaded into SGA
Heap size 2294K exceeds notification threshold (2048K)
Changes
Installed / Upgraded to 10g Release 2
Cause
A number of issues have been logged with these messages in 10GR2, many are
still open. These look like warning messages that should not cause the program
responsible for these errors to fail.
They appear as a result of new event messaging mechanism
and memory manager in 10g Release 2. The meaning is that the
process is just spending a lot of time in finding free memory
extents during an allocate as the memory may be heavily fragmented.
Real memory messages should be ORA-403x when a real memory problem
occurs.
Solution
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
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
故障解决。
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/30060321/viewspace-1374749/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/30060321/viewspace-1374749/