Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Prerequisites for the Oracle database setup

This topic describes the prerequisites for the Oracle database setup.

Required schemas

You need the following schemas for Oracle:

  • Portal content store
  • Reports data warehouse
  • ETL (ODI) master repository
  • ETL (ODI) work repository

Other database requirements

Ensure that the Oracle databases meet the following requirements:

  • The recommended setting for the NLS_LENGTH_SEMANTICS parameter for the reports data warehouse schema is CHAR.
  • Customers using non-English databases (such as Asian customers) should use the nchar character set. Customers using English databases (such as LATIN-1) can use the char character set.
  • The reports data warehouse schema type must align with the 

    The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    database in one of the following ways:
    • If you have one or more 

      The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

      databases using the char schema, the reports data warehouse must use the char schema.
    • If you have one or more 

      The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

      database using nchar schema, the reports data warehouse must use the nchar schema.
    • If you have multiple 

      The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

      databases and some use char and others use nchar schema, the reports data warehouse must use nchar schema.
      See the instructions in To determine the schema being used by the BMC Server Automation database for the schema being used by the 

      The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

      database.
      See the instructions in To determine the schema being used by the BMC BladeLogic Decision Support for Server Automation databasefor the schema being used by the reports data warehouse.
  • The character set of the schema type must match. For example, if the 

    The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    database uses LATIN-1, the data warehouse must use the same character set or its subset character set. If the 

    The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    database uses AL32UTF8, the data warehouse must use the same character set or its subset character set.
  • If you are using nchar schema, you must use a Unicode value of AL16UTF16 (NLS_NCHAR_CHARACTERSET=AL16UTF16).
  • On non-English locales, ensure that the value of the NLS_LANG parameter is set correctly. If this parameter does not exist, create it. For more information about creating and setting the value of this parameter, see the Oracle database documentation.

  • The global_names parameter for the Oracle instance where BMC BladeLogic Decision Support for Server Automation is located must be set to false to ensure that the database link name generated by the site addition utility is resolved correctly. (If the global_names parameter is not set to false, the primary site installation fails.)

    Note

    After you install the product, you can set this parameter to true if needed, as described in Setting global_names to true for Oracle databases.

To determine the schema being used by the BMC Server Automation database

  1. Log on to SQL Plus as any user (for example, system).

  2. Type the following commands:

     select data_type from user_tab_columns where table_name = 'SYSTEM_PROPERTY' and column_name like 'NAME' 

    If the schema is char type, VARCHAR2 is returned as the output. If the schema is nchar type, NVARCHAR2 is returned as the output.

To determine the schema being used by the BMC BladeLogic Decision Support for Server Automation database

  1. Log on to SQL Plus as any user (for example, system).

  2. Type the following commands:

    select * from user_tab_columns where table_name = 'BL_SITE' and column_name like 'NAME'

    If the schema is char type, VARCHAR2 is returned as the output. If the schema is nchar type, NVARCHAR2 is returned as the output.

To ensure that the BMC Server Automation database user has the Execute permission on these packages

  1. Log on to SQL Plus as SYS on the Oracle database instance where the 

    The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    user is located

  2. Run the following commands:

    Grant execute on dbms_job to <BMCBladeLogicDatabaseUser>
    Grant execute on dbms_lock to <BMCBladeLogicDatabaseUser>

    Where <BMCBladeLogicDatabaseUser> is the 

    The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    database user name.

To verify that the database is Unicode

  1. Log on to SQL Plus as any user (for example, system).

  2. Type the following command:

    select parameter, value from nls_database_parameters where parameter='NLS_CHARACTERSET'

    Verify that a Unicode value is returned (AL32UTF8 or AL16UTF16). If a non-Unicode value is returned, create a new Unicode database and specify a Unicode value of AL32UTF8 or AL16UTF16. For instructions, see the database software documentation.

Supported scenarios for secondary BMC Server Automation sites

If you plan to use a system arrangement in which a secondary site uses a different character set, refer to the following scenarios for guidelines on supported setups.

The following setup is supported:

  • Application Server 1 uses char.
  • Application Server 2 uses nchar.

  • The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    server 1 uses nchar.

The following setup is not supported:

  • Application Server 1 uses char.
  • Application Server 2 uses nchar.

  • The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

    server 1 uses char.

The second setup scenario is not supported because you cannot run ETL from an nchar database to a char database.

 

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