I know that this is very much OUTER JOIN bad I don't know why Oracle
can't generate execution plan? Is oacle use 100% CPU to generate
execution plan in fact? This SQL run about 14 hours. On mssql is this
SQL complet in 5 sec. Is possible that this is a bug?
sybrandb napsal:
> The problem is in the database design requiring outer joins almost
> everywhere. Outer joins should be an exception, not the rule.
> Oracle isn't capable of generating efficient execution plans for outer
> joins, and often has to resort to full table scans and/or Merge join
> cartesians.
> A merge join cartesian will inevitably get the cpu to 100 percent.
> If you can't change the design, time to get your creditcard handy and
> buy more and/or more powerful CPUs.
>
> --
> Sybrand Bakker
> Senior Oracle DBA
Received on Thu Jan 18 2007 - 06:39:44 CST
