Comments embedded.
On Dec 31, 2:06 pm, "elmaazouz kamal" <
elmaaz...@gmail.com> wrote:
> I'm trying to optimize the redo apply process in a physical standby
> dataguard configuration using the best practices document from oracle.
> The three wait events recently posted was the top wait system events, for
> the dispatcher timer, I disabled dispatchers on the Both environnements.
> But the event "PX Deq: Test for msg" is still on the top events, especially
> I'm using parallel recovery on a 2 processor dual core standby Server using
> the following query:
>
> *ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE
> the event **SQL*Net message from client seems to be a network bandwidth
> issue.
> how about the **PX Deq: Test for msg
I've explained this one in my last post. It's the parallel
coordinator waiting to dequeue a message from a slave.
> and **rdbms ipc message* *??
This is the cumulative wait time from idle LGWR, DBWR and LMS0
processes. So your log writer, database writer and cache fusion
(LMS0) processes (a component of RAC) are idle.
> Best regards.
> **
> *
> Kamal ELMAAZOUZ- Hide quoted text -
>
> - Show quoted text -
David Fitzjarrell