RE: unique constraint violation on 8i import but not on 9i
- From: <Joel.Patterson@xxxxxxxxxxx>
- To: <afatkulin@xxxxxxxxx>, <ganstadba@xxxxxxxxxxx>
- Date: Thu, 5 Jul 2007 09:51:44 -0400
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@xxxxxxxxxxx
x72546
904 727-2546
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Alexander Fatkulin
Sent: Wednesday, July 04, 2007 8:26 PM
To: ganstadba@xxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
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
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
