[ http://issues.apache.org/jira/browse/DERBY-1641?page=all ]
Kathey Marsden updated DERBY-1641: ---------------------------------- Fix Version/s: 10.2.0.0 Priority: Critical (was: Major) I verified this on 10.2 and verified that I still get the conglomerate does not exist error after exiting ij and reconnecting to the database. Bumping to critical and marking as 10.2 candidate. $ java org.apache.derby.tools.ij ij version 10.2 ij> connect 'jdbc:derby:wombat;create=true'; ij> create table y(pk integer primary key); 0 rows inserted/updated/deleted ij> insert into y values(123); 1 row inserted/updated/deleted ij> create table z( pk integer not null primary key references y ); 0 rows inserted/updated/deleted ij> call syscs_util.syscs_import_table( null, 'Z', '/temp/z', ',', '''', null,1); 0 rows inserted/updated/deleted ij> select * from z; ERROR XSAI2: The conglomerate (1,009) requested does not exist. > Conglomerate requested does not exist after syscs_import_table with FK > ---------------------------------------------------------------------- > > Key: DERBY-1641 > URL: http://issues.apache.org/jira/browse/DERBY-1641 > Project: Derby > Issue Type: Bug > Affects Versions: 10.1.3.1 > Environment: Java 1.5.0_06-b05 Linux (CentOS 4) > Reporter: Matt Frantz > Priority: Critical > Fix For: 10.2.0.0 > > > I have a repeatable sequence that always causes the "Conglomerate (X) > requested does not exist" error on my system. There are several steps. You > can use "ij" as follows: > 1. Start with a new database, e.g. connect 'jdbc:derby:test;create=true'; > 2. create table y( pk integer primary key ); > 3. insert into y values (123); > 4. create table z( pk integer not null primary key references y ); > 5. Create a file containing a single row of ASCII data with the number "123" > (in ASCII) in it. e.g. /tmp/z > 6. call syscs_util.syscs_import_table( null, 'Z', '/tmp/z', ',', '''', null, > 1 ); > 7. Try to access the "Z" table, e.g. SELECT * FROM z; or DROP TABLE z; > At this point, I always get the error. I can use this sequence in other > contexts, but the difference, as far as I can tell, is that the table "Z" has > a column that is both PK and FK. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira