.ora-code.com

Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
X$ksmsp (OSEE 10.2.0.2 on Solaris 8)

X$ksmsp (OSEE 10.2.0.2 on Solaris 8)

2006-06-26       - By Schultz, Charles
Reply:     1     2     3     4     5     6     7     8     9     10     >>  

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



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>X$ksmsp (OSEE 10.2.0.2 on Solaris 8)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=2 FACE="Arial">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.</FONT></P>

<P><FONT SIZE=2 FACE="Arial">Can anyone corroborate or refute this?</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Oracle Server Enterprise Edition 10.2.0.2</FONT>

<BR><FONT SIZE=2 FACE="Arial">Solaris 8 (SunOS 5.8) 64-bit</FONT>
</P>

<P><B><FONT SIZE=1 FACE="Tahoma">charles schultz</FONT></B>

<BR><B><FONT SIZE=1 FACE="Tahoma">oracle dba</FONT></B>

<BR><B><FONT SIZE=1 FACE="Tahoma">aits - adsd</FONT></B>

<BR><B><FONT SIZE=1 FACE="Tahoma">university of illinois</FONT></B>
</P>
<BR>

</BODY>
</HTML>