Home Page for the TeradataForum
 
https:

Archives of the TeradataForum

Message Posted: Wed, 05 Sep 2012 @ 22:00:25 GMT


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


Subj:   Re: SQL Assistant Version 13 - Error 3932
 
From:   Dempsey, Mike

After checking the code I see one situation in which you may get a problem when there are many statements.

This problem will only occur if BOTH:

a) there are exactly (100 x n) + 1 statements. (e.g. 101, 201, ...)

b) there is no semicolon after the last statement However this will cause the app to fail - it will not generate the reported Teradata error.

(I will fix this problem in the next efix)


The only way in which the reported error can occur is if the parser is getting confused and not recognizing one of the semicolons as being an end of statement marker.

This would make it submit multiple statements as a single request - which would be illegal if one of them was DDL.

There have definitely been cases where this has occurred but I can't determine exactly what the cause is without seeing the exact query text.

A number of such problems have been fixed over the past few years so you may find that a newer version of the app solves the problem.

I don't think the original post provided the version number of the app that was exhibiting the problem, but the latest efixes are:

     13.0.0.16    for TTU 13.00 (Does not contain the most recent parser fix)
     13.11.0.5    for TTU 13.10
     14.01.0.1    for TTU 14.00

Mike Dempsey



     
  <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: 28 Jun 2020