Thanks for the update.
I’ll have to hunt around the parameter list and oraus.msg to see if there’s an alternative.

Since profiles are about numbers, rather than plans, I would use stored outlines to achieve your target – run the query with create_stored_outlines enabled, and optimizer_mode set to rule, and the actual text and actual rule-based plan should be stored. The run switch back to cost based and enable use_stored_outlines.

I think there’s a feature in 11.2 that would then allow you to convert a stored outline into an SQL Baseline. (Remember, SQL Profiles allow execution plans to change over time because mostly they use “arithmetic” hints, but a stored outline or SQL Baseline fixes a plan through “micro-management” hints.)

This was done by the following steps
1. Alter optimizer mode to rbo.
2. Creating profile of step 1.( In dba_sql_profiles it puts hint of /*+rule+/ in sql_text field)
3. changing mode to cost.
4. alter sesiion to the category as in 2.
5. alter optimizer mode to cost.
6. running the query followed by explain plan to see if it has actually used outline hints under rbo
Since the sql will not match as /*+rule*/ is additional literal in sql_text of dba_sql_profiles, is their a way to update this or some other way u can suggest to handle this ?

Basically to avoid restructure of a query can query optimizer be forced to ignore cbo path and use stored profile or outline instead ?

Thx