ORA-03113 on dblink to DB2 [message #410696] |
Mon, 29 June 2009 17:52  |
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 #411762 is a reply to message #411594] |
Mon, 06 July 2009 11:11   |
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 #412123 is a reply to message #410696] |
Tue, 07 July 2009 19:39  |
 |
BlackSwan
Messages: 26766 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.
|
|
|