RE: DB Link Error - More Info

[Kevin Lange]

Title: RE: missed Anjo's webcast..

Sorry for the lack of info.   Her it all is:     1) I have tns entries on both database machines that point to each other.   2) I have global_names set to false on both machines.   3) I have the same ID defined with the same password on both machines.   4) We do not use Oracle Names.   On machine A:   I created a link :     create database link b using 'b.world';   On machine B:   I created a link :     create database link a using 'a.world';   Here are the results:     1. I can select data back and fourth between both machines wit no errors.   2. When I try to describe a table accross the link I get the ORA-0219 error.   3. When I try to use the plsql copy command (ultimately what I want to do) , on machine B, I get an error stating that I am trying to Fetch out of sequence.   On machine A I get an unknow error that can not be interpreted ....  a long string of numbers as the error number.     So, thats it.    Currently I am resorting to small selects accross the working part of the links.  But, eventually I need to get to the copy commands because they have the commits in them.   Any help is greatly appreciated.   Kevin -----Original Message----- From: Magaliff, Bill [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 08, 2002 5:29 PM To: Multiple recipients of list ORACLE-L Subject: RE: DB Link Error 1)    are you using global_names = true?  do the link names match the global names?   2)    is there a local tns entry on the machine with database A that points to database B?  we had a problem like then that was traced to our using Oracle Names without local tns files.   -bill -----Original Message----- From: Kevin Lange [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 08, 2002 6:05 PM To: Multiple recipients of list ORACLE-L Subject: DB Link Error Does anyone know the most common reasons why a DB LINK would give me the following error :   ORA-02019: connection description for remote database not found   Both databases exist ....   And even though I get this error going from Database A to Database B, the link I have between Database B and Database A works fine.   Kevin