Weird flash recovery behaviour
Hi all,
I'm completely mind-boggled about what's happening on one of my databases.
To sketch the situation:
The server is on Linux and is running 6 databases locally (11.2.0.2), the flash_recovery_area is on an nfs share pointing to another server.
This is an acceptance database which is set up as the production databases except it has no standby database. (This seems key to the problem)
So the database points to the nfs share for the flash recovery and has dest_3 set up as a local archivelog directory in case the nfs drops, this would just archive in the local directory without blocking the database until the nfs becomes available again. You would think...
0