I suppose the searching for the datafiles and getting permission to actually
drop them could be time consuming. Not sure if you have any additional
alert.log information or information about what the command is waiting for.
I'd suggest losing the "and datafiles" bit (after generating a list of the
files). After the tablespace becomes unreferenced in Oracle you can probably
delete the files from the OS unless something has them open.
10 is very old, btw.
mwf
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of David Barbour
Sent: Sunday, May 24, 2015 4:49 PM
To: oracle-l mailing list
Subject: Ordinary Tablespace Drop Hanging
At least it appears to be.
Oracle 10.2.0.5 on HPUX IA64 11.23.
Issued the 'DROP TABLESPACE XXXXXX INCLUDING CONTENTS AND DATAFILES' command
90 minutes ago. It's an old, unmaintained database I'm trying to convert to
Locally-Managed ASSM tablespaces.
This tablespace has 261 datafiles of varying sizes.
It is NOT going away!
Anybody seen anything like this? Tablespace is currently off-line, and has
no FK Constraints tied to tables in any other tablespace.
