again ran into my most favorite "too complicated SQL statement" error. In this special case however, the statement is not really complex but "just" large:
SELECT DISTINCT A_.ITEM[...] approximately 5000 more ids go here [...],
FROM DOCUMENTS A_
WHERE (A_.id IN(36705154, 36705153, 36705152, 36703976, 36703975, ...
Trying to track this down, I found a few traces of similar issues and suggestions to set particular environment variables in the MaxDB instance both here and on external mailing lists, some of them rather old. However, as far as I can tell, we already tried all these things (including EnableVariableInput and MAX_PACKET_SIZE) before.
Any other ideas? MaxDB is 7.8.02.28 on RedHat. This seems to happen both with a native Linux application connecting via UnixODBC and with a Java application connecting via the 7.8 JDBC driver.
TIA and all the best,