I am experiencing a problem in some way similar to ID
[ 585531 ] :
I'm running Rexx/SQL 2.4 and Regina 126.96.36.199 on a
Win2000 pro (sp4) machine equipped with a PIII
800mhz 256MB Ram, trying to insert rows in a
MSAccess2000 DB via ODBC (drivers ver. 4.00.6200.00).
My program tries to INSERT (via
sqlPREPARE/sqlEXECUTE) rows, read from a .txt file,
into the DB, without particular computation or
When the data to insert are relatively few (e.g. <1000
rows) all works fine.
When trying to massively insert more data (let's say
4000 rows of 200/300 characters each), after a while
(a couple of thousands inserts) I receive to msg "REXX
SQL-10 Out Of Memory".
Tracking it with W2k task manager I effectively notice,
during the running of the script, high usage of cpu and
memory, although not so high to freeze the machine.
I tried - like the guy of 585531 - to do some variations
to the program, like changing the frequence of
SQLCOMMIT, dropping the rexx variables (containing
SQL data), using SQLdispose, calling sqldropfuncs and
rxfuncdrop followed by rxfuncadd and sqlload funcs, in
short I did all I could but there seem to be no way: the
result is always the same.
Since I think this kind of elaboration is quite standard,
I guess I'm not the first one coping with problems like
this: do anyone have any solution or workaround (other
than manually running the program each time on a
small set of data, which could be very annoying when
you got more than 50000 rows once a month to
If not, are there any known bug of the SQL interface
responsible of this?
Any help/comment will be highly appreciated.