I have been very often confronted to non-monitored very big execution plans
and the the reliable fix I have alaways used is to increase the
I haven't experienced any bad side effects induced by increasing
And the funny thing is that, if your query is running and not monitored, it
suffices to increase the _sqlmon_max_planlines parameter and you will get
immediately your monitoring report as if it has been monitored from the
beginning of the *execution*.
Le lun. 18 mai 2020 à 21:52, Henry Poras <henry.poras@xxxxxxxxx> a écrit :
Thanks. My interpretation was a bit different. I thought, well, if you
need to set the underscore parameters, then why have the 'alter system'
command. At that point, everything will be Monitored automatically anyway.
On Mon, May 18, 2020 at 3:44 PM Martin Berger <martin.a.berger@xxxxxxxxx>
It seems, information oracle shares regarding underscore parameters is
vague as always.
A quite good source is
There Maria states, you can enforce monitoring with force=true , but
then immediately the limits are explained.
I read id the way, by force=true, sqlmonitoring is "basically" triggered.
Then it still follows all the rules & limitations, e.g.
This all is only my interpretation. Still I'd recommend to increase
_sqlmon_max_planlines. Maybe you can limit it to the sessions in question
to limit it's impact.
Am Mo., 18. Mai 2020 um 20:59 Uhr schrieb Henry Poras <
Has anyone gotten "alter systems set events 'sql_monitor [sql:xxxxxxx]
force-true'" to work? I'm on 126.96.36.199, enabled monitoring for a sql_id
whose plan is greater than the default for monitoring (> 300 lines). I can
see the sql running, but it isn't being monitored.
Anyone else see this?
Martin Berger Oracle ♠
martin.a.berger@xxxxxxxxx @martinberx <https://twitter.com/martinberx>