It doesn't quite apply to this case (250 indexes on one table), but I started scribbling a note last night (probably publish it tonight) about using the "LIST" options with dbms_stats.gather_schema_stats() to see how far the corresponding "GATHER" option has got. Not sure if it could be warped to do the same for a single "gather_table_stats" - but an easy option would be to "select index_name, last_analyzed" for the table where the last_analyzed is earlier than the start of job.
Regards Jonathan Lewis http://jonathanlewis.wordpress.com----- Original Message ----- From: "Connor McDonald" <mcdonald.connor@xxxxxxxxx>
To: "oracle_l" <oracle-l@xxxxxxxxxxxxx> Sent: Friday, April 01, 2011 6:40 AM Subject: Re: how to find dbms_stats progress in 11g ?
On Thu, Mar 31, 2011 at 6:37 PM, Prem <premj@xxxxxxxxxxxxxx> wrote:Niall - my peer is a part of offshore team and has to update the dba team sitting in client place regularly . People there are more curious about this job's progress (not sure why) and keep asking for frequent updates. That was the reason he wanted to know it . He was saying there is a view (other than session_longops and dba_indexes) which would give all these details . I was not aware of it and so posted here . ~ jp ~ <http://sigads.rediff.com/RealMedia/ads/click_nx.ads/www.rediffmail.com/signatureline.htm@Middle?>dbms_sqltune.report_.... is a great way of monitoring any long running sql (part of tuning pack license I think)
-- //www.freelists.org/webpage/oracle-l