How to use the _FIX_CONTROL hidden parameter (Doc ID 827984.1) | To Bottom |
In this Document
APPLIES TO:Oracle Database Backup Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later Oracle Database Cloud Exadata Service - Version N/A and later Oracle Database Cloud Service - Version N/A and later Oracle Database Cloud Schema Service - Version N/A and later Information in this document applies to any platform. ***Checked for relevance on 01-May-2012*** GOAL_FIX_CONTROL is a special hidden dynamic parameter introduced in 10.2.0.2 which can be used to enable or disable certain bug fixes. This is typically used in the optimizer area to allow specific fixes to be turned on or off as some fixes can have a significant effect on execution plans.
You are using the parameter _FIX_CONTROL to enable or disable specific patches. When you try to add the parameter you get: SQL> ALTER SESSION SET "_FIX_CONTROL"='6626018:ON','6660162:ON','6440977:ON'; SOLUTIONThe syntax for using _FIX_CONTROL is: To enable: To disable:
For _FIX_CONTROL to work, several conditions must be met: 1) The patch that is referenced must have the option to use _FIX_CONTROL. Using _FIX_CONTROL can't be used to backout any patch. The patch (usually an Optimizer patch) has to be enabled to use the _FIX_CONTROL parameter. 2) The patch must be installed and visible in the V$SYSTEM_FIX_CONTROL view. To check this: SQL> SELECT * FROM V$SYSTEM_FIX_CONTROL; Note: To determine which bug fixes have been altered one can select from the fixed views GV$SYSTEM_FIX_CONTROL, GV$SESSION_FIX_CONTROL or their V$ counterparts. |