Re: Create a SQL script used to create a new copy of a user's schema.

From: Brett Neumeier <neumebm_at_hpd.abbott.com>
Date: 1997/06/12
Message-ID: <33A04384.3D7F73C@hpd.abbott.com>#1/1

Bill Hockridge wrote:
>
> No.
> The problem with that approach is that the initial extents in the
> storage clause are gigantic. Even though there is no data, the import
> tries to allocate the initial extents during table creation in the new
> schema. I don't have 12gb of space on my NT so the first or second
> tables get created, consume all of the tablespace I have, and the
> remaining 200+ tables creations fail.

It sounds as though you are telling Export to "compress extents." If you answer "no" to "compress extents" ("yes" is the default) it will keep the extent sizes as they are in the current database.

-bn Received on Thu Jun 12 1997 - 00:00:00 CDT