in reply to DBD::Teradata and Teradata V2R5.1
Are you sure it's a Perl issue? Could the upgrade have deprecated a bunch of username/passwords including the one(s) that your script is using?
Can you connect to the database using the same username and password that the script is using?
A simple google search for:
has given me the following information.teradata V2R5.1 "deprecated logon"
Release V2R5.1 introduces the Encryption feature.
The following table provides information about the option used to control encrypted logons in the Gateway Control utility
Option:
Note: Deprecated logon is a clear text.bAllowDeprecatedLogons
Description:
Enables deprecated logons.
To enable deprecated logons, use the -b option as follows:
allows the gateway to accept deprecated and encrypted logons.gtwcontrol -b yes
ensures that the gateway accepts only encrypted logons.gtwcontrol -b no
The default is NO.
Comments:
In Release V2R5.1, the Teradata Gateway always supports encrypted logons. However, if you have not upgraded to
Teradata Tools and Utilities 7.1, you can enable the gateway to accept both encrypted and unencrypted, also referred
to as deprecated logons.
It doesn't look like a Perl issue at all. Perhaps it's advice to Upgrade client software to latest version is the way to go... Of course, for some bizarre reason the writer of DBD::Teradata has chosen only to sell the later versions and you may not be able to afford the US$2695.00 ... but I can't help you with that. Check that the newest version of DBD::Teradata handles encryption before you spend your money on it though.
Hope this helps.
jarich
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: DBD::Teradata and Teradata V2R5.1
by Anonymous Monk on Jul 09, 2013 at 16:14 UTC | |
by Anonymous Monk on Jul 09, 2013 at 19:47 UTC |