Known issue: The module is not compatible with your Teradata (whatever that is).
It should come as no surprise I haven't worked with a Teradata before. Here's how I arrived at an answer:
- Grep the code. Look for that error message in the modules you're consuming. For that matter, look for that error message in the paths found in your Perl's @INC. Here's one way for if you have the modules installed on your system: grep -rin 'deprecated logon' $(perl -E 'say for @INC'). I do not have those modules all installed, so I used GREP::CPAN to rule-out the Perl libraries. This isn't foolproof, but it's a good start.
- Since that turns up nothing there's a strong possibility that the message isn't coming from Perl, and is coming from this Teradata thing. So now you can search the Internet for "Teradata deprecated logon". Surprisingly the first page of search results turned up Need to test deprecated login. And that page brought me to Known issue.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
