SCN mismatch after RMAN duplicate
edited Sep 1, 2017 5:00AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered
Using RMAN do create a physical standby database, I issued the command
duplicate target database for standby dorecover;
The alert log reports, e.g.,
The input backup piece /rman/D1-t952516342-s13787-p1.bak is in compressed format.Wed Aug 23 06:52:23 EDT 2017Full restore complete of datafile 1 /home/db/system01.dbf. Elapsed time: 0:00:21 checkpoint is 6028004172 last deallocation scn is 6027959222
There are similar entries for the other data files, all with slightly different checkpoints between 6027956543 and 6028004183. So far so good; restore was successful.
But recovery fails, asking for archivelog reaching weeks before the RMAN backup that was used for the restore. And when I check v$datafile,
0