Hello all .
I'm painfully dealing for a week with very strange problem of application heap size overflow.

My system (linux/db2 8.1/512M RAM/1024 pages application heap size)
has few tables, where two of them like folowing:

T1
( id bigint primary key not null
generated by default as identity
( start with 1, increment by 1 ),
val bigint not null
)

T2
( id bigint primary key not null
generated by default as identity
( start with 1, increment by 1 ),
val bigint not null,
CONSTRAINT t1_fk FOREIGN KEY ( val )
REFERENCES T1 ( id )
)

T1 has about 500000 entries.

When i inserting entries to T2 , application heap utilization becomes over 100% , and after few minutes application fails with "application heap size error).
But , what is most important and STRANGE , when i removing constraint of T2,which is FOREIGN KEY to T1 EVERY THING WORK FINE !!!

Is there any way to control application heap (flush)?

Thanks everyone, Arik

Hi,

have you dedined an index on column id in t1 ?
just an idea !

regards

marc

Yeah , and even ran runstats on it

,except, id is primary key which indexed by default