This content has been marked as final. Show 13 replies
Seems you have gaps in standby, see following link for resolving gaps
Managing physical standby
There is another way to resolve by taking back from current SCN in standby database and applying to standby.
Hi Abhay K ,
What is your method of deleting your previous archivelogs? Is it OS command?
If OS command, your controlfile might not be updated so it treats that those archivelogs are still available in your disk. You should update your controlfile when deleting archivelogs using OS command.
RMAN> crosscheck archivelog all; // validate all archvelogs in your disk. If some are missing, it will treat it as expired.
RMAN> delete expired archivelog all; // it ill delete expired archivelog and updates your controlfile.
We are not deleting the archive logs manually, below is the script that we are using.
allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
allocate channel c4 type disk;
sql 'alter system switch logfile';
backup as compressed backupset incremental level 0
backup as compressed backupset archivelog all format 'E:\script\compress\bak1\arch_%U.bak' delete input;
but while restoring the database on different host system was asking the archive log wchich was backed up during backup.
"restoring the database on 'different host system' "?
Does that host system have exisiting database and archivelogs and you are just updating it with new database by restoring the backup from your production?
is the destination of archivelogs and datafiles from your source to your 'different host system' the same?
Is autobackup of controlfile in RMAN enabled? You sure you restore it first before restoring the backup of database?
I already experienced this kind of problem. In standby database, there are exisiting archivelogs that are being cataloged
when I restore my backup of controlfile and mounting the database. What I did is delete this archivelogs in the standby server
and perform restore and recover of the database.