*** 2010-11-19 15:13:49.341
*** SESSION ID:(183.37172) 2010-11-19 15:13:49.325
******** ERROR: UGA memory leak detected 560 ********
******************************************************
HEAP DUMP heap name="session heap" desc=0xaf35e68
........
*** 2010-11-19 15:13:49.361
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [729], [560], [space leak], [], [], [], [], []
.........
*** 2010-11-19 17:29:13.324
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [729], [916], [space leak], [], [], [], [], []


*** 2010-11-20 07:52:06.840
*** SESSION ID:(344.15429) 2010-11-20 07:52:06.826
******** ERROR: UGA memory leak detected 544 ********
******************************************************
HEAP DUMP heap name="session heap" desc=0xaf02c78
.......
*** 2010-11-20 07:52:06.856
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [729], [544], [space leak], [], [], [], [], []
.......

[@more@]=========================
Note: For additional ORA-600 related information please read Note:146580.1

PURPOSE:
This article discusses the internal error "ORA-600 [729]", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.

ERROR:
ORA-600 [729] [a]

VERSIONS:
versions 7.0 to 10.1

DESCRIPTION:

A space leak has been detected in the User Global Area (UGA).

There is NO data corruption as a result of this error.

It is an internal memory housekeeping problem.

ARGUMENTS:
Arg [a] This is the number of bytes leaked

FUNCTIONALITY:
MEMORY COMPONENT

IMPACT:
PROCESS FAILURE - But only during logoff so impact is minimal.
NON CORRUPTIVE - No underlying data corruption.


SUGGESTIONS:

Event 10262 can be set to safely ignore small memory leaks.

Set the following in init.ora for example to disable space
leaks less than 4000 bytes:

event = "10262 trace name context forever, level 4000"

and stop and restart the database.

Repeated errors or large memory leaks can be diagnosed further by
sending the alert.log and trace files to Oracle support.

Known Issues:

Related Articles

Note:403584.1 Understanding and Diagnosing ORA-600 [729] Space Leak Errors

Known Bugs

NB Bug Fixed Description
9365381 12.1.0.0 ORA-600 [729] having called an external procedure followed by PMON dump
7499301 11.2.0.2, 12.1.0.0 Memory leak in XDB / ORA-600 [729]
6870937 10.2.0.4.1, 10.2.0.5, 11.1.0.7.1, 11.2.0.1 Small memory leak / OERI[729] using SHARED_CONTEXT_SENSITIVE RLS policy
6960489 10.2.0.4.1, 10.2.0.5, 11.2.0.1 OERI:729 in DMON
4689285 10.2.0.3, 11.1.0.6 UGA memory leak and AW corrupt after maintenance
3328558 10.1.0.5, 10.2.0.1 OERI[729] ... [space leak] can occur if EXP or EXPDP aborted
2295845 9.0.1.4, 9.2.0.2, 10.1.0.2 OERI:729 if TRUNCATE PARTITION / ALTER TABLE MODIFY COLUMN interrupted
2887209 9.2.0.7, 10.1.0.2 UGA memory leak / OERI:729 with failed shared database link connection
2678481 9.2.0.3, 10.1.0.2 OERI[729] possible on SHUTDOWN
2782196 9.2.0.4, 10.1.0.2 ORA-3106 / OERI:729 after CTRL-C of INSERT..SELECT via a DBLINK
2884469 9.2.0.4, 10.1.0.2 OERI[729] possible using literal replacement
2028564 9.0.1.4, 9.2.0.2, 10.1.0.2 ORA-7445 or OERI:17114 errors possible after OERI:729 - PMON may die
3216432 9.2.0.6, 10.1.0.2 PLSQL using recursive calls which open cursors may get OERI:KGIFLPUSH / 17278 / 17277
4451759 9.2.0.8 OERI:729 using session cached cursors with DB link
2537917 9.2.0.3 OERI:729 possible with XDB
1731079 9.0.1.4, 9.2.0.1 OERI:729 space leak possible
1712645 8.1.7.3, 9.0.1.1, 9.2.0.1 OERI:729 space leak possible if DROP COLUMN is interrupted
1674074 9.2.0.1 Leak of "ktatt" memory chunks possible (OERI:729) on failed creation of a TEMP segment
1366596 9.0.1.0 Leak of "kgbt" memory chunks possible (OERI:729) on failed creation of a TEMP LOB
2177050 8.1.7.4, 9.0.1.0 OERI:729 space leak possible (with tags "define var info" / "oactoid info")
1573524 8.1.7.2, 9.0.1.0 OERI:729 / OERI:kghxhdr1 using DEFERRED TRANSACTION PROPAGATION with AUDITING enabled
918272 8.0.6.2, 8.1.6.2, 8.1.7.0 OERI:729 memory leak when AUDIT_TRAIL=TRUE
744179 7.3.4.5, 8.0.5.2, 8.0.6.0, 8.1.5.1 OERI:729 from shared server using DB Links at logoff
690413 8.0.4.4, 8.0.5.2, 8.0.6.0 OERI:729 possible from failed direct export
410215 7.3.3.1, 7.3.4.0 ORA-600 [729] [493888], [SPACE LEAK] after DIRECT LOAD

-------------------------

Bug 4451759 - OERI:729 using session cached cursors with DB link [ID 4451759.8]
Modified 24-SEP-2008 Type PATCH Status PUBLISHED
Bug 4451759 OERI:729 using session cached cursors with DB link
This note gives a brief overview of bug 4451759.
The content was last updated on: 06-MAR-2006
Click here for details of each of the sections below.
Affects:

Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions < 10.1.0.2
Versions confirmed as being affected

* 9.2.0.6

Platforms affected Generic (all / most platforms affected)

Fixed:

This issue is fixed in

* 9.2.0.8 (Server Patch Set)

Symptoms:

Related To:

* Internal Error May Occur (ORA-600)
* Excessive CPU Usage
* Hang (Process Spins)
* ORA-600 [729]
* ORA-600 [17104]



* Database Link / Distributed
* SESSION_CACHED_CURSORS

Description

ORA-600 [729] can occur when using database links and session cached
cursors.

Workaround:
(event 10262 may avoid the trace files for the ORA-600 [729])
Do not use session_cached_cursors

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice.

References

Bug:4451759 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article