My 32-bit DB2 v9.7.5 *client* on Windows crashes when I compile a specific long
SQL-PL stored procedure (at the command line db2 -tvf proc.sql).
The database is remote.
Windows shows a message popup "IBM(R) DB2(R) has stopped working..." as soon as clp runs the line 'create procedure .....'
The same stored-procedure file compiles successfully on a Linux v9.7.5 client (using the same remote database as the Windows client).
But other smaller stored procedures compile fine on this client box, so it might be a size-related problem.
The file size of the stored-procedure file is around 137KB.
The db2-client db2diag.log shows two relevant messages:
FUNCTION: DB2 UDB, command line process, clp_savecmd, probe:12
MESSAGE : Command is too long to be saved in cmdhistory
DATA #1 : Command text truncated (max 20 chars), PD_CLP_TYPE_CMD, 20 bytes
create procedure xxx
then lots of these:
FUNCTION: DB2 UDB, command line process, clp_bp_con, probe:33
MESSAGE : I22 Read Queue Timeout Loop
Anyone got any suggestions for what *db2-client* settings can be tweaked to workaround this?