Re: IPC versus TCP performance

Hello Amir,
are you sure that this is a communication (latency) problem over the database link and not an optimizer problem (e.g. bad execution plans) due to the involved remote tables (distributed query)?

Best Regards
Stefan Koehler

Independent Oracle performance consultant and researcher Website: http://www.soocs.de
Twitter: _at_OracleSK

> "Hameed, Amir" <Amir.Hameed_at_xerox.com> hat am 30. Oktober 2018 um 14:01 geschrieben:
>
> Hi,
>
> I have two databases running on the same physical server. The OS is RHEL7. Database A is 11.2.0.4 and is running as Active Data Guard. Database B is a reporting database and is version 12.1.0.2. In the past, database A was running on Solaris (four-node RAC) and we were using Oracle Streams to replicate over 400 tables from this particular database over to database B. We were also replicating tables from multiple other databases to database B but that is beside the point for this discussion. After we converted database A to LINUX, we decided to keep database B as the front-end and created synonyms to access tables from database A (ADG) using DB links. We have also setup IPC communication between A and B assuming that IPC would be faster than TCP. Unless I have misconfigured IPC, so far the performance of accessing database from B-to-A over a DB link is abysmal. Before I ask users to start accessing A directly instead of going through B, I wanted to understand the IPC communication a
  bit better.
>
> In my scenario where both databases reside on the same physical server, is there a way to optimize access from B-to-A over a DB link?
>
> Thank you,
>
> Amir

--
http://www.freelists.org/webpage/oracle-l