The Current Log number for multiple clusters in Oracle Data Guard agents is not increasing.
While monitoring a cluster of databases the Data Guard agent does this by monitoring the sequence numbers of files between the different databases and once they get too far apart, it triggers alerts.
In the Oracle Data guard cluster log shipping status screen the primary database is not showing the correct current log sequence number.
It can be updated by clicking on the radio button in the standby database pane. When a user clicks this, the primary updates to correct value. But....if the user leaves that page and goes back to it, it has reverted the primary current log to incorrect value.
