ORA-03106: fatal two-task communication protocol error with Oracle 9i+
Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=4052
Reported by Peter J. Holzer, WSR email@example.com
Pike v7.4 release 340 Copyright � 1994-2004 Linköping University (part of the Roxen 4.0.425 distribution):
When pike is built against Oracle 184.108.40.206 or Oracle 10.2, some (but not all) queries on an Oracle 220.127.116.11 database result in an ORA-03106 error after the first row of the result set is returned. The problem always occurs for the same queries, but I haven't found a pattern, which queries are affected.
When pike is built against Oracle 8.1.7 OR the database is Oracle 8.1.7, the problem doesn't occur - both the database and the libraries need to be 9i or later to show the problem.
In sqlplus: set autocommit on create table foo (KST0 int, kst1 int, name varchar2(80), aktuell number(1)); insert into foo values(1,2, 'Test', 1); insert into foo values(3, 4, 'fasel', 0);
In Roxen Admin interface: SELECT KST0, KST1, NAME, AKTUELL FROM FOO => Run Query
again in sqlplus: delete from foo where kst0=3; insert into foo values(0, 2, 'Administratives', 1);
Click again on Run Query in Roxen:
KST0 KST1 NAME AKTUELL 0 2 Administratives 1 While running SELECT KST0, KST1, NAME, AKTUELL FROM FOO : OCIStmtFetch:code=-1:ORA-03106: fatal two-task communication protocol error Query took 0.001s, 1 rows in the reply