Re: Reducing idle time in Apex

From: Stefan Koehler <contact_at_soocs.de>
Date: Wed, 16 Mar 2022 09:09:25 +0100 (CET)
Message-ID: <1791841033.284253.1647418165198_at_ox.hosteurope.de>


Hello Mark,
you can also enable extended SQL Trace in APEX via URL parameter.

For details please check here: https://stackoverflow.com/questions/46683919/mastering-oracle-trace-data-page-60-apex-tracing-url-extension

Best Regards
Stefan Koehler

Independent Oracle performance consultant and researcher Website: http://www.soocs.de
Twitter: _at_OracleSK

> Stefan Knecht <knecht.stefan_at_gmail.com> hat am 16.03.2022 06:14 geschrieben:
>
>
> If you can't find it or it's somehow somewhere else, another approach is to trace the page load in the database.
>
> If you are allowed & have access to edit the page, you can create a page process that executes a bit of plsql code and just enable 10046 that way. In Apex, the entire page will load in the same database session - so tracing it is easy. Just make sure that it has the lowest sequence number and executes "Before Header" (to ensure it runs before everything else) - and that way you will see what exactly it executes while loading the page and how, which then can also help to track down where & what it is.
>
> Finally, create a second page process and have it execute "After Regions" (or maybe that's "After Footer" in Apex 5, I don't remember for certain) to turn it back off again. That'll give you the most precise set of data to look at.

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Mar 16 2022 - 09:09:25 CET

Original text of this message