Re: DMON killing RSM0?

  • From: Mladen Gogala <gogala.mladen@xxxxxxxxx>
  • To: "Herring, Dave" <HerringD@xxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 17 Jun 2020 16:50:48 -0400

Heuristic guess for "LNO" would be "log number" but I doubt that you have 413 logs. You can try checking the CRS logs to see whether there is anything strange going on. Err 255 is not much help either, it's unspecified status

On 6/17/20 3:57 PM, Herring, Dave wrote:


The RSM tracefiles have the following message in them:

krss_req_task_reg: Removing previously registered task BROKER WORKER for process RSM0

For the RSM that eventually does not get killed, in addition to the above he has a series of messages like:

krsk_srl_access: Failed to open LNO:412: err=235

krsk_srl_access: Failed to open LNO:413: err=235

The "LN0" value increments each line.  I know that RSM attempts to have NSV contact the standby so I checked NSV's tracefile and around the same time it generates messages like:

rfi_chk_ipmsg: Timeout in executing inter-instance message.

--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217

Other related posts: