Archives of the TeradataForum
Message Posted: Thu, 06 Mar 2008 @ 11:08:17 GMT
My documentation suggests (ODBC User Guide, ca. 2006) that 1MB is possible for the entire "array request" but the array is used to store not only the SQL statement but also what they call "parameter rows".
Some conditions is N * (T + R)<= 1MB, T + N * R <= 1MB
N stands for the number of parameter rows;
R - the size of a parameter rows;
T - the size of the SQL statement.
Not knowing the number and size of your parameter rows I can't say for sure whether these conditions are satisfied but I would guess that they probably should be as T in you case is just 180K so it is difficult to imagine that there would be so many parameters.
More likely you hit other limitations listed in the Guide:
N * R <= 64 KB
R <= 64 KB
I'd say try and inspect the tracing logs to find out more details on the "parameters" with parsing disabled.
The latter confirms that ODBC extensions are not used.
Try also to compare "parameter rows" in case ODBC parsing is enabled.
I forget which driver version you are using. 2006 and higher should support this and the documentation does not specify any additional restrictions for the "parsing disabled" cases so if the "parameter rows" inspection does not reveal any suspects this case can be submitted as a bug.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|