RE: Dropping Tablespaces - All Nighter

Hi Kirsten,

If by your point 3. you mean that there are indeed segments with large numbers of extents, then you should be aware that dropping such segments is known to take a very long time. Also, the damage done to the data dictionary by having had them there cannot be undone except by rebuilding the database. Have a look at the tip on "Planning Extents" on my web site for more information.

Regards,
Steve Adams

http://www.ixora.com.au/
http://www.oreilly.com/catalog/orinternals/
http://www.christianity.net.au/

-----Original Message-----
From: Weerd de E.C. Kirsten [mailto:Kirsten.deWeerd_at_Oranjewoud.nl] Sent: Tuesday, 1 August 2000 5:57
To: 'Steve Adams'
Cc: ORACLE Fatcity Mail (E-mail)
Subject: RE: Dropping Tablespaces - All Nighter

Steve,

The problems I would like to gid rid of are :

1. Incorrectly sized and placed datafiles. I'm faced with tablespaces a mere 300Mb large with 3 datafiles scattered around. This creates plenty of free space, but no big chunk for big tables ...
2. Objects created in tablespaces not assigned for the owner of the object
3. Automatically resizing tables created with abnormal small initial extent and rapidly growing ...

Though I would love the challenge of rebuilding the entire database, the new
DBA that I am, I wouldn't really know how to achieve all results listed above and my bosses aren't creating enough window for me to do it. The DB
can only be stopped at night ....

> -----Original Message-----
> From: Steve Adams [SMTP:steve.adams_at_ixora.com.au]
> Sent: Monday, July 31, 2000 7:23 PM
> To: ORACLE-L_at_fatcity.com; Kirsten.deWeerd_at_oranjewoud.nl
> Subject: RE: Dropping Tablespaces - All Nighter
>
> Hi Kirsten,
>
> If the problem is large numbers of extents in some segments,
> then it may be quicker to take a full database export and rebuild the
> entire database.
>
> Regards,
> Steve Adams
> http://www.ixora.com.au/
> http://www.oreilly.com/catalog/orinternals/
Received on Mon Jul 31 2000 - 14:04:15 CDT