INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10

If your jdbc client

    (1) executes an INSERT INTO ... SELECT FROM ... statement
that would insert more than 32K rows and
    (2) utilizes the Statement.RETURN_GENERATED_KEYS in an
executeUpdate method and
    (3) utilizes the stmt.getGeneratedKeys() method

Then you can exceed a session's open table limit 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:

    0x00000000013da807 (oninit) afstack
    0x00000000013dd99e (oninit) afhandler
    0x00000000013dde12 (oninit) affail_interface
    0x0000000000ded4c1 (oninit) check_traperror
    0x00000000006fb943 (oninit) sqerr
    0x00000000006fbdae (oninit) sqerr1
    0x00000000006fcf28 (oninit) sqnameerr
    0x0000000000822d81 (oninit) process_autokey
    0x00000000008238e8 (oninit) addone
    0x0000000000826fff (oninit) insert_next
    0x000000000088f427 (oninit) doinsert
    0x00000000005d204e (oninit) excommand
    0x0000000000a141dc (oninit) sq_execute
    0x0000000000ad7243 (oninit) sqmain
    0x0000000001504176 (oninit) spawn_thread
    0x00000000013cc6c0 (oninit) th_init_initgls
    0x0000000001433568 (oninit) startup

****************************************************************
* USERS AFFECTED:                                              *
* Users of IDS 12.10.xC8 and earlier versions.                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* JDBC client that retrieves auto generated keys for insert    *
* into ... select from ... statement leaks opentable memory    *
* and open table entries in IDS.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

05.03.2019
08.10.2019
31.08.2020