RE: tmon
Date: Mon, 18 Sep 2017 21:11:35 +0000
Message-ID: <11105_1505769099_59C0368B_11105_5312_1_ECDEF0CC6716EC4596FCBC871F48292AB18FBA13_at_ZRH-S231>
Hi Yong,
Thank you for providing this new information!
I haven't claimed that the TMON was killed. I wrote that TT0 was killed based on the entry in the system state dump
PROCESS 36: TT00
…
O/S info: user: oracle, term: UNKNOWN, ospid: 14994 (DEAD)
But your statement is correct: I've just killed a tt0 process and the instance hasn't gone down yet.
Here is the content of the tmon trace just before the crash:
- 2017-09-18 05:27:04.196
- SESSION ID:(755.34480) 2017-09-18 05:27:04.196
- CLIENT ID:() 2017-09-18 05:27:04.196
- SERVICE NAME:(SYS$BACKGROUND) 2017-09-18 05:27:04.196
- MODULE NAME:() 2017-09-18 05:27:04.196
- CLIENT DRIVER:() 2017-09-18 05:27:04.196
- ACTION NAME:() 2017-09-18 05:27:04.196
ksedsts()+439<-kjzdicrshnfy()+816<-ksuitm()+2459<-ksumcl()+177<-ksbcti()+1428<-ksbabs()+2231<-ksbrdp()+1734<-opirip()+844<-opidrv()+651<-sou2o()+122<-opimai_real()+317<-ssth rdmain()+558<-main()+164<-_start()+123
----- End of Abridged Call Stack Trace -----
- 2017-09-18 05:27:04.242 TMON (ospid: 14954): terminating the instance due to error 472 ksuitm: waiting up to [5] seconds before killing DIAG(14763)
- 2017-09-18 05:27:09.355 skgvtime: process 18006 unix pid wrap detected 1 1505705224
Nenad
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Yong Huang
Sent: Montag, 18. September 2017 22:35
To: oracle-l_at_freelists.org
Subject: Re: tmon
Hi Noveljic,
TMON ('Transport Monitor') and TT* ('Redo Transport') sound like background processes meaningful only if you have a standby. But according to x$ksbtabact (as Stefan showed), they seem to perform some actions other than those specific to a data guard.
As to killing tmon killing the instance, I doubt it. You can test by sending a kill signal to it, with or without -9. TMON is a non-fatal background process, as shown in its environment variable SKGP_HIDDEN_ARGS:
$ ps eww 14903
PID TTY STAT TIME COMMAND 14903 ? Ss 0:00 ora_tmon_sand12r2 PATH= ORACLE_SID=...SKGP_HIDDEN_ARGS=<BG/S/TMON/x0/x7/x32238/x923A472E/59813/59848/x157826/x8/x27/x97DEC923/1505765816/1505765816/196609/0/(nil)>...
The first field of the value for this variable is BG. If it were FATAL, killing the process would crash the instance. (By the way, the 9th field indicates its spawning process. You can use that to construct an Oracle background process creation tree, which shows PMAN -> TMON -> TT* processes.)
The message
TMON (ospid: 14954): terminating the instance due to error 472
just means TMON killed the instance. It doesn't mean killing TMON would bring down the instance. As to why TMON did that in your case, I don't know. Is there a function call stack in a trace file during the time? If you do, search for the top function below those error-handling ones and see if there's a document on MOS.
Yong Huang
--
http://www.freelists.org/webpage/oracle-l
Please consider the environment before printing this e-mail. Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain confidential or privileged information. If you are not the named addressee you should in particular not disseminate, distribute, modify or copy this e-mail. Please notify the sender immediately by e-mail, if you have received this message by mistake and delete it from your system.
E-mail transmission may not be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also processing of incoming e-mails cannot be guaranteed. All liability of the Vontobel Group and its affiliates for any damages resulting from e-mail use is excluded. You are advised that urgent and time sensitive messages should not be sent by e-mail and if verification is required please request a printed version.
†Ûiÿü0ÁúÞzX¬¶Ê+ƒü n– {ú+iÉ^ Received on Mon Sep 18 2017 - 23:11:35 CEST