Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Sanjay Shah got an ODBC error saying a table had been dropped, altered or renamed. Art Kagel identified SQL error -710, caused when a prepared plan is invalidated by schema changes or update statistics, common before 11.10 or when AUTO_REPREPARE is 0. Fixes: run UPDATE STATISTICS FOR PROCEDURE, re-prepare and retry, or enable AUTO_REPREPARE. Sanjay said updating procedures and functions fixed it.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
SANJAY SHAH — — source: IIUG Forums & Mailing Lists
randomly during application running we are getting below error message
40002S 1000 ODBC Informix driver[informix]Table (informix.dpr) has been
dropped, altered or renamed.
What does it mean? it is Informix error message or ODBC or application error
messasge?
↪ replying to SANJAY SHAH
DAN MUELLER — — source: IIUG Forums & Mailing Lists
I would guess that this is a 710 error. There have been problems reported to
IBM about this. It would help in this case if you listed your o/s & version
al;ong with your IBM product versions.
What it means to you in a practical sense if that you need to recycle your
Informix engine and it will go away.
Version and platform information is important. Please post that when you
post a question.
That said, your application is receiving the SQL level error -710 which
indicates that after a query was optimized and a query plan developed
something changed to invalidate that query plan. This will typically affect
stored procedures or long running processes that prepare statements at
startup and execute them over and over again over time. The change could be
as serious as someone altered a table or dropped an index or as simple as
having updated statistics on one of the tables referenced in the query.
If you are using Informix version11.10 or later you should ONLY see this
error very rarely unless the ONCONFIG parameter AUTO_REPREPARE is set to
zero (0). If you are using Informix version 10.00 or earlier, then this is
a common problem. Solutions are:
- Recompile all stored procedures that reference tables that have been
altered who for which you have run update statistics by running UPDATE
STATISTICS FOR PROCEDURE... immediately after the change.
- In long running applications, trap the error and reprepare the affected
statement and retry the execution of that statement.
- Enable AUTO_REPREPARE in your ONCONFIG file if it is disabled.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
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 Tue, Jul 19, 2011 at 1:08 AM, SANJAY SHAH <shah@hcma.com.au> wrote:
> randomly during application running we are getting below error message
>
> 40002S 1000 ODBC Informix driver[informix]Table (informix.dpr) has been
> dropped, altered or renamed.
>
> What does it mean? it is Informix error message or ODBC or application
> error
> messasge?
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--bcaec54859d239aa8e04a86b1d0d
↪ replying to SANJAY SHAH
SANJAY SHAH — — source: IIUG Forums & Mailing Lists
Thank you all for replying. Updating procdures & functions did the trick. So
far have not received that error message.
Sanjay
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.