Setting up an Oracle database user and schema for BMC Server Automation

This topic provides instructions for setting up an Oracle user and database for the fresh installation of the BMC Server Automation database. For more information, see Minimum-software-requirements.

Use the create_oracle_instance.sql script to set up the database user (typically BLADELOGIC). In addition to creating the database user, this scripts performs the following tasks:

  • Creates the BLADELOGIC and BLADELOGIC_INDEX tablespaces

  • Grants the following privileges explicitly to the user account that you specify in the script: 

    CONNECT
    CREATE VIEW
    RESOURCE
    SELECT ANY DICTIONARY
    UNLIMITED TABLESPACE

    Note

    • If your company policy does not allow you to grant the RESOURCE privilege to BLADELOGIC, revoke the RESOURCE privilege and provide the following granular privileges instead:
      • CREATE TRIGGER
      • CREATE SEQUENCE
      • CREATE TYPE
      • CREATE PROCEDURE
      • CREATE CLUSTER
      • CREATE OPERATOR
      • CREATE INDEXTYPE
      • CREATE TABLE
    • If your company policy does not allow you to grant the UNLIMITED TABLESPACE privilege to BLADELOGIC, revoke the UNLIMITED TABLESPACE privilege and provide the following granular privilege on the relevant tabelspaces (BLADELOGIC and BLADELOGIC_INDEX) instead:
      Grant UNLIMITED QUOTA on <tablespace>

Recommendation

Use only Latin alphabet letters, numbers, and underscores (_) in database names. Do not begin database names with a number. Do not use hyphens (-). While database names with hyphens work in the BMC Server Automation system, they do not work in BMC BladeLogic Decision Support for Server Automation.

To set up an Oracle database user and schema

Warning
  • These tasks should be performed by a database administrator (DBA). Perform the steps in these tasks in the exact order in which they are described. If you are not using the following scripts to create the schema, refer to them to determine the privileges required.

  • BMC does not recommend, nor does it support database schema changes.

  1. Create the directory to be used for the tablespace for the new schema.
     BMC recommends creating a directory on a disk separate from the Oracle system tables located at .../oradata/<SID>.
  2. Copy install scripts from external-files.zip into the directory that you created for the tablespace. For details on external-files.zip, see Obtaining-the-installation-files.
     If you extract the entire contents of external-files.zip, the relevant scripts appear in the /db_scripts/oracle/ and /db_scripts/oracle/schema directories.
  3. Change (cd) to /db_scripts/oracle/schema.

  4. Modify the create_oracle_instance.sqlscript and change the path for data files to match the directory you created for the tablespace for the new schema.

    Note

    Be sure to change both the CREATE TABLESPACE and ALTER DATABASE commands. You must change the path in four places.

  5. Start SQL*Plus using a user name that has sysdba privileges. For example, you might enter the following commands:

    sqlplus /nolog
    SQL> connect sys/manager as sysdba

  6. Run the create_oracle_instance.sqlscript by using the following commands:

    SQL> @create_oracle_instance.sql
    SQL> exit
  7. Change (cd) to /db_scripts/oracle.

  8. Log on to the BMC Server Automation database by using the following command:
    sqlplus <bl_user>/<bl_pwd>@<bl_tns_entry>
    Replace the variables with the following values:

  9. Start a log and run the master script that corresponds to the character sets for which your database is configured.

    SQL> spool create_bladelogic_schema.log
    SQL> start <master_script.sql> <BL_DATA> <BL_INDEX>
    SQL> spool off

    Replace the variables with the following values:

  10. After executing the master script, check the create_bladelogic_schema.log file for errors.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*