duplicate value error running dbexport
Posted in 2003
Topics: Error Codes & Troubleshooting, Server Administration, Migration, Import/Export & Data Conversion, Versions, Editions & End-of-Life
Been doing this 10 years
and have never come across this before. I'm
getting this error:
100 - ISAM error: duplicate value for a record with unique key.
while running a dbexport. Furthermore, I get the same error running a
dbschema.
Running IDS 7.30.FC7B
How is this even possible?
Barry Leb
Senior DBA - Informix/DB2
John H. Harland
bleb@harland.net
770.593.5050 x6137
Two
different tables with the same name and different owners?
-----Original Message-----
From: bleb@harland.net [mailto:bleb@harland.net]
Sent: Thursday, June 26, 2003 1:20 PM
To: ids@iiug.org
Subject: duplicate value error running dbexport [1435]
Been doing this 10 years and have never come across this before. I'm
getting this error:
100 - ISAM error: duplicate value for a record with unique key.
while running a dbexport. Furthermore, I get the same error running a
dbschema.
Running IDS 7.30.FC7B
How is this even possible?
Barry Leb
Senior DBA - Informix/DB2
John H. Harland
bleb@harland.net
770.593.5050 x6137
"CONFIDENTIALITY NOTICE: This message originates from WHSmith USA Travel
Retail. This email message and all attachments may contain legally
privileged and confidential information intended solely for the use of the
addressee. If you are not the intended recipient, you should immediately
stop reading this message and delete it from the system. Any unauthorized
reading, distribution, copying, or other use of this message or its
attachments is strictly prohibited. All personal messages express solely the
sender's views and not those of WHSmith USA Travel Retail. This message may
not be copied or distributed without this disclaimer."
Thanks for all the responses. Most everyone has indicated that they thought there was a problem with duplicate entries in the system catalogs, either tables or indexes. That was my first assumption as well, but I couldn't find anything there. However, I did search comp.databases,informix and found this was a pervasive problem in 7.x versions of informix. I've been able to work around this by dropping and recreating the tables manually. Thanks again. Barry Leb Senior DBA - Informix/DB2 John H. Harland bleb@harland.net 770.593.5050 x6137