Oracle Enterprise Manager Ops Center stores product data in an Oracle Database Enterprise Edition database. This database can be an embedded database installed on the same system as the Enterprise Controller, or a customer-managed database that is accessible to the Enterprise Controller system. Run the OCDoctor to check for basic database requirements.
A backup feature enables you to back up your environment. The backup feature supports an embedded or customer-managed database. If you are using a customer-managed database, you can also back up the database schema using the existing backup and recovery processes implemented by your database administrator.
Note:
If you plan to implement high availability for the Enterprise Controller, you must use a customer-managed database.
Use the following sizing guidelines to estimate the maximum size of the database based upon the number of assets managed:
Operational Data: 74 megabytes (MB) per asset.
Reporting Data: 166 MB per asset. Steady state is reached at 180 days when using the default rollup schedule. USERS tablespace (Reporting) is required when report attributes are enabled. Use one of the following methods to change the size of the reporting data:
Customize the amount of attributes shown in the Enterprise Controller.
Stop the report service, which will stop generating report data in the database.
See Report Service Configuration Properties for more information about the report service.
UCE Data: 4 gigabytes (GB) needed for 10 channels. 12 GB additional for disconnected mode. You will generally need 400 megabits (Mb) for each additional channel. In some cases, you might need up to 600 Mb for a channel.
Oracle Solaris and Linux operating system updates and provisioning use UCE data. A channel, or UCE channel, is a supported Oracle Solaris or Linux operating system distribution, such as an Oracle Solaris 10 on a SPARC platform.
Schema Backups: Each backup dump requires 40% of Enterprise Manager Ops Center Schema Size on the database server in the OC_DUMP_DIR directory location.
Embedded, or Ops Center Local, database: A maximum of seven (7) copies of the backup are kept online.
Customer managed database: The database administrator must manage the Oracle Enterprise Manager Ops Center dump directory backup content.
Archival: An embedded database does not run in archive mode. For a remote database running in archive mode, the size of the archive is set according to the redo logs size.
Table 3-1 shows the estimated database size for when 1000 assets and 100 assets are managed and 10 UCE channels are configured in connected mode.
Table 3-1 Estimated Database Size
| Use Pattern | Size for 1000 Assets (MB) | Size for 100 Assets (MB) |
|---|---|---|
|
SYSTEM tablespace |
1000 |
1000 |
|
UNDO tablespace |
2750 |
275 |
|
SYSAUX |
1200 |
1200 |
|
USERS tablespace (Operational) |
100000 (100 GB) |
10000 (10 GB) |
|
USERS tablespace (Reporting) |
230000 (230 GB) |
23000 (23 GB) |
|
USERS tablespace (UCE) |
4000 |
4000 |
|
TEMP |
2000 |
200 |
|
TOTAL DB Size |
340950 |
39675 |
|
Spaced Reserved for Backups |
954660 |
103600 |
The database size also depends on your retention policy of gathered data. The default retention is 180 days for a 24 hour sample.
When using an embedded (Ops Center local) database, the Enterprise Controller system must meet the requirements for an Oracle Database Enterprise Edition installation. You can improve the embedded database performance by using the following configuration:
Use the ZFS filesystem as your underlying database
Set the redo log files to a block size of 8K
Set the logbias=throughput
Separating the redo logs onto a separate zpool (a different underlying disk) will further improve the embedded database performance.
On Oracle Solaris 10 1/13 systems and Oracle Solaris 11 SRU 7.5 or later systems, the embedded database is Oracle Database 12c. Oracle Database 12c uses the Optimized Shared Memory (OSM) model of Oracle Solaris to implement Automatic Memory Management. OSM allows dynamic resizing of System Global Area (SGA) without restarting the instance.
On Oracle Solaris 10 systems prior to Oracle Solaris 10 1/13 and Oracle Solaris 11 SRU 7.5, Dynamic Intimate Shared Memory (DISM) allows a database to dynamically extend or reduce the size of the shared data segment. The embedded database is configured to use a minimum of 12 GB RAM using DISM (TOTALMEMORY in the response file.)
See the Related Resources for Scaling section for information about local database requirements.
You can use a customer-managed, or remote, Oracle database with Oracle Enterprise Manager Ops Center.
A remote database system must use a supported Oracle Database version. See the Related Resources for Scaling section for a list of supported database versions.
The network connection to the remote database should have a low latency.
Note:
If you are implementing high availability, the remote database system must be accessible for all of the Enterprise Controller nodes.
The recommended database memory size is 12 GB.
The following are the minimum initialization parameters to use when you create the database:
open_cursors=1000
pga_aggregate_target=0
processes=500
recyclebin=OFF
sga_target=0
See the Related Resources for Scaling section for detailed database requirements.