On 17 Oct, 16:31, "Art S. Kagel" <art.ka...@gmail.com> wrote:
> On Oct 17, 8:05 am, "Habichtsberg, Reinhard" <RHabichtsb...@arz-
>
> emmendingen.de> wrote:
> > Is there any way to kill a running update statistics.
>
> > UPDATE STATISTICS HIGH FOR TABLE foo (bar) DISTRIBUTIONS ONLY.>
> > I tried with with onstat -z several times but it runs and runs and seems to
> > do nothing anyway.
>
> I concur with DL, there's no way to kill a running UPDATE STATISTICS
> thread.
>
> Art S. Kagel
Why not? What is the stack for the thread? Is it in a critical section
otherwise that is a bug that needs to be reported to IBM.
David.
↪ replying to david@smooth1.co.uk
On Oct 24, 2:29 pm, "da...@smooth1.co.uk" <da...@smooth1.co.uk> wrote:
> On 17 Oct, 16:31, "Art S. Kagel" <art.ka...@gmail.com> wrote:
>
> > On Oct 17, 8:05 am, "Habichtsberg, Reinhard" <RHabichtsb...@arz-
>
> > emmendingen.de> wrote:
> > > Is there any way to kill a running update statistics.
>
> > > UPDATE STATISTICS HIGH FOR TABLE foo (bar) DISTRIBUTIONS ONLY.>
> > > I tried with with onstat -z several times but it runs and runs and seems to
> > > do nothing anyway.
>
> > I concur with DL, there's no way to kill a running UPDATE STATISTICS
> > thread.
>
> > Art S. Kagel
>
> Why not? What is the stack for the thread? Is it in a critical section
> otherwise that is a bug that needs to be reported to IBM.
It's apparently in some kind of critical section because it dies
eventually if you kill the client task or onmode -z the session and
usually it rolls back. You'd have to ask John Miller why it works
that way and if it's WAD.
Art S. Kagel
> David.