ORA-600 [729] UGA 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:


Bug# 6960489 See Note:6960489.8
OERI:729 in DMON
Fixed: 10.2.0.4.1, 10.2.0.5, 11.2

Bug# 6870937 See Note:6870937.8
Small memory leak / OERI[729] using SHARED_CONTEXT_SENSITIVE RLS policy
Fixed: 10.2.0.4.1, 10.2.0.5, 11.1.0.7.1, 11.2, 10.2.0.4.P07, 11.1.0.6.P06, 11.1.0.7.P01

Bug# 4689285 See Note:4689285.8
UGA memory leak and AW corrupt after maintenance
Fixed: 10.2.0.3, 11.1.0.6

Bug# 4451759 See Note:4451759.8
OERI:729 using session cached cursors with DB link
Fixed: 9.2.0.8

Bug# 3328558 See Note:3328558.8
OERI[729] ... [space leak] can occur if EXP or EXPDP aborted
Fixed: 10.1.0.5, 10.2.0.1

Bug# 3216432 See Note:3216432.8
PLSQL using recursive calls which open cursors may get OERI:KGIFLPUSH / 17278 / 17277
Fixed: 9.2.0.6, 10.1.0.2

Bug# 2887209 See Note:2887209.8
UGA memory leak / OERI:729 with failed shared database link connection
Fixed: 9.2.0.7, 10.1.0.2

Bug# 2884469 See Note:2884469.8
OERI[729] possible using literal replacement
Fixed: 9.2.0.4, 10.1.0.2

Bug# 2782196 See Note:2782196.8
ORA-3106 / OERI:729 after CTRL-C of INSERT..SELECT via a DBLINK
Fixed: 9.2.0.4, 10.1.0.2

Bug# 2678481 See Note:2678481.8
OERI[729] possible on SHUTDOWN
Fixed: 9.2.0.3, 10.1.0.2

Bug# 2537917 See Note:2537917.8
OERI:729 possible with XDB
Fixed: 9.2.0.3

Bug# 2295845 See Note:2295845.8
OERI:729 if TRUNCATE PARTITION / ALTER TABLE MODIFY COLUMN interrupted
Fixed: 9.0.1.4, 9.2.0.2, 10.1.0.2

Bug# 2177050 See Note:2177050.8
OERI:729 space leak possible (with tags "define var info" / "oactoid info")
Fixed: 8.1.7.4, 9.0.1.0

Bug# 2028564 See Note:2028564.8
ORA-7445 or OERI:17114 errors possible after OERI:729 - PMON may die
Fixed: 9.0.1.4, 9.2.0.2, 10.1.0.2

Bug# 1731079 See Note:1731079.8
OERI:729 space leak possible
Fixed: 9.0.1.4, 9.2.0.1

Bug# 1712645 See Note:1712645.8
OERI:729 space leak possible if DROP COLUMN is interrupted
Fixed: 8.1.7.3, 9.0.1.1, 9.2.0.1

Bug# 1674074 See Note:1674074.8
Leak of "ktatt" memory chunks possible (OERI:729) on failed creation of a TEMP segment
Fixed: 9.2.0.1

Bug# 1573524 See Note:1573524.8
OERI:729 / OERI:kghxhdr1 using DEFERRED TRANSACTION PROPAGATION with AUDITING enabled
Fixed: 8.1.7.2, 9.0.1.0

Bug# 1366596 See Note:1366596.8
Leak of "kgbt" memory chunks possible (OERI:729) on failed creation of a TEMP LOB
Fixed: 9.0.1.0

Bug# 918272 See Note:918272.8
OERI:729 memory leak when AUDIT_TRAIL=TRUE
Fixed: 8.0.6.2, 8.1.6.2, 8.1.7.0

Bug# 744179 See Note:744179.8
OERI:729 from shared server using DB Links at logoff
Fixed: 7.3.4.5, 8.0.5.2, 8.0.6.0, 8.1.5.1

Bug# 690413 See Note:690413.8
OERI:729 possible from failed direct export
Fixed: 8.0.4.4, 8.0.5.2, 8.0.6.0

Bug# 410215 See Note:410215.8
ORA-600 [729] [493888], [SPACE LEAK] after DIRECT LOAD
Fixed: 7.3.3.1, 7.3.4.0

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/110396/viewspace-1057146/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/110396/viewspace-1057146/