By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,851 Members | 1,746 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,851 IT Pros & Developers. It's quick & easy.

DB2 Error

P: n/a
Exception EDBEngineError in module Cserv.exe at 0013E2C8.
General SQL error.
[IBM][CLI Driver][DB2/NT]SQL0727N An error occurred during implicit
system action type "1". Information returned for the
error includes SQLCODE "-101", SQLSTATE "54001" and message tokens "".
SQLSTATE=56098.

I get the above error when using an application that performs an insert
into a DB2 table. I added a new Trigger to the table. There are a few
triggers on the table. I do not get the error when any one trigger is
the only trigger on the table. However, when there are multiple
triggers on the table then I get the above error. I believe that two
of the triggers are "too complicated" and can't both be on the table at
the same time.

Is there anything I can do to fix this error and keep my triggers
(which cause no error individually) on the table?

THX,
Karl

Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Karl wrote:
Exception EDBEngineError in module Cserv.exe at 0013E2C8.
General SQL error.
[IBM][CLI Driver][DB2/NT]SQL0727N An error occurred during implicit
system action type "1". Information returned for the
error includes SQLCODE "-101", SQLSTATE "54001" and message tokens "".
SQLSTATE=56098.

I get the above error when using an application that performs an insert
into a DB2 table. I added a new Trigger to the table. There are a few
triggers on the table. I do not get the error when any one trigger is
the only trigger on the table. However, when there are multiple
triggers on the table then I get the above error. I believe that two
of the triggers are "too complicated" and can't both be on the table at
the same time.

Is there anything I can do to fix this error and keep my triggers
(which cause no error individually) on the table? db2 "? sql0101"

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.

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.
You might want to increase the statement heap.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Nov 12 '05 #2

P: n/a
Knut Stolze wrote:
Karl wrote:

Exception EDBEngineError in module Cserv.exe at 0013E2C8.
General SQL error.
[IBM][CLI Driver][DB2/NT]SQL0727N An error occurred during implicit
system action type "1". Information returned for the
error includes SQLCODE "-101", SQLSTATE "54001" and message tokens "".
SQLSTATE=56098.

I get the above error when using an application that performs an insert
into a DB2 table. I added a new Trigger to the table. There are a few
triggers on the table. I do not get the error when any one trigger is
the only trigger on the table. However, when there are multiple
triggers on the table then I get the above error. I believe that two
of the triggers are "too complicated" and can't both be on the table at
the same time.

Is there anything I can do to fix this error and keep my triggers
(which cause no error individually) on the table?


db2 "? sql0101"


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.

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.
You might want to increase the statement heap.

One more thought: Are your triggers building a recursion?
And I don't mean whether a recursion can appear at runtime. What matters
is whether you soemhow end up comoiling in a recursion. (ie coming back
to a table which actually cause teh trigger to fire).

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.