TWO TASK COMMUNICATION ERROR

Hi,
I am using ORACLE 9i DB (SERVER).
I am getting the following error when I run a process that does a query on this DB.
NAME" -> "UTPLIB_IT%"
(utplib_getdnbynameop_ittest.cc - 191): caught=CPFDEF::Error_c, exception=[ERROR=0xa1990051][text=]
[details=ORA-03106: fatal two-task communication protocol error
; ; SELECT CO_GID, CO_DN, CO_NAME, CO_OC_ID FROM UTP_MO WHERE CO_NAME LIKE :NAME ]
[location=file: utplib_dbsession.cc line: 285]
[timestamp=11:41.43 21.03.2003]
[pid=4809]
[ptype=0x0]
[uid=phaniraj]
I would like to seek help on this topic. What does this " fatal two-task communication protocol error" mean?
--RA

This forum is meant for discussions about OTN content/site and services.
Questions about Oracle products and technologies will NOT be answered in this forum. Please post your product or technology related questions in the appropriate product or technology forums, which are monitored by Oracle product managers.
Product forums:
http://forums.oracle.com/forums/index.jsp?cat=9
Technology forums:
http://forums.oracle.com/forums/index.jsp?cat=10
As a general guideline, please first search the forum to see if your question is already answered. You will find answers for the most frequently asked questions by simply searching the forum. This will help you to find the answer right away and will save time for all of us.

Similar Messages

Fatal two-task communication protocol error (when using db link)

I have created the db link betwen two databases of oracle version 9i 9.0.2
the db link connects to specific user
when i access the table with same name as user then recieve following message
ORA-03106: fatal two-task communication protocol error
when i access the other tables having different name that the user to which the db link connects
that works alright
so what is solution of problem in this particular case?

What is your Oracle release? Is it 9.0.1.2 or 9.2.0?
What version of Sql*Plus client are you using?

ORA-03106: fatal two-task communication protocol error

Hello everyone,
we have a problem with one of our table.
the problem occurs when i execute
SQL> select * from t;
select * from t
ERROR at line 1:
ORA-03106: fatal two-task communication protocol error
but i can access the data by giving the column names for the whole table.
also there is nothing wrong with the other tables in the schema.
many thanx in advance

first of all thanx in advance
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Productio
NLSRTL Version 10.2.0.1.0 - Production
SQL> select comp_id, version, status from dba_registry;
COMP_ID VERSION STATUS
CATALOG 10.2.0.1.0 VALID
CATPROC 10.2.0.1.0 VALID
OWM 10.2.0.1.0 VALID
JAVAVM 10.2.0.1.0 VALID
XML 10.2.0.1.0 VALID
CATJAVA 10.2.0.1.0 VALID
EXF 10.2.0.1.0 VALID
ODM 10.2.0.1.0 VALID
CONTEXT 10.2.0.1.0 VALID
XDB 10.2.0.1.0 VALID
RUL 10.2.0.1.0 VALID
COMP_ID VERSION STATUS
ORDIM 10.2.0.1.0 VALID
APS 10.2.0.1.0 VALID
XOQ 10.2.0.1.0 VALID
AMD 10.2.0.1.0 VALID
SDO 10.2.0.1.0 VALID
EM 10.2.0.1.0 VALID
but i cannot understand why..
as far as i know, nothing changed. but maybe the other admins:)
as i said i can query all colums in table t without using a *,
also i can use * when i include rowid in the query
select m.*,rowid from t m;
i am very confused now:S

ORA-3106 : fatal two-task communication protocol error

We get the following error intermittantly in our server. We are using WebLogic 6.1. Any reason. Here is the log we are getting...
Parsing: BEGIN gid_msg_fund.fund_get_details (:1, :2, :3, :4, :5, :6, :7, :8)
; END;
Executing: BEGIN gid_msg_fund.fund_get_details (:1, :2, :3, :4, :5, :6, :7, :8
) ; END;
SQLException: SQLState() vendor code(3106)
java.sql.SQLException: ORA-03106: fatal two-task communication protocol error
at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:240)
at weblogic.jdbc.oci.Statement.executeUpdate(Statement.java:990)
at weblogic.jdbc.oci.Statement.execute(Statement.java:1430)
at ...

ORA-03106
========
Possible reasons for the ORA-03106 errors include:
1. Incompatibilities between the client application and the RDBMS server.
For
example, version incompatibilities, or a client trying to use a feature not
supported by the database kernel.
2. When using database links or gateways.
3. Network or SQL*Net problems.
4. Corruptions.
5. PL/SQL - language related.
RDBMS - Troubleshooting two-task common errors
==============================================
1. Check for NLS incompatibilities between the client and server. This is
a very popular cause of the ORA-03106 error.
2. Check the alert log and RDBMS trace files for any pertinent information /
errors that coincide with receiving the ORA-03106 error.
3. Try to get a testcase and reproduce the problem in-house.
4. If a testcase is not possible, ask for SQL*Net trace files, SQL traces,
and
try setting event 3106 to obtain the error stack.
5. In extreme circumstances, this could indicate that a shared memory
segment
used by Oracle is corrupted. You will have to shut down the database,
possibly using the abort option. Make sure all semaphores have been
released by using the IPCS command on Unix. Oracle uses semaphores to
control concurrency between all of the background processes (pmon, smon,
drwr, lgwr, and oracle shadow processes). Semaphores are also used to
control Two-Task communication between the user process and the shadow
process.
6. Try and narrow down the code that may be causing it. For example it might
have started to happen after increasing the number of parameters in a PL/SQL
block or when using certain values for bind variables, etc.
7. If we still do not make headway, file a bug under RDBMS, but we still may
need some or all of the above information as indicated above
hope it helps!!
"Prasanna" <[email protected]> wrote in message
news:[email protected]...
We get the following error intermittantly in our server. We are usingWebLogic 6.1. Any reason. Here is the log we are getting...
>
Parsing: BEGIN gid_msg_fund.fund_get_details (:1, :2, :3, :4, :5, :6,:7, :8)
; END;
Executing: BEGIN gid_msg_fund.fund_get_details (:1, :2, :3, :4, :5, :6,:7, :8
) ; END;
SQLException: SQLState() vendor code(3106)
java.sql.SQLException: ORA-03106: fatal two-task communication protocolerror
at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:240)
at weblogic.jdbc.oci.Statement.executeUpdate(Statement.java:990)
at weblogic.jdbc.oci.Statement.execute(Statement.java:1430)
at ...

ORA-03106: fatal two-task communication protocol error USING INFORMATICA

Hi,
We are testing Oracle 10203 with linux using INFORMATICA 8.1.1
The user who run the informaica is getting the following error , after runing query against a remote database.
READER_12_1_1> RR_4035 SQL Error [
ORA-03106: fatal two-task communication protocol error
(Please note that informatica is not using db links to open a connection against a remote db).
The informatica client is installed on the same machine as the oracle database and they are using the same oracle client (e.g: 10203)
I also set a trace in the sqlnet.ora at server side and at the client side.
No error regarding ora-3106 was generated in the trace files.
I also added: alter system set events '3106 trace name errorstack level 10', but nothing writthen to the trace file.
Any suggestion ?
Thanks.

Error: ORA 3106
Text: fatal two-task communication protocol error
Cause: The communication path between Oracle and the user task has stopped.
This is an internal error message not usually issued.
Action: Contact customer support.
====================================================
Unfortunately the error text doesn't lie, this error is difficult to catch. You may search metalink's knowledge base for possible reasons,but there are many. And, since this is a 3rd party application, I would ask INFORMATICA (not Oracle), do they certify against 10g? Sometimes simply the application is not ready for the used Oracle version.
Werner

Two task communication protocol error

I have a Database Data block. I want to i retrieve the records
with execute query and save the item after changes. when i do
this for the second time connection between ORacle Server and
Forms Runtime is last. Message comming is Two task communication
protocol error. Also the runtime exits.
I need help very urgently as the project is held up because of
this.
Srini

I wrote a class for the Oracle 8 OCI calls in php3...I'm not having any problems with php and Oracle...if anyone is interested in the class, email me ([email protected]) and i'll send you the code...it makes traversing a recordset very easy...
$rs = new CData("user","pwd","sid","domain");
$sql = "select col_a, col_b from table";
if ($rs->GetRecordset($sql)) {
while (!$rs->REOF()) {
echo $rs->Val("COL_A")."<br>";
echo $rs->Val("COL_B")."<p>";
$rs->MoveNext();
$rs->MoveFirst();
echo $rs->Val("COL_B");
$rs->MoveNext();
echo $rs->Val("COL_A");
$rs->MovePrevious();
echo $rs->Val("COL_A");
$rs->MoveLast();
echo $rs->Val("COL_B");
echo $rs->RowCount();
echo $CurrentRow();
$sql = "delete from table";
if (!$rs->Execute($sql)) {
echo "Error: ".$rs->err_num.$rs->err_msg;
...you get the picture...

File: e:\pt849-905-R1-retail\peopletools\SRC\PSRED\psred.cppSQL error. Stmt #: 1849 Error Position: 24 Return: 3106 - ORA-03106: fatal two-task communication protocol error Failed SQL stmt:SELECT PROJECTNAME FROM PSPROJECTDEFN ORDER

File:
e:\pt849-905-R1-retail\peopletools\SRC\PSRED\psred.cppSQL error. Stmt #:
1849 Error Position: 24 Return: 3106 - ORA-03106: fatal two-task
communication protocol error
Failed SQL stmt:SELECT PROJECTNAME FROM PSPROJECTDEFN ORDER
BY PROJECTNAME
Got this error when opening the peopletools application designer 8.49. The same is working fine within the server, but not working from the client's machine.
We can still able to connect to the database & URL
Please help by throwing some lights.
Thanks,
Sarathy K

Looks like a SQL error. ARe you able to connect to the database with SQL*Plus ? Probably the Oracle client is badly configured.
Nicolas.

EJB Error: ORA-03106: fatal two-task communication protocol error

after weblogic running some time,my program often throw this Exception:
javax.ejb.EJBException: ejbLoad: ORA-03106: fatal two-task communication
protocol error
at
com.ebao.life.ejb.entity.customer.CustomerBean.ejbLoad(CustomerBean.java:206
at
weblogic.ejb.internal.EntityEJBContext.load(EntityEJBContext.java:160)
at
weblogic.ejb.internal.EntityEJBContext.afterBegin(EntityEJBContext.java:217)
at
weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
t.java:165)
at
weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
at
com.ebao.life.ejb.entity.customer.CustomerBeanEOImpl.getData(CustomerBeanEOI
mpl.java:105)
at
com.ebao.life.bean.newbizgroup.entry.code.CodeBean.entry(CodeBean.java:120)
at
com.ebao.life.servlet.newbizgroup.entry.code.CodeEntryServlet.doPost(CodeEnt
ryServlet.java:39)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
I use weblogic 5.1 sp10,Redhat Linux 6.2,and JDK 1.3
and the sp9 is the same.

I think there are too many bugs weblogic sp9 and later.
There are many strange jdbc error in these service pack
"Narinder" <[email protected]> wrote:
It seems like the connection to the oracle database is lost for no reason.
What is the oracle database server and the jdbc driver you are using?
Most
of the time this happens because the jdbc driver is not compatible with
the
oracle server.
-Narinder
"jason" <[email protected]> wrote in message
news:[email protected]..
after weblogic running some time,my program often throw this Exception:
javax.ejb.EJBException: ejbLoad: ORA-03106: fatal two-task communication
protocol error
at
com.ebao.life.ejb.entity.customer.CustomerBean.ejbLoad(CustomerBean.java:206
at
weblogic.ejb.internal.EntityEJBContext.load(EntityEJBContext.java:160)
at
weblogic.ejb.internal.EntityEJBContext.afterBegin(EntityEJBContext.java:217)
at
weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
t.java:165)
at
weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
at
com.ebao.life.ejb.entity.customer.CustomerBeanEOImpl.getData(CustomerBeanEOI
mpl.java:105)
at
com.ebao.life.bean.newbizgroup.entry.code.CodeBean.entry(CodeBean.java:120)
at
com.ebao.life.servlet.newbizgroup.entry.code.CodeEntryServlet.doPost(CodeEnt
ryServlet.java:39)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
I use weblogic 5.1 sp10,Redhat Linux 6.2,and JDK 1.3
and the sp9 is the same.

Help about "ORA-03106: fatal two-task communication protocol error"

Hello.
After having changed some functions written in pro*C, I am getting "ORA-03106: fatal two-task communication protocol error", in the functions I have changed (all of them).
Can someone tell me what the problem can be ?
Tahnks in advance.

The problem seems to be in pro*C code:
My pro*C function is like this:
int CSRIRDB_checkGT(char* in_CO_GT_V,
char* out_SQ_GZL_01)
int var_Error = CSRIRDB_OK;
char var_Sqlerrmc[2000];
char var_msg[512]; /* 512 es la longitud máxima del mensaje oracle incluyendo saltos de línea */
size_t var_buf_len, var_msg_len;
/* and the error is beacuse the following assignment */
:out_SQ_GZL_01 := to_char(v_SQ_GZL_01);
/* where v_SQ_GZL_01 is a NUMBER(5) */
I don't know what I'm doing wrong.

ORA-03106: Fatal Two Task Communication Protocol Error due to multilanguage

1) I have installed oracle 10.2 with multi language support enabled Unicode (AL32UTF8) on windows 2003 Server.
2) Forms 6i installed on same machine but Form close immediately after Database connection.
3) In Net8 Easy Config following error appear "ORA-03106: Fatal Two Task Communication Protocol"
4) If I reinstall database without multi language support, Forms run and connect successfully.

Forms 6i does not support multi language support enabled Unicode(UTF-8)
and unicode character has to take a long word size where form6i word's length is less
thats why the message is coming as Two Task Communication Protocol because the same protocol
is used for both database as well as for form6i and database is capable of taking unicode characters
whereas the forms 6i is not able to perform the same.

PL/SQL calling giving ORA-03106: fatal two-task communication protocol erro

Hi
I am facing some issue when I am calling a Pl/SQL function from Reports Region of APEX page.
Calling of the PL/SQL code is :
declare
v_query varchar2(4000) := null;
begin
SELECT DPSS_TS_SSA_PKG.getuserid('51552','3618') INTO v_query FROM DUAL;
return v_query;
end;
ERROR MSG :
report error:
ORA-03106: fatal two-task communication protocol error
ORA-02063: preceding line from DPSS_EBUST
When I am executing any other function the same way it is working correctly.
Not able to find out why its happening.
Thanks
Deepak

Error: ORA 3106
Text: fatal two-task communication protocol error
Cause: The communication path between Oracle and the user task has stopped.
This is an internal error message not usually issued.
Action: Contact customer support.

InitialLOBFetchSize causes ORA-03106: fatal two-task communication protocol

After my previous problem with setting InitialLOBFetchSize to -1 (see {thread:id=2338611}) I worked with a setting of 5 KB. This works fine on our development and testing database (11.2.0.1.0 Windows x86).
But on the database of our customer (11.2.0.1.0 Windows x64) some queries throw an "ORA-03106: fatal two-task communication protocol error" exception. This is completely reproduceable, selecting some specific rows work, but others don't work. I've also tried a value of -1 on the customers database, this seems to fail on the same rows, but with a different error: "ORA-03149: Invalid Oracle error code".
Interestingly, the first exception (ORA-03106) is only thrown if I also set a value to FetchSize (I'm currently using 1 MB for that). If I don't modify FetchSize the app just freezes (seems like the query call never returns). But setting the FetchSize doesn't change the behaviour of InitialLOBFetchSize with a value of -1 (always ORA-03149).
I'd really like to use InitialLOBFetchSize (either with a positive value of about 5 KB or with -1) because this brings a huge performance increase for queries that select many CLOBs. Why causes this setting so many problems? Are there any known solutions?
I'm using ODP.NET 11.2.0.3.0 x86 with .NET 4.0.
Edited by: user12301043 on 21.03.2012 01:32

In case someone tracks this thread, here is an update:
The problem on the customer database was caused by the "DB_SECUREFILE=ALWAYS" setting. Oracle Support has now created a bug report for it (Bug 14279250).

Spam - ORA-03106: fatal two-task communication protocol

Hi gurus.
I'm having this error always I import a queue.
Before the error I continue with the "import queue" and it goes to the end, no problem.
Could any one help me how to solve this?
Above the abend details.
Runtime Error          DBIF_SETG_SQL_ERROR
Database error text........: "ORA-03106: fatal two-task communication protocol
error"
Internal call code.........: "[SETG/GET /INDX_HIER ]"
"DBIF_SETG_SQL_ERROR" C
"SAPLSHI2" or "LSHI2U25"
"STREE_READ_BUFFERED_DATA_GENER"
System environment:
    SAP Release.............. "640"
Application server....... "PCINTRA"
    Network address.......... "192.168.200.100"
    Operating system......... "Windows NT"
    Release.................. "5.1"
    Hardware type............ "Intel 80686 (Mo"
    Character length......... 8 Bits
    Pointer length........... 32 Bits
    Work process number...... 1
    Short dump setting....... "full"
Database server.......... "PCINTRA"
    Database type............ "ORACLE"
    Database name............ "NWW"
    Database owner........... "SAPNWW"
Character set............ "English_United State"
SAP kernel............... "640"
    Created on............... "Mar 21 2007 23:47:09"
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "
Patch level.............. "175"
    Patch text............... " "
Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
    SAP database version..... "640"
    Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Thanks in advance
Paulo

Hi Ben,
i m also getting the same error. we are using ORacle 10.2.2 on Linux.
The problem is that the Updates are not getting processed and are waiting for V2 update process which is processing one of the v2 process for much time and status is running sequential read - VBdata table.
the status of the updates are - v1 processed. Find the error log of SM21 below-
NiConnect Unsuccessful, Return Code: -0003
> Host: ACPLAPP
> Service: sapgw01
Communication error, CPIC return code 020, SAP return code 665
> CPI-C function: CMINIT(SAP)
SQL error 3106 . Work processes in reconnect status
Perform rollback
Work process has left reconnect status
Run-time error "DBIF_SETG_SQL_ERROR" occurred
> Short dump "070828 020442 SAPPRD AMTFINISHING" generated
Transaction Canceled 00 671 ( DBIF_SETG_SQL_ERROR 20070828020442SAPPRD AMTFINISHING0091 )
Perform rollback
Update terminated
> Update key: 46CE6156C66E4997E1000000C0A80107
> Update module: G_PCA_0_POSTING
SQL error 3113 . Work processes in reconnect status
Kindly suggest
Thnx
Kishore

ORA-03106: fatal two-task communication protocol e

Hi Experts
I am upgrading my system to Ehp3. When i am doing the upgrade i am getting a error
SQL error 3106 accessing T100S: ORA-03106: fatal two-task communication protocol
error----
Log File:
MEL-SRV-SAP3\sapmnt\trans\log\SAPI-603DTINSAPAPPL.RID
Start import R3TRTABUT100S ...
1 entry for T100S updated (8A                  014).
1 entry for T100S updated (8A                  015).
1 entry for T100S updated (8B                  526).
1 entry for T100S updated (AA                  816).
1 entry for T100S updated (FAGL_ORG_UNITS      011).
1 entry for T100S updated (FF                  785).
1 entry for T100S updated (FF                  788).
1 entry for T100S updated (FIPAY_GTS           001).
1 entry for T100S updated (FIPAY_GTS           002).
1 entry for T100S updated (FIPAY_GTS           003).
1 entry for T100S updated (GA                  572).
[dev trc     ,00000] Sun May 10 14:34:29 2009                         16918558 17.094935
[dev trc     ,00000] OCI-call failed with -1=OCI_ERROR                     22 17.094957
[dev trc     ,00000]     SQL error 3106: 'ORA-03106: fatal two-task communication protocol error'
                                                                             30 17.094987
[dbsloci.    ,00000] *** ERROR => Error 3106 in stmt_fetch() from oci_execute_stmt(), orpc=1
                                                                             46 17.095033
[dbsloci.    ,00000] *** ERROR => ORA-3106 occurred when executing SQL stmt (parse error offset=0)
                                                                             32 17.095065
[dev trc     ,00000] sc_p=0000000000297990,no=96,idc_p=0000000000000000,con=0,act=1,slen=137,smax=256,#vars=2,stmt=0000000006662F
                                                                             43 17.095108
[dev trc     ,00000] SELECT /*+ FIRST_ROWS (1) */ TABNAME , VARKEY , DATALN , VARDATA FROM ATAB WHERE TABNAME\
                                                                             30 17.095138
[dev trc     ,00000]   = :A0 AND VARKEY = :A1 FOR UPDATE;                16 17.095154
   [dev trc     ,00000] SELECT /*+ FIRST_ROWS (1) */ TABNAME , VARKEY , DATALN , VARDATA FROM ATAB WHERE TABNAME\
                                                                                29 17.095424
   [dev trc     ,00000]   = :A0 AND VARKEY = :A1 FOR UPDATE;                16 17.095440
   [dbtran      ,07512] ***LOG BY4=>sql error 3106   performing SEL on table ATAB       [dbtran#11 @ 7512]
                                                                             5833 17.101273
   [dbtran      ,07512] ***LOG BY0=>ORA-03106: fatal two-task communication protocol error [dbtran#11 @ 7512]
                                                                                33 17.101306
   [dev trc     ,00000] dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL'         39 17.101345
                          RSLT: {dbsl=99, tran=1}
                          FHDR: {tab='ATAB', fcode=33, mode=2, bpb=0, dbcnt=0, crsr=0,
                                 hold=0, keep=0, xfer=0, pkg=0, upto=0, init:b=0,
                                 init:p=0000000000000000, init:#=0, wa:p=0X00000000014CC570, wa:#=15000}
   [dev trc     ,00000] dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL'         80 17.101425
                          STMT:
                          CRSR: {tab='', id=0, hold=0, prop=0x88000, max.in@0=1, fae:blk=0,
                                 con:id=0, con:vndr=5, val=2,
                                 key:#=2, xfer=0, xin:#=0, row:#=0, upto=1, wa:p=0X00000000014CC570}
SQL error 3106 accessing T100S: ORA-03106: fatal two-task communication protocol e
52718 9059062
    0 entries from T100S (GLT0                300) deleted.
Please help to resolve the issue
Thanks in Advance

Hi,
check any log in alert log/user trace file as wll as sql net trace file.
it might be problm in shared memory,semaphores ..
Check NLS compatibility.
If u upgraded database also then first time login through single more and run u*...sql as given in read me file.
surendra jain

ORA-03106: fatal two-task communication protocol erro

Hi,
I have been writing an oracle client application for Linux and I am
getting the error ORA-03106: fatal two-task communication protocol:
fatal two-task communication protocol error".
I am trying to do a Piecewise fetch of long data using
OCIDefineDynamic() and a callback function. The callback is being called
but after setting the buffer information for the data I get an ORA-03106
error.
If I just do this as a normal fetch it works.
Any ideas?

Hi,
"Two-task common errors are generally RDBMS related issues, but could be caused by a problem with SQL*Net, or an application (i.e. Pro*C).
ORA-03106
========
Possible reasons for the ORA-03106 errors include:
1) Incompatibilities between the client application and the RDBMS server. For example, version incompatibilities, or a client trying to use a feature not supported by the database kernel.
2) When using database links or gateways.
3) Network or SQL*Net problems.
4) Corruptions.
5) PL/SQL - language related."
For more information, take a look at Note:1012295.102 from Oracle Metalink.
Cheers
Legatti

TWO TASK COMMUNICATION ERROR

Similar Messages

Maybe you are looking for