RE: import oddity

> -----Original Message-----
> From: Dennis Taylor [mailto:ismgr_at_pctc.com]
>
> To my inexperienced eye, it looks like the import is trying
> to create the
> table with an initial size of 1.3 GB or so. The table is
> *not* that big. I
> think it's around 200MB at most. As my tablespace datafiles
> are only 1GB
> each, I can see why the create fails (assuming I'm not
> misunderstanding
> everything).

P.S. In my previous e-mail, I forgot to mention that when you create a table with large INITIAL storage allocation in a locally managed tablespace, the table is NOT created with one large extent, but with enough extents (using the locally managed tablespace storage defaults) to reach the size specified for INITIAL. I imagine that importing a table in a locally managed tablespace would follow the same algorithm. Received on Fri May 18 2001 - 20:33:20 CDT