Oracle database installation and configuration best practices
You can either allow the BMC TrueSight Infrastructure Management Server installer to create the schema for Infrastructure Management in the Oracle database, or you can create the schema manually using scripts provided with the installer. For more information, see Installing the Infrastructure Management Server on Microsoft Windows with Oracle.
Oracle schema configuration
Each schema in an Oracle instance must have a unique Oracle database user that owns the schema. When you install the BMC TrueSight Infrastructure Management Server, the installer prompts you for the user who owns the schema for the current instance as shown in the following screen. Ensure that you enter a unique user for each BMC TrueSight Infrastructure Management Server instance that you install.
Oracle tablespace configuration
Additionally, each unique BMC TrueSight Infrastructure Management Server schema must be installed in separate data files and corresponding tablespaces in the Oracle Instance. The BMC TrueSight Infrastructure Management Server installer allows you to specify these criteria as shown in the following figure:
The BMC TrueSight Infrastructure Management Server installer requires remote connectivity to the Oracle instance and must be able to “connect as sysdba” remotely. You must validate this connectivity before trying to install the BMC TrueSight Infrastructure Management Server. BMC recommends that you install SQL*Plus or the Oracle Instant Client on the target BMC TrueSight Infrastructure Management Server and test/validate the Oracle database connectivity as “sysdba” from that server before starting BMC TrueSight Infrastructure Management Server installation. For more information, see Manually setting up an Oracle database.
Oracle listener configuration
You can configure Oracle so that each database instance has a unique Oracle listener, or a single listener that can support multiple database instances. BMC recommends that you designate a unique Oracle listener for each database instance. This isolates listener issues to a single instance. Additionally, high availability (HA) must be set up for the Oracle listeners and the databases.
Additional best practices for configuring and administering the Oracle database
The following are additional best practices when using Oracle as the database platform:
Create at least two Infrastructure Management users, one for data storage and one for data views. Consider a third “backend user” to manage issues like locked accounts.
- The backup and restore process must be executed by Infrastructure Management users.
Use BMC Database Recovery Management or an Oracle tool such as RMAN.
Enable archive logging.
Use Oracle Data Guard for disaster recovery.
- Use Oracle Storage Area Network (SAN).