I'm wondering who else out there has had a problem with -710 errors using Informix 7 and/or 9?

We had a lot of them with Informix 7.31 on AIX 4.3.3 and never solved the problem. When we upgraded to Informix 9.4 (AIX 5.2) we moved the data via "dump and reload" and the problem went away for a while.

The problem seems greatest on a table called "update_source" which, while static, has foreign keys to 25 other tables, most of which are updated frequently and two of which are completely rebuilt (via drop/create table) about once a week. Even so, we get the -710 on other tables as well with the only common thread being that there is a large amount of insert/update activity on the table(s).

Full statistics are run every Sunday, partial stats are run daily and a (very) few tables get stats multiple times a day. Procedure statistics are run twice a day, every day.

Anyone got a clue?

Thanks,
Jay

sending to informix-list

Konigsberg, Jay wrote:
> I'm wondering who else out there has had a problem with -710 errors using Informix 7 and/or 9?
>
> We had a lot of them with Informix 7.31 on AIX 4.3.3 and never solved the problem. When we upgraded to Informix 9.4 (AIX 5.2) we moved the data via "dump and reload" and the problem went away for a while.
>
> The problem seems greatest on a table called "update_source" which, while static, has foreign keys to 25 other tables, most of which are updated frequently and two of which are completely rebuilt (via drop/create table) about once a week. Even so, we get the -710 on other tables as well with the only common thread being that there is a large amount of insert/update activity on the table(s).
>
> Full statistics are run every Sunday, partial stats are run daily and a (very) few tables get stats multiple times a day. Procedure statistics are run twice a day, every day.
>
> Anyone got a clue?

Are you re-preparing prepared statements in long-running processes and
middleware servers after running update statistics? Often the update stats
on an active table will invalidate the query plan computed when a statement
is PREPAREd. The next time you try to EXECUTE such a statement or OPEN a
cursor declared for it you will get a -710 error. Our middleware is coded
to just reprepare the statement and try the EXECUTE/OPEN again when it gets
-710.

Art S. Kagel