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. Second argument is the number of bytes leaked.
As seen in the UGA heap dump, there is a freeable chunk of define var info memory type. This chunk looks leaked.
Workaround:
There is no data corruption in this error, and can be safely ignore for small memory leaks by adding the following event to init.ora:
event = "10262 trace name context forever, level 500"
Then, restart your database. This event disables space leaks less than 500 bytes.
You can see the details at Metalink Note:31056.1 ORA-600 [729] "UGA Space Leak"
Bug:
Bug:2177050: ORA-600 [729] after application of the 8.1.7.3 patchset. The resulting trace file will include a memory dump which shows unfreed memory chunks with the tags "define var info" and/or "oactoid info".
Ref: Metalink Note:31056.1 ORA-600 [729] "UGA Space Leak"
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. Second argument is the number of bytes leaked.
As seen in the UGA heap dump, there is a freeable chunk of define var info memory type. This chunk looks leaked.
Workaround:
There is no data corruption in this error, and can be safely ignore for small memory leaks by adding the following event to init.ora:
event = "10262 trace name context forever, level 500"
Then, restart your database. This event disables space leaks less than 500 bytes.
You can see the details at Metalink Note:31056.1 ORA-600 [729] "UGA Space Leak"
Bug:
Bug:2177050: ORA-600 [729] after application of the 8.1.7.3 patchset. The resulting trace file will include a memory dump which shows unfreed memory chunks with the tags "define var info" and/or "oactoid info".
Ref: Metalink Note:31056.1 ORA-600 [729] "UGA Space Leak"
Error code:
Error code definition:
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. Second argument is the number of bytes leaked.
UGA Heap dump:
Problem explanation:
As seen in the UGA heap dump, there is a freeable chunk of define var info memory type. This chunk looks leaked.
Workaround:
There is no data corruption in this error, and can be safely ignore for small memory leaks by adding the following event to init.ora:
Then, restart your database. This event disables space leaks less than 500 bytes.
You can see the details at Metalink Note:31056.1 ORA-600 [729] "UGA Space Leak"
Bug:
Bug:2177050: ORA-600 [729] after application of the 8.1.7.3 patchset. The resulting trace file will include a memory dump which shows unfreed memory chunks with the tags "define var info" and/or "oactoid info".
Ref: Metalink Note:31056.1 ORA-600 [729] "UGA Space Leak"