Re: DMON killing RSM0?

Offered from a position of complete ignorance of any interaction between DMON & RSM0. Since ORA-16665 is a timeout error and the kill is happening on ALL the databases, is it possible that something floods your network to such an extent that DMON starts getting timeouts when talking to RSM0 and interprets this as RSM0 becoming unstable (I think there are some bugs about memory leaks and subsequence performance problems on MOS) and responds by requesting for it to be killed and restarted.

Regards
Jonathan Lewis

On Fri, Jun 12, 2020 at 10:40 PM Herring, Dave <dmarc-noreply_at_freelists.org> wrote:

> I have a situation where it looks like the DMON process is killing off
> RSM0 processes every night around the same time and I don't have a good
> explanation as to why. This is on a 4-node Exadata env running 18c with 6
> dbs, all using DG (the standby is also a 4-node Exadata env).
>
>
>
> Every night between 20:12 and 21:35 we get a series of ORA-16665 errors
> from all databases, errors found in the broker's logfile. Checking each
> db's alert log I see messages like the following:
>
>
>
> Process RSM0, PID = 51310, will be killed
>
> Process termination requested for pid 51310 [source = rdbms], [info = 2]
> [request issued by pid: 76161, uid: 110]
>
>
>
> SPID 76161 is DMON, which means every night DMON kills off RSM0 processes
> around the same time. This is done for all databases.
>
>
>
> Is there a DG broker setting that says to wipe out all DGB resource
> processes and restart them?
>
>
>
> Regards,
>
>
>
> Dave
>

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