Re: Re: Re: Explain Plan and Security
Date: Sun, 17 Jun 2018 12:28:11 +0200 (CEST)
Message-ID: <1709644387.76024.1529231292151_at_ox.hosteurope.de>
Hello Lothar,
here we go with a (admittedly geeky) solution which is based on Oracle's kernel low-level debug & diagnostics infrastructure.
Set an event with a scope on the specific SQL-ID (if you already have it otherwise without a scope but for your own session only), a filter on the specific call stack that only occurs at the start of fetching data (e.g. opifch*() -> ....) and finally an action to debug the process (e.g. suspend / abort) with an external system debugger.
The syntax of this event might need a few test cycles but then it should work like a charm :-)
Best Regards
Stefan Koehler
Independent Oracle performance consultant and researcher
Website: http://www.soocs.de
Twitter: _at_OracleSK
> "l.flatz_at_bluewin.ch" <l.flatz_at_bluewin.ch> hat am 16. Juni 2018 um 15:28 geschrieben:
>
> Hi Martin,
>
> that would not work. I am working for a service provider. The data is not ours. We are by policy forbitten to run queries on prod other than against the dictionary.
> We must look for an other way. Maybe some instant clone would work.
>
> Thanks
>
> Lothar
-- http://www.freelists.org/webpage/oracle-lReceived on Sun Jun 17 2018 - 12:28:11 CEST