Understanding and Diagnosing ORA-600 [729] Space Leak Errors_403584.1
Understanding and Diagnosing ORA-600 [729] Space Leak Errors (Doc ID 403584.1)
In this Document
Applies to:Oracle Database - Personal Edition - Version 7.1.4.0 to 12.1.0.1 [Release 7.1.4 to 12.1]Oracle Database - Enterprise Edition - Version 7.0.16.0 to 12.1.0.1 [Release 7.0 to 12.1] Oracle Database - Standard Edition - Version 7.0.16.0 to 12.1.0.1 [Release 7.0 to 12.1] Information in this document applies to any platform. ***Checked for relevance on 17-Jun-2014*** GoalThe purpose of this article is to assist Oracle customers in understanding ORA-600 [729] UGA Space Leak errors. This article should help you understand what a space leak error is and what to do when one is encountered.
SolutionWhat is a space (memory) leak?
Memory leak problems generally occur when Oracle is trying to free memory allocated to a process. The memory leak dump is generally discovered during session logoff, when Oracle frees the heaps that are allocated for the user process.
The memory is organized in to heaps and every heap consists of one or more extents. Each extent contains a series of contiguous memory chunks, and these chunks can be either FREE or ALLOCATED. The Generic Heap Manager takes care of allocating and deallocating the memory chunks, with the help of FREE LISTS and LRU LISTS.
1. FREE
When the process terminates, all of the memory that has been allocated for the process is automatically released. When the memory is released the allocated heaps are freed. Generally, when the heap is freed the only chunks that the process should identify as allocated are the PERMANENT chunks and FREE chunks on the freelist. If the process finds there are still FREEABLE or RECREATABLE chunks remaining, then the process has not properly deallocated the memory. This situation is considered a space leak. A space leak problem will generally capture the trace information and the heap dump. In the alert.log, the error will be reported as:
After the operating system and Oracle process header information you will see the following in the trace file:
How do I handle a space leak?
Step 1. Review the alert.log to verify the error and obtain the trace file information.
Below the operating system and Oracle process header information, you will see the following:
Step 3. Verify the leak was during session logoff.
4. Are you using Dedicated Server or Multi Threaded Server?
5. Can I ignore the leak?
Setting EVENT 10262: After the amount of bytes leaked has been determined to be minimal, and no other errors have been noted, you can choose to safely ignore the errors. Leaks up to 90,000 bytes in size are considered to be within the allowable range. In cases where the amount of bytes leaked is allowable and you do not want the errors to be reported in the alert.log file, set event 10262. This will stop reporting of the ORA-600 [729] error in the alert log file up to the specified number of bytes.
If the level is set to 1, space leak checking is disabled. This is not advised because large memory leaks will be missed. If the event is set to a value greater than 1, any space leak up to the number specified in the event is ignored.
If you find them, this bug is likely:
This issue is fixed in
ReferencesNOTE:19837.1 - OERR: ORA 4031 "unable to allocate %s bytes of shared memory ("%s","%s","%s")"NOTE:21235.1 - EVENT: 10262 "Do not check for memory leaks" - Reference Note NOTE:31056.1 - ORA-600 [729] "UGA Space Leak" |
|
|
- Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Personal Edition > Internals Errors (ORA-600 & ORA-7445) > Manageability & Memory Management
- Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Enterprise Edition > Internals Errors (ORA-600 & ORA-7445) > Manageability & Memory Management
- Oracle Database Products > Oracle Database Suite > Oracle Database > Oracle Database - Standard Edition > Internals Errors (ORA-600 & ORA-7445) > Manageability & Memory Management
|
|
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/17252115/viewspace-1260321/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-00600: internal error code, arguments: [729], [4280], [space leak]Error
- 處理Oracle記憶體洩露 ORA-00600 [729] [space leak]Oracle記憶體洩露
- Understanding and Diagnosing ORA-00600 [13011] Errors [ID 1392778.1]Error
- Understanding and Diagnosing ORA-00600 [12333] Errors [ID 389713.1]Error
- Understanding and Diagnosing ORA-00600 [12333] / ORA-3137 [12333] ErrorsError
- Python729Python
- GCHandle LeakGC
- WindowBlinds 2.0 (入門)?????? (729字)
- 如何理解Memory leak
- [Memory Leak] 1. console.log cause memory leak
- Understanding Service Types
- CF729B Spotlights 題解
- Understanding JSON SchemaJSON
- Understanding Delegated JavaScript EventsJavaScript
- Understanding Parallel Execution PlanParallel
- [翻譯] Understanding deletedelete
- Understanding RabbitMQ Exchange & QueueMQ
- Understanding Initialization Parameters (85)
- .net sql connection pool leakSQL
- Understanding Linux CPU statsLinux
- Understanding React `setState` 翻譯React
- Understanding the CREATE DATABASE Statement (69)Database
- Understanding Buffer Overflow Bugs
- Android memory leak using MATAndroid
- [Memory leak] 3. Garbage collection in Closure
- Hilbert Space
- Understanding HBase and BigTable 譯文
- 【譯】Understanding NodeJS Event LoopNodeJSOOP
- Understanding Swing’s Model (轉)
- 使用awr來分析session leak問題Session
- 關於session leak的問題分析Session
- ORA-600(kghfremptyds)和ORA-600(kghasp1)錯誤REM
- DIAGNOSING ORA-3113 ERRORS [ID 1020463.6]Error
- No space left on devicedev
- Tablespace Space Script
- 理解梅爾譜圖 Understanding the Mel Spectrogram
- Understanding SaltStack --Guided Book 官方文件GUIIDE
- Understanding Windows Communication Foundation ExtensibilityWindows