_kgl_large_heap_warning_threshold
hi,
Today Morning i have found that the message “Memory Notification: Library Cache Object Loaded Into SGA” is been written in alert log file.Last week this database has been upgraded to 10g.
To avoid these messages being generated, we need to adjust the size of a hidden initialization parameter “_kgl_large_heap_warning_threshold” to a high value or zero.
To find out a hidden parameter value in the database.
SQL> SELECT a.ksppinm “Parameter”,
2 b.ksppstvl “Session Value”,
3 c.ksppstvl “Instance Value”
4 FROM x$ksppi a, x$ksppcv b, x$ksppsv c
5 WHERE a.indx = b.indx AND
6 a.indx = c.indx AND
7 a.ksppinm LIKE ‘%kgl_large_heap%’;
Parameter
————————————————–
Session Value
————————————————–
Instance Value
————————————————–
_kgl_large_heap_warning_threshold
2097152
2097152
To modify this parameter:
login as sysdba
SQL> connect sys as sysdba
SQL> alter system set “_kgl_large_heap_warning_threshold”=8388608 scope=spfile ;
System altered.
SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP;
SQL> SELECT a.ksppinm “Parameter”,
2 b.ksppstvl “Session Value”,
3 c.ksppstvl “Instance Value”
4 FROM x$ksppi a, x$ksppcv b, x$ksppsv c
5 WHERE a.indx = b.indx AND
6 a.indx = c.indx AND
7 a.ksppinm LIKE ‘%kgl_large_heap%’;
Parameter
————————————————–
Session Value
————————————————–
Instance Value
————————————————–
_kgl_large_heap_warning_threshold
8388608
8388608
Mehraj,
Its good to mention the database release number. This error warning is there in 10201. From 10202, this limit is already increased to 50meg which doesn’t let it come pretty often as in 10201.
Nonetheless, its always better to check with support before attempting to change any undocumented parameter.
Cheers
Aman….
thankz for ur comment… yes its 10201