RE: sql - Drop and Add constraints

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxxxxx>]

Patrick,

Is anything happening between the clearing of the file and the second
RUNSQLSTM which repopulates Table1?  Or is Table1 empty when the
constraints get put back?

If Table1 is populated when the constraints are added back, is the size
of Table2 relatively constant or has it increased significantly over
time?

Has anything happened over time to increase the number of indexes built
over Table1?

Regards,
Andy Nolen-Parkhouse

> We have a process that drops the constraints on tables (physical
files),
> clears them with a CLRPFM, and then rebuilds the constraints.
> At first this process took 20 minutes. Now it takes 2 1/2 hours. My
> question is why? or how is this possible?
>
> Here is a small sample:
>
> RUNSQLSTM  SRCFILE(SourceLib/SourceFile) SRCMBR(Member1) +
>              NAMING(*SQL) DFTRDBCOL(DataLib)
>
> CLRPFM     FILE(Table1)
> .
> .
>
> RUNSQLSTM  SRCFILE(SourceLib/SourceFile) SRCMBR(Member2) +
>              NAMING(*SQL) DFTRDBCOL(DataLib)
>