DB LINK CONNECTION FAILURE [message #250273] |
Mon, 09 July 2007 06:58 |
systemkhabir
Messages: 2 Registered: June 2007 Location: Dhaka
|
Junior Member |
|
|
Hi everybody,
I have faced a problem with database linking and the following error is occured whenever i tried out to link to the remote DB server.
ORA-03113: end-of-file on communication channel
In the following way I have tried out to create the DB link
Create database link link_name
connect to current_user
user <service_name>
And then I have tried to link to remote DB
using the follwoing syntax:
SELECT *FROM remote_table_name@link_name
Thank u all
Mr.Khabir
|
|
|
|
Re: DB LINK CONNECTION FAILURE [message #250319 is a reply to message #250276] |
Mon, 09 July 2007 11:07 |
DreamzZ
Messages: 1666 Registered: May 2007 Location: Dreamzland
|
Senior Member |
|
|
Quote: | 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.
ORA-03113 issues happen due to various reasons including Network Issues, Forceful Disconnection of a Server Session,
Oracle Database Crash, Oracle Server Crash, Oracle internal errors like ORA-00600 or ORA-07445 causing aborts, Oracle Client or TNS layer inability to handle the connections and so on...
An example of this error is shown below. In this example, the ORA-3113 was generated by unavailability of Oracle as shown in ORA-01034 which indicates that either the oracle database session has been killed or the oracle database instance is down or has just crashed.
ORA-03113: end-of-file on communication channel
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
You as the dba or the user should be aware that this error can be very misleading and is also a catch-all error in the oracle software. Similar errors include the ORA-00600 and you should realize that oracle can just report this error sometimes when ever it has an internal issue.
This error requires analysis as a whole based on the accompanying error messages and should be search in Oracle Metalink. Oracle metalink Note 17613.1 will help you further analyze and understand this issue.
|
|
|
|
|
|
|
|