|
Archives of the TeradataForumMessage Posted: Fri, 30 Apr 2004 @ 13:47:33 GMT
This info can be found in Performance Optimization manual (I'm looking at the V2R4 version) page 3-20. Chapter 3 is about the dbscontrol record, and page 20 discusses the MaxParseTreeSegs field. Using The remote console utility from Teradata Manager, select the DBS Control utility. Then modify the PERFORMANCE category MaxParseTreeSegs to 1000. This creates more parsing segments for the PE to use. The command would be: MODIFY PERFORMANCE 4 = 1000 Then, after it notifies that the category is changed you need to write the new Control record with the write command: WRITE This info can be found in Performance Optimization manual (I'm looking at the V2R4 version) page 3-20. Chapter 3 is about the dbscontrol record, and page 20 discusses the MaxParseTreeSegs field. The default value is way too low for most complex queries and the more joins you have the higher the value should be. I use 1000, and never get that error message anymore, and we have a highly normalized database model, so our queries can get fairly complex in a hurry! Michael E. McBride
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||