Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Mon, 23 Feb 2004 @ 19:57:26 GMT

  <Prev Next>  
Next> Last>>  

Subj:   Message "3705 Request executed in interpretive EVL mode"
From:   Priya Chander


When we are executing a complex query we faced the following message

"3705 Request executed in interpretive EVL mode".

The error explanation we got from manuals is

Explanation: This is a warning only, not an error. It indicates that the current request will be executed using interpretive EVL code rather than executable EVL code.

Cases where this warning will be returned are:

a) Ran out of parser tree segments when trying to generate the executable EVL code.

b) Ran out of Plastic Step segment when trying to fit both interpretive EVL code and executable EVL code in the Plastic Steps.

c) Ran out of space in the concrete step segment when building one large single step. In an attempt to save space, the compiled is replaced with the interpretive EVL code. The only remedy is to simplify the query.

Generated By: GNCStEvl, GncApply.

For Whom: DBA User and System Support Representative. Note: The request is still processed despite the warning.

Remedy: This message is for information only. To avoid the warning, user may increase the DBS Control Record field MaxParseTreeSegs for case (a) and field StepsSegmentSize for case (b). See Teradata Database Administration Manual, Chapter 2. titled Setting Up Teradata.

Can some one explain about the

1) "Interpretive EVL code" and "executable EVL code" and the difference between them.

2) What does "parser tree segments", "Plastic Step segment", "concrete step segment" signify?

Thanks in Advance.

With Regards,

Prakash Attili.

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