Scheduler Error
On IDS 11.50.FC5 the SCHAPI scheduler stopped running tasks: dbWorker threads shut down with -213 "Statement interrupted by user" errors while Auto Update Statistics Refresh ran. The poster found "execute function task('scheduler start')" restarted the scheduler enough to run some tasks manually, but Art Kagel reported the same bug at a client where only a full server restart helped, and suggested upgrading (fixed around 11.50.xC7; xC8 then current). The poster did have to bounce the server, after which the worker threads failed again mid-AUS; he asked how to diagnose the shutdowns and no further answer is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
IDS 11.50.FC5 I have just noticed that none of my scheduled tasks seem to have executed since 11-29-10, when about half of the AUS statements executed. I have the following entry in my informix log: 20:34:05 SCHAPI: thread dbWorker1 task post_alarm_message(15-160390) shutting down 20:34:05 SCHAPI: Error -213 Statement interrupted by user. 20:34:05 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh, Location: NULL. 20:34:05 SCHAPI: Error -213 Statement interrupted by user. 20:34:06 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh, Location: NULL. 20:34:06 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh, Error Message: Unable to execute function [ aus_refresh_stats(integer,integer) ] . 20:34:06 SCHAPI: Error -213 Statement interrupted by user. 20:34:06 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh, Location: NULL. 20:34:06 SCHAPI: Error -213 Statement interrupted by user. 20:34:06 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh, Location: NULL. 20:34:06 SCHAPI: thread dbWorker2 task post_alarm_message(15-160390) shutting down 20:37:33 Checkpoint Completed: duration was 0 seconds. 20:37:33 Mon Nov 29 - loguniq 833, logpos 0x14b3018, timestamp: 0x584d6579 Interval: 71483 I'm not sure as to why it is reporting that the statement was interrupted by a user as I am the only person who directly accesses the server. I have verified that I was not working on the server at that time. Is there a method to restart just the scheduler threads or do I have to restart the Informix instance? Thanks for any assistance, Scott
reading through another thread, I found the syntax to restart the scheduler: "execute function task("scheduler start")" This seems to have restarted the scheduler successfully.
I've seen this one before at a client. Your dbWorker threads have
shutdown. They may or may not have restarted (onstat -g ath to see) but
even if they did, the new threads are not doing anything. The only solution
I have found is to bounce the entire server. IB this was fixed in the .xC7
release though the currently most stable release is the new .xC8 release
that came out a couple of weeks ago.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Thu, Dec 9, 2010 at 9:44 AM, SCOTT PERRY <scott.perry@state.mn.us> wrote:
> IDS 11.50.FC5
>
> I have just noticed that none of my scheduled tasks seem to have executed
> since 11-29-10, when about half of the AUS statements executed. I have the
> following entry in my informix log:
>
> 20:34:05 SCHAPI: thread dbWorker1 task post_alarm_message(15-160390)
> shutting
> down
> 20:34:05 SCHAPI: Error -213 Statement interrupted by user.
> 20:34:05 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh,
> Location:
> NULL.
> 20:34:05 SCHAPI: Error -213 Statement interrupted by user.
> 20:34:06 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh,
> Location:
> NULL.
> 20:34:06 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh, Error
> Message: Unable to execute function [ aus_refresh_stats(integer,integer) ]
> .
> 20:34:06 SCHAPI: Error -213 Statement interrupted by user.
> 20:34:06 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh,
> Location:
> NULL.
> 20:34:06 SCHAPI: Error -213 Statement interrupted by user.
> 20:34:06 SCHAPI: Type: TASK, Name: Auto Update Statistics Refresh,
> Location:
> NULL.
> 20:34:06 SCHAPI: thread dbWorker2 task post_alarm_message(15-160390)
> shutting
> down
> 20:37:33 Checkpoint Completed: duration was 0 seconds.
> 20:37:33 Mon Nov 29 - loguniq 833, logpos 0x14b3018, timestamp: 0x584d6579
> Interval: 71483
>
> I'm not sure as to why it is reporting that the statement was interrupted
> by a
> user as I am the only person who directly accesses the server. I have
> verified
> that I was not working on the server at that time. Is there a method to
> restart just the scheduler threads or do I have to restart the Informix
> instance?
>
> Thanks for any assistance,
>
> Scott
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001636c5afe9f9658a0496fc98c0
Thanks Art, I figured I would need to restart the server. However, it does appear as though the worker threads are performing work as the last runtimes of the tasks are now after I ran the scheduler start command. I was also able to run the AUS Evaluation task manually through OAT, which I couldn't do prior. I'll check the AUS Refresh task tonight and respond back as to whether it ran without bouncing the server.
Great! The dbWorker threads wouldn't restart for my client, glad it was easier for you. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) IIUG Board of Directors (art@iiug.org) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Thu, Dec 9, 2010 at 11:33 AM, SCOTT PERRY <scott.perry@state.mn.us>wrote: > Thanks Art, I figured I would need to restart the server. > > However, it does appear as though the worker threads are performing work as > the last runtimes of the tasks are now after I ran the scheduler start > command. I was also able to run the AUS Evaluation task manually through > OAT, > which I couldn't do prior. I'll check the AUS Refresh task tonight and > respond > back as to whether it ran without bouncing the server. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001636c5a78fc305870496fcf398
I did end up having to restart the server in order for the AUS Refresh task to run. Now, the real problem is that the dbworker threads failed again (after about half of the update statistics statements) with the following message in the log: 22:07:25 SCHAPI: thread dbWorker1 task post_alarm_message(15-161072) shutting down 22:07:25 SCHAPI: thread dbWorker2 task post_alarm_message(15-161073) shutting down How do I figure out why the worker threads are shutting down?