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

"Gerard H. Pille" <ghp_at_skynet.be> wrote in message news:<3B862BE0.13254326_at_skynet.be>...
> 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
>
> If the schema is not too complex (no. of tables), you could extract the
> create table statements from the dump-file (imp indexfile=... ), modify
> those statements where needed and create an empty schema with those, and
> then run the import with ignore=yes.

I'm afraid that won't help matters any, since the table is created whether IMP puts the data in it or not. The table create is not negated, just the insert.

I would check the db_block_size of the source instance; my guess is that it's much larger than the 2K set for your 8.1.6 instance. The only way to correct that is to recreate the 8.1.6 instance with a larger db_block_size.

David Fitzjarrell Received on Fri Aug 24 2001 - 08:43:05 CDT