Techniques for populating large databases when testing -

we running 3 oracle databases 100+ tables in each. in order test our code looking alternatives populating them testdata. tools have found far dbsetup , dbunit.

the problem having these tools manual work needed specify data. example if test table d required populate tables a, b, c data also. dont care data is, care data in table d. reason have populate b c because concistency checks on derived keys in table d.

my questions how type of problem uasually handled? sign of badly designed database testability point of view?

if database strictly testing purposes, don't see stopping dropping consistency checks (fk etc), populate data, test it, truncate table, , readd consistency checks again later.
other alternative can think of
1. copy table structure (columns etc), , testing there
2. alter fks "deferrable deferred" postpone consistency checking until commit transaction