Re: Connect w/o Listener

On Mon, 02 Oct 2006 20:17:13 +0200, Frank van Bortel <frank.van.bortel_at_gmail.com> wrote:

>Jaap W. van Dijk schreef:
>> Hi Frank,
>>
>> Can you also use this solution to connect a 9.2.0.6 database to a
>> 8.1.4.7 database on the same server through a database link? And
>> because these are two databases with two different oracle executables,
>> do I have to specify things differently?
>>
>> And if you can, could this affect the runtime considerably of the
>> following statement:
>>
>> INSERT /*+ APPEND */ INTO local_table
>> SELECT * FROM remote_table_at_dblink
>>
>> I noticed that this statement uses a lot of CPU for processing the
>> records that come over the database link with a TCP-protocol. I wonder
>> if this is due to the nature of the TCP connection and if CPU
>> consumption would be noticebly lower for a BEQ-protocol.
>>
>> Kind regards, Jaap.
>>
>
>Oh - in addition to the (listenerless) BEQueath protocol, which
>may not alwyas be easy to set up, make it a habit of using IPC.
>It is far more efficient than TPC/IP for local traffic.
>
>Use TCP/IP only for what is was meant: routable network traffic
>--
>Regards,
>Frank van Bortel
>
>Top-posting is one way to shut me up...

I saw a note on Metalink where a PROGRAM entry was added to the ADDRESS part, with the specification of the directory and the name of the oracle executable. And also an ENVS entry, specifying the ORACLE_SID and the ORACLE_HOME. I have some trouble getting the link to work (ORA-12545). I can imagine that on Open VMS one has to specify these things for a database link between to databases that are on different Oracle homes, like in my situation.

I keep your tip about IPC in mind. I assume that it takes the same clauses as the TCP protocol.

Regards,

Jaap. Received on Mon Oct 02 2006 - 15:13:53 CDT