I got great advice and support from a number of folks, in particular Martin J. Evans (martin.ev...@easysoft.com), who helped me diagnose the root cause of the problem.
"We found tusc off this thread and the resultant trace pin pointed the problem which was a bug with the semaphore code I think I fixed in unixODBC in 2004 - which explains why I didn't remember it. Deleting the semaphore fixed the problem temporarily but upgrading to 2.2.9 (or later) or recompiling without stats support is the only sure long term fix." On Fri, Jun 28, 2013 at 12:44 PM, <eric.b...@barclays.com> wrote: > DBI->trace(…) might help.**** > > ** ** > > You should also review the docs on the use of errstr. You should be using > $DBI::errstr, not DBI->errstr to the best of my knowledge and according to > the docs.**** > > ** ** > > Eric D. Berg**** > > IPRS Infrastructure **** > > ** ** > > *From:* dbenti...@gmail.com [mailto:dbenti...@gmail.com] *On Behalf Of *Dan > Bent > *Sent:* Wednesday, June 26, 2013 4:15 AM > *To:* dbi-users@perl.org > *Subject:* "connect" not connecting**** > > ** ** > > I have been using DBI for several years, and have a fairly extensive group > of programs that relay on DBI to connect to a database and extract data. > All my programs use a common library of functions that includes a function > which connects to the database:**** > > **** > > $dsn = 'dbi:ODBC:prod1' ;**** > > $user = 'user' ;**** > > $passwd = 'XXXXXXXX' ;**** > > $dbh = DBI->connect($dsn, $user, $passwd, > {RaiseError => 1, AutoCommit => 0}) > or die "Could not connect to database: " . DBI->errstr ;**** > > **** > > This has worked for years, but yesterday, it suddenly stopped working. Now > my programs get to this function, and stop. No error messages are > generated, and the database logs do not show a connection attempt, failed > or otherwise.**** > > **** > > The database itself is an odd thing that I don't expect folks to be > familiar with. We use Relativity, which allows CISAM flat files to be used > like a relational database. There have not been recent changes to > Relativity, and I can see that other (non-Perl) applications are accessing > the database without any issues. So the problem seems to be isolated to > Perl programs attempting to connect to this database.**** > > **** > > I am not sure what to do to gather more information about this issue. I > wrote s test program to isolate the DBI->connect method, and gather > information. I am able to list the available drivers: Proxy, Sponge, DBM, > ExampleP, File, ODBC, but I'm not sure what else I can do.**** > > **** > > I would appreciate any suggestions about how to gather more information or > resolve this issue.**** > > _______________________________________________ > > This message is for information purposes only, it is not a recommendation, > advice, offer or solicitation to buy or sell a product or service nor an > official confirmation of any transaction. It is directed at persons who are > professionals and is not intended for retail customer use. Intended for > recipient only. This message is subject to the terms at: > www.barclays.com/emaildisclaimer. > > For important disclosures, please see: > www.barclays.com/salesandtradingdisclaimer regarding market commentary > from Barclays Sales and/or Trading, who are active market participants; and > in respect of Barclays Research, including disclosures relating to specific > issuers, please see http://publicresearch.barclays.com. > > _______________________________________________ >
