Also
if you are analyze table compute statistics - you can do several command
in parallel in different sessions
analyze table ... compute statistics for table
analyze table ... compute statistics for all
indexes
analyze table ... compute statistics for all indexed
columns
analyze table
... compute statistics for <col1>, <col2>, etc - for columns
with squed values
Alex Hillman
-----Original Message-----
From: Hillman, Alex [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 13, 2001 11:07 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Forever running AnalyzeLooks like nobody offered to increase sort_area_size for the session that is doing analyze - at least to such size that it will require only one merge phase. See Steve Adams web site for formula how to calculate the size, but I think that 20M should be more than enough.Alex Hillman
[Hillman, Alex]-----Original Message-----
From: Kevin Lange [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 5:31 PM
To: Multiple recipients of list ORACLE-L
Subject: Forever running AnalyzeHi folks;We have an Analyze running that is taking forever. Here is the setup:The table is about 250 bytes wide.The table is normally 100,000 rowsThe table has grown to over 4,000,000 rows.There is one index on 1 column.We used the Compute Statistics optionsDoes anyone have any suggestions on how we can get this analyze to complete and still generate worthwile statistics ??ThanksKevin