The apps servers were shutdown and I even bounced the database to make sure
there were no spurious connections. It just now completed the drop.
Still have never seen a tablespace grow like this when dropping. Maybe
it's because I've not dealt with Dictionary-Managed tablespaces in years
and never one as big as this, but still, would like to hear if anyone can
explain. Might have to do with segment reordering during the drop, but
that's a guess.
On Sun, May 24, 2015 at 4:30 PM, Mark W. Farnham <mwf@xxxxxxxx> wrote:
What does your alert log show? Is some process extending datafiles? I'm
not sure what would cause an offline tablespace to grow.
I guess I'd make sure all the datafiles are set to not autoextend. Is it
possible some process was still inserting when you took this tablespace
offline?
mwf
*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *David Barbour
*Sent:* Sunday, May 24, 2015 5:23 PM
*To:* oracle-l mailing list
*Subject:* Fwd: Ordinary Tablespace Drop Hanging - Tablespace is
Growing???
The tablespace is actually growing in size. I've never seen this before.
It's added about 250GB.
What am I missing?
---------- Original Message ----------
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.
