17.10 - Working Around Optimizer Memory Problems Encountered When Creating Join Indexes for Partitioned Tables - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - SQL Data Definition Language Detailed Topics

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Release Date
July 2021
Content Type
Programming Reference
Publication ID
B035-1184-171K
Language
English (United States)

If 3710 errors occur when running queries against a partitioned table with a join index, you can increase the amount of memory that is available to the Optimizer by updating the MaxParseTreeSegs DBS Control flag to a value that ensures that it can process any request on the partitioned table.

The recommended initial setting for the MaxParseTreeSegs field is as follows.

System Format MaxParseTreeSegs Setting
Byte-packed 2000
Byte-aligned 4000

You might find that your query workloads are such that these values need to be increased still further.

See Teradata Vantage™ - Database Utilities, B035-1102 for information about how to change the setting for the MaxParseTreeSegs field in the DBS Control record. You must contact a Teradata support representative to complete this process.

See Teradata Vantage™ - Database Design, B035-1094 for information about some special applications of join indexes to partitioned tables.