I am working with Oracle Database 19c RAC with DataGuard Far Sync and Standby instances. Last week a heavy update caused the archive logs to fill the physical and ASM disks on the Far Sync instance. I was able to restore the standby instance with the primary's data file and clear the far sync archive logs both in ASM and from a dbs directory on the physical machine. Now everything appears to be running correctly. The primary, far sync and standby are all online and status looks good in srvctl and v$instance, but archive logs are continuing to pile up in the primary's ASM archive log space (defined in the db_recovery_file_dest_size parameter). Running an rman crosscheck and delete on the archive logs in the primary database does not clear out any of the logs. The primary archive logs in the db_recovery_file_dest_size are still filling up. I believe this means the archive logs are not moving through.
What else can I check to determine why the archive logs aren't moving and fix the issue?
Thanks in advance for any insight, solutions, or advice.