Re: Import inserts rows more than once

Duplication problems can occur when you use IGNORE=Y ... if you're shure the drop works fine, before you import then you should try removing the ignore=Y and run the import again to verify that the table was really dropped ... if the table exists you'll get an error

Hope this helps, that's the only thing that occur's to me for having duplicate values ... but it's strange that this doesn't happen always ...

Best Regards,

Eduardo Tavares

"Wolfram Roesler" <wr_at_grp.de> wrote in message news:Xns9277688E1E848wrgrpde_at_62.153.159.134...
> Hello,
>
> I have a peculiar problem importing data from one 8.1.6.3 W2K database
> into another. Sometimes one of the imported tables, which has 90 rows
> in the export database, is imported with 400+ rows, and imp fails with
> ORA-02437 when trying to create the PRIMARY KEY. imp writes "90
> rows imported" to the screen, but the table has much more rows! Some
> rows seem to have been imported more than once so that the primary key
> can't be established, hence the ORA-02437.
>
> The table was dropped in the import database immediately before starting
> the import. The problem doesn't occur every time; sometimes it works
> fine, sometimes it doesn't. The dump file is 147 MB. There's nothing
> special (no LOBs, no partitioned tables etc.) about either of the two
> databases, and the import DB works fine apart from this one problem.
> My export parameters are simply:
>
> userid=myuser/mypassword
> consistent=Y
> file=myfile.dmp
> tables=(155 table names)
>
> and the import parameters are
>
> userid=myuser/mypassword
> fromuser=myuser
> touser=myuser
> file=myfile.dmp
> ignore=Y
> commit=Y
>
> Although 155 tables are involved, the problem occurs only with one
> particular table (if it occurs at all).
>
> Has anyone seen anything like this before? Any idea what's happening?
>
> Thanks for any help
> W. Roesler
>
Received on Tue Aug 27 2002 - 03:32:13 CDT