|
Problem IT36294
|
Status: Closed |
EXECUTING PROCEDURE ON SECONDARY CAN PERSISTENTLY RETURN 640 QPLAN SANITY FAILURE
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
This problem was originally reported running a special build of
IDS 12.10.FC9W1 on hpia64. The test
case I developed, reproduces the problem running IDS 12.10.FC9W1
on linux x86_64 and I also confirmed
it reproduces on 12.10.FC14.
When a client (ESQL, JDBC, ODBC) prepares an execute stored
procedure statement and continually
executes that prepared statement, there is a small window where
a -640 error can be returned to the
client upon executing the statement on a secondary. This window
is opened when the minversion of the
table is modified via some action on the primary like an update
stats of a table in the procedure or granting
or revoking privs on a table in the procedure.
If execute of the procedure on the secondary does return the
640: Qplan sanity failure then this error will
persist for all subsequent executions of the procedure on the
secondary.
One workaround to this problem is to 'set optimization low' in
the same session before executing the procedure
on the secondary. To remedy the -640 error, you can run update
statistics for procedure on the primary.
As a point of reference, if you trap for the -640 error on the
secondary, you will see a stack like:
0x0000000001410459 (/work2/prod/12.10.FC14/bin/oninit) afstack
0x0000000001413431 (/work2/prod/12.10.FC14/bin/oninit) afhandler
0x0000000001413c12 (/work2/prod/12.10.FC14/bin/oninit)
affail_interface
0x0000000000e10757 (/work2/prod/12.10.FC14/bin/oninit)
check_traperror
0x0000000000701f21 (/work2/prod/12.10.FC14/bin/oninit) sqerr
0x000000000070238e (/work2/prod/12.10.FC14/bin/oninit) sqerr1
0x0000000000b54456 (/work2/prod/12.10.FC14/bin/oninit) d_tabdesc
0x0000000000b52e17 (/work2/prod/12.10.FC14/bin/oninit) d_expr
0x0000000000b55378 (/work2/prod/12.10.FC14/bin/oninit) d_node
0x0000000000b55cbd (/work2/prod/12.10.FC14/bin/oninit) d_extree
0x0000000000b56416 (/work2/prod/12.10.FC14/bin/oninit) d_qplan
0x00000000006a6b46 (/work2/prod/12.10.FC14/bin/oninit)
qd_getqplan
0x0000000000694ecb (/work2/prod/12.10.FC14/bin/oninit)
ip_evalexpr
0x0000000000699cc4 (/work2/prod/12.10.FC14/bin/oninit) runproc
0x000000000069b691 (/work2/prod/12.10.FC14/bin/oninit)
udrlm_spl_execute
0x0000000000a630be (/work2/prod/12.10.FC14/bin/oninit)
udrlm_exec_routine
0x00000000006d6e19 (/work2/prod/12.10.FC14/bin/oninit)
udr_execute
0x00000000006dd5e5 (/work2/prod/12.10.FC14/bin/oninit) exroutine
0x0000000000a2afdd (/work2/prod/12.10.FC14/bin/oninit) sq_exproc
0x0000000000ae7b71 (/work2/prod/12.10.FC14/bin/oninit) sqmain
0x000000000154290b (/work2/prod/12.10.FC14/bin/oninit)
spawn_thread
0x0000000001401c70 (/work2/prod/12.10.FC14/bin/oninit)
th_init_initgls
0x0000000001448997 (/work2/prod/12.10.FC14/bin/oninit) startup |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when *
* available). *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC15 and 14.10.xC7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when *
* available). *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC15 and 14.10.xC7. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.03.2021
26.08.2021
26.08.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
