Pages

Sunday, February 21, 2016

Disabling AWR Feature .Controlling Diagnostic and Tuning Pack Usage

Disabling AWR Feature .Controlling Diagnostic and Tuning Pack Usage


Why do you disable AWR feature?

If your client did not take  AWR licensing while purchasing database then you have to disable the AWR feature. Database licensing doesn't include AWR and portioning table .

In order to use above feature you take separate licensing from oracle. If you didn't take then you have to disable the feature . 

Disabling AWR Feature .Controlling Diagnostic and Tuning Pack Usage (Doc ID 436386.1)

AWR Reporting - Licensing Requirements Clarification (Doc ID 1490798.1)
 

How to disable AWR feature ?

From 11g, the CONTROL_MANAGEMENT_PACK_ACCESS parameter allows you to control which packs are utilized. This parameter can be set as one of three values:

Values:

NONE - Neither pack is available.

DIAGNOSTIC - Only the DIAGNOSTIC pack is available.

DIAGNOSTIC+TUNING - Both packs are available. This is the default.

The diagnostic pack includes AWR and ADDM while diagnostic and tuning includes sql tuning advisor and sql access advisor.

To check what is set in current environment, you can run the following:

This parameter is dynamic; so to change the parameter from default to none, the following command can be used:

SQL> select NAME from v$parameter where NAME like '%control_management_pack_access%';

NAME
-----------------------------------
control_management_pack_access

SQL> select NAME,value from v$parameter where NAME like '%control_management_pack_access%';
NAME                                VALUE
----------------------------------- -----------------------------------
control_management_pack_access      DIAGNOSTIC+TUNING

SQL> ALTER SYSTEM SET control_management_pack_access=NONE;
System altered.
SQL>
Disabled

SQL> select NAME,value from v$parameter where NAME like '%control_management_pack_access%';

NAME                                VALUE
----------------------------------- -----------------------------------
control_management_pack_access      NONE

No comments:

Post a Comment