Learn to monitor ACFS replication.

Use the following command to monitor ACFS replication:

/sbin/acfsutil repl info -c -v /mnt/acfs_gg

You can use the command on both the primary and standby databases.

For example, running the command on the primary cluster where ACFS is mounted produces the following output. Ensure that Primary Status is Running and Background Resources are Active for the primary cluster.

[grid@oggclt1-node1 ~]$ /sbin/acfsutil repl info -c -v /mnt/acfs_gg
Site: Primary
Primary hostname: prim.oggclt.goldengate.com
Primary path: /mnt/acfs_gg
Primary status: Running
Background Resources: Active 

Standby connect string: grid@stby.oggclt.goldengate.com
Standby path: /mnt/acfs_gg
Replication interval: 0 days, 0 hours, 0 minutes, 0 seconds
Sending primary as of: Wed Mar 06 17:12:34 2024
Status: Sending incremental differences
Lag Time: 00:00:34 (Constant mode)
Retries made: 0
Last send started at: Wed Mar 06 17:12:35 2024
Last send completed at: In progress
Next send starts at: On send completion
Replicated tags: 
Data transfer compression: On
ssh strict host key checking: On
Debug log level: 3
Replication ID: 0x966f1b11

The next example demonstrates the command run on the standby cluster where ACFS is mounted:

[grid@oggclt2-node1 ~]$ /sbin/acfsutil repl info -c -v /mnt/acfs_gg
Site: Standby
Primary hostname: prim.oggclt.goldengate.com
Primary path: /mnt/acfs_gg

Standby connect string: grid@stby.oggclt.goldengate.com
Standby path: /mnt/acfs_gg
Replication interval: 0 days, 0 hours, 0 minutes, 0 seconds
Last sync time with primary: Wed Mar 06 17:17:18 2024
Receiving primary as of: Wed Mar 06 17:17:18 2024
Status: Receive Completed
Last receive started at: Wed Mar 06 17:17:19 2024
Last receive completed at: Wed Mar 06 17:17:25 2024
Elapsed time for last receive: 0 days, 0 hours, 0 minutes, 6 seconds
Data transfer compression: On
ssh strict host key checking: On
Debug log level: 3
Replication ID: 0x966f1b11