Informix - Problem description
Problem IT34040 | Status: Closed |
-9700 ERROR CAN OCCUR ON OPEN CURSOR AFTER AUS_EVALUATOR TASK RUNS AND UPDATE STATISTICS | |
product: | |
INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70 | |
Problem description: | |
The following problem was first reported by customer running 11.70.FC9 on linux x86_64. This has also been reproduced in 12.10.FC10 and does not appear to be platform specific. The reproduction involves running a multi-threaded client having each associated server session prepare a statement and open it several hundred times before repeating the prepare again. On occasion after the aus_evaluator task has run and update statistics has run as well on the tables involved in the query that the open cursor can fail with -9700. Ifyou try a subsequent open ... with re-optimization, it will fail as well. To workaround the problem, it seems you have to prepare the statement again and re-declare the cursor before you can open it again, so you will have to error check opens for -9700 errors and re-prepare. If you use 'onmode -I -9700' to trap for the -9700 error, you will see in the af.file that the onstat -g ses output for the trapped session shows a stack like: afstack afhandler affail_interface check_traperror sqerr sqerr1 udr_determine expr_determine routine_bind sqbind sq_common_bind sqmain spawn_thread th_init_initgls startup and for the session currently running: Sess SQL Current Iso Lock SQL ISAM F.E. Id Stmt type Database Lvl Mode ERR ERR Vers Explain 23934 SELECT dbname CR Not Wait -9700 0 9.35 Off Current statement name : democursor1 Current SQL statement (5908) : Host variables : address type flags value ----------------------------------------- 0x000000005c11e038 CHAR 0x000 25000.0 0x000000005c11e0c8 CHAR 0x000 25000.0 0x000000005c11e158 INT 0x000 4144996 0x000000005c11e1e8 INT 0x000 4144998 0x000000005c11e278 INT 0x000 4145000 0x000000005c11e308 INT 0x000 -1 The interesting thing here is that the first two host variables are normally DECIMAL and not CHAR type and a typical onstat -g ses for a session's running thread would look more like: Id Stmt type Database Lvl Mode ERR ERR Vers Explain 36 SELECT dbname CR Not Wait 0 0 9.37 Off Current statement name : democursor1 Current SQL statement (0) : Host variables : address type flags value ----------------------------------------- 0x000000005ba3c038 DECIMAL 0x000 25000 0x000000005ba3c0c8 DECIMAL 0x000 25000 0x000000005ba3c158 INT 0x000 4144996 0x000000005ba3c1e8 INT 0x000 4144998 0x000000005ba3c278 INT 0x000 4145000 0x000000005ba3c308 INT 0x000 -1 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 11.70.xC9W2, 12.10.xC15 * * and 14.10.xC5. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server to 11.70.xC9W2, 12.10.xC15 and * * 14.10.xC5. * **************************************************************** The fix by default is disabled, enable it with ONCONFIG SQL_DEF_CTRL bit 0x2000000. | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 11.70.xC9W2, 12.10.xC15 * * and 14.10.xC5. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server to 11.70.xC9W2, 12.10.xC15 and * * 14.10.xC5. * **************************************************************** The fix by default is disabled, enable it with ONCONFIG SQL_DEF_CTRL bit 0x2000000. | |
Comment | |
Fixed in Informix Server 11.70.xC9W2, 12.10.xC15 and 14.10.xC5. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.08.2020 11.09.2020 11.09.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |