RE: unique constraint violation on 8i import but not on 9i

Or apply the constraint exceptions into exceptions and find the duplicates.

I would then look them up in the 9i database. You say there is no nls funny stuff, but the character set point (in another email answer) seemed like a good lead.

Joel Patterson
Database Administrator
joel.patterson_at_crowley.com
x72546
904 727-2546

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Alexander Fatkulin Sent: Wednesday, July 04, 2007 8:26 PM
To: ganstadba_at_hotmail.com
Cc: oracle-l_at_freelists.org
Subject: Re: unique constraint violation on 8i import but not on 9i

>The export taken from an 8i database fails on import into the same
(newly
>rebuilt 8i database) with primary key violation.

Do the import with the ignore=y option then.

As Alex already said - PK is enabled AFTER table data is loaded.

After you load everything up you will end up without that violated PK and some related FK's.

Do the "select col1, col2 from that_nasty_table group by having count(*) > 1" and see what is causing duplicates. Maybe this will give some clue.

HTH

-- 
Alexander Fatkulin
--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l