(10g) 자동 통계정보 수집(AUTOMATIC OPTIMIZER STATISTICS COLLECTION)

제품 : ORACLE SERVER
작성날짜 : 2006-07-21
PURPOSE
이 문서는 10g의 new feature인 자동 통계정보 수집(Automatic Optimizer
Statistics Collection)에 대한 소개와 기능에 대한 자료이다.
Explanation
1. 개요
Optimizer statistics는 GATHER_STATS_JOB에 의해서 자동으로
수집된다. 이 JOB은 SYS 소유로서 OBJECT_TYPE이 JOB이다.
이 JOB은 통계정보가 없거나 stale 상태의 통계정보를 갖는 DB 내의
모든 OBJECT들에 대한 통계정보들을 수집한다.
2. 자동 통계정보 수집을 위한 설정과 방식
1) STATISTICS_LEVEL = TYPICAL | ALL
2) 통계정보들은 predefined GATHER_STATS_JOB에 의해 수집된다.
3) JOB이 수행될 때 JOB은 다음과 같은 사항들을 결정한다.
- missing 또는 stale 상태의 통계정보를 갖는 object를 결정한다.
- 좋은 통계정보를 생성하기 위해 필요한 적당한 sampling percentage.
- histogram과 histogram의 사이즈를 요구하는 적절한 column.
- 통계정보 수집에 대한 parallelism의 degree.
- 어느 object에 대한 통계정보를 수집할지에 대한 우선순위
3. GATHER_STATS_JOB에 대한 설명
이 job은 데이타베이스 생성 시점에 생성되고 스케줄러에 의해 관리된다.
GATHER_STATS_JOB 은 DBMS_STATS.GATHER_DATABASE_STATS_JOB_PROC procedure를
call함으로써 통계정보를 수집한다.
이 프로시져는 'GATHER AUTO' 옵션을 사용한 DBMS_STATS.GATHER_DATABASE_STATS
procedure와 아주 유사한 형태로 동작한다. 이것과 다른 점은
GATHER_DATABASE_STATS_JOB_PROC procedure는 통계정보를 수집해야 할
Object에 대해 우선순위를 두고 순서대로 처리한다. 즉, 가장 많이
통계정보가 update가 되어야 할 object를 가장 먼저 처리하는 것이다.
이것은 maintenance window가 close되기 전에 가장 필요한 통계정보가
먼저 수집되도록 하기 위함이다.
4. Dictionary Objects에 대한 통계정보
1) Oracle Database 10g부터 최적의 performance 결과를 얻기 위해 dictionary
table들에 대한 통계정보도 수집할 수 있다.
언제라도, DBMS_STATS.GATHER_SCHEMA_STATS procedure를 사용하여
dictionary table들에 대한 통계정보를 수집하는 것이 가능하다.
이 때 GATHER_SYS argument는 TRUE로 셋팅되어 있어야 한다.
2) DBMS_STATS.GATHER_DICTIONARY_STATS라 하는 새로운 procedure도 사용
하는 것이 가능하다. 이것을 사용하기 위해서는 ANALYZE ANY DICTIONARY
라는 새로운 system privilege가 있어야 한다.
이 권한은 만약 어떤 user가 SYSDBA 권한이 없는 경우 dictionary object와
fixed object들을 analyze할 수 있도록 한다.
3) GATHER_DATABASE_STATS라는 프로시져는 GATHER_FIXED라 불리우는 새로운
argument를 가진다. 이 값은 default로 FALSE로 셋팅된다. 즉, 기본적으로
fixed table들에 대해서는 통계정보를 생성하지 않도록 한다.
전형적인 System WorkLoad가 있는 동안에는 fixed table들에 대하여
한번만 analyze하면 충분하다.
4) GATHER_FIXED_OBJECTS_STATS라는 procedure를 사용하여 fixed table들에
대한 통계정보를 모으는 것도 가능하다. 또한 모든 fixed table들에 대하여
통계정보를 delete하는 것도 가능하고, fixed table에 통계정보를
export 또는 import하는 것도 가능하다.
Example
none
Reference Documents
<Note:266040.1>

Hi,
Please see here,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/stats.htm#i41448
If the table/s are changing very frequently than its better to gather the stats manually.This would lead teh volatile table coming up into the stats job again and again.
For the system stats and data dictionary stats,they are not collected by default.So there is no choice but to gather them manually.
Aman....

Similar Messages

Automatic Optimizer Statistics Collection Enabled still tables not analyzed

Hello,
We have Oracle 11g R1 database. Our automatic Optimizer Statistics Collection settings are enabled, still I don't see the tables being analyzed, any suggestions if I am missing any settings. All tables do get analyzed if I do manual statistics gathering.
SQL> select CLIENT_NAME ,STATUS from DBA_AUTOTASK_CLIENT;
CLIENT_NAME STATUS
auto optimizer stats collection ENABLED
auto space advisor ENABLED
sql tuning advisor ENABLED
Thanks,
SK

user599845 wrote:
Hello,
We have Oracle 11g R1 database. Our automatic Optimizer Statistics Collection settings are enabled, still I don't see the tables being analyzed, any suggestions if I am missing any settings. All tables do get analyzed if I do manual statistics gathering.
SQL> select CLIENT_NAME ,STATUS from DBA_AUTOTASK_CLIENT;
CLIENT_NAME STATUS
auto optimizer stats collection ENABLED
auto space advisor ENABLED
sql tuning advisor ENABLED
Thanks,
SK
still I don't see the tables being analyzed, post SQL & results that lead you to this conclusion.
realize that statistics can be "collected" without updating LAST_ANALYZED column.
if data within table does not change, the nothing would be gained by "updating" statistics to same values as now/before.

Optimizer Statistics collection after upgrade from 8i to 10R2

I just upgraded database from 8.1.7 to 10R2 .
What would the best approach for Optimizer Statistics collection. We would like to open database for test , but I afraid some quries going to run slow without latest stats. Should I run it manually or let Oracle run it’s default stats collection job later on.
Any suggestions?

user594143
You really need a strategy before an upgrade like this, but you have two options -
a) try to make the 10g stats collection identical to the 8i stats collection. Check the code you used to run, check the 8i default values for the parameters in your current dbms_stats() calls, and write them in explicitly when you run the code under 10g.
OR
b) do a full 10g conversion. Get rid of your own collection code, clear out most of the old settings you had in your parameter file for fiddling with the optimizer, do a 'gather_schema_stats' then leave 10g to do its default thing and fix any problems that appear.
If you have testing time on a non-production system, then (b) is the strategic option - although personally I think it tends to collect too many histograms and still needs some refinement; if you don't have any testing time and you're going straight into production then (a) is the least threatening option (and if someone's made you do that, you might also set the optimizer_features_enable to 8.1.7 until you can do some proper upgrade tests).
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Disable Automatic Optimizer Statistics

Hi there
I wanted to query user_tab_modifications to track, number of rows updated in a week. Since this view is refreshed automatically when Automatic Optimizer Statistics gathers statistics, i disabled the Automatic Optimizer Statistics. Now i am executing execute dbms_stats.FLUSH_DATABASE_MONITORING_INFO(); manually to get the view populated with number of rows updated.
My concern here is , will i get the exact number of rows updated in a week from user_tab_modifications by doing this ? Also, is there anything else that is also updating this view apart from optimizer statistics that are gathered on a table.
Thanks

You could try writing some PLSQL on your own.
How about :
SQL> create table count_X_updates (update_count number);
Table created.
SQL> insert into count_X_updates values (0);
1 row created.
SQL> commit;
Commit complete.
SQL>
SQL> create table X (col_1 varchar2(5), col_2 varchar2(5), col_3 number);
Table created.
SQL> insert into X values ('a','first',1);
1 row created.
SQL> commit;
Commit complete.
SQL>
SQL> create or replace trigger count_x_updates_trg
2 after update of col_1,col_2,col_3
3 on X
4 for each row
5 declare prev_cnt number;
6 begin
7 update count_X_updates set update_count = update_count+1;
8* end;
SQL> /
Trigger created.
SQL> update x set col_1 = 'b', col_2='secnd',col_3=2;
1 row updated.
SQL> commit;
Commit complete.
SQL> select * from count_X_updates;
UPDATE_COUNT
           1
SQL> update x set col_1 = 'c' where col_3=2;
1 row updated.
SQL> commit;
Commit complete.
SQL> select * from count_X_updates;
UPDATE_COUNT
           2
SQL> select * from x;
COL_1 COL_2      COL_3
c     secnd          2
SQL>Note : This trigger code has to be improved because
a. Multiple sessions might get the same value
b. It introduces a point of serialisation -- multiple session will wait on a row lock on the table count_X_updates -- effectively meaning that all other sessions attempting to update X will wait (even if they are updating different rows in X) till each preceding one issues a COMMIT.
So, this demo code is only to show you PLSQL Triggers. But it cannot be used in Production.
Practice some PLSQL. Read up on autonomous transactions.
Hemant K Chitale

Doubt Regarding Statistics Collection in 10g

Hello,
Me Jr Dba i have a doubt regarding statistics calculation in 10g.As we know that if we set
the initilization parameter STATISTICS_LEVEL=Typical then AOS(Automatic Optimizer staistics) calculate the statistics for the tables, whose blocks are greater then 10% changed from the last calculation.Here my doubt is since already statistics are gathered,
is there any necessity for us to gather the statistics manually by using
DBMS_STATS.GATHER to see the tables or system statistics.
Can u plz assist me on the above
Regards,
Vamsi

Hi,
Please see here,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/stats.htm#i41448
If the table/s are changing very frequently than its better to gather the stats manually.This would lead teh volatile table coming up into the stats job again and again.
For the system stats and data dictionary stats,they are not collected by default.So there is no choice but to gather them manually.
Aman....

How stop the automatic statistics collection job after the maintenance wind

Hi,
we are for a solution to stop the automatic statistics collection job after the maintenance window finished.
we disable all jobs except the automatic statistics collection, because this is the only one we want to run. Then we define specific values for the interval and duration parameters of the maintenance window to customize this task.
But for their systems it is very important that this job/task will immediately stop when the window is closed!!!
So, how could we ensure this behavior.
For Oracle 10g it is easy because the statistic job always exists and it is possible to set its duration and create an addtional event based job which kills all jobs that are running over duration.
In Oracle 11g the statistic job is created by the system during the maintenance window is open.
We are not able to modify parameters of this system job. After the maintenance window closed the job is already running - only with another resource priority - but it is running.
Please help me in this scenario
Thanks&Regards
Prem

?So basically you are saying is if none of the tables are changed then GATHER_STATS_JOB will not run, but i see tables are updated still the job is not running. I did >query dba_scheduler_jobs and the state of the job is true and scheduled. Please see my previous post on the output
Am i missing anything here, do i look for some parameters settings
So basically you are saying is if none of the tables are changed then GATHER_STATS_JOB will not run,GATHER_STATS_JOB will run and if there are any table in which there's a 10 percent change in data, it will gather statistics on that table. If no table data have changes less than 10 percent, it will not gather statistics.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/stats.htm#i41282
Hope this helps.
-Anantha

How to disable automatic statistics collections on tables

Hi
I am using Oracle 10g and we have few tables which are frequently truncated and news rows added to it. Oracle automatically analyzes the table by some means which collects statistics of the table but at the wrong time(when the table is empty). This makes my query to do a full table scan rather using indexes since the statistics was collected when the table was empty.Could any one please let me know how to disable the automatic statistics collection feature of Oracle?
Cheers
Anantha PV

Hi
I am using Oracle 10g and we have few tables which
are frequently truncated and news rows added to it.
Oracle automatically analyzes the table by some means
which collects statistics of the table but at the
wrong time(when the table is empty). This makes my
query to do a full table scan rather using indexes
since the statistics was collected when the table was
empty.Could any one please let me know how to disable
the automatic statistics collection feature of
Oracle?
First of all I think it's important that you understand why Oracle collects statistics on these tables: Because it considers the statistics of the object to be missing or stale. So if you just disable the statistics gathering on these tables then you won't have statistics at all or outdated statistics.
So as said by the previous posts you should gather the statistics manually yourself anyway. If you do so right after loading the data into the truncated table, you don't need to disable the automatic statistics gathering as it only processes objects that are stale or don't have statistics at all.
If you still think that you need to disable it there are several ways to accomplish it:
As already mentioned, for particular objects you can lock the statistics using DBMS_STATS.LOCK_TABLE_STATS, or for a complete schema using DBMS_STATS.LOCK_SCHEMA_STATS. Then these statistics won't be touched by the automatic gathering job. You still can gather statistics using the FORCE=>true option of the GATHER__STATS procedures.
If you want to change the automatic gathering job that it only gathers statistics on objects owned by Oracle (data dictionary, AWR etc.), then you can do so by calling DBMS_STATS.SET_PARAM('AUTOSTATS_TARGET', 'ORACLE'). This is the recommended method.
If you disable the schedule job as mentioned in the documentation by calling DBMS_SCHEDULER.DISABLE('GATHER_STATS_JOB') then no statistics at all will be gathered automatically, causing your data dictionary statistics to be become stale over time, which could lead to suboptimal performance of queries on the data dictionary.
All this applies to Oracle 10.2, some of the features mentioned might not be available in Oracle 10.1 (as you haven't mentioned your version of 10g).
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle:
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

10g Automatic Stats Collection -- AUTO ( METHOD_OPT)

I have implememted Oracle 10g Auto Stats collection feature. To generate new stats on 10g optimizer I deleted the schema stats and then scheduled the DBMS_SCHEDULER to collect stats in AUTO method_opt.
I see that the new 10g optimizer is collecting stats differently in different databases eben through they have the same data.
For exampl I see that it collected Histograms on 10 columns in one table in one environment but it generatd histograms only on 9 columns in another env.
I am concerned that the stats difference will result in the execution plan getting changed across different instances.
Can someone please clarify the cause of the same. How can I make sure tha the 10g optimizer is collecting stats uniformly across different envs.
Thank You

You wrote:
"I am concerned that the stats difference will result in the execution plan getting changed across different instances."
and you should be concerned.
I would recommend not collecting stats the way you are but rather to use a nuanced approach where you collect only when they are stale or only when you know that changes have rendered old statistics invalid.

Creteria for generating optimizer statistics

Dear membes,
Oracle 10.2.0.2
os : HP-UX 11i
I want to know is there any creteria for generating optimizer statistics
for the production database, like we have a creterai for rebuilding indexes
through checking the index_stat table.
Is there any tables present in database for this kind pre checking before
generating the optimizer statistics.
Thanks.

VIRENDER SINGH wrote:
Dear membes,
Oracle 10.2.0.2
os : HP-UX 11i
I want to know is there any creteria for generating optimizer statistics
for the production database, like we have a creterai for rebuilding indexes
through checking the index_stat table.
Is there any tables present in database for this kind pre checking before
generating the optimizer statistics.First of all I hope you've heard that rebuilding indexes is something that should only be done under very rare circumstances, see e.g. here or here.
Since you're on 10g already you should be aware of the fact that the database is coming with a pre-configured default statistics collection job that runs every night and attempts to gather statistics on stale objects (either with no statistics at all or more than 10% changes since the last statistics gathering).
If you're having an application that modifies large chunks of data in batch jobs, then you should consider gathering statistics right after these batch modifications because otherwise it might take too long until the default job is activated and refreshes the statistics and many execution plans until then might suffer from the incorrect/outdated statistics.
Ideally you should know your application and data and work out when to gather the statistics and in particular how to gather the statistics and in some cases even use hand-crafted statistics (using the DBMS_STATS.SET__STATS procedures) that lead the optimizer in the desired direction.
There are many potential pitfalls to consider, e.g. the default method for generating histograms has changed in 10g to "FOR ALL COLUMNS SIZE AUTO" which means you'll get histograms for columns that are used in WHERE clauses (when using equal or range comparisons) and have skewed data or contain large gaps in the values. This was not the case in 9i and not always does the existence of histograms change execution plans for the better, in particular if you're using bind variables.
In addition 10g introduced the possibility of "out-of-range" predicates which means that the optimizer takes into account if a predicate value is outside the recorded minimum and maximum value of the column. If the gap is becoming significant the selectivity is adjusted and eventually you get an estimate of 1 (or actually 0 adjusted to 1) rows which can have dramatic effects on your execution plans.
This means you need to be careful if the default "staleness" of 10% changes is applicable to your particular situation otherwise you might be confronted with execution plans that either deteriorate over time and/or "switch" at a certain point in time to a really "bad" plan to due the adjusted selectivity caused by the "out-of-range" predicates. If this is the case you should consider refreshing the statistics more often (using your own logic/job) to avoid such situations.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Error in Update optimizer statistics - index is in unusable state

Hello,
we have this error in log Check and update optimizer statistics:
12.02.2009     23:21:20     'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPPB1"', TABNAME => '"/BIC/FZPPC0002"', ESTIMATE_PERCENT => 10, METHOD_OPT =
12.02.2009     23:21:20     ORA-20000: index "SAPPB1"."/BIC/FZPPC0002~010" or partition of such index is in unusable state
12.02.2009     23:21:20     ORA-06512: at "SYS.DBMS_STATS", line 13452
12.02.2009     23:21:20     ORA-06512: at "SYS.DBMS_STATS", line 13472
12.02.2009     23:21:20     ORA-06512: at line 1
12.02.2009     23:21:20     BR0886E Checking/collecting statistics failed for table SAPPB1./BIC/FZPPC0002
i can temporary fix this problem when i delete and recreate index via SE14, but this help only for one next running update statistics, every next running update statistics has same error: index "SAPPB1"."/BIC/FZPPC0002~010" or partition of such index is in unusable state. Exist any definitive solution for this problem. Thanks

Hi,
Two methods for checking/repairing Indexing issues
1)RSRV for a particular cube
2)SAP_INFOCUBE_INDEXES_REPAIR report
You can also use this sql to rebuild an Index.
alter index <index name> rebuild online; Or you can rebuild Index by using ABAP report 'RSANAORA'.
Please check below thread it may help you.
/message/6483705#6483705 [original link is broken]
https://forums.sdn.sap.com/click.jspa?searchID=12942068&messageID=2052264
Thanks,
Sushil

Check and Update Optimizer Statistics Error

Hello,
I have scheduled 'Check and Update Optimizer Statistics' from DB 13 but I always get this error.
BR0280I BRCONNECT time stamp: 2009-01-05 01.00.46
BR0301E SQL error -20000 at location stats_ind_collect-3, SQL statement:
'BEGIN DBMS_STATS.GATHER_INDEX_STATS (OWNNAME => '"SAPSR3"', INDNAME => '"/BIC /B0000412000KE"', ESTIMATE_PERCENT => 30, DEGREE => NULL, NO_INVALIDATE => FALSE); END;'
ORA-20000: index "SAPSR3"."/BIC/B0000412000KE" or partition of such index is in unusable state
ORA-06512: at "SYS.DBMS_STATS", line 10610
ORA-06512: at "SYS.DBMS_STATS", line 10645
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for index SAPSR3./BIC/B0000412000KE
Tried checking the table /BIC/B0000412000KE and got this from the check:
Enhancement category for table missing
Enhancement category for include or subtype missing
Table /BIC/B0000412000 was checked with warnings
I am still checking what this means but appreciate you have any idea on how to solve it.
Thank you.
Best Regards,
Julius
Edited by: Julius Baron Manuel on Jan 7, 2009 7:39 AM

Hi Julius,
Have your tried scheduling the update stats via DB13 'Immediately'. ??? Does it still gives you the same error when its done 'immediately'?
Try out DB02 and check your whole Database along with missing indexes. Refresh database and update histories.
Regards,
Pranay

Check and update optimizer statistics failed

Hellow Friends,
After running job Check and update optimizer statistics each and every time from db13 in my BI production server it got failed please
view the logs
BR0301E SQL error -20000 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BIC/B0000228000"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL
ORA-20000: index "SAPSR3"."/BIC/B0000228000KE" or partition of such index is in unusable state
ORA-06512: at "SYS.DBMS_STATS", line 13159
ORA-06512: at "SYS.DBMS_STATS", line 13179
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPSR3./BIC/B0000228000
BR0280I BRCONNECT time stamp: 2009-05-19 18.17.19
BR0883I Table selected to collect statistics after check: SAPSR3./BIC/B0000229000 (161130/1480:0:0)
BR0280I BRCONNECT time stamp: 2009-05-19 18.17.19
BR0881I Collecting statistics for table SAPSR3./BIC/B0000229000 with method/sample E/P10 ...
BR0280I BRCONNECT time stamp: 2009-05-19 18.17.21
BR0301E SQL error -20000 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BIC/B0000229000"', ESTIMATE_PERCENT => 10, METHOD_OPT => 'FOR ALL C
ORA-20000: index "SAPSR3"."/BIC/B0000229000KE" or partition of such index is in unusable state
ORA-06512: at "SYS.DBMS_STATS", line 13159
ORA-06512: at "SYS.DBMS_STATS", line 13179
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPSR3./BIC/B0000229000
BR0280I BRCONNECT time stamp: 2009-05-19 18.17.21
BR0883I Table selected to collect statistics after check: SAPSR3./BIC/B0000230000 (0/13545:0:0)
BR0280I BRCONNECT time stamp: 2009-05-19 18.17.21
BR0881I Collecting statistics for table SAPSR3./BIC/B0000230000 with method/sample E/P30 ...
BR0280I BRCONNECT time stamp: 2009-05-19 18.17.21
BR0301E SQL error -20000 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BIC/B0000230000"', ESTIMATE_PERCENT => 30, METHOD_OPT => 'FOR ALL C
ORA-20000: index "SAPSR3"."/BIC/B0000230000KE" or partition of such index is in unusable state
ORA-06512: at "SYS.DBMS_STATS", line 13159
ORA-06512: at "SYS.DBMS_STATS", line 13179
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPSR3./BIC/B0000230000
Please help me to resolve the issue.

some of your PSA tables are inconsistent - ex: /BIC/B0000228000 - check PSA partitioning in RSRV to correct the same or delete data from the same using SE14 and try running the same.

Optimizer Statistics questions

Hi All,
I have no clear picture about Optimizer Statistics
From Oracle 9i docs ( http://download.oracle.com/docs/cd/B10501_01/server.920/a96533/stats.htm#26713 )
GATHER_INDEX_STATS - Index statistics
GATHER_TABLE_STATS - Table, column, and index statistics
GATHER_SCHEMA_STATS - Statistics for all objects in a schema
GATHER_DATABASE_STATS - Statistics for all objects in a database
GATHER_SYSTEM_STATS - CPU and I/O statistics for the systemMy questions are:
1)if I use the 3rd option it should gather stats for all the objects including indexes. However, when I used that option it didn't gather satas for Index. Do I need to use cascade=>TRUE option?
2) I need to backup my current stats and gather new stats for entire DB. If I export DATABASE stats will it export all stats including index, system?
3) If I collect stats using GATHER_DATABASE_STATS, Do I need to explicitly collect other stats for index, system etc?
Any suggestions are most welcome.
Thanks,

Hi
1)if I use the 3rd option it should gather stats for
all the objects including indexes. However, when I
used that option it didn't gather satas for Index. Do
I need to use cascade=>TRUE option?
Yes, default is FALSE, so need to force TRUE
2) I need to backup my current stats and gather new
stats for entire DB. If I export DATABASE stats will
it export all stats including index, system?
Yes
3) If I collect stats using GATHER_DATABASE_STATS, Do
I need to explicitly collect other stats for index,
system etc?
No

CDMC - Activate Statistics Collection

Hi,
I have a question related to CDMC Statistics Collection.It is not clear for me, after activate the collection what are the periods to evaluate and period type?
Please can you clarify?
Best Regards,
Zsuzsanna

Hi Zsuzsanna,
As shown in the screenshot in my first reply it will take input as per the given period and perid type and will fetch usage statistics data for the given time period but to shcedule the same for every three months you need to give inout in the next pop-up screen here you can give input to schedule three different jobs for future as per your requirement, According to the period and period type given these jobs will be scheduled and run in the statistics/production system and will update usage information in the CDMC table in the statistics system.
According to the given input it will schedule jobs and run in the statistics/produdction system , if you give 1 day then job will run daily and will update and store usage statistics data in the CDMC database table in the statistics system itself and not in Solution manager system.
This data will only get imported in the solman when you create and execute new Clearing analysis project and execute activities in the same.
If you are expecting the latest usage results then yes,you need to create new CDMC Clearing Analysis project every time as this usage information will not get updated automatically in the CDMC project.
Please let me know if you have any doubts.
Best Regards,
Pritish

Auto optimizer stats collection interval

Hi,
I have a question about "auto optimizer stats collection" in 11gR2.
I see on the history, 1 execution of "auto optimizer stats collection" on Monday, Tuesday, Wenesday, Thursday and Friday and 5 executions on Saturday and Sunday.
I find the duration of each window (4 hours on Mon, Tue, Wen, Thu and Friday, 20 hours on Sat and Sun) and start date (22 hour Mon, Tue, Wen, Thur and Friday and 6h on Sat and Sun), but i don't find the interval between executions or frenquency of execution for each window.
Someone can tell me, if is it possible to change this and where ?
Regards,

Thank's for all reply, but it's not the answer of my question.
I know how disable/enable automatic task, i know to add/delete window, etc ... but where can i configure the frequency or interval of the "auto optimizer stats collection" task.
I try to explain what i want to know.
By defaut, on window Mon, Tue, Wen, Thu and Fri, the task start at 22:00 and run once, the window duration is 4 hours. Why one run ?
On window Sat and Sun, the task start à 6:00 and run 5 times ( 6:00, 10:00, 14:00, 18:00 and 22:00), the window duration is 20 hours. Why 5 runs ? or why 4 hours between 2 runs ?
Regards

(10g) 자동 통계정보 수집(AUTOMATIC OPTIMIZER STATISTICS COLLECTION)

Similar Messages

Maybe you are looking for