Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Thu, 06 Nov 2003 @ 19:29:59 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: Insufficient memory to parse request error
 
From:   Ferry, Craig

Just got this from the GSC. I tried the DIAGNOSTIC command and it worked.

Thanks for all the suggestions.


-------------------------

Tech Note: With V2R5, improvements were made to enhance the performance when using Derived Tables. Teradata now manipulates the Derived Tables in memory rather than materializing them into a spool file. To realize these performance gains, it is recommended that the Internal Flag:

44.   SpoolDerivedTables     = FALSE

within the DBSControl Utility be set to FALSE (the default).

There have been instances in which this sites have seen a significant increase in memory consumption. The following errors have also been observed:

Failure 3710: Insufficient memory to parse.
Failure 3809: Column is ambiguous.
Failure 5699: Internal error: Could not convert a parse tree into text.

If you encounter this type of problem, you should report them to the Teradata Global Support Center (TGSC).

While the problems are being pursued, the following temporary workarounds are available:

If possible, prior to submitting the function, submit the following SQL statement:

DIAGNOSTIC nodt ON FOR SESSION;

This will cause Teradata to spool the Derived Table rather than manipulating it in memory. If this is not practical in your environment, the alternative is to set this parameter universally by setting the Internal DBSControl parameter:

   44.   SpoolDerivedTables     = TRUE


     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023