Diag and Tuning Pack: disable

Disable Diag and Tuning pack (oracle 10g and 11g)

– Baselines must not be used:
for m in (select * from dba_hist_baseline where baseline_name != ‘SYSTEM_MOVING_WINDOW’) loop
end loop;
end ;

– Manual Snapshots must not be used:
for m in (select * from dba_hist_snapshot where snap_flag0) loop
end loop;
end ;

– awr disable
begin sys.dbms_awr.disable_awr(); end;

– Disable Advisors

– 11g: tuning schedulers disabled. That should be optional as far as licenses are concerned but there are many reasons to get rid of them.

– OEM (Cloud Control, formerly Grid Control, formerly OEM): disable Packs in Grid Control interface, menu on the top-right corner.

Next: mapping between licensed features and dba_feature_usage_statistics is known – see metalink id: Database Options/Management Packs Usage Reporting for Oracle Database 11g Release 2 (Doc ID 1317265.1)

Then one can do this:

1) map features to dba_feature_usage_statistics and sys.wri$_dbu_feature_metadata

2) sys.wri$_dbu_feature_metadata describes how oracle checks for feature usage

3) the feature is disabled based on analysis of sys.wri$_dbu_feature_metadata

4) Mos article “MMON Suspended Due to ORA-12751 “cpu time or run time policy violation” (Doc ID 761298.1)” is used to execute oracle FUS immediately:
alter session set events ‘immediate trace name mmon_test level 6’;

5) repeat from step 2 untill dba_feature_usage_statistics is satisfactory


This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s