Dear List,
As an example for an article I'm working on, I'm showing how a hanging connect can be timed out in a Perl script via the alarm() call. By 'hanging connect' I mean a connection attempt that never connects and never returns an error code. I have one right now on my Linux box. I started a database, did kill -9 on the oracle processes, and now attempts to login to the database hang. It's been that way for 24 hours now. e.g. sqlplus scott/tiger@ts98 ... never returns an error code, never connects. Guess it isn't going to connect. This could be a problem in a ksh script written to check connectivity. ( which is why I use Perl ) The question is, why? What is a consistent way to reproduce this error? The method I used isn't consistent. This is something that I see happen from time to time on Oracle databases, both NT and Unix platforms, hence the reason for the timeout on the connect. Any thoughts on how to consistently reproduce this, on either platform? Thanks, Jared -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jared Still INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
