Re: Query "stopped" in its tracks, still "running"

[Dan <dan27649@xxxxxxxxx>]

Who knows what really is going on under the covers?  I expect that IBM's
got the DB2 (sorry, "Db2") engine tuned to a 'T'.  It's just *really*
strange that it wrote 5M records to the new table and then, JUST STOPPED.

DASD's only at 41%.

Funny thing is, this particular query is actually the CTE portion of
another query that I broke out for this test.

Since it's EOD, I'm going to kill the job and resubmit it.

- Dan

On Tue, Feb 13, 2018 at 5:30 PM, Musselman, Paul <
pmusselman@xxxxxxxxxxxxxxxx> wrote:

> I'm no SQL expert, but when AS/400 Query did something like that, it was
> joining every possible combination of join fields into a massive work
> file...
>
> I don't know if SQL does something similar, but how's your disk space
> looking??
>
> If all else fails, try just the A-B join by itself; and the B-C by itself,
> and see what you get...