steve.jackson@canremote.uucp (STEVE JACKSON) (10/22/89)
>We recently started getting an Oracle error -3106 on a few embedded >SELECT commands. The error manual indicates indicates "fatal >two-task communication protocal error" and says to contact Oracle >customer support. So far Oracle customer support has not been of >help, and with the earthquake we do not expect to hear much from them >soon. Mark: I have encountered this problem using the FAST driver, when it encounters a divide by zero. If you are using the fast driver try switching to the default pipe driver and see what error you get. sjackson --- * Via ProDoor 3.1R
orpe@imtws3.im.se (rjan Pettersson IMT) (10/27/89)
>>We recently started getting an Oracle error -3106 on a few embedded >>SELECT commands. The error manual indicates indicates "fatal >>two-task communication protocal error" and says to contact Oracle >>customer support. So far Oracle customer support has not been of >>help, and with the earthquake we do not expect to hear much from them >>soon. >Mark: >I have encountered this problem using the FAST driver, when it >encounters a divide by zero. If you are using the fast driver try >switching to the default pipe driver and see what error you get. >sjackson The original posting never made it here so my point may not be relevant. (It applies to Oracle V5.1 on NCR 32/850) Be aware that the error 3106 does not necessarily mean a two-task comm. error. We have had that error message on some 'ordinary' SELECT errors also. Finding the real error was pain... orjan -- Orjan Petersson | orpe@im.se Industrimatematik Teknik AB | orjan@cs.chalmers.se V Hamngatan 8 | Phone. nat 031-171075 S-411 17 GOTEBORG, SWEDEN | int +46-31-171075