Use the information in this appendix to select database shapes, or templates, for your planned databases.
Topics:
Review this information to help determine the database shape to use.
Oracle Database Appliance shapes define databases with parameters selected specifically to optimize performance on Oracle Database Appliance. In addition, these shapes help you to set up appropriate instance caging and to acquire an appropriate license.
Oracle Database Appliance enables you to consolidate many databases into a single system. Consolidation can minimize idle resources, maximize efficiency, and lower costs. By using instance caging in conjunction with Oracle Database Resource Manager (the Resource Manager), you can provide desired levels of service across multiple instances on a single Oracle Database Appliance.
Oracle Database Appliance shapes are already tuned for the size of each database instance workload. They are designed to run on a specific number of cores. Caging ensures that each database workload is restricted to the set of cores allocated by the shape, enabling multiple databases to run concurrently with no performance degradation, up to the capacity of Oracle Database Appliance. You can select database shape sizes larger than your current needs to provide for planned growth, which you accommodate later by adjusting System Global Area (SGA) and Program Global Area (PGA) sizes as well as the number of cores.
The Oracle Appliance Manager Configurator refers to the database sizing shapes as classes of databases.
Note:
Oracle strongly recommends that you use the Oracle Database Appliance shapes, because they implement best practices and are configured specifically for Oracle Database Appliance.
Choosing a Database Shape
Database shapes are configured specifically for the type of database workload that you want to carry out on your databases on Oracle Database Appliance. Choose the shape that best matches the common workload your databases perform (OLTP, DSS, In-Memory).
The database sizing tables provide shape names and sizing based on the number of CPUs and memory attributes for each type of database workload.
Identify the shape type that is appropriate to your database workload and hardware:
Use Oracle Database Appliance OLTP Database Shapes if your database workload is primarily online transaction processing (OLTP).
Use Oracle Database Appliance DSS database shapes if your database workload is primarily decision support services (DSS) or data warehousing.
Use Oracle Database Appliance In-Memory (IMDB) database shapes if your database workload can fit in memory, and can benefit from in-memory performance capabilities.
Use the database shape tables to help select the best shapes for your databases. When using these tables remember that:
The information in the tables assumes that you are creating disk backups. The information in the tables assume that you are creating local disk backups. Consider the space requirements for your database and the policy for local disk backups versus external backups. Typically, external backups have more space available for the database than local backups.
The log file size assumes three (3) REDO log groups for each instance with a log switch every 15 minutes when the system is running at full capacity.
Use Oracle Database Appliance OLTP Database Shapes if your database workload is primarily online transaction processing (OLTP).
Table E-1 Oracle Database Appliance OLTP Database Shape Sizes
| Shape | CPU Cores | SGA (GB) | PGA (GB) | Processes | Redo log file size (GB) | Log buffer (MB) |
|---|---|---|---|---|---|---|
|
odb1s |
1 |
2 |
1 |
200 |
1 |
16 |
|
odb1 |
1 |
4 |
2 |
200 |
1 |
16 |
|
odb2 |
2 |
8 |
4 |
400 |
1 |
16 |
|
odb4 |
4 |
16 |
8 |
800 |
1 |
32 |
|
odb6 |
6 |
24 |
12 |
1200 |
2 |
64 |
|
odb08 |
8 |
32 |
16 |
1600 |
2 |
64 |
|
odb10 |
10 |
40 |
20 |
2000 |
2 |
64 |
|
odb12 (X6-2M and X6-2L only) |
12 |
48 |
24 |
2400 |
4 |
64 |
|
odb16 (X6-2M and X6-2L only) |
16 |
64 |
32 |
3200 |
4 |
64 |
|
odb20 (X6-2M and X6-2L only) |
20 |
80 |
40 |
4000 |
4 |
64 |
Use Oracle Database Appliance In-Memory (IMDB) database shapes if your database workload can fit in memory, and can benefit from in-memory performance capabilities.
Table E-2 Oracle Database Appliance In-Memory Database Shape Size
| Shape | CPU Cores | SGA (GB) | PGA (GB) | In-Memory (GB) | Processes | Redo log file size (GB) | Log buffer (MB) |
|---|---|---|---|---|---|---|---|
|
odb1s |
1 |
2 |
1 |
1 |
200 |
1 |
16 |
|
odb1 |
1 |
4 |
2 |
2 |
200 |
1 |
16 |
|
odb2 |
2 |
8 |
4 |
4 |
400 |
1 |
16 |
|
odb4 |
4 |
16 |
8 |
8 |
800 |
1 |
32 |
|
odb6 |
6 |
24 |
12 |
12 |
1200 |
2 |
64 |
|
odb08 |
8 |
32 |
16 |
16 |
1600 |
2 |
64 |
|
odb10 |
10 |
40 |
20 |
20 |
2000 |
2 |
64 |
|
odb12 (X6-2M and X6-2L only) |
12 |
48 |
24 |
24 |
2400 |
4 |
64 |
|
odb20 (X6-2M and X6-2L only) |
20 |
80 |
40 |
40 |
4000 |
4 |
64 |
Use DSS database shapes if your database workload is primarily decision support services (DSS) or data warehousing.
Table E-3 Oracle Database Appliance DSS Database Shape Sizes
| Shape | CPU Cores | SGA (GB) | PGA (GB) | Processes | Redo log file size (GB) | Log buffer (MB) |
|---|---|---|---|---|---|---|
|
odb1s |
1 |
1 |
2 |
200 |
1 |
16 |
|
odb1 |
1 |
2 |
4 |
200 |
1 |
16 |
|
odb2 |
2 |
4 |
8 |
400 |
1 |
16 |
|
odb4 |
4 |
8 |
16 |
800 |
1 |
32 |
|
odb6 |
6 |
12 |
24 |
1200 |
2 |
64 |
|
odb8 |
8 |
16 |
32 |
1600 |
2 |
64 |
|
odb10 |
10 |
20 |
40 |
2000 |
2 |
64 |
|
odb12 (X6-2M and X6-2L only) |
12 |
24 |
48 |
2400 |
4 |
64 |
|
odb20 (X6-2M and X6-2L only) |
20 |
40 |
80 |
4000 |
4 |
64 |