Configuring the Database for PXE-Based Provisioning

This topic describes how to install the database schema and configure the database for BMC Server Automation.

• Prerequisites
• Required Files
• Required steps for all database platforms
• Additional steps for SQL Server Databases
• Additional steps for Oracle Databases

Prerequisites

• The database server must be available, with an installed operating system and installed and configured SQL Server or Oracle database.
• You must have network connectivity or direct access to the database server.

Required Files

The external-files.zip file for the version of BMC Server Automation that you are installing. (For example, 8xx-xxx-external-files.zip.)

Required steps for all database platforms

1. Copy the external-files.zip file to the database server.
2. Extract the external-files.zip file on the database server. The file contains all of the database scripts to create the BMC Server Automation database.
3. To continue configuring the database, go to one of the following sections:
   • #Additional steps for SQL Server Databases
   • #Additional steps for Oracle Databases

Additional steps for SQL Server Databases

The following instructions are specific to SQL Server 2008. If you are using an earlier version of SQL Server, you might observe minor differences. For more information, see Setting-up-a-SQL-Server-database-user-and-schema-for-BMC-Server-Automation.

1. Log on to SQL Server Management Studio.
2. Create a new database called BladeLogic (All lowercase is also acceptable. You must remember the value you specify.)
3. Create a new login called bladelogic. Use the following options:
   • Select SQL Server authentication with password bladelogic.
   • Do not enforce password policy.
   • Do not set SQL user account to expire.
   • Do not require the SQL user to change the password.
   • Set the Default Database to the value you used in Step 2.
4. For User Mapping, select the BladeLogic database.
   • For DB role membership, select db_owner.
5. In SQL Server Management Studio, create the following new query and run the query.
   ALTER DATABASE BladeLogic SET READ_COMMITTED_SNAPSHOT ON;
    The query prevents deadlocks.
6. Open a command prompt window and change to the sqlserver directory:
   cd <external-files_dir>/db_scripts/sqlserver

7. Run the following command:

   sqlserver_master.bat localhost* *<_database_name>_* *<_sql_login>_* *<_password>_

   For example:

   sqlserver_master.bat* *localhost BladeLogic bladelogic bladelogic

8. Make sure you see the following message indicating a successful run:

   SQL SERVER SCHEMA INSTALL COMPLETED

Additional steps for Oracle Databases

1. Set db_block_size to 8192.
2. Set processes to at least 200.
3. To ensure that you have the required permissions for a successful installation, one of the following must be true:
   • When you install the BMC Server Automation database, you must be the owner of the schema.

   • If your organizational policy does not permit you to own the schema, your user account must have the following grants:

     SELECT ANY TABLE
     UPDATE ANY TABLE
     INSERT ANY TABLE
     DELETE ANY TABLE
     CREATE ANY TABLE
     ALTER ANY TABLE
     DROP ANY TABLE
     SELECT ANY SEQUENCE
     SELECT ANY DICTIONARY
     EXECUTE ANY PROCEDURE
     CREATE VIEW
     

     You assign these grants to the bladelogic user that you create in the following steps.

4. In the Oracle_Install_Dir\oradata folder, create a folder called bladelogic owned by the Oracle user. (This folder becomes the container for the BladeLogic database.)
5. Open the following file in an editor: <external_file_path>\db_scripts\oracle\schema\create_oracle_instance.sql
6. Modify the file, replacing this path name: /space/oracle/db/oradata/bladelogic/with the following path name:
   • (Windows) <Oracle_install_dir>\oradata\bladelogic\

   • (UNIX and Linux) <Oracle_install_dir>/oradata/bladelogic\

     • The path name requiring the change occurs four times in the file.
     • Do not change other file names such as BLADELOGIC.ora and BLADELOGIC_INDEX.ora.
7. Start a command session. (In Windows, select Start > Run > cmd.)

8. Navigate to the Oracle scripts directory in the location where you extracted the external-files.zip file. For example:

   cd C:\Temp\bl_<version>\db_scripts\oracle\schema
9. Start SQLPlus: sqlplus /nolog
10. Connect as the sys user. For example: connect sys/<password>@bladelogic as sysdba
11. Run the database creation scripts: @create_oracle_instance.sql
     This step creates an instance of the new BMC Server Automation database schema. In the next step, you log on to the database as a different user and populate the schema.

12. Exit, change to the directory above the current one, (for example, C:\Temp\bl_<version>\db_scripts\oracle), and re-launch sqlplus:

    exit
    cd ..
    sqlplus /nolog
    
13. Connect as the newly created bladelogic user: connect bladelogic/sa@bladelogic
14. Turn on logging: spool create_bladelogic_schema.log
15. Start the database population scripts: start oracle_master.sql bladelogic bladelogic_index

16. Turn off spooling and exit:

    spool off
    exit
    
17. To view the log file that was created during the database installation, open the following file in Notepad or Wordpad: create_bladelogic_schema.log