IDS Forum

Re: aus_work_info

Posted By: JACQUES RENAUT
Date: Wednesday, 20 November 2013, at 12:21 p.m.

In Response To: aus_work_info (FRANK)

Original post:

Folks,

IDS11.50 FC8, Redhat Linux.

A couple of days ago, we reverted IDS from 11.70 FC7 back to 11.50 FC8.
Today we did a inplace upgrade of OS of Linux from Redhat Linux 5 to 6.

When I started database, the error shows,

SCHAPI: [Auto Update Statistics Evaluation 38-14] Error -206 The specified
table (aus_work_info) is not in the database.
15:52:18 SCHAPI: [Auto Update Statistics Evaluation 38-14] Error -111 ISAM

Any comments?

Thanks,
Frank

Response:

I believe the aus_work_info table is dropped and created every time the Auto Update Statistics Evaluation task is run. Also, in the SPL where the table is dropped, there is on exception blocks that would have the SPL ignore the 206 error...so that would imply to me the error happened in some other place during the task...and it seems to me the only way that would be possible is if somehow perhaps the Auto Update Statistics Evaluation task was trying to be run by 2 worker threads so the 2nd run dropped the table after the 1st run had dropped/recreated the table and so then the 1st run got an error the table didn't exist and then the 2nd run completed with no problems. I think you could check to see if that happened by finding the tk_id of the Auto Update Statistics Evaluation task (you can do select * from ph_task where tk_name matches "Auto Update Statistics Evaluation") and then using the tk_id, do a select * from ph_run where run_task_id = <the td_id from previous query>...that will get you all the times that task was run and the run_time column is when that task was run...so perhaps you'd find that task run at either 2 identical times with different run_id's and run_task_seq numbers (indicating different runs of that task) or run_time's within a couple seconds/minutes of each over (not sure how far apart they could possibly be...it would depend on your system and how long that task took to complete).

Generally speaking, I would say the error was likely harmless and it would just mean the task failed at that particular time...as long as it doesn't continually fail and ran successfully the next time around I'd guess you are ok. But to get the 206 error when the task itself is dropping and creating the aus_work_info table, I think either the task got started twice by 2 different worker threads (or maybe the worker threads internally started up the task and then somebody manually executed the task as well so that's how it got started twice) and 1 stepped on the other, or somebody else would have had to drop the aus_work_info table while the task was running.

Jacques Renaut
IBM Informix Advanced Support
APD Team

Messages In This Thread

• aus_work_info
  FRANK -- Wednesday, 20 November 2013, at 11:08 a.m.
  • Re: aus_work_info
    Art Kagel -- Wednesday, 20 November 2013, at 11:17 a.m.
  • Re: aus_work_info
    JACQUES RENAUT -- Wednesday, 20 November 2013, at 12:21 p.m.
  • Re: aus_work_info
    Nita Dembla -- Wednesday, 20 November 2013, at 1:49 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.