This documentation supports the 9.0 version of BMC Remedy ITSM Deployment.

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 the Oracle database instance on the same computer on which you plan to install BMC Remedy AR System.

  2. You do not require to install Oracle clients on the computer where BMC Remedy AR System server is installed. BMC Remedy AR System Server now uses JDBC to connect to remote\local database (and does not refer to tnsnames.ora ).

  3. Enable TCP/IP for the database.
  4. Confirm connection to your Oracle database.
    Contact your database administrator for more information.
  5. 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.

  6. Ensure that the database parameters listed in the following table and those described in Tuning an Oracle server are specified.

    Note:

    The following settings and size estimates must be used as a starting point. You should conduct benchmarks in your environment because sizing will vary depending on your workload mix, data volumes, and data composition. 

    ParameterSuggested value

    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

    statistics_level

    Typical

    timed_statistics

    True

    UNDO_RETENTION

    14400

    workarea_size_policy

    auto

    REDO log files

    Three (at least 1 GB each)

    NLS_LENGTH_SEMANTICS

    BYTE

    NLS_CHARACTERSET

    AL32UTF8

  7.  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;
  8.  Set the tablespace and temporary tablespace to at least the following minimum settings:

    ParameterSuggested value

    arsys

    2000 MB

    artmpf

    500 MB

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

  10. 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 11g, set the maximum SGA size and enable the database to automatically manage the internal memory structures of the SGA.
    For example, to change the SGA size to 1 GB, use the alter system set sga_target=1G scope=both command.
    Verify or set the following environment variables.

    Environment variableDescription

    NLS_LANG (Windows)

    Set NLS_LANG as a system environment variable value as per your database character set . For information about NLS_LANG and its usage, see the following notes from Oracle: 144808.1, 227330.1, 260192.1.

    LANG (UNIX)

    Specifies globalization settings.

  11. 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 1024M reuse;
    create temporary tablespace ARSTMPSPC tempfile 'C:\DB-DATA\SSIORA12\DATA\ARTEMP.dbf' size 512M 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. 

      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.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Andreas Mitterdorfer

    Please can you review the following:

    cursor_sharing

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

     

    In https://docs.bmc.com/docs/display/public/ars9000/ar.cfg+or+ar.conf+options+N-R

    the recommendation is EXACT so IMHO when preparing the DB the setting should be EXACT aswell. Please also review the information from ISS04512971 where we got confirmation that EXACT is the recommended setting with 9.0.

     

    Aug 19, 2015 08:35
  2. Jan Sierens

    The link  "Tuning an Oracle server" refers to a deleted page.

    Sep 23, 2015 03:21
  3. Nas Remedy

    Oracle 12c is not supported by Atrium Integrator, We can not connect to database using Database Connections wizard through AI console.

    Sep 28, 2015 06:08
    1. Hemant Baliwala

       Hi Nas,

      Hi,

      Oracle 12 c is supported. However, a RFE is created for creating Oracle Service name from the Wizard. For now please use the workaround disccused in in the following community post:

      https://communities.bmc.com/thread/135543?start=0&tstart=0

      Thanks,

      Hemant

      Sep 29, 2015 12:41