|
Blue Forest http://www.lslnet.com at 11:08 on July 18, 2006
[Sentence was too long or too complicated --
Can there are mistakes what is the solution? :
[IBM][CLI Driver][DB2/HP64] SQL0101N sentences too long or too complicated. SQLSTATE=54001
SCRIPT : Connection : left *** 130.17.0.102-sdinst-SDBI (sdinst) *** Mar-15-2005 13:09:53 |
[Sentence was too long or too complicated --
I have encountered this error, stmtheap first to try the increase. Not the case then divided into a number of phrases or sentences changed to implement. |
[Sentence was too long or too complicated --
I have not yet seen such a mistake, look at the posted sgl |
[Sentence was too long or too complicated --
| [Sentence was too long or too complicated --
Met, and think of ways to change sgl |
[Sentence was too long or too complicated --
How have this problem, the mechanisms DB2 is not good? |
[Sentence was too long or too complicated --
There is also a good mechanism for the Eastern limit! |
[Sentence was too long or too complicated --
Not? 83 small firms ah, write the sentence is too long to see the test switch. |
[Sentence was too long or too complicated --
Met many times, the final solution is to sgl apart. I do not know whether there are better ways |
[Sentence was too long or too complicated --
| [Sentence was too long or too complicated --
Tablespace increase the size seems to be able to solve the problem. But also there should be a limit! |
[Sentence was too long or too complicated --
Try padding bind. . . . /@db2cli.lst Clipkg=6. |
[Sentence was too long or too complicated --
There have been such things. Optimization sgl : a phrase that : Optimizing database, increased buffer pool |
| |