This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Configuring Oracle databases

This section describes the steps to configure your Oracle database before you install BMC Remedy Action Request (AR) System or any application in the BMC Remedy IT Service Management (ITSM) Suite.

Typically, Oracle database administrators create instances, directories, and groups, and they install the Oracle database and Oracle client before proceeding with the BMC Remedy AR System installation.

Recommendation

Review Performance tuning for BSM in preparation for performing this upgrade.

To prepare your Oracle database

  1. As a database administrator, install at least one instance of the Oracle database.
    You can install it on the same computer as the one on which BMC Remedy AR System is installed, or on a remote server that is networked to the computer on which you plan to install BMC Remedy AR System.

  2. Install Oracle clients on the AR System server.
  3. (UNIX only) Ensure that the administrator who is installing BMC Remedy AR System is a part of the database group.
  4. Enable TCP/IP for the database.
  5. Confirm connection to your Oracle database.
    Contact your database administrator for more information.
  6. For remote installations, install and configure the Oracle client on the same system on which you will install the AR System server.
  7. Set the BMC Remedy AR System data file size to at least 2 GB.

    Note

    For each additional product, add at least 2 GB to the data file size.

  8. Confirm that the database parameters listed in the following table and in Tuning an Oracle server are set.

    ParameterSuggested value

    memory_target

    3 GB (minimum 2 GB) for small database size.

    For Oracle recommendations based on database size, see Tuning an Oracle server .

    _b_tree_bitmap_plans

    False

    cursor_sharing

    FORCE (at least SIMILAR). If you set cursor_sharing to FORCE, you must also update
    the ar.cfg file.

    cursor_space_for_time

    False

    db_block_checking

    False

    db_file_multiblock_read_count

    0 (or do not set)

    LOG_BUFFER

    10485760

    OPEN_CURSORS

    500

    optimizer_dynamic_sampling

    2

    session_cached_cursors

    100

    statistic_level

    Typical

    timed_statistics

    True

    UNDO_RETENTION

    14400

    workarea_size_policy

    auto

    Sessions

    300

    Processes

    300

    Temporary tablespace

    1 GB

    Log files

    Three (512 MB each)

    REDO log files

    Three (at least 1 GB each)

    NLS_LENGTH_SEMANTICS

    BYTE

    NLS_CHARACTERSET

    AL32UTF8

    NLS_LANGUAGE

    AMERICAN

    NLS_TERRITORY

    AMERICA

    Note

    NLS_SORT must be derived from NLS_LANGUAGE.

  9. To prevent BMC Remedy AR System from reaching the size limit of the database, set your tablespaces with the AUTOEXTEND parameter to ON, by executing the following SQL statement as the system user:

    ALTER DATABASE DATAFILE '<OracleHome>/DATABASE/ARSYS' AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED;
  10. Set the tablespace and temporary tablespace to at least the following minimum settings:

    ParameterSuggested value

    arsys

    2000

    artmpf

    500

    These tablespace names may be different, depending on your environment.

  11. To avoid timeout errors during installation, set the System Global Area (SGA) minimum size to at least 1 GB (small database), 3 GB (medium database), or 6 GB (large database).
    For Oracle 10g or 11g, set the maximum SGA size and enable the database to automatically manage the internal memory structures of the SGA.
    Verify or set the following environment variables.

    Environment variableDescription

    NLS_LANG (Windows)

    Specifies globalization settings. For information about NLS_LANG and its usage, see the following notes from Oracle: 144808.1, 227330.1, 260192.1. If you are using the Oracle Instant Client, see step 13.

    LANG (UNIX)

    Specifies globalization settings.

    ORACLE_HOME

    Points to the directory in which the Oracle client is installed. Use the following value:
    $<ORACLEHOMEDirectoryPath>

    If you are using the Oracle Instant Client, see step 13.

    Note: The installer accepts the ORACLE_HOME path as a user input in UNIX.

    PATH

    (For Windows) Points to the bin directory of the Oracle client; for example, C:\oracle\product\10.2.0\client_1\bin. The bin directory contains the path to the Oracle binary files. Add the following value to the path: $ORACLE_HOME/bin

    Note: If you are using multiple versions of Oracle, ensure that the entry for the version you want to use appears before the others.

  12. (For Oracle Instant Client) Perform the following actions:
    1. Set the system path to the folder in which the Oracle Instant Client is located on the local computer.
    2. Set the ORACLE_HOME system variable to point to the folder in which the Oracle Instant Client is located on the local computer.
    3. Set the TNS_ADMIN system variable to point to the folder in which the correct tnsnames.ora file is located.

      Note

      By default, the Oracle Net Services configuration files are located in the OracleHome\network\admin directory. To change the default location, set the TNS_ADMIN environment variable to the appropriate value (for example, OracleBase\OracleHome\test\admin). The AR System suite installer accepts the value of the Database Client Home Path field only for UNIX installations. If the installer does not find the tnsnames.ora file in dbClientHomePath\network\admin or in the directory specified in TNS_ADMIN, it prompts you to enter the path in the AR System Server Database Information panel. If you provide a valid path, the installer sets the TNS_ADMIN environment variable in the arsystem.sh script. The installer accepts your input and sets the value for TNS_ADMIN only if you have Read permission for the tnsnames.ora file.

    4. Set the NLS_LANG system variable value to non-Unicode or Unicode.
    5. Create the following soft links that point to libclntsh.so.11.1:
      • libclntsh.so
      • libclntsh.so.10.1
    6. Create the following directories: ORACLE_HOME/bin and ORACLE_HOME/lib.
  13. Configure the tnsnames.ora file to ensure that the service name is the same as the entry name for the server on which you are installing BMC Remedy AR System; for example:

    COMPUTER1 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = computer1.xyzcompany.com)(PORT = 1521))
    )
    (CONNECT_DATA =
    (SERVICE_NAME = COMPUTER1)
    )
    )


    During the installation, you are asked for the database instance name, which should match the entry in the tnsnames.ora file (for example, MACHINEA).
    For more information about tnsnames.ora, see your Oracle documentation.

  14. Find the Connection Identifier in the tnsnames.ora file (located in the $ORACLE_HOME/network/admin folder).
    If multiple listeners are configured, locate the correct tnsnames.ora file in the correct $TNS_ADMIN value path.
    The following example shows an entry in tnsnames.ora:

    MyConnectionIdentifier =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))
        )
        (CONNECT_DATA =
          (SERVICE_NAME = ORCL.MYWORLD)
        )
      )
  15. Ensure that the Oracle listener is running and is configured correctly for the database.

To use a previously created tablespace in BMC Remedy AR System

For a BMC Remedy AR System server, you can use a tablespace that you previously created in Oracle.

Note

If you are using a RAC or ASM Oracle database, you must create tablespaces before you install BMC Remedy AR System. For more information about creating tablespaces in RAC or ASM Oracle databases, refer to your Oracle documentation.

Perform the following steps to use create a tablespace, user, role, set privileges for the role, and grant the role to the created user:

  1. In a SQL*Plus window, create the tablespace and the temporary tablespace; for example:

    create tablespace ARSYSTEM
    datafile 'C:\DB-DATA\SSIORA12\DATA\ARSYS.dbf' size 7000M reuse;
    create temporary tablespace ARSTMPSPC tempfile 'C:\DB-DATA\SSIORA12\DATA\ARTEMP.dbf' size 1000M reuse;
  2. Create a user; for example:

    create user aradmin identified by AR#Admin#
    default tablespace ARSYSTEM
    temporary tablespace ARSTMPSPC
    quota unlimited on ARSYSTEM;
  3. Create a role for the user you created in step 2; for example:

    create role ARole_arsys not identified;
  4. Set the privileges for the role; for example:

    grant alter session, create cluster, create 
    database link, create sequence, create session, create synonym, create 
    table, create view, create procedure, create trigger, query rewrite to 
    ARole_arsys;
  5. Grant the role to the user; for example:

    grant ARole_arsys to aradmin;
    go

Working with Oracle 12C database

When working with Oracle 12c database, consider the following:

  • Understand the Oracle architecture change in 12c. Please consult you Oracle DB administrator for architectural changes in Oracle 12c.  For more information refer to the Oracle documentation. 
  • The following options are available when you choose to use the Oracle 12c database: 
    • If want to use a non multi-tenant database, you must create a non-Container Database (CDB) database.
    • If you want to use a multi-tenant database, you must create a CDB with Pluggable Database (PDB) inside it.
  • If you are using non-CDB, no specific settings are required.
  • If you are using the CDB with Pluggable Database (PDB) inside it, perform the following steps before installing BMC Remedy AR System:
    1. Create the PDB. For example you could create a database called REMPDB. For more information, see Oracle documentation for Multitenant architecture.
    2. Register the PDB as service to the listener. For more information, see Oracle documentation for Multitenant architecture.
    3. Update the tnsnames.ora file with connection details of the registered service. This file is located at<Oracle_home>\network\admin. Following is the snippet of the entry you need to update. 

      REMPDB =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = <DB_server_host>)(PORT = <Listener port number>))
          (CONNECT_DATA =
            (SERVER = DEDICATED)
            (SERVICE_NAME = <Pluggable_database_service_name>)
          )
        )

      Note

      During installation choose Oracle service name option in the AR System Server User and Database Information panel. 

Related topics

Preparing to install on a Unicode database

ar.cfg or ar.conf options C-D for information about adding the Db-Case-Insensitive option to perform case-insensitive queries on Run If qualifications for active links, filters, and escalations.

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.

Comments