Closed H0bbitBaron closed 5 years ago
@escheie sorry to bother you, can you please have a glance at this issue, may be you have some ideas?
First, I would only initialize teradata.UdaExec() once, outside the loop.
Second, that error message is coming from the Database and it means your sessions transaction mode is different than the transaction mode used to create the stored procedure. You can explicitly set the transactionMode of the session using "transactionMode" argument/property.
First, I would only initialize teradata.UdaExec() once, outside the loop.
Second, that error message is coming from the Database and it means your sessions transaction mode is different than the transaction mode used to create the stored procedure. You can explicitly set the transactionMode of the session using "transactionMode" argument/property.
Yes, this helped! Thank you a lot. There can be 'Default', 'ANSI' and 'Teradata' modes. Solution for my conditions:
connect("${dataSourceName}", transactionMode='TERADATA')
P.S. Still wondering, why it worked using brute-force...
Hello! I'm trying to call stored procedure with parameters on Teradata server from Linux server via python:
and it works as a rule from 2-th time, but sometimes from 11-th and so on. Error is:
My udaexec.ini:
And full console log with error - https://pastebin.com/T3fwEcf0.
I suppose there is some timeout issue, but may be i'm wrong. Anyway, thank you in advance!