Far Sync Best Practice Recommendations (for Oracle 12.1)
Hi, This post is a continuation of my post, Using Standby as an Alternate for Far Sync (12c): Limitations and Considerations . It is for database administrators who want to set up Far Sync for the first time. Creating a Far Sync instance requires a number of manual steps and there are many parameters to consider or set. I recently ran numerous scenarios using Oracle™ Active Data Guard with a Far Sync instance. Our goals were to: • Check Far Sync functionality and reliability • Validate that Far Sync has a low footprint under heavy load After running a large number of benchmark scenarios, where we changed one parameter at a time, here are my recommendations for using Active Data Guard with Far Sync: The primary database, the standby database, and the Far Sync instance should all be using the same software version and patch level; if not, upgrade the database(s) to the latest version with the latest patch sets. Consider changing the following database initialization parameters