JDBC, two-task/datatype error

I have an interesting problem. I am able to install and run JDK1.2/JDBC (thin) drivers on RH Linux, and execute sample code. Please note I can get everything to work fine on NT. All the sample code is the equivalent of 'select ename from emp', which works great. I notice, though, that if I select more than one column, two problems can occur. For instance, if I say 'select ename, ename from emp' (or any variation w/ two columns), I get either:

Exception in thread "main" java.sql.SQLException: ORA-03115: unsupported network datatype or representation

or in another table/case:

java.sql.SQLException: ORA-03120: two-task conversion routine: integer overflow

This is a problem for obvious reasons; I'd like to get more than one column at a time. The installation of Oracle is pretty vanilla and I do remind you that the same code runs properly on NT.

Thanks!

Oh, actually, I lied about 1 thing. I had been using the JDBC-ODBC bridge driver on NT, not the Oracle driver, so I can't say I was using the Oracle driver in NT.
But, I still have the problem in Linux.
Thanks!
null

Similar Messages

FATAL ERROR IN TWO-TASK SERVER: error = 12571

Hi all,
I have a stored procedure which inserts quite a number of records in different tables.When it executes, the sessions seems to hang. When I checked alert log, I found that some trace file is genereated. GIven below is the content of trace file:
Dump file D:\orant\rdbms80\trace\IMS\ORA00393.TRC
Fri Mar 19 16:25:58 2004
ORACLE V8.0.5.0.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V4.0, OS V5.101, CPU type 586
Oracle8 Release 8.0.5.0.0 - Production
PL/SQL Release 8.0.5.0.0 - Production
Windows NT V4.0, OS V5.101, CPU type 586
Instance name: ims1
Redo thread mounted by this instance: 1
Oracle process number: 45
pid: 189
*** 2004.03.19.16.25.58.218
*** SESSION ID:(69.590) 2004.03.19.16.25.58.062
FATAL ERROR IN TWO-TASK SERVER: error = 12571
*** 2004.03.19.16.25.58.265
ksedmp: internal or fatal error
Current SQL statement for this session:
begin sp_update_kit_01(:a); end;
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
ksedmp+9e                       CALLrel ksedst+0
21E5F0
opitsk+cdb                      CALLrel ksedmp+0 2
opiino+4fe                      CALLrel opitsk+0 0
_opiodr+4a6                      CALLreg 00000000                         3C 4
E21FBFC
opidrv+335                      CALLrel opiodr+0 3C 4
E21FBFC
0
sou2o+f                         CALLrel opidrv+0 3C 4
E21FBFC
opimai+10c                      CALLrel sou2o+0
OracleThreadStart@4+47e         CALLrel opimai+0 2
E21FE78
77F04EED CALLreg 00000000
----- Argument/Register Address Dump -----
Argument/Register addr=e21e5f0. Dump of memory from E21E5B0 to E21E6F0
E21E5A0 00000000 00000003 00000000 655221D0
E21E5C0 00000033 00000000 00000003 0E21E589 00000001 00000000 00000000 00000000
E21E5E0 00000000 0000001D 0F841AD0 0E21E600 009E7F78 009E7F78 009E7F78 009E7F80
E21E600 009E7F78 009E7F78 009E7F78 009E7F78 009E7F80 0F841AD0 00000000 00000000
E21E620 00000000 0F841AD0 0E21E6D8 007F85BC 0E21E63C 0000001C 00000000 2A2A2A0A
E21E640 30303220 33302E34 2E39312E 322E3631 38352E35 32332D25 2D252073 25207338
E21E660 7332332D 0E270020 00000001 00002F78 0000311B 31324520 38374546 25207300
E21E680 7332332D 342D2520 00000A73 0E270030 655221F4 00000033 00000000 0F841AD0
E21E6A0 0E21E6C0 00000020 00000000 00000000 0E21FFEC 00000000 0E21FE78 00000000
E21E6C0 00000001 00000001 00000000 0E21DE38 00000003 0E21E6FC 007BB0F3 0E21E614
E21E6E0 00000000 0000311B 0F844368 00000001
Argument/Register addr=e21fbfc. Dump of memory from E21FBBC to E21FCFC
E21FBA0 77F1C9CF
E21FBC0 0E21FBF0 001F0003 0E273BD8 002C40E0 00000000 00000000 00000000 00000048
E21FBE0 0E21FBD0 00000000 00000000 00000000 00000830 0E21FC14 77F1C952 0E21FD85
E21FC00 FFFFFFFF 00000000 00000001 00000000 0E21FE8C 77F02ED7 0E21FFB8 004027D3
E21FC20 00000002 0E21FE78 000000F0 01399530 01399768 0F845F80 00000000 00000000
E21FC40 00000000 00000000 00000000 00000000 00000000 00000000 00000000 44414853
E21FC60 00000000 00000000 00000002 00C39F78 000008D4 00000000 00000000 00000000
E21FC80 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Repeat 2 times
E21FCE0 00000000 00000000 00000000 00000000 77B2BE71 77B20000 00000002
Argument/Register addr=e21fe78. Dump of memory from E21FE38 to E21FF78
E21FE20 FFFFFFFF 0E21FE54
E21FE40 77F88C19 00400000 00131DE4 00400000 77663BC8 0E21FE9C 77F6406F 00400000
E21FE60 00000001 00000009 0E21FE78 00131DE4 7FFDF000 77663BC8 0E21FD78 0E21FD85
E21FE80 0E21FE3C 0E21FE6C 0E21FF0C 61726F2A 77617073 65725F6E 5F796C70 31736D69
E21FEA0 3339335F 0040002A 00000002 0E21FF1C 00000000 77F61292 77FA6560 77F61298
E21FEC0 0E21FF30 01399530 01399768 00000000 00000000 00000000 00000000 00000000
E21FEE0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
E21FF00 00000000 0E21FEC0 00000000 FFFFFFFF 77F92F94 77F9E0E8 FFFFFFFF 00000000
E21FF20 77F76547 77F7654F 0E21FF30 00000001 00010017 00000000 00000000 00000000
E21FF40 00000000 00002005 00000000 80154388 80117280 80F7EA8C 80F7EA20 80154380
E21FF60 80154388 80117454 0000000A 80E1242B 80E1B020 7FFD6000
----- End of Call Stack Trace -----
===================================================
Files currently opened by this process:
===================================================
PROCESS STATE
Process global information:
process: 20c7c80, call: 0, xact: 0, curses: 0, usrses: 20f5c08
SO: 20c7c80, type: 1, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=45, calls cur/top: 0/24891b4, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 4
last post received-location: kslpsr
last process to post me: 20bfee0 1 2
last post sent: 38080860 0 15
last post sent-location: ksasnd
last process posted by me: 20bfee0 1 2
(latch info) wait_event=0 bits=0
O/S info: user: SYSTEM, term: SCDFHQINT04, ospid: 00189
OSD pid info: pid: 189
SO: 24891b4, type: 2, owner: 20c7c80, flag: INIT/-/-/0x00
(call) sess: cur 20f5c08, rec 0, usr 20f5c08; depth: 0
END OF PROCESS STATE
Can anyone help me about this?
Thanks in advance.

Sorry to point to you to someone else but, sounds like you should talk to Oracle Support.

FATAL ERROR IN TWO-TASK SERVER: error = 12592

*** 2010-09-27 10:02:52.790
*** SESSION ID:(1350.24486) 2010-09-27 10:02:52.790
FATAL ERROR IN TWO-TASK SERVER: error = 12592
*** 2010-09-27 10:02:52.790
ksedmp: internal or fatal error
Current SQL statement for this session:
select SN,PRODUCT_SN,DATE_CODE,CONFIGURATION,REPLACED from UW_Runcard where wo_key=:1 order by create_time desc
----- Call Stack Trace -----

It's a communication problem, check your sqlnet config and metalink.oracle.com.
Fred

ORA-013124 -Two-task internal error

when i try to remove the data in a column table i am getting the follwoing error
But i am able to change the data in the table
ORA-013124 -Two-task internal error
Pls help me in this

Hi,
TOAD 8.0 is quite old, you might want to grab 9.0.1 from www.quest.com (assuming you can arrange the appropriate access). But that shouldn't be causing this error.
In addition, what version of Oracle software are you using with TOAD? ie the Oracle client software version. If this is indeed Oracle 8.0 then you need to upgrade this (and this is probably what's causing the error).
Cheers,
Colin

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.

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 ...

Oracle 8i database: FATAL ERROR IN TWO-TASK SERVER

Hi,
We've been using Portal 3.0.7.6.2 since it was available. We've just upgraded to Oracle Database 8.1.6.3 (to resolve Apache GPF crashing problems) and have now noticed that our database server process terminates with a fatal error when we try to administer users, though in particular, adding users to existing groups. Error message as follows:
*** SESSION ID:(8.8) 2001-01-16 16:43:16.140
FATAL ERROR IN TWO-TASK SERVER: error = 12571
*** 2001-01-16 16:43:16.156
ksedmp: internal or fatal error
ORA-12571: TNS:packet writer failure
ORA-06512: at line 18
The only way to recover is to terminate the instance's service and restart. This happens every time we add more than 2 users to a group.
Any help would be appreciated.
Gary

Hi..
From metalink
>
# symptom: FATAL ERROR IN TWO-TASK SERVER:
# symptom: ERROR = 12571
# symptom: trace file generated
# symptom: Database operations continue successfully
# cause: The most common cause for the above error is an ungraceful disconnection of a session from the oracle db while the db is currently running a dml statement issued by that session. The error is recorded when oracle attempts to reply back to the session with the results of the dml and cannot access the session. Overall database operations are usually not affected.
====================
The ora-12571 error usually occurs when the client abruptly terminates with a Ctrl-C or powers down.
OR
The ora-12571 error, usually, indicates an instability with Oracle with the network. Communication Gap between eHub and Database Server.
>
Refer to Doc ID: 164839.1 and Doc ID: 576929.1 on metalink
HTH
Anand
Edited by: Anand... on Jan 16, 2009 1:18 PM DoC ID added

FATAL ERROR IN TWO-TASK SERVER

Hello all,
I am getting this error in a trace log a fatal error .Please suggest
Fri Jun 19 16:23:28 2009
ORACLE V9.2.0.7.0 - 64bit Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 1, CPU type 2200
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
Windows 2000 Version 5.2 Service Pack 1, CPU type 2200
Instance name: prd
Redo thread mounted by this instance: 1
Oracle process number: 17
Windows thread id: 4540, image: ORACLE.EXE
2009-06-19 16:23:28.145
SESSION ID:(27.4) 2009-06-19 16:23:28.105
FATAL ERROR IN TWO-TASK SERVER: error = 12152
2009-06-19 16:23:28.145
ksedmp: internal or fatal error
Call Stack Trace -
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
.opiino3840         CALL??? .opitsk8480         000000000 000000000 000000000
                                                   007EE8000
.opiodr3840         CALL??? .opiino3840         0000000E6 01425A428
                                                   C000000000000818 000000000
.opidrv2848         CALL??? .opiodr3840         0160A1658 000000004 158D3DA34
                                                   158D3DA30
.sou2o80            CALL??? .opidrv2848         0160A0038 000000000 000000000
                                                   000000008
.opimai544          CALL??? .sou2o80            01824FC04 00000003C 0160A03A0
                                                   0051B3AA0
.OracleThreadStart+ CALL??? .opimai+544          01824FC04 01824FC78 007EE8000
7328                                               158D2E008
0000000076EA7420     CALL??? .OracleThreadStart+ 01644FBD0 C00000000000040C
                              7328                 000000000 000000000
Binary Stack Dump -
thanks,
Kumar

> ORACLE V9.2.0.7.0 - 64bit Production vsnsta=0
> vsnsql=12 vsnxtr=3
> Windows 2000 Version 5.2 Service Pack 1, CPU type 2200
> Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
> With the Partitioning, OLAP and Oracle Data Mining options
> JServer Release 9.2.0.7.0 - Production
> Windows 2000 Version 5.2 Service Pack 1, CPU type 2200
Is this IA64/Itanium-2?
Markus

FATAL ERROR IN TWO-TASK error=12571

Hi ,
I am using 9.2.0.1.0 on windows 2000 server SP4 and we are getting FATAL ERROR IN TWO-TASK
SERVER: error = 12571
How do I correct this problem.
Here is the beginning of the TRC file. It is too large to include all.
*** 2005-10-04 10:48:43.259
*** SESSION ID:(22.783) 2002-03-25 19:05:23.259
FATAL ERROR IN TWO-TASK SERVER: error = 12571
*** 2002-03-25 19:05:23.259
ksedmp: internal or fatal error

cause: The most common cause for the above error is an ungraceful
disconnection of a session from the oracle db while the db is currently running
a dml statement issued by that session. The error is recorded when oracle
attempts to reply back to the session with the results of the dml and cannot
access the session. Overall database operations are usually not affected.
Read metalink note : 164839.1.
Jaffar

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

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.

ORA-03118 two-task error while doing a non blocking OCI call

Hi,
I have an application that runs on Linux and uses OCI API (version 8.1.6).
If I do the following in non blocking mode after polling about
70 times I get the error:
ORA-03118: two-task coroutine has invalid state
do {
call_cnt++;
rtc = OCIStmtFetch(stmtptr->stmt, oracle_err, 1, OCI_FETCH_NEXT,
OCI_DEFAULT);
} while (rtc == OCI_STILL_EXECUTING);
This doesn't happen all the time but it happens most often on big selects.
Does anyone have any idea what is happening here?
I have searched for related information but have come up dry. If anyone
knows anything or maybe a better place to ask this question please tell me.
Thanks,
Barry
null

Ask your basis guys to increase the table space...
check this thread...
[Error : DBIF_RSQL_SQL_ERROR;
--- Thanks...

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-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

JDBC, two-task/datatype error

Similar Messages

Maybe you are looking for