On occassions when an oracle instance is having trouble, my DBI connections hang. For example, if the oracle archive log destination is full or the OS itself is hung, the DBI connection will also hang.
With DBI's trace level 3, it remains hung on the following: -> connect for DBD::Oracle::dr (DBI::dr=HASH(0x40245c28)~0x4055c1f4 'DS1' 'su' **** HASH(0x40553c28)) The program itself connects to a list of Oracle servers and works fine except when the oracle instance itself is in difficulties. This stops the processing of the rest of the list, and does not even return an error message. At this site, there are a number of perl programs performing various functions across multiple dataservers. This issue has surfaced with Oracle but not with Sybase. Is there a way to have connections timeout when they do not respond? regareds, David
