Thanks, but it was not in a locally managed tablespace.
-Roger
> Just to check, but if the exported database object was in a locally
> managed tablespace with uniform extents and was imported into a
> dictionary managed tablespace you can get a maxextents error on the
> imp. In this case truncating the new object copy, altering its
> storage setting, and re-importing with ignore=y would be one way to
> bypass the problem. In fact if this is the case then it may be
> advisable to import all the tables without data, indexes, or
> constraints, alter the storage, and then import the data, indexes, and
> constraints.
>
> HTH -- Mark D Powell --
Received on Mon Dec 16 2002 - 11:04:59 CST
