Oracle Data Recovery-Carefully remove cases with OEM misoperation data files

A thorough set of deletions containing data files and content is emitted, and if used manually, DBAs will be extremely cautious in spelling such commands:

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: Cannot delete data file D:oracleoradatawndtwndt. ORA
Ora-27056:skgfrdel: Unable to delete file
OSD-04024: Unable to delete file.
O/s-error: (OS 32) Another program is using this file and the process is inaccessible.

It seems fortunate that the initial deletion encountered an error and that the file was held by another process and could not be deleted.

Unfortunately, further hints show that the file was eventually successfully deleted:

The code is as follows	Copy Code
Wed May 02 10:46:23 2012 Completed:/* Oracleoem/DROP tablespace "Wndt" Includi

This case warns us: As far as possible with OEM and other graphics tools for database important management and maintenance operations, if you do not know the foreground of an operation in the background will be how to perform, then be sure to use such tools carefully.

For such cases, if the user can protect the site in time, through the storage level of recovery can be retrieved data files.