ERROR at line 1: ORA-03113: end-of-file on communication channel

Question

I have a DRDA gateway set up between my Oracle 10.2.0.4 instance (linux 64 bit), and a DB2 UDB instance (v 8.2 32 Bit). Within a SQLPlus session, I'm able to successfully interact with tables (select, update, delete) that do not have CLOB columns defined. However, whenever I try to access a table with a CLOB column (even doing a select on a single row), I get an end-of-file communication error and it kicks me out of my session. I can interact with the table as long as I don't include the CLOB/BLOB columns. Is there some additional configuration or memory settings I'm missing?
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select * from mytablewithaclob@db2 where l_column= 1;
select * from dbo.mytablewithaclob@db2 where l_column= 1
ERROR at line 1:
ORA-03113: end-of-file on communication channelI add the following codepage.map (as per another post) - packages are bound properly, and tables without clobs I can interact with just fine.:
S 367 > US7ASCII
D 13488 > AL16UTF16
D 1200 = AL16UTF16
M 1208 = UTF8
MBC 1208 = 1208 1200
column in question is defined as follows in DB2:
mycol CLOB(1G) DEFAULT ''  NOT NULL  NOT LOGGEDAny thoughts? Much appreciated.
Edited by: kpw on Sep 3, 2009 4:21 PM

Answer 1

Unfortunately TG4DRDA 10.2.0 does not support DB2 (C)LOB datatype. A crash is a rather unpleasant way to report this inability... but that could depend on the version of TG4DRDA you use (10.2.0.1.0). I guess when you upgrade TG4DRDA to 10.2.0.4.0 you will get a proper error message (ORA-28527 - datatype conversion error).
As workaround you could:
- create a view on the DB2 table and exclude the (C)LOB columns
- move/copy the (C)LOB data into a TG4DRDA supported datatype ((long) varchar for bit data)
Regards,
Ed