RE: X$ksmsp (OSEE 10.2.0.2 on Solaris 8)
- From: "Hallas, John, Tech Dev" <John.Hallas@xxxxxxxxxxxxxxxxx>
- To: <sac@xxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 26 Jun 2006 15:56:30 +0100
Whilst I was looking at x$ksmsp I came across the following link which
provides a useful summary of the x$tables and some interesting queries
against some of them.
http://www.stormloader.com/yonghuang/computer/x$table.html
Charles, in your database is there only 1 entry in total for that table
as I see many thousands of entries (same Oracle version but 2.9 Solaris)
_____
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Schultz, Charles
Sent: 26 June 2006 15:27
To: oracle-l@xxxxxxxxxxxxx
Subject: X$ksmsp (OSEE 10.2.0.2 on Solaris 8)
Granted that x$ksmsp is not documented and therefore subject to changes
from version to version (or patch to patch), I have an Oracle Support
Engineer telling me that one entry in ksmsp might actually show
fragmented memory in the case of a memory leak. My understanding, from
what I have gleaned from others much smarter than I, was that each row
of ksmsp showed one contiguous chunk of memory, be it small or large,
FREE or PERM (or something in between). The whole idea of a memory leak
causing ksmsp to report a fragmented chunk as one piece is a little
disturbing.
Can anyone corroborate or refute this?
Oracle Server Enterprise Edition 10.2.0.2
Solaris 8 (SunOS 5.8) 64-bit
charles schultz
oracle dba
aits - adsd
university of illinois
Other related posts:
