I'm afraid that you're not giving us a lot to go on NateTut. Teradata is a database well outside of my experience. What version of Teradata were you using when your Perl code used to work?
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:
teradata V2R5.1 "deprecated logon"
has given me the following information.
Teradata Database Utilities - Gateway Control
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:
bAllowDeprecatedLogons
Note: Deprecated logon is a clear text.
Description:
Enables deprecated logons.
To enable deprecated logons, use the -b option as follows:
gtwcontrol -b yes
allows the gateway to accept deprecated and encrypted logons.
gtwcontrol -b no
ensures that the gateway accepts only encrypted logons.
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.
You can read more about all of this kind of thing at
http://www.teradataforum.com/teradata_pdf/b035-1098-083a.pdf
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 |