Audit Vault Agent Fails To Start in RAC Deployment

If the Audit Vault Agent fails to connect to the database server in a RAC deployment, you should ensure the SCAN listener entries are added to the agent hosts in the /etc/hosts files.

Problem

The Audit Vault Agent is unable to connect to the database server when deploying on RAC.

Symptoms

The agent host can not perform ping <scan listener name> to resolve the scan listener IP but the agent host can perform ping <scan listener name> proving the connection can be completed.

Solution

Add the SCAN listener entries on the Audit Vault Agent host in /etc/hosts files.

1. To get the SCAN listener values, run the following command on AVS:

   su - grid -c "srvctl config scan"

   The output will look similar to the below:

   SCAN name: avs-scan-rac1.vboxlocal.net, Network: 1
   Subnet IPv4: 10.0.x.x/255.255.248.0/enp0s3, static
   Subnet IPv6:
   SCAN 1 IPv4 VIP: 10.0.x.x
   SCAN VIP is enabled.
   SCAN 2 IPv4 VIP: 10.0.x.x
   SCAN VIP is enabled.
   SCAN 3 IPv4 VIP: 10.0.x.x
   SCAN VIP is enabled.

2. Add the listed IP addresses of the SCAN to /etc/hosts on the Audit Vault Agent host.

   Also ensure that any entries added to /etc/hosts are added to the bottom of /usr/local/dbfw/templates/template-hosts.

   Use the same SCAN name and node hostnames that were configured for the cluster. To find the fully qualified domain name, run the following command on the relevant host:

   hostname -f

   For example:

   <-- end of file -->
   
   <scan ip 1> scan-name.fqdn rac-scan-name
   <scan ip 2> scan-name.fqdn rac-scan-name
   <scan ip 3> scan-name.fqdn rac-scan-name
   
   <node 1 ip> node1.fqdn node1
   <node 1 vip> node1-vip.fqdn node1-vip
   
   <node 2 ip> node2.fqdn node2
   <node 2 vip> node2-vip.fqdn node2-vip