Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Recover Tablespace with IMPORT and get ORA-01658

Re: Recover Tablespace with IMPORT and get ORA-01658

From: Howard J. Rogers <dba_at_hjrdba.com>
Date: Tue, 28 May 2002 10:04:20 +1000
Message-ID: <jSzI8.20$xn.34@news.oracle.com>


The real ultimate solution is to use locally managed tablespace, of course, since that causes the tablespace to ignore the demand for a huge INITIAL extent.

Regards
HJR "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:h765fusl3kgg9d6sopaii5jotcr6re846r_at_4ax.com...
> On Mon, 27 May 2002 19:33:49 GMT, Ralf Bender <ralf.bender_at_nexgo.de>
> wrote:
>
> >Hi,
> >
> >my Database (8i) runs with a lot of Tablespaces. Now, I must recreate one
> >of them on a second machine. I want to use IMPORT to recreate it on
> >another the machine. But now, I got ORA-01658 unable to create INITIAL
> >extent for segment in tablespace. What's going wrong here? How can I
> >solve this problem?
> >
> >I thought that the INITIAL Parameter in the Export File was very large...
> >
> >bye
> >Ralf
>
> 1658 means there is no *contiguous* extent free as large as or larger
> than the initial of your segment.
> You must have run the export with compress=y (the default), which
> calculates a new initial extent as the sum of all existing extents for
> that segment in the source database. Usually this strategy results in
> the problem you describe above.
> You can solve this problem by enlarging the tablespace, or precreating
> the affected segment with a smaller initial extent that does fit.
> The ultimate solution however would be re-exporting with compress=n.
>
> Hth
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Mon May 27 2002 - 19:04:20 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US