High Foreground Sql*Net More Data From Client wait on a snapshot standby

From: jacques kostic <jacques.kostic_at_gmail.com>
Date: Tue, 28 Sep 2021 21:47:08 +0200
Message-ID: <CAGLWksr2QQtib1XUNwEyzoNi8ej0k_kpGbfJW7-PC=9Fy04bdA_at_mail.gmail.com>



Hi There,

Nice case where Primary is under ODA in DC1, Standby is on Exadata in DC2 (distance between the two DCs is around 50 Miles) Line speed around 5Gb/s Database size is almost 4TB.

Goal is to move the primary database to Exadata Tests are in progress but performances are nearly the same as in the primary ODA based system.
To do the tests, the standby is converted into snapshot standby.

During the workload, we have a high foreground Sql*Net More Data From Client wait rate!
[image: image.png]

We can notice in Top Sessions section that the top one is coming from the primary host.

[image: image.png]

I have already managed a couple of snapshot standby scenarios but never came to this case...
Could be possibly related to the low network bandwidth impacting the communication between the snapshot standby and the primary...

Will check that tomorrow...
Does anyone have any ideas?

Cheers
jko



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



Received on Tue Sep 28 2021 - 21:47:08 CEST

Original text of this message