Doing PITR requires two restore commands as the first one resets the incarnation
I am testing some basic recovery scenario's in my Oracle 19c environment (Windows 2016 as the server OS) and am running into a very strange issue when attempting to do a PITR of my database. I am trying to restore to a previous point in time, before my latest resetlog using a backup from a previous day, and after restoring that controlfile, the initial restore command seems to change the CURRENT incarnation. I then have to reset the incarnation and perform the restore again in order to get the restore to work. My scenario is as follows:
I’ve got a backup from 21-JUN-2021 18:04:38 that I’m trying to use to do a PITR to 21-JUN-2021 22:00:00. I’ve restored the control file from this backup since I’ve already got a newer resetlog from a previous PITR that I had performed. With my older controlfile restored, I have the following resetlog and incarnation, which looks correct to me. I am trying to restore to 21-JUN-2021 22:00:00 so this should work right?