Tag Info

New answers tagged

0

The message indicates that no archivelog exists with this sequence in the current incarnation. Failover starts a new incarnation, and log sequences start from 1 again. Let's say your database is at sequence 10 now, and the log sequence was 159 before the failover. V$ARCHIVED_LOG at this point still contains entries about previous incarnation, so the above ...


1

The unique names of the databases in a Data Guard configuration are listed in the log_archive_config parameter in the following form: log_archive_config='DG_CONFIG=(PDB10,PDB10_STBY)' You can remove the old one and add the new one as: alter system set log_archive_config='DG_CONFIG=(PDB10,PDB10SBY)'; After this, you can set log_archive_dest_N to the new ...



Top 50 recent answers are included