Oracle Memory Management - Revision history

Stuart: /* Handy views to look at */

2014-09-16T13:28:23Z

‎Handy views to look at

Stuart: /* Handy views to look at */

2014-05-02T09:40:16Z

‎Handy views to look at

Stuart: /* How memory is used (assuming conventional path reads - not direct path and dedicated server) */

2014-05-02T09:39:39Z

‎How memory is used (assuming conventional path reads - not direct path and dedicated server)

Stuart: /* How memory is used (assuming conventional path reads (not direct path), dedicated server */

2013-03-29T17:38:22Z

‎How memory is used (assuming conventional path reads (not direct path), dedicated server

Stuart at 17:17, 29 March 2013

2013-03-29T17:17:06Z

Stuart: Created page with "Options are: * Leave it completely up to the database then just set memory_max_size and memory_target * Set minimum values for some components then set values for pga_aggregat..."

2013-03-29T16:53:18Z

Created page with "Options are: * Leave it completely up to the database then just set memory_max_size and memory_target * Set minimum values for some components then set values for pga_aggregat..."

New page

Options are:
* Leave it completely up to the database
then just set memory_max_size and memory_target
* Set minimum values for some components
then set values for pga_aggregate_target and/or sga_target
* Set maximum values for some components
then set values for things like sga_max_size
====Handy views to look at====
<pre>
V$SGAINFO
V$SGASTAT
V$SGA_DYNAMIC_COMPONENTS
</pre>

@@ Line 33: / Line 33: @@
 Startup overhead in Shared Pool           365946152 No
 Free SGA Memory Available                         0
 rows selected.

@@ Line 17: / Line 17: @@
 select * from v$sgainfo
 </pre>
 <pre>
 NAME                                          BYTES RESIZEABLE
@@ Line 35: / Line 36: @@
 rows selected.
 </pre>
 ====How memory is used (assuming conventional path reads - not direct path and dedicated server)====
 A user runs a query which either finds the blocks it needs already in the SGA or fetches the blocks<br />

@@ Line 13: / Line 13: @@
 </pre>
 ====How memory is used (assuming conventional path reads - not direct path and dedicated server)====
 A user runs a query which either finds the blocks it needs already in the SGA or fetches the blocks<br />

@@ Line 13: / Line 13: @@
 </pre>
-====How memory is used (assuming conventional path reads (not direct path), dedicated server====
+====How memory is used (assuming conventional path reads - not direct path and dedicated server)====
 A user runs a query which either finds the blocks it needs already in the SGA or fetches the blocks<br />
 needed from disk into the SGA.<br />

← Older revision		Revision as of 17:17, 29 March 2013
Line 12:		Line 12:
	V$SGA_DYNAMIC_COMPONENTS		V$SGA_DYNAMIC_COMPONENTS
	</pre>		</pre>
		+
		+	====How memory is used (assuming conventional path reads (not direct path), dedicated server====
		+	A user runs a query which either finds the blocks it needs already in the SGA or fetches the blocks<br />
		+	needed from disk into the SGA.<br />
		+	The desired rows/data is taken from those blocks in the SGA and pulled over to the PGA for sorting and/or grouping.<br />
		+	If more than a "reasonable amount" of memory is required then the sorting and/or grouping spills over to TEMP space on disk and ultimately returns the rows to the user.<br />
		+
		+	====References====
		+	[http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1137385000346840516 asktom]