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

"The statement is too long or too complex".for a simple Alter table statement from CLP

P: n/a
Hi,

I ran the scripts in a file from Command Line Processor and it gave
the error for all the constraints being added, but not the indexes
being added.

For a simple statement like
Alter table A add constraint A_const foreign key(col1) references
B(col2);

it gives the error like "The statement is too long or too complex".

However, it doesn't give the error for the indexes being created.

If i run this statement in some other tool(or start a new session of
CLP), it works fine.

Before running this file, i ran a big file (around 138 MB) containing
insert scripts.

Could it have caused this unexpected behaviour?
What else could be the reason of this?

Rahul

Nov 5 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Rahul Babbar wrote:
Hi,

I ran the scripts in a file from Command Line Processor and it gave
the error for all the constraints being added, but not the indexes
being added.

For a simple statement like
Alter table A add constraint A_const foreign key(col1) references
B(col2);

it gives the error like "The statement is too long or too complex".

However, it doesn't give the error for the indexes being created.

If i run this statement in some other tool(or start a new session of
CLP), it works fine.

Before running this file, i ran a big file (around 138 MB) containing
insert scripts.

Could it have caused this unexpected behaviour?
What else could be the reason of this?
Looks like something was leaking memory. Can you open a PMR?
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Nov 5 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.