Archives of the TeradataForum
Message Posted: Fri, 29 Mar 2002 @ 15:44:06 GMT
I've run into this problem before, and here's what I can tell you.
In DBSCONTROL, a utility that sets system wide settings, there are a couple of parameters that can affect the amount of memory available to parse a request. As of V2R3.x, I know there were two, MaxParseTreeSegs and StepsSegmentSize. Increasing these limits from the default can often eliminate the type of error you are getting. It seems to me that I recall that with V2R4.0, there was a third setting related to Parsing memory that was also increased significantly to further reduce this problem, but I don't recall if it was simply an internal setting, or a new tunable parameter. Perhaps someone else could help here?
Thomas F. Stanek
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|