Path: news.easynews.com!easynews!news-out.cwix.com!newsfeed.cwix.com!newsfeed1.cidera.com!Cidera!cyclone.tampabay.rr.com!news-post.tampabay.rr.com!typhoon.southeast.rr.com.POSTED!not-for-mail
From: "Pamela Samuels" <xyz@hotmail.com>
Newsgroups: comp.databases.oracle.server
Subject: Table Extents Question
Lines: 21
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <dBS68.38070$A51.17125345@typhoon.southeast.rr.com>
Date: Sat, 02 Feb 2002 14:20:57 GMT
NNTP-Posting-Host: 24.163.117.220
X-Complaints-To: abuse@rr.com
X-Trace: typhoon.southeast.rr.com 1012659657 24.163.117.220 (Sat, 02 Feb 2002 09:20:57 EST)
NNTP-Posting-Date: Sat, 02 Feb 2002 09:20:57 EST
Organization: RoadRunner - Cox
Xref: easynews comp.databases.oracle.server:133680
X-Received-Date: Sat, 02 Feb 2002 07:48:34 MST (news.easynews.com)

Please tell me if my logic has a fallacy.  We have a PeopleSoft
application that requires the existence of thousands of tables that
are used temporarily during the execution of a batch process (App
Engine).  For our installation, many of the tables are not used, but
we are required to create them anyway.

As the program runs, it loads data into them, processes it, then
truncates the table.

To conserve space, especially since may are never used, but also to
minimize dynamic extent allocation, I have created all these thousands
of tables with an initial extent of 16k, and a next of 1m.  The
thinking is that all tables will be created tightly packed with small
extents, and as extents are allocated and then given back with the
truncate, having a uniform 1m next will keep the tablespace
unfragmented.

Is there a better way of managing this?  We don't have the option of
using Oracle temporary tables, we have to do it this way.


