Oracle kernel function from which the problem is raised:
ksmdpg()
Deallocate variable PGA. Just free top PGA heap, the callback will free. the extents to the OSD.
Ref: Bug:1283286
Process state:
PROCESS STATE
-------------
Process global information:
process: 0, call: 0, xact: 0, curses: 0, usrses: 0
No process is allocated.
END OF PROCESS STATE
As seen above and included in your trace, the memory class of some chunks are "LGWR PIC ins ar" and similar. If you notice that sum of them is 5200 bytes, and they are freeable chunks. These chunks are leaked.
Also, there is no allocated process for LGWR. The most probably, you are closing the database.
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 6000"
Then, restart your database. This event disables space leaks less than 6000 bytes.
You can see the details at Metalink Note:39308.1 ORA-600 [723] "PGA memory leak"
Oracle kernel function from which the problem is raised:
ksmdpg()
Deallocate variable PGA. Just free top PGA heap, the callback will free. the extents to the OSD.
Ref: Bug:1283286
Process state:
PROCESS STATE
-------------
Process global information:
process: 0, call: 0, xact: 0, curses: 0, usrses: 0
No process is allocated.
END OF PROCESS STATE
As seen above and included in your trace, the memory class of some chunks are "LGWR PIC ins ar" and similar. If you notice that sum of them is 5200 bytes, and they are freeable chunks. These chunks are leaked.
Also, there is no allocated process for LGWR. The most probably, you are closing the database.
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 6000"
Then, restart your database. This event disables space leaks less than 6000 bytes.
You can see the details at Metalink Note:39308.1 ORA-600 [723] "PGA memory leak"
Oracle - Internals
Closed
Major
ORA-00600 [723]: Memory leak in LGWR.
Error code:
Oracle kernel function from which the problem is raised:
Process state:
PROCESS STATE ------------- Process global information: process: 0, call: 0, xact: 0, curses: 0, usrses: 0 No process is allocated. END OF PROCESS STATEPGA Heap dump:
Problem explanation:
As seen above and included in your trace, the memory class of some chunks are "LGWR PIC ins ar" and similar. If you notice that sum of them is 5200 bytes, and they are freeable chunks. These chunks are leaked.
Also, there is no allocated process for LGWR. The most probably, you are closing the database.
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 6000 bytes.
You can see the details at Metalink Note:39308.1 ORA-600 [723] "PGA memory leak"
Bug:
Bug:1125724 ORA-600[723] DURING SHUTDOWN