[DERBY-655] getImportedKeys returns duplicate rows in some cases

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: SQL
• Environment: Sun JDK 1.4.2, Windows XP
• Assignee: Mamta A. Satoor
• Reporter: Deepa
• Created: 28/Oct/05 01:18
• Updated: 18/Jun/13 16:15
• Resolved: 30/Jun/06 09:53

Description

I have a database with a large number of tables. I get duplicate rows when I call DatabaseMetaData.getImportedKeys for a particular table. However, if I create the same table with same number of foreign keys in another database (which has fewer number of tables), then getImportedKeys returns me the correct number of rows. This error seems to happen only when the database has a large number of tables. I will attach a repro for this shortly.

Issue Links

• is related to: DERBY-6269 Misleading warning text if you create an index duplicating a constraint.
• is related to: DERBY-1343 It is possible to have duplicate entries in conglomerateId of sysconglomerates before DERBY-655 was fixed in 10.0 or 10.1 databases. It is desirable to patch these databases on upgrade to 10.2 so conglomerateId becomes unique again.
• relates to: DERBY-5249 A table created with 10.0.2.1 with constraints cannot be dropped with 10.5 due to NullPointerException with insane build or ASSERT FAILED Failed to find sharable conglomerate descriptor for index conglomerate with sane build