Art of BI: Modify and Set Variables in Analysis Advanced Tab

On the fly and per Analysis an end-user with Advanced Tab permissions can update variables, logging levels, etc. within the report in an ad-hoc fashion.  The benefit here is that if one is just running quick tests or looking to identify issues, one need not make changes permanent in the RPD, etc. just to run a few quick tests.

In order to modify any user variable or session variable such as loglevel, disable_cache_hit, locale, etc. (must be marked available for updating) a user can just specify the override in the Prefix Section of the Advanced tab.

The syntax would look something like, SET VARIABLE [VariableName] = value.  For example: SET VARIABLE LOGLEVEL=4;

The loglevel override example would set the users session logging level to 4 so when the query runs the next time a log for that query will appear in the nqquery.log file.

[simage=526,400,y,center]

NOTE:

When hierarchical columns are use, they restrict access to may components of an Analysis, however, the Prefix section is still unaffected in the Advanced tab so this functionality is still possible even when Hierarchical columns are used.

[simage=525,400,y,center]

References:

http://download.oracle.com/docs/cd/E14571_01/bi.1111/e10544/analyses.htm#i1016968

http://download.oracle.com/docs/cd/E14571_01/bi.1111/e10544/analyses.htm#CJAJCAHI

Contact Us
Christian Screen
Christian is an innovator in analytics and data warehousing design, best practices, and delivery. With more than fifteenyears of decision support and data warehousing with key experiences at Office Depot HQ, Sierra-Cedar, and Capgemini, he oversees the Oracle Analytics Practice which includes the technical development and delivery of Oracle BI collaboration software, data warehouse solutions, Oracle BI/EPM projects, and packaged analytics solutions at Datavail.

Leave a Reply

Your email address will not be published.
Required fields are marked (*).

1 thought on “Art of BI: Modify and Set Variables in Analysis Advanced Tab”
  1. My favorite is the following:

    set variable LOGLEVEL=2,DISABLE_CACHE_HIT=1;

    Makes it really easy to get at the physical SQL. It's also worth noting that you cannot modify any session variable using this technique if it is marked as "security sensitive."