Database Initialization Parameter Sizing
This section provides sizing recommendations based on the active Applications user counts. The following table should be used to size the relevant parameters:
|
Parameter Name |
Development / Test Instance |
11 – 100 Users |
101 – 500 Users |
501 – 1,000 Users |
1,001 – 2,000 Users [1] |
|
Processes |
200 |
200 |
800 |
1200 |
2500 |
|
Sessions |
400 |
400 |
1600 |
2400 |
5000 |
|
db_block_buffers |
20000 |
50000 |
150000 |
250000 |
400000 |
|
db_cache_size [2] |
156M |
400M |
1G |
2G |
3G |
|
sga_target [3] |
1G |
1G |
2G |
3G |
14G |
|
undo_retention [4] |
1800 |
3600 |
7200 |
10800 |
14400 |
|
Shared_pool_size (csp) |
N/A |
N/A |
N/A |
1800M |
3000M |
|
Shared_pool_reserved_size (csp) |
N/A |
N/A |
N/A |
180M |
300M |
|
Shared_pool_size (no csp) |
400M |
600M |
800M |
1000M |
2000M |
|
Shared_pool_reserved_size (no csp) |
40M |
60M |
80M |
100M |
100M |
|
pga_aggregate_target [5] |
1G |
2G |
4G |
10G |
20G |
Total Memory Required [6] |
~ 2 GB |
~ 3 GB |
~ 6 GB |
~ 13 GB |
~ 25 GB |
The Development / Test instance refers to a small instance used for only development or testing in which no more than 10 users exist.
The range of user counts provided above refers to active Applications users, not total or named users. For example, if you plan to support a maximum of 500 active Oracle Applications users, then you should use the sizing per the range 101-500 users.
The parameter values provided in this document reflect a development / test instance configuration, and you should adjust the relevant parameters based on the Applications user counts (refer to the table above).
The CSP and NOCSP options of the shared pool related parameters refer to the use of cursor_space_for_time, which is documented in the common database initialization parameters section. The use of cursor space for time results in much larger shared pool requirements.
