You could try the Selectivity-clause in your SQL statement, forcing
usage of indexes (of which you know they exist, and are the proper ones
to use) and thereby limiting the number of possibilities DB2 has to
search through. It might save very much on the temporary space DB2 is
going to use to find the 'right' path.

-----Original Message-----
From: Harish Reddy V.
[mailto:db2udbdba-ezmlmshield-x2069382.[Email address protected]
Sent: woensdag 29 juni 2005 19:08
To: LazyDBA Discussion
Subject: The statement is too long or too complex - Very Urgent

Hi,

We are facing following when running long SQL (Informatica Mappings)

[IBM][CLI Driver][DB2/SUN64] SQL0101N The statement is too long or too
complex. SQLSTATE=54001

sqlstate = 54001

My STMTHEAP and APPLHEAPSZ are set to 4096.

I have run same SQL on different Server having same database having
STMTHEAP 3072 and APPLHEAPSZ 4096. It has run successfully.

I would like what could be reason I was able to run same SQL in that
particualar server. In order to run this, what should be done on my
first server where I have got the above error.

Regards

Harish







DB2 & UDB email list listserv db2-l LazyDBA home page