 |
 |
Archives of the TeradataForum
Message Posted: Thu, 27 Mar 2008 @ 16:17:46 GMT
| Subj: | | Re: Impact of Increasing MaxParseTreeSegs |
| |
| From: | | Victor Sokovin |
| | The manual says, I should increase the value of the MaxParseTreeSegs. My question now is: Which side effects do I have to expect if I do
so? Does Teradata allocate the maximum number of possible segments (then increasing MaxParseTreeSegs would certainly have negative impact on the
memory available for other tasks)? Or does Teradata allocate only as many parser segments as are currently needed (then increasing
MaxParseTreeSegs would have almost no impact on the memory available for other tasks)? | |
| | (in fact, I have some other options than increasing the value, the statement that caused the error is really complex) | |
Martin,
My understanding is that this parameter has been becoming increasingly complex and its tuning has indeed too many ins and outs for regular
customers to deal with so the value you find in your configuration is pretty much part of the product delivery by Teradata. I don't know whether
it is an officially recognized policy or not but there is at least an expectation that they advise on this parameter for all new installations and
updates of existing ones. You may check whether this is indeed the case in your particular situation. If it is, then you just need to reduce
complexity of the query. Usually you would have a feeling as to which part of the statement is likely to cause the problem.
Victor
| |
