Informix - Problembeschreibung
Problem IT19870 | Status: Geschlossen |
JDBC CLIENT THAT RETRIEVES AUTO GENERATED KEYS FOR INSERT INTO ... SELECT FROM ... STATEMENT LEAKS OPENTABLE MEMORY AND OPEN TAB | |
Produkt: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problembeschreibung: | |
If a JDBC client executes an INSERT INTO ... SELECT FROM ... statement that inserts more than 32K records and it utilizes a Statement.RETURN_GENERATED_KEY n an executeUpdate method and it also utilizes the stmt.getGeneratedKeys() method, it an exceed a sessions's open table limite of 32K and the insert will fail with a -242/-104 error: -242 Could not open database table table-name. -104 ISAM error: too many files open. If you trap for the -242 on the server (onmode -I -242) you will see close approximately 32K open table entries in "onstat -g opn" output for the asserting thread and a large opentable mem usage in "onstat -g ses " output for the asserting session# and a stack from the trap like: (oninit) afstack (oninit) afhandler (oninit) affail_interface (oninit) check_traperror (oninit) sqerr (oninit) sqerr1 (oninit) sqnameerr (oninit) process_autokey (oninit) addone (oninit) insert_next (oninit) doinsert (oninit) excommand (oninit) sq_execute (oninit) sqmain (oninit) spawn_thread (oninit) th_init_initgls (oninit) startup | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Informix users with JDBC auto generated key * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC9 * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.03.2017 10.07.2017 10.07.2017 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
12.10.xC9 | |
Problem behoben lt. FixList in der Version |