The project involved in this article is done on a test machine, which is scaled according to the hardware capabilities of the real project.
There is an aviation analysis system, its user volume is about 20, its nature between OLTP and Datawarehouse, the use of ordinary server, Linux platform, physical memory for 4g,5 block disk.
The initial memory is planned for
Oracle system occupancy: 4g*80% =3.2g
System Reservation: 4g*20%=800m
PGA Occupancy: 4g*80%*20%=640m
SGA Occupancy: 4g*80%-pga_aggregate_target=2.56g
shared_pool:200m
redo_buffer:1m
larger_pool:100m-For late Rman, data migration preparation for improved efficiency
java_pool:0m--The data operation is set to 0 because the system user uses the Cmd method
db_buffer_cache:2g
The following code is 4 times times smaller than the above data
1. Set up the PGA
View Code
2. Setting the SGA
View CodeView Code
3. Set Shared_pool_size
View CodeView Code
4. Set Large_pool_size
View Code
5. Set Db_cache_size
View CodeView Codeext.: http://www.cnblogs.com/jerryxing/archive/2012/04/09/2439740.html
Oracle project that's the thing----memory planning