Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: index creation fails because temp tablespace is too small
DA Morgan wrote:
> Jonathan Lewis wrote:
>
>>> Am I missing something? Hopefully not something too obvious. >> >> >> Try running a query that requires some temp space. >> The column is not reported if none of the rows >> have populated it. (The default is null, not zero). >> >> rem 9.2.0.6 >> rem optimizer_mode = all_rows >> rem system stats have been gathered >> >> explain plan for >> select source from sys.source$ order by source; >> >> select * from table(dbms_xplan.display); >> >> PLAN_TABLE_OUTPUT >> ----------------- >> >> --------------------------------------------------------------------------------- >> >> | Id | Operation | Name | Rows | Bytes |TempSpc| >> Cost (%CPU)| >> --------------------------------------------------------------------------------- >> >> | 0 | SELECT STATEMENT | | 1324K| 2528M| | >> 724K (1)| >> | 1 | SORT ORDER BY | | 1324K| 2528M| 5172M| >> 724K (1)| >> | 2 | TABLE ACCESS FULL | SOURCE$ | 1324K| 2528M| | >> 4128 (2)| >> --------------------------------------------------------------------------------- >> >> >> 8 rows selected.
10G displays the SQL hashvalue in the explain plan. But is hash value always unique? Received on Thu May 12 2005 - 19:47:31 CDT