Database Initialization Parameter Sizing for Oracle E-Business Suite Release 12

 Database Initialization Parameter Sizing 

section provides sizing recommendations based on the active Oracle E-Business Suite user counts. The following table should be used to size the relevant parameters:

Parameter Name	Development or Test Instance	11-100 Users	101-500 Users	501-1000 Users	1001-2000 Users
processes	200	200	800	1200	2500
sessions	400	400	1600	2400	5000
sga_target Footnote 1	2G	2G	2G	3G	14G
shared_pool_size	400M	600M	800M	1000M	2000M
shared_pool_reserved_size	40M	60M	80M	100M	100M
pga_aggregate_target	1G	2G	4G	10G	20G
Total Memory Required Footnote 2	~ 3 GB	~ 4 GB	~ 6 GB	~ 13 GB	~ 34 GB

General Notes on Sizing Table

• "Development or Test instance" refers to a small instance used only for development or testing, with no more than 10 users.
  
  
• The range of user counts provided above refers to active Oracle E-Business Suite users, not total or named users. For example, if you plan to support a maximum of 500 active Oracle E-Business Suite users, then you should use the sizing as per the range 101-500 users.
  
  
• The parameter values provided in this document reflect a small instance configuration, and you should adjust the relevant parameters based on the Oracle E-Business Suite user counts as listed in the table above.

Footnote 1

• The parameter sga_target should be used for Oracle 11g or 12c or 19c based environments. Also, it is not necessary to set the parameter undo_retention for 11g or 12c or 19c-based systems,  since undo retention is set automatically as part of automatic undo tuning

• Enabling the 11g or 12c Automatic Memory Management (AMM) feature is supported in Oracle E-Business Suite, and has been found to be useful in scenarios where memory is limited, as it will dynamically adjust the SGA and PGA pool sizes. 
• AMM is enabled by using the memory_target and memory_max_target initialization parameters. MEMORY_TARGET specifies the system-wide sharable memory for Oracle to use when dynamically controlling the SGA and PGA as workloads change. The memory_max_target parameter specifies the maximum size that memory_target may take. AMM has proven useful for small to mid-range systems as it simplifies both the configuration and management. However, many customers with large production systems have experienced better performance with manually sized pools (or large minimum values for the pools). 
• On Linux, Hugepages has resulted in improved performance; however, this configuration is not compatible with AMM. 
• For large mission-critical applications systems, it is advisable to set sga_target with a minimum fixed value for shared_pool_size and pga_aggregate_target.

Footnote 2

• The total memory required refers to the amount of memory required for the database instance and associated memory, including the SGA and the PGA. You should ensure that your system has sufficient available memory in order to support the values provided above. The values provided above should be adjusted based on available memory so as to prevent paging and swapping.