Release Notes › System Requirements › CA RCM Server Requirements › Database Requirements

Database Requirements

CA RCM creates databases for user, role, and resource information, and for ticket-based review workflows. You can implement databases in two ways:

• A dedicated local RDMBS installed on the CA RCM server.
• An existing RDBMS in the network.

For a list of supported databases, see the CA RCM Compatibility Matrix that is available from the CA RCM product page on CA Support Online. For information about system requirements for your RDBMS, see the documentation for your product.

Note: We recommend using Microsoft SQL Server for CA RCM databases. During testing in CA labs, SQL Server provided the best performance.

The following privileges and settings are required for Microsoft SQL Server:

• User Account—The CA RCM database user must have system administrator (SA) level privileges
• Server Authentication mode—"Mixed Authentication mode" only
• Communications protocols—TCP/IP and Named Pipes protocols enabled

The following privileges and settings are required for Oracle Database:

• Database—The database must be defined either in a local tnsnames.ora file (under the Oracle Client installation), or in an Oracle directory server
• Encoding—CA RCM databases must use UTF-8 (AL32UTF8) encoding
• Either one of the following:
  • Schemas—Empty, separate, schemas for sdb, ticketdb, and Workpoint (wpds), whose owners have the CONNECT and RESOURCE roles
  • User Account—A user with DBA privileges for the installer to create and populate the required schemas

    Note: We recommend that your database administrator creates the empty schemas for you before you install CA RCM. If you do not prepare empty schemas for the CA RCM databases, the installation requires the credentials of an Oracle Database user with DBA privileges. The installation program then creates the schemas using the information you provide.