This documentation supports the 20.02 version of Remedy Action Request (AR) System.

To view an earlier version, select the version from the Product version menu.

Setting database options

Use the Database tab to view and configure information about the database that you are using.

Best practice

BMC recommends using the Remedy Management Console to set the database options. For more information, see Setting global-level and local-level configurations using the Remedy Management Console
To display and update information about the database


This form shows the local level value of the configuration. If a local value does not exist, the form displays the global level configuration. If you modify the value on this form, the local level configuration value is modified.

For example, if a configuration shows global level value and you modify the value by using this form, the local level value gets created for the configuration.

  1. In a browser, open the AR System Administration Console, and click System > General > Server Information
    The AR System Administration: Server Information form appears. 
  2. Click the Database tab.

    AR System Administration: Server Information form — Database tab
    (Click the image to expand it.)

    The information displayed on this tab varies depending on the relational database you have installed.
  3. Edit the options, as needed:

    Database tab fields

    Field NameDescription
    Database TypeDisplays the type of database that the AR System server is using.
    Database Home(UNIX only) Displays the directory path of the underlying database that the AR System server is using.
    Database NameDisplays the name of the database created for AR System in the underlying database server.
    Database VersionDisplays the version of the database that the AR System server is using.
    Database User NameDisplays the user name that BMC Remedy AR System uses to access the database.
    Database Password(Oracle, Microsoft SQL Server databases only) Enables you to define the password that BMC Remedy AR System uses to access the database. The existing password is not displayed. To change the password, enter a value in the Database Password field. The default database password created by BMC Remedy AR System is AR#Admin#. If you changed the password and do not remember it or if you changed it outside AR System and must reflect the change in AR System, log on to the database as the database administrator and change it back to the default. If the encrypted password is in the ar.confconfiguration file, delete it from that file.
    Database Configuration FileDisplays the contents of the ardb configuration file used by the advanced BMC Remedy AR System feature that appends clauses to the SQL statements that create tables and indexes. For more information about the ardb file, see ardb.cfg or ardb.conf.
    Database Case SensitiveIndicates whether the database in use is case sensitive. This field is read-only.
    Request ID Uses Clustered Index(Microsoft SQL Server only) Indicates whether AR System creates the Request ID field as a clustered index to boost performance. By default, this option is selected.
    Store CLOB In-Row

    (Oracle databases only) Specifies how Oracle CLOBs are stored:

    By default, this option is selected, and CLOBs are created "in row." In-row CLOBs can increase CPU usage, but In-Row CLOBS perform better than Out-Row CLOBS. If the CLOB data in a specific row gets too large, it is automatically moved to "out row".

    If you do not select this option, CLOBs are created "out row." Out-Row CLOBs can cause the database to grow rapidly and will take longer to retrieve the CLOB data.

    Note: Before installing BMC Remedy AR System applications, select this option so that all database tables for applications are created in the desired manner.

  4. Click Apply.

 Using read-only database

The AR System server automatically detects if you have a read-only database. BMC Remedy AR System does not support the following features with a read-only database. You need to disable the following features through Java Driver when you are using a Read-only database. Refer to Runtime configuration to run the Java Driver program.

Use the procedure shown below in the example to disable the features.

Example — Using Java Driver command to disable archiving for server group
Command: ssi
   Number of server info operations (0): 1
    Operation (1-443) (1):419
(0 - 14, 30-34, 40-43) (0): 2
Integer Value (0): 1
Set Server Information Status
ReturnCode:  OK
Status List : 0 items 

Enter the ID for the feature to be disabled on the line below:

Operation (1-443) (1):419

Replace 419 in the above example with the ID for the feature to be disabled. Refer to the table below for IDs.


ID for single server environment – 191

ID for server group environment – 419


ID for single server environment – 143

ID for server group environment – 422

Full Text SearchID – 190
Vendor form search

You cannot search Vendor form if you have read-only database because Vendor form search results in creating temporary tables.


To recreate hash for a database password, update the new database password in the ar.cfg file or Centralized Configuration by using the Db-password parameter. Set the password in clear text and restart the server. After restart, the server hashes the clear text string.

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