Nikolay Serbezov said...Tim, so the process is exactly the same as in your post for version 12.2?
No any new/extra steps in this version?
There are additional features in 18c, but the *basic* setup is unchanged, which is not that surprising since the broker does the heavy lifting.
There are some changes in the way 18c handles Oracle Managed Files, so you will see slight changes in the vagrant builds.
Anonymous said...How should you manage the cleanup of the archived redo at the standby site ?
Giorg said...on Oracle 18c the switchover and/or failover seems doesn't work following this guide...
Error: ORA-1034: ORACLE not available
Error: ORA-16625: cannot reach member "orc1"
Unable to switchover, primary database is still "orc1"
My guide doesn't mention ORCL, so clearly your config is not the same. Maybe you've missed something out.
You can try it out with my Vagrant and you will see it all works fine. I just did a clean build and a switchover worked no problem.
Brian said...Really great article!
I see you're turning FORCE LOGGING on. I'm thinking about trying this with an E-Business Suite database where we really don't want that turned on database-wide. As long as I'm not concerned about the tables that don't have logging on and I'm never planning on switching the standby to primary is this required? Any other concerns?
This all comes down to what you are prepared to lose/cleanup in the event of a switchover/failover.
You might also want to read this.
DO NOT ask technical questions here! They will be deleted!
These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!
If you post personal information (name, email address etc.) you are agreeing to them being stored and displayed. Feel free to remain anonymous.