This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Preparing your Oracle database before you install the AR System server

This section describes the steps you should perform with your Oracle database before you install BMC Remedy AR System or any application in the BMC Remedy IT Service Management Suite. The following topics are provided:

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.

Note

BMC highly recommends that you review Performance tuning for BSM for other recommendations about tuning your Oracle database in preparation for performing this upgrade. This section includes recommendations for:

  • Small, medium, or large Oracle databases
  • Cursor sharing
  • Cost-Based Optimizer
  • CLOB storage
  • Case-insensitivity
  • Diagnostics

To prepare your Oracle database

  1. Install at least one instance of the Oracle database. (Only your database administrator can create database instances.)
    You can install it on the same computer where the BMC Remedy AR System is installed, or on a remote server that is networked to the computer where you plan to install BMC Remedy AR System.
  2. Install Oracle clients on the AR System server.
  3. (UNIX only) Make sure that the administrator who is installing BMC Remedy AR System is a part of the database group.
  4. Enable the TCP/IP Protocol 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 where 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 database parameters listed in the following table and in the Tuning an Oracle server topic are set.

    ParameterSuggested Value

    memory_target

    3GB (at least 2 GB)

    _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

    3 (512 MB each)

    REDO log files

    3 (at least 1 GB each)

    NLS_LENGTH_SEMANTICS

    BYTE

    NLS_CHARACTERSET

    AL32UTF8

    NLS_LANGUAGE

    AMERICAN

    NLS_TERRITORY

    AMERICA

  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 table space and temporary table space to at least the following minimum settings:

    ParameterSuggested Value

    arsys

    2000 MB

    artmpf

    500 MB

    These tablespace names may be different depending on your environment.

  11. To avoid time-out 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, BMC Software recommends setting the maximum SGA size and enabling 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.
  12. 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 14.

    LANG (UNIX)

    Specifies globalization settings.

    ORACLE_HOME

    Points to the directory where the Oracle client is installed. Use this value: $<ORACLEHOMEDirectoryPath>

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

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

    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, make sure that the entry for the version you want to use appears before the others.

  13. When using the Oracle Instant Client, complete the following steps:
    1. Set the system path to the folder where the Oracle Instant Client is located on the local computer.
    2. Set the ORACLE_HOME system variable to point to the folder where the Oracle Instant Client is located on the local computer.
    3. Set the TNS_ADMIN system variable to point to the folder where 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, you can 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 permissions on the tnsnames.ora file.

    4. Set the NLS_LANG system variable value for 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 directory structure as follows: ORACLE_HOME/bin and ORACLE_HOME/lib.
  14. Configure the tnsnames.ora file to make sure 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, and it should match the entry in the tnsnames.ora file (for example, MACHINEA).
    For more information about tnsnames.ora, see your Oracle documentation.

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

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

Setting up a previously created tablespace

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 installing BMC Remedy AR System. For more information about creating tablespaces in RAC or ASM databases, refer to your Oracle documentation. 

To use a previously created tablespace in BMC Remedy AR System

  1. In a SQL*Plus window, create the tablespace and 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#
    defaulttablespace ARSYSTEM
    temporary tablespace ARSTMPSPC
    quota unlimited on ARSYSTEM;
  3. Create a role for the user you created in step 2 above. 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

Where to go from here

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

  1. Charles Mousseau

    For the Oracle Instant Client, one library is not installed in the directory where the code looks for it, and a soft link should be created to let it use the library (UNIX/Linux).

     

    1. If it is Unix/Linux, we need to create softlink for one of the library file
    2. Create Directory structure as lib bin network/admin under /opt/oracle/11gR2 if not done laid down by installer [/opt/oracle/11gR2 is treated as ORACLE_HOME here]. Put all library files under lib and bin. Create tnsnames.ora under network/admin
    Sep 27, 2013 10:53
  2. Chris Tilley

    I noticed in the create tablespace instructions, there is a space included at the end of the datafile file name.  Is this a typo or intentional?

    refer to this line:

    datafile 'C:\DB-DATA\SSIORA12\DATA\ARSYS.dbf 'size 7000M reuse;
    Jan 05, 2015 08:13
    1. Bhakti Paranjpe

      Hello Chris,

      Thank you for your comment. There should not be a space at the end of the datafile file name. I have updated the content.

      Thanks,
      Bhakti

      Jan 06, 2015 03:22
  3. Volker Scheithauer

    I've executed these commands, but the ARS server fails to start:

    --------------------------------------------------------------------------------------------------------------------------------

    alter session set "_ORACLE_SCRIPT"=true;

    commit;

    Create temporary tablespace ARTemp

      TempFile '/app/oracle/oradata/CLM/datafile/ARSystem.tmp' SIZE 4096M

      Extent management local uniform SIZE 16M;

    create tablespace ARSystem

      datafile '/app/oracle/oradata/CLM/datafile/ARSystem.dbf'

      size 10000M reuse;

    create user ARAdmin identified by AR#Admin#

      default tablespace  ARSystem temporary tablespace ARTemp

      quota unlimited on ARSystem;

    create role ARole_arsys not identified;

    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;

    grant ARole_arsys to ARAdmin;

    alter user ARAdmin identified by clmAdm1n;

    --------------------------------------------------------------------------------------------------------------------------------

    Jul 01, 2016 08:52
    1. Amit Durgapal

      Hi Volker,

      Were you able to resolve the issue after Hans' inputs?

      Regards,

      Amit 

      Jul 07, 2016 03:01