Session Settings (remember most of these can be called into the OLAP$ALTER_SESSION table if you need to diagnose OLAP API sessions, such as BI Beans, Discoverer for OLAP, Spreadsheet Add-in or any other application that utilizes the Oracle OLAP API, see Diagnose OLAP API Client Sessions with SYS.OLAP$ALTER_SESSION for more information)

For the best possible outcome you should work with Oracle Support. Use these settings at your own risk. Oracle typically does not support using "_" parameters without being instructed to do so by Oracle. This list is incomplete. There are far more diagnostic events that can be set with the assistance of Oracle Support. They are not being listed here because the level of detail is so complex that the typical database practitioner will gain no value in the information.

Build Debugging

Diagnose	Setting
SQL Tracing	alter session set sql_trace true
OLAP Continuous Tracing	alter session set "_olap_continuous_trace_file"=true
OLAP Debug Information to Trace	alter session set "_olap_dbgoutfile_echo_to_eventlog"=true
OLAP POutLog (Aggregation) to Trace	alter session set "_olap_poutlog_echo_to_eventlog"=true
OLAP SQL Import to Trace	alter session set events ''37390 trace name context forever, level 1''
OLAP Update to Trace	alter session set events ''37396 trace name context forever, level 1''

Query Debugging

Diagnose	Setting
SQL Tracing (Binds and Waits)	alter session set events ''10046 trace name context forever, level 12''
CBO Decisions	alter session set events ''10053 trace name context forever, level 1''
OLAP Continuous Tracing	alter session set "_olap_continuous_trace_file"=true
OLAP Table Function to Trace	alter session set "_olap_table_function_statistics"=true

Program Debugging

Diagnose (SQL)	Setting
SQL Tracing	alter session set sql_trace true
OLAP Continuous Tracing	alter session set "_olap_continuous_trace_file"=true
OLAP Debug Information to Trace	alter session set "_olap_dbgoutfile_echo_to_eventlog"=true
Diagnose (OLAP DML Commands)	Setting (if you are running OLAP Worksheet there is no need for the PL/SQL wrapper)
Details when bad line of code	exec dbms_aw.execute('BADLINE=yes');
OLAP Program Execution	exec dbms_aw.execute('PRGTRACE=on');
OLAP Model Execution	exec dbms_aw.execute('MODTRACE=on');
Show Error Messages	exec dbms_aw.execute('ECHOPROMPT=yes');