If the database is in NOARCHIVELOG mode, you must specify the DROP
clause to take a datafile offline. However, the DROP clause does not
remove the datafile from the database. To do that, you must drop the
tablespace in which the datafile resides. Until you do so, the
datafile remains in the data dictionary with the status RECOVER or
OFFLINE.
If the database is in ARCHIVELOG mode, Oracle ignores the DROP keyword.
On Mon, 27 Dec 2004 06:08:10 -0800 (PST), Joe Cooper
<aregularjoe8@(protected) > wrote:
> I 'm away from my office this week, and currently (conveniently?) away from my VPN access, so this response is strictly from memory. However, if memory serves me correctly, the difference is that on *NIX systems, 'offline drop ' not only makes the datafile unavailable to the Oracle instance, it removes the datafile from the O/S (freeing the disk space for other uses). Thus, if you use the 'drop ' option and don 't have adequate backups elsewhere, you 'd have a hard time recovering the file. As you have clearly demonstrated, it appears to make no difference on Windows systems.
>
> Of course, this is from memory, so any corroboration (or opposing view) is welcome.
>
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
--
http://www.freelists.org/webpage/oracle-l
