Oracle Magazine, July/August 2019
Database Developer and DBA ETL QBLOCK_ NAME VARCHAR2 128 REMARKS VARCHAR2 4000 OTHER_ XML CLOB CON_ ID NUMBER Fortunately there is an API to act as a wrapper around the information exposed in the V SQL_ PLAN performance view which can simplify the process of getting a nicely formatted execution plan That wrapper DBMS_ XPLAN DISPLAY_ CURSOR is a table function that is it can be queried as if it were a database table to return the true execution plan from an execution of a SQL statement By default it will output the execution plan of the most recently executed SQL statement in the current database session Listing 4 shows an example of this some sections of the output have been omitted for simplicity Listing 4 The true execution plan for the problematic SQL statement ORACLE MAGAZINE JULY AUGUST 2019 142 SQL select e department_ id sum salary 2 from employees e 3 job_ history j 4 where e employee_ id j employee_ id 5 and extract year from e hire_ date 1985 6 and j end_ date j start_ date 1 7 and j start_ date e hire_ date 8 group by e department_ id
You must have JavaScript enabled to view digital editions.
