Examine the parameters for your database instance:

You generate an execution plan for this query and the plan table shows a nested loop join in the plan :

After query execution, you see that a hash join was performed:

What explain this optimizer behavior?