|
You are here |
jonathanlewis.wordpress.com | ||
| | | | |
rwijk.blogspot.com
|
|
| | | | | ||
| | | | |
tanelpoder.com
|
|
| | | | | Jonathan Lewis has already written about this behavior from the angle of PARALLEL hints. I'm writing a similar article just because the word FORCE in the ALTER SESSION FORCE PARALLEL QUERY syntax. Force should mean that some behavior would always happen (when possible), right? Let's test: SQL> CREATE TABLE t AS SELECT * FROM dba_objects; Table created. SQL> CREATE INDEX i ON t(owner); Index created. SQL> @gts t Gather Table Statistics for table t... PL/SQL procedure successfully completed. Now let's "force" the parallel query in my session, run the query and check the execution plan: - Linux, Oracle, SQL performance tuning and troubleshooting training & writing. | |
| | | | |
kerryosborne.oracle-guy.com
|
|
| | | | | ||
| | | | |
dincosman.com
|
|
| | | The performance issue with an SQL query was resolved by using the /*+ PARALLEL(2) */ hint, reducing execution time from 180-200 seconds to milliseconds. The decision to perform a direct read from disk to memory instead of reading blocks from disk was made by the database engine and is controlled by the hidden "_serial_direct_read" parameter.... | ||