A flashback database can be done to bring the database to a state in the past. This is done when any changes to the database by way of application, patch, etc are undesired and need to be rolled back. It is not possible to do it on source but on target it can be done subject to some limitations.
This solution delves on such limitations.
Any recovery of the target database that is incomplete (which would typically be the case with flashback) would result in out of sync. The following steps should be performed when carrying out this type of activity:
4. Resync the target database at a later time. See Shareplex Reference Guide chapter titled “Solving synchronization problems” for details.