Oracle RAC configuration and feature support - Applications Manager
search cancel

Oracle RAC configuration and feature support - Applications Manager

book

Article ID: 449978

calendar_today

Updated On:

Products

Automic Applications Manager

Issue/Introduction

Applications Manager (AM) supports Oracle Real Application Clusters (RAC) with specific configuration requirements to ensure process stability and performance.

This article outlines the support status for Oracle-specific features like Fast Application Notification (FAN) and custom driver properties.

Environment

  • Product: Applications Manager 
  • Database: Oracle RAC, Oracle SCAN

Cause

This is a guidance article for configuring Applications Manager in an Oracle RAC environment. Applications Manager uses connect-time failover and requires specific settings to prevent performance degradation caused by instance-specific DBMS pipes (still being used on on some Java threads even after moving to Oracle Advanced Queues).

Resolution

Oracle RAC Configuration

Configure Oracle RAC to use Failover only. Disable Load Balancing on both the client side (tnsnames.ora) and the server side.

Applications Manager utilizes DBMS pipes for internal process communication (e.g., wake-up signals for the Automation Engine). Because pipes are instance-specific, load balancing across multiple nodes can prevent processes from receiving signals, leading to performance delays or TROUBLE status.

Oracle RAC Monitor

Because AM uses connect-time failover, a restart is required if the primary database node becomes inactive. Enable the Oracle RAC Monitor to automate this process:

  1. Enable OracleRACAutoRestartRMI in the Options.properties file.
  2. Set the OracleRACcheckDBInterval (default 300 seconds).

Feature Support Status

  • Oracle FAN / Fast Connection Failover (FCF): Not supported. AM uses an internal interval-based RAC-awareness mechanism rather than event-driven notifications.
  • Custom Validation Queries: Not supported. AM performs internal connection validation; there is no customer-facing setting for custom queries.
  • Oracle Driver Properties (e.g., ReadTimeout): Not configurable. Individual Oracle JDBC driver properties are not currently exposed in the application settings.

Additional Information