15.00 - Working Around Optimizer Memory Problems Encountered When Creating Join Indexes for Partitioned Tables - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

Product
Teradata Database
Release Number
15.00
Content Type
Programming Reference
Publication ID
B035-1184-015K
Language
English (United States)

Working Around Optimizer Memory Problems Encountered When Creating Join Indexes for Partitioned Tables

If you experience 3710 errors 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 PPI table.

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

 

FOR this type of system …

YOU should set the value for MaxParseTreeSegs to …

byte‑packed format

2000

byte‑aligned format

4000

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

See Utilities: Volume 1 (A-K) for information about how to change the setting for the MaxParseTreeSegs field in the DBS Control record. You cannot complete this process without contacting a Teradata support representative.

See Database Design for information about some special applications of join indexes to partitioned tables.