RE: tmon

From: Noveljic Nenad <nenad.noveljic_at_vontobel.ch>
Date: Tue, 19 Sep 2017 18:50:56 +0000
Message-ID: <1238_1505847059_59C16713_1238_6823_1_ECDEF0CC6716EC4596FCBC871F48292AB18FCC0B_at_ZRH-S231>

Hey Yong,

Thank you for providing your much appreciated insight on the functions on the cleanup stack.

I've already opened an SR and will keep you posted.

Besides that, I keep running kill.d in the background to record any interference by the application ( such as in http://nenadnoveljic.com/blog/avaloq-database-crash/ ) in the case of a new occurrence.

Nenad

Twitter: _at_NenadNoveljic
Home page: http://nenadnoveljic.com

-----Original Message-----
From: Yong Huang [mailto:yong321_at_yahoo.com] Sent: Dienstag, 19. September 2017 17:09 To: oracle-l_at_freelists.org
Cc: Noveljic Nenad
Subject: Re: tmon

Hi Nenad,

I searched for your call stack on MOS but can't locate a good match. There are a few for Oracle 11gR2 but there's an additional function between ksuitm and ksumcl, i.e. ksuinstalive, e.g. Bugs 16426985, 10179554. One is for Oracle 12.1 (Bug 18077020) and there's no such intermediate function, but there's ktsj_smco_main further down the stack. Anyway, I suggest you open an SR and have the Support take a look.

Your stack:
ksedsts: error handling, always ignore
kjzdicrshnfy: crash notification

ksuitm: some kind of timeout
ksumcl: not sure, process memory cleanup?
ksbcti: "call timeout/interrupts" according to various bug reports
ksbabs: "Background process: Action based server"
ksbrdp: "run a detached (background) process"

ksumcl may be interesting. But if it's already doing cleanup, then this stack is not helpful.

If Oracle Support finds anything interesting, let us know. Thanks.

Yong Huang

---

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 Tue Sep 19 2017 - 20:50:56 CEST