The difference between using parallelism "/*+parallel(4)*/" in the subquery or the outer query in terms of performance in Oracle I have the below query :
select /*+parallel(4)*/ ---&gt; First Location
       &lt;Desc_1&gt; Amount,
       &lt;Desc_2&gt; Amount,
       &lt;Desc_3&gt; Amount
from (select /*+parallel(4)*/ ---&gt; Second Location
             &lt;Column_1&gt;,
             &lt;Column_2&gt;
      from &lt;Example_Table&gt;
      where &lt;Conditions&gt;
      )
pivot(sum(Column_1) Amount
for &lt;Column_2&gt; in (1 as &lt;Desc_1&gt;,
                   2 as &lt;Desc_2&gt;,
                   3 as &lt;Desc_3&gt;)
                   );

The point is that &lt;Example_Table&gt; is a very big table and I want to ask where is the best to location to use the /*+parallel(4)*/ ? Is it better to use it in theSubQuery or in the outer select? What if we use /*+parallel(4)*/ in both outer and inner select? Is it bad for performance?
Well, if you have just one table, and your outer select is not accessing other tables, I would guess that &quot;Second Location&quot; would be the only one the optimizer looks at.  In practice, easy to test:  just do an explain plan on the two options, and see.  Then invoke it both ways, and verify what happens.
Oracle is pretty smart in doing the right thing for parallel queries; take a look at the following parameters, if neither option is producing a parallel execution plan:
select name, value from v$parameter where name like 'parallel%' order by 1;

And look at Oracle Database Reference section on &quot;Initialization Parameters&quot; such as parallel_adaptive_multi_user for details.
So nothing terrible is likely to happen if you put it in both places, but definately test in a development environment first.