Operations Center stores data in both embedded databases and databases that you create and configure using third-party tools.You’ll need to set up and configure the database to handle the following features:
Configuration Storage: define a database for Operations Center configuration data, version tracking, and to control connections to all databases configured for use with Operations Center, including the Event Data Store, Service Warehouse, Configuration Storage.
Dashboard: must be configured to use an external database. See Operations Center 5.6 Dashboard Guide for more information and configuration information.
Event Data Store: define a database for SNMP Integrator, Event Manager, and/or alarm suppression.
Service Warehouse: define a database to record alarm history and comments, historical performance and Service Level metrics. For more information about the data stored in the BSW, see the Operations Center 5.6 Service Warehouse Data Dictionary.
For these databases, the /OperationsCenter_install_path/database/samples directory contains individual directories for each of the supported databases. Within each directory is a Readme file that contains suggestions for assigning a default tablespace for managing performance and Service Level Agreement (SLA) data, suggestions for installing and configuring the database for use with the Service Warehouse, and scripts, which the database administrator should review for compliance and usefulness.
For information about calculating space requirements for the Operations Center database, see the Operations Center 5.6 Server Configuration Guide.
Database definitions, which are managed in the Operations Center console, establish configuration settings and other parameters required to establish a connection between the Operations Center server and the database.
Operations Center also supports connections to an external data source for limited management of service level agreements. For more information, see the Operations Center 5.6 Service Level Agreement Guide.