Param ‘_datafile_write_errors_crash_instance’ , TRUE or FALSE?
Since 11.2.0.2 there's a new parameter, "_datafile_write_errors_crash_instance" to prevent the intance to crash when a write error on a datafile occurs. But.. should I use this or not.
Since 11.2.0.2 there's a new parameter, "_datafile_write_errors_crash_instance" to prevent the intance to crash when a write error on a datafile occurs. But.. should I use this or not.
With this setup we are facing the issue that if we loose a complete SAN, the IO’s to the ASM diskgroups will be blocked for approx 3 till 4 minutes. Oracle does not like this. After 70 seconds after a freeze, rdbms is starting to reboot (expected behaviour).
The metric 'swap utilisation (%)' on the node where Grid Control resides, shows permanently a very hig value. Red Hat Linux, 64-bits, 32GB RAM, 4GB swap. Adding 4GB to the swap-file solved the problem.