Solution to Database Failure Caused by physically deleting DBF Files

The solution for physically deleting the DBF File causes the database to fail to work properly. Because the space on the E disk where the local oracle installation is located is insufficient, the unused data file E is: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ ORCL \ TCM_BM.DBF is directly physically deleted, and www.2cto.com causes normal database users to log on normally. Solution: log on to the database with the sys user and execute the command: SQL> alter database open; alter database open ORA-01157: unable to identify/lock data files 6-see DBWR trace file ORA-01110: data file 6: 'e: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ ORCL \ tcm_bm.dbf' Delete the data file in non-archive mode (the file has been physically deleted, the purpose here is to delete the file ing): SQL> alter database datafile 'e: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ ORCL \ tcm_bm.dbf' offline drop; Database altered SQL> alter database open; database altered the common oracle account can be used normally at this time.