Note to customers:
~~~~~~~~~~~~~~~~~~
  This is an Oracle X$ table reference note which gives a summary
  description of the X$KSMLRU fixed view. This view exists in Oracle
  releases 7 through 8.1 but may change in future releases.

View:   X$KSMLRU
         [K]ernal [S]torage [M]emory Management
            Least recently used shared pool chunks
             [LRU] flushes from the shared pool

 Column          Type               Description
 --------        ----               --------
 ADDR            RAW(4|8)           address of this row/entry in the array or SGA
 INDX            NUMBER             index number of this row in the fixed table array
 INST_ID         NUMBER       8.x   oracle instance number
 KSMLRCOM        VARCHAR2(20)       Comment about type of allocation
 KSMLRSIZ        NUMBER             Size of the allocation in bytes
 KSMLRNUM        NUMBER             Number of items flushed from the shared pool
 KSMLRHON        VARCHAR2(32)       Name of the object being loaded
 KSMLROHV        NUMBER             Hash value of object being loaded
 KSMLRSES        RAW(4|8)           Session performing the allocation
                                     Join to  . SADDR


Notes:
  The contents of this view are ZEROED when it is queried and so it shows
  the largest allocations since the view was last queried.

  The view can be useful when looking for the cause of memory allocations
  in the shared pool. It is quite normal for Oracle to flush chunks of
  memory from the shared pool to make space for new allocations. However,
  on heavily concurrent systems the shared pool can become a point of
  contention if SQL is not well shared. This view can help show sessions
  and statements requesting the largest memory allocations.
  The important thing to watch for is entries which are showing large 
  values in KSMLRNUM as this indicates the number of items flushed to
  find a chunk of memory of size KSMLRSIZ. Under normal operation 
  where SQL it not fully shared this table will show entries with 
  KSMLRNUM set to 7 or 8 (as we flush in batches). If the figure is
  much higher than this then normal flushing is not finding space and
  is having to loop through the 'flush' code to find more space.

  If the entries are always from the same session then it may be
  useful to see what the offending session is doing (eg: running a
  literal SQL script)

  In Oracle8i this table cannot be selected from by anyone other than
  the SYS user.