Re: JDEdwards and Uniform tablespaces

I'm not really keen on system managed (autoallocate) tablespaces, but this seems like a good place to use them. Objects tend to start with a single 64K extent, then gain a few more at 64K before jumping by degrees through 1M, 8M, 64M. Consequently small objects don't waste much space but big objects don't have an extreme number of extents.

A variation on Ricky's theme might be to start everything off in autoallocate tablespaces, then move the items that are obviously
growing into uniform tablespaces a few at a time.

--
Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Practical Oracle 8i:  Building Efficient Databases
Publishers:  Addison-Wesley

Reviews at: http://www.jlcomp.demon.co.uk/book_rev.html



Ricky Sanchez wrote in message <3AD35A18.3F454243_at_more.net>...


>Jay-

>

>Is there any way you can figure out from their scripts, etc. which objects

 do


>not get used? You could always place those in a sort of "dummy" tablespace,

 or


>group of tablespaces, with particularly small extents and just let them sit

>there.

>

>Or, you might do a trial install with small-extent tablespaces and then run

 the


>product and identify the useless objects, then reinstall. Probably a

 tedious


>hassle, but may save lots of grief in the long run.

>

>- ricky

>

>

>Jay Strauss wrote:

>

>> Hi,

>>

>> We're doing a JDEdwards implementation.  I'm building a new database so I

>> figure what better time to try out locally managed tablespaces and

 uniform


>> extents.  But when you install jdedwards it builds ~2200 tables, not all

 are


>> used (20-25%), they build all the tables for all their modules, even if

 you


>> don't use all the modules.

>>