Database crash caused by alter system events in oracle

Since I/O waits for a large amount of data to be imported into the database, new storage cannot be mounted directly. You need to use nfs mounting and store redo to relieve the I/O pressure.
Database version information
SQL> select * from v $ version;
 
BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-64bi
PL/SQL Release 10.2.0.4.0-Production
CORE 10.2.0.4.0 Production
TNS for IBM/aix risc System/6000: Version 10.2.0.4.0-Productio
NLSRTL Version 10.2.0.4.0-Production
Mount parameters (view the mount command)
10.240.10.1/top/data4/nfs/back1 nfs3
Aug 29 cio, rw, bg, hard, nointr, rsize = 32768, wsize = 32768, proto = tcp, noac, vers = 3, timeo = 600
Try to create redo
SQL> alter database add logfile group 13 ('/back/newxff/redo13.log') size 2048 m;
Alter database add logfile group 13 ('/back1/newxff/redo13.log') size 2048 m
*
ERROR at line 1:
ORA-00301: error in adding log file '/back1/newxff/redo13.log'-file cannot be
Created
ORA-27054: NFS file system where the file is created or resides is not mounted
With correct options
Additional information: 6
According to the mos document
ORA-27054 errors when running rman with nfs (Document ID 387700.1)
SQL> Alter system set events '10298 trace name context forever, level 32 ';
 
System altered.
 
Mon Sep 5 10:10:18 2016
Thread 1 advanced to log sequence 109 (LGWR switch)
Current log #1 seq #109 mem #0: + DATA/xff/onlinelog/group_1.257.921671023
Mon Sep 5 10:12:19 2016
OS Pid: 160710 executed alter system set events '2017 trace name context forever, level 32'
Redo created successfully
SQL> alter database add logfile group 13 ('/back1/newxff/redo13.log') size 2048 m;
 
System altered.
 
Mon Sep 5 10:18:13 2016
Alter database add logfile group 13 ('/back1/newxff/redo13.log') size 2048 m
Mon Sep 5 10:18:43 2016
Completed: alter database add logfile group 13 ('/back1/newxff/redo13.log') size 2048 m
Database crash
Mon Sep 5 10:19:06 2016
Errors in file/opt/oracle/admin/xff/bdump/xff1_lgwr_246566.trc:
ORA-00313: open failed for members of log group 13 of thread 1
ORA-00312: online log 13 thread 1: '/back1/newxff/redo13.log'
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 6
Mon Sep 5 10:19:06 2016
Errors in file/opt/oracle/admin/xff/bdump/xff1_lgwr_246566.trc:
ORA-00313: open failed for members of log group 13 of thread 1
ORA-00312: online log 13 thread 1: '/back1/newxff/redo13.log'
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 6
Mon Sep 5 10:19:06 2016
LGWR: terminating instance due to error 313.
Mon Sep 5 10:19:06 2016
System state dump is made for local instance
System State dumped to trace file/opt/oracle/admin/xff/bdump/xff1_diag_299654.trc
Through the error is clearly can be seen that the cause of database crashes and at that time can not create redo for the same reason, is due to the ORA-27054 caused by the database crashes, but why the creation of redo successful, but failed to use redo?
The events command takes effect for the current session and subsequent sessions. That is, it does not take effect for the existing background processes of the database, it can be understood that the redo I created is processed in the current command line window of events execution, so it can be created successfully. However, the lgwr process is a process that exists when the database is started, currently, the configured events does not affect the user. Therefore, when lgwr uses redo, it cannot be used normally. Therefore, the database crashes. If you want the event to take effect for an existing process, you can use oradebug to set the event for the process (in this case, you must set multiple background processes to not only access redo by lgwr ), or set event =, and then restart the database to make it take effect.