The nested loop is the original join access path. In this case, Oracle designates one of the tables as the driving table. Unless there is an index on the driving table that can be used to reduce the number of rows chosen, Oracle performs a full table scan on the driving table. It then uses an index to retrieve rows based upon the WHERE clause from the second table.