Jonathan
Thanks for your update. Currently, I can see that app is using the procedure in
most of the call but there are some direct calls too. So will definitely take
this point to make all calls to be done as procedure call as possible with the
app team. Your another suggestion for SDU size is also good as an alternative.
ThanksSanjay
On Friday, March 15, 2019, 5:58:22 AM EDT, Jonathan Lewis
<jonathan@xxxxxxxxxxxxxxxxxx> wrote:
Almost certainly - but I believe you can replace default Informatica processing
with a call to a "native procedure", so Informatica can call a pl/sql procedure
to do "insert as select" instead of sucking millions of rows across the network
and pushing them back into a different table. This assumes, of course, that
you don't do something in Informatica that can't be done locally in the
database.
If you can't call native procedures there are a couple of way to optimise the
traffic. How are you doing the inserts, and how have you configure the SQL*Net
SDU size ?
Regards
Jonathan Lewis
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf
of Sanjay Mishra <dmarc-noreply@xxxxxxxxxxxxx>
Sent: 15 March 2019 03:20:30
To: Oracle-L Freelists
Subject: Oracle and Infomatica connection
Hi
I had infomatica server running ETL load which is selecting data from One
Schema to another schema in the same database. Data loaded are millions of
rows. Does network bandwidth matter in such scenario as my Infomatica server is
in different Centre then Database Tier and there is high communication issue as
ping shows 45ms reposnse time. I can see multple SQL Net kind of waits but not
sure if that should come when infomatica is reading and writing on Database
server itself.
TIA
Sanjay
--
//www.freelists.org/webpage/oracle-l
