Re: IMP, extents error again!!(HELP!!!!!)

From: Reid Lai <reidlai_at_netvigator.com>
Date: Fri, 31 Aug 2001 15:43:59 +0800
Message-ID: <3B8F403F.63769F58@netvigator.com>

Or to change temporary tablespace next extent size to larger for long-term maintenance.

Sybrand Bakker wrote:

> "JK Yao" <jkyf0131_at_hotmail.com> wrote in message
> news:93f65984.0108302310.7cb99274_at_posting.google.com...
> > dear all,
> >
> > Following is the error msg for my import. There are about 12 millions
> > rows, so the table is large. The table is about 2GB. Any suggestion
> > for datafiles and tablespace or other setting for this table? And how
> > to correct this problems and prevent it happen again?
> >
> > Thanks a lot.
> >
> > regards,
> > JK
> >
> > ****************
> > IMP-00017: following statement failed with ORACLE error 1630:
> > "ALTER TABLE "PART_COST_BUCKET_HISTORY_TAB" ADD CONSTRAINT
> > "PART_COST_BUCKE"
> > "T_HISTORY_PK" PRIMARY KEY
> > ("PART_NO","CONTRACT","HISTORY_SEQ_NO","COST_BUCK"
> > "ET_ID","TOP_LEVEL_PART_NO","BUCKET_LEVEL","BUCKET_SEQ") USING INDEX
> > PCTFREE"
> > " 10 INITRANS 2 MAXTRANS 255 STORAGE (INITIAL 1254371328 NEXT 2097152
> > MINEXT"
> > "ENTS 1 PCTINCREASE 0 FREELISTS 1 ) TABLESPACE
> > "MPC_INDEX""
> > IMP-00003: ORACLE error 1630 encountered
> > ORA-01630: max # extents (249) reached in temp segment in tablespace
> > TEMP
> > *********************

>

> alter tablespace temp
> default storage (maxextents unlimited)

>

> You may also want to check whether the temp tablespace is big enough.
> estimated size
> the total size of all the columns in the key
> times the number of rows
> times 2.

>

> Hth,

>
> Sybrand Bakker, Senior Oracle DBA
Received on Fri Aug 31 2001 - 02:43:59 CDT