Effect of join order on join plan

For example, consider the following query:

SELECT --+ORDERED, AVOID_FULL(e)
* FROM employee e, department d
WHERE e.dept_no = d.dept_no AND e.salary > 5000

In this example, the optimizer chooses to join the tables with a hash join. However, if you arrange the order so that the second table is employee (and must be accessed by an index), the hash join is not feasible.

SELECT --+ORDERED, AVOID_FULL(e)
* FROM department d, employee e
WHERE e.dept_no = d.dept_no AND e.salary > 5000;