Oracle data recovery-Case Study of accidental data file deletion using OEM

Oracle data recovery-if you need to learn how to delete data files due to incorrect OEM operations, refer.

Oracle data recovery-if you need to learn how to delete data files due to incorrect OEM operations, refer.

Oracle data recovery-if you need to learn how to delete data files due to incorrect OEM operations, refer.

A complete group deletion that contains data files and content is sent out. If you use it manually, I am afraid DBAs will be very careful in spelling this command:

Wed May 02 10:46:09 2012
/* OracleOEM */drop tablespace "WNDT" INCLUDING CONTENTS AND DATAFILES CASCADE CONSTRAINTS
Wed May 02 10:46:23 2012
Errors in file d: oracleadminwndtudumpwndt_ora_4816.trc:
ORA-01259: Unable to delete data file D: ORACLEORADATAWNDTWNDT. ORA
ORA-27056: skgfrdel: the file cannot be deleted
OSD-04024: the file cannot be deleted.
O/S-Error: (OS 32) another program is using this file and the process cannot be accessed.

Fortunately, when an error occurs during initial deletion, the file is held by another process and cannot be deleted.

However, it is a pity that a further prompt shows that the file is successfully deleted:

The Code is as follows:
Wed May 02 10:46:23 2012 Completed:/* OracleOEM */drop tablespace "WNDT" INCLUDI

This case reminds us that we should try to use OEM and other graphical tools to manage and maintain important database operations. If you do not know how to perform an operation on the background, you must use this tool with caution.

In this case, if the user can promptly protect the site, the data files can be retrieved through storage-level recovery.