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.
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).
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.
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:
OracleRACAutoRestartRMI in the Options.properties file.OracleRACcheckDBInterval (default 300 seconds).