While preparing for the upgrade from 10.2.0.3 to 22.214.171.124 I noticed an
interesting change from 126.96.36.199 on ;
if a datafile is unavailable for write the database performs a shutdown abort unless _datafile_write_errors_crash_instance is set.
Before if the database was in running archive log and the datafile in question was not a “system” one the datafile would just be put offline…. now the database stops.
Will test it soon and put some excepts of the alert.log