RE: Statspack (shared pool) memory leak
- From: "Henry Poras" <henry@xxxxxxxxxxxxxxx>
- To: <henry@xxxxxxxxxxxxxxx>, <daniel.wittry@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 21 Dec 2004 17:20:18 -0500
I ran it a bit more until I got a 4031, but it was because the =
shared_pool
free memory kept increasing.
Henry
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx =
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Henry Poras
Sent: Tuesday, December 21, 2004 5:00 PM
To: daniel.wittry@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Statspack (shared pool) memory leak
I just ran this script on a 10.1.0.2 database on Linux. Most loops lost =
=3D
41K of memory, but about every 5th to 10th loop, a large chunk of memory =
was
added. If I have a chance I'll look a bit more carefully.
Henry
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx =3D =
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Daniel Wittry
Sent: Tuesday, December 21, 2004 4:43 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Statspack (shared pool) memory leak
Oracle claims to have fixed the leak in 9.2.0.4 and 10g (Bug #3519807).
(Mark - you're running 9205 and you confirmed the leak) I reOpened my =
=3D
iTAR and will press them harder this time for a fix. Is anyone on OraDev =
=3D
reading this?
Interesting enough, we traced ADDM and it does not use the x$ksolsfts
structure, yet creates a horizontal structure for segment statistics =3D =
that
is deallocated when ADDM exits. Maybe OraDev knows it leaks?
The long and short of it seems to be: when select * from
v$segment_statistics is typed, 1400 bytes of shared pool goes poof! That
smells bad. Granted, there are cases where we can run the query in a =
=3D test
loop and not leak memory, but it is unpredictable, even on the same =3D
instance (and usually does leak).
__that's our findings
-----Original Message-----
From: Powell, Mark D [mailto:mark.powell@xxxxxxx]=3D3D20
Sent: Tuesday, December 21, 2004 12:57 PM
To: Daniel Wittry; oracle-l@xxxxxxxxxxxxx
Subject: RE: Statspack (shared pool) memory leak
I ran your script a dozen times or so (9.2.0.5 64 bit RAC on AIX 5.2) =
=3D and
sure enough 04031 errors starting poping up. Unfortunately I do not =3D =
have
any more time to look at this, but perhaps one of the board guru's will
look. I was wondering if you have brought this issue to Oracle support
attention?
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
