Home » RDBMS Server » Networking and Gateways » ORA-03113 on dblink to DB2
ORA-03113 on dblink to DB2 [message #410696] Mon, 29 June 2009 17:52 Go to next message
jetoc
Messages: 3
Registered: June 2009
Junior Member
We created new test db, along with a dblink to a DB2 database. We have an existing db with dblink to the exact same DB2 database, which works fine.

BUT in the new db, we get error ORA-03113 (end-of-file on communication channel) when we try to do select on the DB2 table using dblink. After doing a select, we also get knocked out of Oracle.

What is missing in the new db / dblink? Would appreciate any suggestions. Tnsping to the remote DB appears to be ok.

Thanks!
Re: ORA-03113 on dblink to DB2 [message #410709 is a reply to message #410696] Mon, 29 June 2009 20:49 Go to previous messageGo to next message
BlackSwan
Messages: 25036
Registered: January 2009
Location: SoCal
Senior Member
No Operating System name or version
No Oracle version number (from v$version).
No DDL.
No DML.
No help is possible at this time.

Something is different between the two Oracle systems or installations.
Find the difference & correct it.

You have not provided us any meaningful facts.

Was a trace file produced?
Does trace file contain any useful clues?
Re: ORA-03113 on dblink to DB2 [message #411594 is a reply to message #410709] Sun, 05 July 2009 20:57 Go to previous messageGo to next message
babuknb
Messages: 1734
Registered: December 2005
Location: NJ
Senior Member

Quote:
What is missing in the new db / dblink? Would appreciate any suggestions. Tnsping to the remote DB appears to be ok.


We don't know your database link creation statement/database link status/ tnsping status.

Please post all the details.

Thanks
Re: ORA-03113 on dblink to DB2 [message #411762 is a reply to message #411594] Mon, 06 July 2009 11:11 Go to previous messageGo to next message
jetoc
Messages: 3
Registered: June 2009
Junior Member
Hi,

This is the dblink creation:
create database link ABC.DEF.COM
connect to X001
identified by <pwd>
using 'ABC.DEF.COM';

It looks like dblink was created. But here is the errors when we try to access:
SQL> connect X001/*******@iserv11
Connected.
SQL> desc DBASQP3.SQT500_INSVC_MWE@ABC.DEF.COM
ERROR:
ORA-03113: end-of-file on communication channel


Note: The dblink exists in other schemas (in a different unix server) and works fine there.

Tnsping appears to be ok:
tnsping abc

TNS Ping Utility for IBM/AIX RISC System/6000: Version 10.2.0.4.0 -
Production o
n 26-JUN-2009 17:20:05

Copyright (c) 1997, 2007, Oracle. All rights reserved.

Used parameter files:
/usr/local/opt/oracle/product/10.2.0.4/network/admin/sqlnet.ora

Used LDAP adapter to resolve the alias
Attempting to contact
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=DBAIP01.MVS.DEF
.COM)(PORT=62103))(HS=)(CONNECT_DATA=(SID=ABC)))
OK (70 msec)
oracle@rtst1j05 iserv11 /usr/local/opt/oracle/admin/iserv11/scripts.


Re: ORA-03113 on dblink to DB2 [message #411766 is a reply to message #410696] Mon, 06 July 2009 11:17 Go to previous messageGo to next message
BlackSwan
Messages: 25036
Registered: January 2009
Location: SoCal
Senior Member
DESC can be a problem over dblink.

select count(*) from user_objects@ABC.DEF.COM
use CUT & PASTE to show results from above SQL

You need to help us by following the Posting Guidelines as stated below.
http://www.orafaq.com/forum/t/88153/0/
Go to the URL above click the link "Posting Guidelines"
Go to the section labeled "Practice" & do as directed.
Re: ORA-03113 on dblink to DB2 [message #412097 is a reply to message #411766] Tue, 07 July 2009 15:25 Go to previous messageGo to next message
jetoc
Messages: 3
Registered: June 2009
Junior Member
I did the select, and got this:
ORA-03113: end-of-file on communication channel
Re: ORA-03113 on dblink to DB2 [message #412123 is a reply to message #410696] Tue, 07 July 2009 19:39 Go to previous message
BlackSwan
Messages: 25036
Registered: January 2009
Location: SoCal
Senior Member
03113, 00000, "end-of-file on communication channel"
// *Cause: The connection between Client and Server process was broken.
// *Action: There was a communication error that requires further investigation.
//          First, check for network problems and review the SQL*Net setup. 
//          Also, look in the alert.log file for any errors. Finally, test to 
//          see whether the server process is dead and whether a trace file
//          was generated at failure time.


A trace file may have been generated & hold additional clues.
Submit a Service Request on Metalink.
Previous Topic: ORA-12560: TNS:protocol adapter error
Next Topic: Generic Connectivity Not Working (Oracle -Ms Access)
Goto Forum:
  


Current Time: Sun Dec 04 06:20:54 CST 2016

Total time taken to generate the page: 0.05172 seconds