Here's some troubleshooting procedures you can try.

Make these changes to your code:

#DBI->trace(DBD::ODBC->parse_trace_flag('odbcconnection'));
# Note: parse_trace_flags ('s' at the end) here:
DBI->trace(DBD::ODBC->parse_trace_flags('5|odbcconnection|odbcunicode'
+));

#my $dbh = DBI->connect('dbi:ODBC:nhitest','delli28','XXXXXXX');
my $connect_attrs = { PrintError => 0, RaiseError => 1, AutoCommit => 
+1 };
my $dbh = DBI->connect('dbi:ODBC:nhitest','delli28','XXXXXXX', $connec
+t_attrs);

[download]

Here's references to the documentation for those changes:

You can try running with AutoCommit => 1 and AutoCommit => 0.

You can increase the trace level from 5 up to 15.

-- Ken

In reply to Re^3: DBD::ODBC to Teradata by kcott
in thread DBD::ODBC to Teradata by DanEllison

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.