We just configured a basic availability group in Synchronous mode (and not auto-failover) between db1 and db2 last week. Okay, so the original state before planned failover was normal meaning no warnings/errors and the application was happily attached.
So we did a planned failover to transition the pair to db1 being (primary) and db2 (standby) and the displays echoed that they were happy to do so (and were synchronized). We then started our apps on the new primary node(db1), everything
attached and was happy. We then simulated a hard network outage by pulling the network cables out of the standby server and the primary reported that it was no longer synchronized with the standby (to be expected), but then all the apps were immediately
ejected from the primary database...is that behavior to be expected? I was looking around for documentation on this behavior and couldn't really find anything, so I thought I'd reach out to a forum of people that are nice and not condescending
like the self appointed Gods present on the Oracle forums. :) Is there any case other than a shutdown that would eject the apps from the primary database? This is what my testers reported and I wasn't there this weekend when they
tested out failover (I was playing golf...there, I said it!). Thanks for any input that you have.
↧