You are currently browsing the tag archive for the ‘ORA-01110:’ tag.
You can hit this error on your alert.log. Error could be similar as:
ORA-01578: ORACLE data block corrupted (file # 12, block # 4207)
ORA-01110: data file 11: ‘/xx/sytem.dbf’
There are many possible causes of a block corruption including:
– Bad IO hardware / firmware
– OS problems
– Oracle problems
– Recovering through “UNRECOVERABLE” or “NOLOGGING” database actions (in which case ORA-1578 is expected behavior)
I faced with that errors our 12c database. With those errors MRP process has been stopped at standby database and GAP started to increased
Complete errors are:
Reading datafile '/xxx/datafile/ts_1.dbf' for corruption at rdba: 0x08d6e9fd (file 35, block 1501693) Reread (file 35, block 1501693) found same corrupt data (logically corrupt) Sat Jan 18 17:43:50 2020 ERROR: ORA-00756 detected lost write of a data block Slave exiting with ORA-756 exception Sat Jan 18 17:43:50 2020 Errors in file /u01/app/oracle/diag/rdbms/sid/sid/trace/sid_pr01_74757.trc: ORA-00756: recovery detected a lost write of a data block ORA-10567: Redo is inconsistent with data block (file# 35, block# 1501693, file offset is 3711934464 bytes) ORA-10564: tablespace TS ORA-01110: data file 35: '/xxx/datafile/ts_1' ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 102109 Sat Jan 18 17:43:50 2020 Recovery Slave PR01 previously exited with exception 756
I faced with those errors on 12c database. While I try to drop some tablespace it throws errors such as:
SQL> DROP TABLESPACE MY_TABLESPACE INCLUDING CONTENTS AND DATAFILES; DROP TABLESPACE MY_TABLESPACEINCLUDING CONTENTS AND DATAFILES * ERROR at line 1: ORA-01116: error in opening database file 35 ORA-01110: data file 35: '/u01/app/oracle/product/12.1.0/dbhome_2/dbs/MY_TABLESPACE02_A.DBF' ORA-27041: unable to open file SVR4 Error: 2: No such file or directory Additional information: 3
