Today I installed for the first time the patchset 10.2.0.5. While reading the README file, I noticed the following piece of information.
To enable a new native full outer join implementation in the database, a user has to set the following underscore parameter:
_optimizer_native_full_outer_join =force
You can set this parameter for the system or for a specific session.
Besides dramatically improving the performance of a full outer join, the new implementation fixes a variety of issues, for examples a variety of ORA-942 (table or view doesn’t exists) and ORA-4331 (unable to allocate string bytes of shared memory) errors.
This issue is tracked with Oracle bug 6322672.
Great! At last we can officially take advantage of native full outer join also in 10.2 (the feature was officially introduced in 11.1, but was already “available” in 10.2.0.3).
Here is an example:
- By default native full outer joins are disabled (notice the implementation with the UNION ALL operation):
SQL> SELECT * FROM emp FULL OUTER JOIN dept USING (deptno); Execution Plan ---------------------------------------------------------- Plan hash value: 2291915024 --------------------------------------------- | Id | Operation | Name | --------------------------------------------- | 0 | SELECT STATEMENT | | | 1 | VIEW | | | 2 | UNION-ALL | | |* 3 | HASH JOIN OUTER | | | 4 | TABLE ACCESS FULL| EMP | | 5 | TABLE ACCESS FULL| DEPT | | 6 | NESTED LOOPS ANTI | | | 7 | TABLE ACCESS FULL| DEPT | |* 8 | INDEX RANGE SCAN | EMP_DEPTNO_I | --------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 3 - access("EMP"."DEPTNO"="DEPT"."DEPTNO"(+)) 8 - access("EMP"."DEPTNO"="DEPT"."DEPTNO")
- As suggested by the README file, the feature can be enabled at the session level:
SQL> ALTER SESSION SET "_optimizer_native_full_outer_join" = force; SQL> SELECT * FROM emp FULL OUTER JOIN dept USING (deptno); Execution Plan ---------------------------------------------------------- Plan hash value: 51889263 ------------------------------------------ | Id | Operation | Name | ------------------------------------------ | 0 | SELECT STATEMENT | | | 1 | VIEW | VW_FOJ_0 | |* 2 | HASH JOIN FULL OUTER| | | 3 | TABLE ACCESS FULL | DEPT | | 4 | TABLE ACCESS FULL | EMP | ------------------------------------------ Predicate Information (identified by operation id): --------------------------------------------------- 2 - access("EMP"."DEPTNO"="DEPT"."DEPTNO")
Hi Christian,
>the feature was officially introduced in 11.1, but was already “available” in 10.2.0.4
It was 10.2.0.3 (can be confirmed using v$sql_hint in 11g)
Hi Timur
Thank you for the feedback. For some reasons I was sure that it was 10.2.0.4… Anyway, I modified the post.
Cheers,
Chris
[…] Christian Antognini pored over the 10.2.0.5 liner notes and discovered that it comes with a native implementation of FULL OUTER JOIN that does not require an inefficient UNION operation. Is that one more reason to stick with Oracle […]
[…] again (another “invalid dba exception”, should have done before ) and it reminded me Christian Antognini’s post about native full outer join support (Being a blog reader is good thing !!!) then I checked the parameter and immediatelly realized that […]
Hi Chris,
it’s also interesting to note that the feature is supported (and not simply available) since (at least) 10.2.0.4: note 1383952.1, paragraph 15.15, explicitly suggests to set _optimizer_native_full_outer_join =force. Actually, the wording seems to strongly encourage users in doing so…
Thanks for this post – with this setting, today an outer join completed in less than a second instead of an hour.
Al
[…] Before that, it was implemented using the UNION ALL operation. (Cristian Antognini explains it here and gives some […]
[…] In the most current Oracle version no relevant limitations exist regarding the Oracle join syntax. Hence choosing ANSI join syntax just because in the past some limitations existed is doing the right for the wrong reasons… I favor the ANSI join syntax because filter and join conditions are clearly separated. For full outer joins, there is simply no better performance option than to use ANSI join syntax. See also also Chris Antognini’s post about native full outer join. […]