standby after primary has been flashed back
We are trying to find a solution to our standby which needs rebuilding everytime the primary database is flashed back.At the moment, the primary is used for testing before the go-live and as a result of this testing we create restore points and use flashback database to flash it back to these guaranteed restore points. Because the primary is then opened with resetlogs, the standby database reports of orphan incarnation.
Does anyone know what could be a viable solution to sync the standby with primary without having to rebuild? Have found something that if the flashback is switched on in the secondary we could flash the standby to the restlogs scn but because the standby didnt have it switched on in our case , we are unable to do this. Even after switching it on, it doesnt work as the target time is when the flashback was turned off in the standby.