Re^2: System error: can't recv msg header Illegal seek; closing connection. at connect16.pl line 23

Hi Corion, Please note: The same code is running perfectly in another server which has (perl 5.8.0 and DBI version = 1.50 Teradata version = 1.20) installed in it.
As the recommended version of DBI and teradata for perl 5.8.4 is as below:
DBI version is 1.616 DBD::Teradata version is 12.001
Do you have any idea which is the compatible version of DBI and teradata modules which is required for perl 5.8.4 ?
It would be of great help.
Thanks

Comment on Re^2: System error: can't recv msg header Illegal seek; closing connection. at connect16.pl line 23

Replies are listed 'Best First'.
Re^3: System error: can't recv msg header Illegal seek; closing connection. at connect16.pl line 23 by Corion (Patriarch) on Sep 10, 2011 at 09:33 UTC
I gave you a list of four points. What point do you have problems with? You are running different code with different module versions on different machines. Eliminate the differences and you will find a cause for the different behaviour. ~~Also, how could I tell you how to change your code if you don't show your code?~~ You posted code, but the difference in behaviour is not from that code.	[reply]
Re^4: System error: can't recv msg header Illegal seek; closing connection. at connect16.pl line 23 by andrew878 (Initiate) on Sep 10, 2011 at 10:18 UTC
Hi Corion, Thanks for your response. Actually our requirement is such that the code which I have posted should be capable of running in perl v5.8.4 as well. So it will be great if you can suggest me the DBI and Teradata packages required for perl 5.8.4. Googling didn't help me much.. Thanks in advance	[reply]
Re^5: System error: can't recv msg header Illegal seek; closing connection. at connect16.pl line 23 by Corion (Patriarch) on Sep 10, 2011 at 11:48 UTC
Why do you think that I would know what versions of what packages work in your environment? You already know which versions of the packages work in your environment. I recommended in my previous posts that you try those before asking more questions. What problem do you have with these steps? Also not that the first step should be to investigate the network connectivity from the not-working machine. Check if you can connect with other tools, like ping, telnet to the Teradata port and the vendor tools of Teradata. If these steps prove problematic to you, consult with your system administrator, your database administrator and your database vendor.	[reply]