TUNING THE LARGE POOL
FOR
RMAN
SUCCESSFUL CUSTOM BR/DR/BC MODELS
NYOUG MEETING, DECEMBER 2008
ANTHONY D NORIEGA
[email protected]
ADN R & D www.adnmis.com
Speaker Qualifications
Independent Consultant, ADN
Speaker at NYOUG meetings
24 years of IT experience
18 years of Oracle experience, 13 as a DBA
RMAN experience with Oracle8i,9i, 10g, and 11g, since 1999.
BS Systems Engineering, Universidad del Norte, 1987.
MS Computer Science, NJIT, 1993
PhD CIS candidate, NJIT, 1997
MBA MIS, Montclair State University, 2006
College Math Professor and former HS Math Teacher Principal.
Objectives
Provide a concise approach to tune the
Large Pool for RMAN
Analyze and compare Oracle
recommendations and custom settings
Present a robust approach to optimize
RMAN time and storage space
Derive a series of technical arguments
and useful rules to attain a BR/BC/DR
optimization methodology.
Large Pool: Memory Structures
Server Server Background
PGA PGA PGA
Process Process Process
Buffer
Java Redo SGA
Cach
Pool Buffer
e
Shared Stream Large
s Pool
Other
Pool Pool
Server PGA Background PGA
Process Process
Large Pool Purposes
Session memory for the shared server and
the Oracle XA interface (used where
transactions interact with more than one
database)
I/O server processes
Oracle Database backup and restore
operations
Used by backup process for disk I/O
buffers.
RMAN Reliability
Based on experimental gathering RMAN
tasks are more reliable with a Large pool
sized with Oracle recommended settings.
RMAN tasks tend to improve performance
with higher Large Pool settings.
Production Environment
Linux 4-node RACs, 9i and 10g
SAN architecture using Symantec
(Veritas) Netbackup
MPP (Linux Intel 64-bit 8/16 dual-
core processor RH Linux servers).
Oracle RAC and Data Guard in place
(MAA).
Incremental backup level 0 mostly.
Block Change Tracking
(Oracle10g/11g)
Oracle-Recommended Settings
According to Oracle Corporation, the
recommended setting for the Large Pool
Size is 16M.
So, your init.ora parameter should read:
LARGE_POOL_SIZE=16M
fast_start_mttr_target=900
Custom Settings
Some of the custom settings are;
Third-Party
(Veritas Netbackup including both RAC databases and Standalone Databases)
LARGE POOL SIZE RELIABILITY PERFORMANCE
4M Best Decreased
8M Better Average
16M Average Improved
High-Value Expected Better
* e.g., 32M-180M, 180M-2G +
Custom Settings
With ASM and File System Databases
LARGE POOL SIZE RELIABILITY PERFORMANCE
4M Improved Decreased
8M Better Average
16M Average Improved
High-Value Expected Better
* e.g., 32M-180M, 180M-2G +
Shared Segment and LP Size
Analogy relating Large Pool and Shared segment sizes
LARGE POOL SIZE SHARED SEGMENT USED
4M
8M
16M
High-Value *
* e.g., 32M-180M, 180M-2G+
Storage Space and Time
Storage Space and Time
Storage Space and Time
Backup Size and Duration
Duration
Size
t0
4M 8M 16M 2G+
Relating the Large pool size and backup size and duration
Duration
Size
RMAN Compatibility Table
Oracle By Version
VERSION LARGE POOL REMARKS
Oracle 8i NO N/A
Oracle9i YES Dynamic Parameter, BR disk buffers,
Parallel Execution Message Buffer,
No LRU, Optional. Defaults to 0.
ksfqxcre internal shared memory
allocation error
Oracle10g YES Like 9i. Enhanced for Shared Server
Oracle11g YES Better satisfied segment requests
than using shared pool.
Faster parallel query execution.
Automatic Memory Management.
Oracle By Version
VERSION LARGE POOL REMARKS
Oracle9i YES Dynamic Parameter, BR disk buffers,
Parallel Execution Message Buffer,
No LRU, Optional. Defaults to 0.
ksfqxcre internal shared memory
allocation error
Oracle recommended setting: 8M
300 KB to at least 2 GB (actual
maximum is operating system-
specific)
About Oracle9i Large Pool
SELECT POOL, NAME, SUM(BYTES)
FROM V$SGASTAT
WHERE POOL LIKE '%pool%'
GROUP BY ROLLUP (POOL, NAME);
POOL NAME SUM(BYTES)
----------- -------------------------- ----------
large pool PX msg pool 38092812
large pool free memory 299988
large pool 38392800
….
….
Oracle By Version
VERSION REMARKS
Oracle10g Dynamic Parameter, BR disk buffers (Oracle
allocates buffers that are a few hundred kilobytes)
Parallel query, Parallel Execution Message Buffer
No LRU and no aging out of pool
Optional.
Specified LARGE_POOL_SIZE value a minimum
value for the memory pool (allocation heap).
300 KB to at least 2 GB (actual maximum is operating
system-specific)
Oracle By Version
VERSION REMARKS
Oracle11g Dynamic Parameter, BR disk buffers (Oracle
allocates buffers that are a few hundred kilobytes)
Parallel query, Parallel Execution Message Buffer
No LRU and no aging out of pool
Optional.
Defaults to 0. Minimum Value 300K.
30M recommended for about 100 sessions (shared server,
about 200-300k/session).
For effective sort usage of LP, set sort_area_size and
sort_area_retained_sime to same value.
Practical in Automatic Memory Management.
Oracle11g Dynamic Sizing
V$MEMORY_CURRENT_RESIZE_OPS: current memory resize operations
(both automatic and manual) in progress.
V$MEMORY_DYNAMIC_COMPONENTS: current sizes of all dynamically
tuned memory components, including SGA and PGA.
V$MEMORY_RESIZE_OPS: last 800 completed memory resize operations
(both automatic and manual), no current operations.
V$MEMORY_TARGET_ADVICE: tuning advice for the MEMORY_TARGET
initialization parameter.
V$SGA_CURRENT_RESIZE_OPS: current SGA resize operations in
progress, i.e., a grow or a shrink of a dynamic SGA component.
V$SGA_RESIZE_OPS: last 800 completed SGA resize operations. No
current operations.
V$SGA_DYNAMIC_COMPONENTS: dynamic components in SGA, summary
of all completed SGA resize operations since startup.
V$SGA_DYNAMIC_FREE_MEMORY: amount of SGA memory available for
future dynamic SGA resize operations.
Sample RMAN Shell
RMAN
Backup
shell for
Oracle
Instances
Studied
(Without
a
Recovery
Catalog)
Backup Size and Duration
RMAN Backup Duration for Oracle Instances
Studied (With a Recovery Catalog)
Backup Size Duration Line Chart
Sample Shell
RMAN
Backup
shell for
Oracle
Instances
Studied
(With a
Recovery
Catalog)
Backup Size and Duration
RMAN Backup Duration for Oracle Instances
Studied (With a Recovery Catalog)
A Simple RMAN Regression Model
RMAN Configuration
Session Long Operations
Business Considerations
Overall Preparedness for any RMAN
process.
Disaster Recovery (DR)
Business Continuity (BC)
Backup and Recovery (BR)
SDLC
Quality Assurance
Backup set approach
Archived reo log backup policy
Retention policy strategy.
Concluding Remarks
The Large Pool Size Setting could affect
BR/DR/BC Processes, involving both
reliability and performance.
Large Pool Size is a factor when
Correlating database size/backup size
and duration.
The large pool size is directly
proportional to the backup size and
inversely proportional to the backup
duration.
