Thursday, 17 February 2022

ORA-15080 ORA-27070 ORA-63999 ORA-01114 ORA-15081 in alert log

ORA-15080: synchronous I/O operation to a disk failed | ORA-27070: async read/write failed | ORA-15081: failed to submit an I/O operation to a disk

These Oracle errors would lead Oracle instance to crash and won't let it start till you fix the issue. The below IO errors shows the issue with Oracle Storage Management when there's some issue while performing write operation on Oracle file. 


The full error description is shown below,


WARNING: Write Failed. group:1 disk:0 AU:3351 offset:663552 size:131072

Errors in file D:\APP\ORACLE11G\diag\rdbms\prodrac\prodrac1\trace\prodrac1_dbw0_3448.trc:

ORA-15080: synchronous I/O operation to a disk failed

ORA-27070: async read/write failed

OSD-04016: Error queuing an asynchronous I/O request.

O/S-Error: (OS 2) The system cannot find the file specified.

WARNING: failed to write mirror side 1 of virtual extent 504 logical extent 0 of file 300 in group 1 on disk 0 allocation unit 3351 

KCF: read, write or open error, block=0xfc51 online=1

        file=3 '+DATA/prodrac/datafile/undotbs1.300.1026294375'

        error=15081 txt: ''

Errors in file D:\APP\ORACLE11G\diag\rdbms\prodrac\prodrac1\trace\prodrac1_dbw0_3448.trc:

Errors in file D:\APP\ORACLE11G\diag\rdbms\prodrac\prodrac1\trace\prodrac1_dbw0_3448.trc:

ORA-63999: data file suffered media failure

ORA-01114: IO error writing block to file 3 (block # 64593)

ORA-01110: data file 3: '+DATA/prodrac/datafile/undotbs1.300.1026294375'

ORA-15081: failed to submit an I/O operation to a disk

ORA-15081: failed to submit an I/O operation to a disk

Tue Feb 15 02:56:49 2022

System state dump requested by (instance=1, osid=3448 (DBW0)), summary=[abnormal instance termination].

System State dumped to trace file D:\APP\ORACLE11G\diag\rdbms\prodrac\prodrac1\trace\prodrac1_diag_6816_20220215025649.trc

DBW0 (ospid: 3448): terminating the instance due to error 63999

Tue Feb 15 02:56:50 2022

opiodr aborting process unknown ospid (7480) as a result of ORA-1092


Resolution:

1) Check if you have enough space on the storage disk where your datafiles are placed. In our case, it was because the storage was full due to high DML operations and we had to add extra space to let data files increase their size.

2) If option 1) is OK for you and still you are facing this issue, the below workaround can be tried,

Changing the parameter 'DISK_ASYNCH_IO' to 'FALSE' can help the system from crashing anymore. If you set DISK_ASYNCH_IO to false, then you should also set DBWR_IO_SECONDARY to a value other than its default of zero in order to simulate asynchronous I/O.

No comments:

Post a Comment