Re: rootdbs

You need to create an index on those columns in the dbs you want, and then create the constraint. It will share the existing index and hence be where you want it! >>>>> Hi, I am running Online 7.22 on HP-UX 10.20 create table "information".fact_offense ( loc_id integer not null constraint "informix" .n167_232, per_id integer not null " " event_id integer not null " " offense_id integer not null " " judge_io_ind integer not null "" " offense_count integer, primary key (loc_id,per_id,event_id,offense_id, judge_io_find) constraint "informix".u167_226) fragment by round robin in factdbs1 , factdbs2 , factdb3 , factdbs 4 extent size 16 next size 16 lock mode page; revoke all on "informix".fact_offense from "public";alter table "informix" .fact_offense add constraint (foreign key (judge_io_ind) references "informix".dim_judge_io constraint "informix" .6_16); The data went to factdbs1, factdbs2, factdbs3, and factdbs4 but why did constraint (alter table - foreign key) go to rootdbs? I tried to put "in factoalter" after .6_16); (i.e. .6_16) in factoalter;) that did not work. Is that something I am missing? factoalter is a dbspace name. Index can go to the specific dbspace but can constraint go to a specific dbspace? thanks in advance for your response. Thuc