RE: X$ksmsp (OSEE 10.2.0.2 on Solaris 8)

Charles,
 
I agree that a row in x$ksmsp should equal a single memory chunk - but is it 
possible that there is a chunk with an outrageous value?  I don't recall that 
particular case, but I have seen  x$ksmsp sum to values significantly larger 
than the size of the SGA.
 
In addition, I have also had significant performance issues on a production 
system when selecting on this table in a very busy system which is severely 
fragmented.
 
Cheers,
Duncan.
 
Duncan Lawie 
DBE - Oracle.

"There will always be plenty of things to compute in the detailed affairs of 
millions of people doing complicated things."  -- Vannevar Bush, As We May 
Think; Atlantic Monthly - July 1945.


  _____  

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Schultz, Charles
Sent: 26 June 2006 15:59
To: Hallas, John, Tech Dev; oracle-l@xxxxxxxxxxxxx
Subject: RE: X$ksmsp (OSEE 10.2.0.2 on Solaris 8)


Sorry, let me clarify. We have thousands of entries in ksmsp as well, but I was 
under the impression that 1 row = 1 contiguous chunk. Sorry for the confusion.

  _____  

From: Hallas, John, Tech Dev [mailto:John.Hallas@xxxxxxxxxxxxxxxxx] 
Sent: Monday, June 26, 2006 9:57 AM
To: Schultz, Charles; oracle-l@xxxxxxxxxxxxx
Subject: RE: X$ksmsp (OSEE 10.2.0.2 on Solaris 8)



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 
<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 

 


==============================================================================
Please access the attached hyperlink for an important electronic communications 
disclaimer: 

http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================

Other related posts: