archive logs not marked as applied on primary database
edited Jun 16, 2013 7:25PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered ✓
Hi,For some reason the archive logs are not being marked as applied on the primary database. They are applied on the standby and marked as applied, but not on the primary.
This started almost a month ago. Since than we also have problems with the backups, but we handle the backups (baby-seat them).
We are absolutely sure those logs are applied. Even now, we see the latest logs being applied on the dr db, but still applied='NO' on the primary db.
How can we make that change in V$ARCHIVED_LOG, to see those logs as applied='YES'; or in general, how to get the primary database to recognize the fact that the logs are applied to the dg db.
This started almost a month ago. Since than we also have problems with the backups, but we handle the backups (baby-seat them).
We are absolutely sure those logs are applied. Even now, we see the latest logs being applied on the dr db, but still applied='NO' on the primary db.
How can we make that change in V$ARCHIVED_LOG, to see those logs as applied='YES'; or in general, how to get the primary database to recognize the fact that the logs are applied to the dg db.
0