Memory Notification: Library Cache Object loaded into SGA Heap size 2098K exceeds notification thres
Memory Notification: Library Cache Object loaded into SGA
Heap size 2098K exceeds notification threshold (2048K)
出現原因:
These are 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.
這都是警告資訊不會因為這些錯誤資訊造成應用程式執行失敗.在oracle10gr2中是由於新的事件訊息機制和記憶體管理才出現的.
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. Fragmentation in memory is impossible to eliminate completely, however, continued messages of large allocations in memory indicate there are tuning opportunities on the application.
這個訊息意味著程式在記憶體呆能存在大量碎片的情況下在執行記憶體分配時花了很長的時間來尋找可用的記憶體空間.記憶體中的碎片不可能完全消除,然而在進行記憶體分配時持續出現這種訊息說明可能是時候對應用程式進行最佳化了.
The messages do not imply that an ORA-4031 is about to happen.
這個訊息並不意味著ora-4031錯誤會立刻出現.
解決方法:
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.
在oracle10g中有一個新的隱含引數來設定KGL堆大小警告閾值.這個引數在10gr1中沒有.當堆大小超過閾值時就會寫入警告資訊.
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.
將_kgl_large_heap_warning_threshold設定為一個合理的較高的值或為0可以阻止這些警告資訊.它的大小單位是byte.
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
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.
注意:在10.2.0.1中這個預設的閾值是2M.因此在有些程式環境中這些警告資訊經常出現.
In 10.2.0.2, the threshold was increased to 50MB after regression tests, so this should be a reasonable and recommended value.
在10.2.0.2中,這個預設的閾值增加到50M.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26015009/viewspace-1061039/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Android 《Notification》Android
- laravel NotificationLaravel
- influxdb報錯:cache-max-memory-size exceededUX
- Android中的NotificationAndroid
- Android O 新特性 — NotificationAndroid
- Flutter 通知(Notification)冒泡原理Flutter
- Android之Notification和RemoteviewAndroidREMView
- Notification桌面通知實踐
- User Notification Framework 框架的使用Framework框架
- Android 8 通知渠道(Notification Channels)Android
- oreo上的notification詳解
- [轉]Android 通知Notification 詳解Android
- library cache pin和library cache lock(一)
- library cache pin和library cache lock (zt)
- library cache pin和library cache lock(二)
- 近期使用10G時遇到的兩個問題:Memory Notification和ORA-3136
- Ant design的Notification原始碼分析原始碼
- Android 深入理解 Notification 機制Android
- 當Notification和Websocket遇到https、httpWebHTTP
- Library Cache最佳化篇(一)降低library cache lock和library cache pin的方法
- library cache lock和library cache bin實驗_2.0
- Oracle Library cacheOracle
- Flutter學習筆記(35)--通知NotificationFlutter筆記
- SAP QM Quality Notification的憑證流
- PWA(Progressive Web App)入門系列:NotificationWebAPP
- [20191211]Free SGA Memory Available.txtAI
- ORA-01144: File size (4224000 blocks) exceeds maximum of 4194303BloC
- Android 之 Notification 必須掌握知識點Android
- 瀏覽器語音桌面通知,Notification API瀏覽器API
- Android系統修改之Notification佈局修改Android
- 訊息通知(Notification)系統最佳化
- H5 notification瀏覽器桌面通知H5瀏覽器
- Notification之 – Android5.0實現原理(一)Android
- library cache pin(轉)
- [20240920]跟蹤library cache lock library cache pin使用gdb.txt
- [20240824]跟蹤library cache lock library cache pin使用gdb.txt
- 聊聊HTML5中的Web Notification桌面通知HTMLWeb
- SAP QM 在Quality Notification裡維護Internal Note
- SAP QM QM11顯示Quality Notification List