"db2sysc" <db*****@yahoo. com> wrote in message
news:69******** *************** ***@posting.goo gle.com...
We have defined a NICKNAME to go to Mainframe table and when do a
SELECT * FROM NICKNAME from a version 8 client we get SQL0101N error.
Maybe:
o Increase the size of the statement heap (stmtheap) in the database
configuration file.
Regards
Paul Vernon
Business Intelligence, IBM Global Services
C:\SQL>db2 ? SQL0101N
SQL0101N The statement is too long or too complex.
Explanation:
The statement could not be processed because it exceeds a system
limit for either length or complexity, or because too many
constraints or triggers are involved.
If the statement is one that creates or modifies a packed
description, the new packed description may be too large for its
corresponding column in the system catalogs.
Federated system users should also check to see if the
statement:
o Exceeds either a federated server system limit or a data
source system limit for length or complexity.
o Violates some other data source specific limit.
The statement cannot be processed.
Note: Where character data conversions are performed for
applications and databases running under different
codepages, the result of the conversion is exceeding the
length limit.
User Response:
Either:
o Break the statement up into shorter or less complex SQL
statements.
o Increase the size of the statement heap (stmtheap) in the
database configuration file.
o Reduce the number of check or referential constraints
involved in the statement or reduce the number of indexes on
foreign keys.
o Reduce the number of triggers involved in the statement.
o Federated system users: determine which data source is
failing the statement (see the problem determination guide
for procedures to follow to identify the failing data source)
and determine the cause of the rejection. If the rejection
is coming from the federated server, increase the size of the
statement heap (stmtheap) in the database configuration
file.
sqlcode : -101
sqlstate : 54001
