Skip to Main Content
  • Questions
  • SQL*Net message from client for MView refresh

Breadcrumb

Question and Answer

Chris Saxon

Thanks for the question, Chittaranjan Tandel.

Asked: August 12, 2016 - 9:45 am UTC

Last updated: August 12, 2016 - 1:26 pm UTC

Version: 11g

Viewed 1000+ times

You Asked

Hi tom,
I am getting wait events with SQL*Net message from client continuously while I am doing mview refresh.
Now here while refreshing the mview it is accessing the data through db link & source db & destination db are on same server.
So can u suggest the solution for the above wait event because this wait event is seen for longer when the job executes & due to it my mview refresh job runs more than 13 hours.

Regards,
Chittaranjan T

and Chris said...

SQL*Net message from client means the database is waiting for the remote system to do its work. So the "problem" here isn't this wait. It's whatever the other database is doing!

You need to look at the remote database and find out what it is doing when you refresh the MV. This will help you determine how to reduce the runtime.

Rating

  (1 rating)

Is this answer out of date? If it is, please let us know via a Comment

Comments

Wait event Information

Chittaranjan Tandel, August 12, 2016 - 12:43 pm UTC

In our case both the DB's are in the same server both source and target. So I believe Data retrieval through DB link should be faster and There should not be Network Latency in this case. But we are facing the same. Can you please elaborate on this?

Regards
Chittaranjan Tandel
Trivandrum - India
Chris Saxon
August 12, 2016 - 1:26 pm UTC

It doesn't matter that they're on the same server. This is unrelated to network latency. Your local database is waiting for the other database to do "something".

What? I don't know! Look on the other database!