Re: IMP problems, extents changed ..(HELP!!!!)

JK Yao wrote:
>
> dear all,
>
> I export my Oracle7.3.4 database use compress=n. ]
> Then import to Oracle8.1.6. There are some import error for tables
> showing below:
>
> IMP-00058: ORACLE error 1631 encountered
> ORA-01631: max # extents (121) reached in table
> IFSAPP.MANUF_STRUCTURE_TAB
> IMP-00028: partial import of previous table rolled back: 261286 rows
> rolled back
>
> 1. I know the problem is extents too canont be extended. However, in
> the original database those extent is good enough for my data, but why
> cannot fit for Oracle8.1.6? Is that normal?
> Please clarify. How can I solve it?
>
> 2. If this is normal, so should I just import anyway and then alter
> table setting and then import those tables? Or there is better way to
> prevent this kind of import error before I impot it?
>
> thanks in advance for any help.
>
> regards,
> JK

Hi all.

I'd bet a slightly used 1.0 GHz Athlon CPU that the PCTINCREASE was set at 50%.
Now importing into a uniformly sized LMT - he runs out of extents. Lets assume that the LMT has extents of 128K 121*128K = 15.1M - not large

7.3.4
even with a starter extent size of 12K -(lets assume he used the defaults)

12288 * 1.5 ^ n

n	f(n)
1	   12288	12K
2	   18432
3	   27648
4	   41472
5	   62208
6	   93312
7	  139968		cross-over point
8	  209952
9	  314928
10	  708588
11	 1062882
12	 1594323
13	 2391484
14	 3587227
15	 5380840
16	 8071260
17	12106890
18	18160335		damn 50% increase bit me already

Sound likely?
The only way to combat an exponential like that - is with a (big) log.

Paul Received on Tue Aug 28 2001 - 02:00:25 CDT