From: cetz@cetz.rhein-main.de (Christopher Etz) In article, mageshdi@worldaccess.nl wrote: >Sometimes reports started from the commandline fail during a short period of >time with the error-message as described below. > >At the same time application-programs (OpenRoad: batch/interactive) connect >and run without any problem against the same database. > >After a short time, the report-connect problem disappears automatically and >reports run well wihtout any intervention. I've come across a similar problem: A shell script calls a lot of commands written in embedded SQL. Sometimes the CONNECT fails with "Unable to make outgoing connection" and the Unix error is "address already in use". After programming re-tries, the CONNECT always succeeds (earlier or later). I suspect, it takes a certain emount of time until a socket can be re-used after a DISCONNECT. The situation I described, happens with Ingres 6.4 on RS6000/AIX (!). So it looks like an OS related socket problem. Unfortunately, I haven't heard of any fixes, either from CA or from IBM. Christopher Etz -- ________________________________________________________________________ Christopher Etz Telefon: (069) 318091 od. 30851063 Kopernikusstr. 28 Telefax: (069) 30851163 D-65929 Frankfurt/Main Email: cetz@cetz.rhein-main.de
© William Yuan 2000
Email William