Strange error/dumps when using QuantumDB

[Peter.Colpaert@xxxxxxxxx]

Hi group,

I've managed to bring our system to its knees when using QuantumDB in WDSC 
Lite.

I did an SQL update to approximately 40.000 records in a file having an 
*after *update trigger, and got an MCH2804 error:

Tried to go larger than storage limit for object 
  QGY_QZDASOINITQUSER_____996796. 
Problem log updated. 
Space offset X'00000000' or X'0000000000000000' is outside current limit
  for object &1. 
Dump output directed to spooled file 4, job 996796/QUSER/QZDASOINIT 
  created on system HI000001 on 26/04/06 11:21:26. 

The strange thing is that, when I do the exact same update from a 
green-screen STRSQL session, the update is done correctly without dumps.

I searched the archives of midrange-l for (and googled) this error, but 
the hits referred to user profiles not having *NOMAX for max storage (both 
my own profile and QUSER have *NOMAX).

Has anybody encountered this error, or is it maybe time to give IBM a 
call?

Thanks,

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----