You should not have to start up a second DBI connection. All that should be required is as follows: 
# set DB and SQL values as necessary
use DBI;
$dbh = DBI->connect "$DB_SERVER:$DB_NAME;$DB_HOST") or die "Can't conn
+ect to $DB_NAME, error ";
$sth = $ccmd_auth::dbh->prepare($sql) or die "Can't prepare $sql: $dbh
+->errstr\n";
$sth->execute;
$sth->finish;

[download]

After the $sth is 'finished', you should be able to prepare and use $sth again in other queries.

One thing I noticed in your code is that you refer to a $dbh2 when you set up your second $sth. Is this for a connection to a second database? Otherwise it should use the same $dbh that was originally set up. This may be what is causing your problem.

In reply to Re: Two connections are unnecessary by mosiondz
in thread Are 2 database connections neccesary w/DBI? by mculey

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.