You should be familiar with these drill-through report guidelines:
Drill-through operations cannot be performed on a Unicode Essbase database.
Drill-through reports may be directed to an alternate Integration Server. Select the alternate server in the OLAP Metaoutline Properties dialog box in Integration Services Console.
Drill-through operations can be performed with Dynamic Time Series.
Drill-through operations can be performed on an alternate data source. An alternate data source is a source other than the primary or secondary data source used to create a metaoutline. The alternate data source must contain the same data structure, including column names and data types, as the primary or secondary data source originally used to create the report. Drill-through operations can be performed on an alternate data source that is in a second language.
Integration Services is not capable of processing drill-through report requests from more than one instance of Essbase running on one server. In order for Integration Services to successfully process requests for drill-through reports from instances of Essbase running on non-standard Agent ports, an essbase.cfg file with the non-standard AGENTPORT setting must be present in eis/server/bin at the time Integration Services is started.
If you create drill-through reports for a metaoutline based on multiple data sources, the SQL used for each drill-through report cannot include a join across a data source boundary; that is, each drill-through report can be based on only one data source. A metaoutline can contain multiple drill-through reports but all must be based on a single data source.
Multi-cell drill-through is supported under the following conditions:
The metaoutline in which you are designing a drill-through report cannot contain alternate recursive hierarchies. For example, you cannot insert the same member from a recursive hierarchy into a dimension more than once.
You cannot use the $$ substitution variable in the template SQL (user-defined SQL) for a drill-through report when the intersection level of the dimension is defined at Generation 1 and the dimension is built from a parent/child table.
Oracle does not recommend using Drill-Through Template SQL for OLAP metaoutlines that support duplicate member names. Integration Server generates special tags internally to uniquely identify the duplicate members.
If you still choose to use Drill-through Template SQL with OLAP metaoutlines that support duplicate member names, refer to the Essbase Integration Services Online Help for guidelines.
Drill-through operations can be performed on an database containing multibyte character sets.
There is a limit to the amount of information that can be stored in the Universal Member Comments (UMC) of an Essbase outline, meaning that users can typically store information for about 40 to 50 drill-through reports only. Because of this limitation, Oracle recommends that users design their drill-through reports so that the total number of reports is kept to under 40.
In the following scenarios, drill-through operations may not work even after using the “Update Drill-through Data” command:
If you created an Essbase application and database using Integration Services, and then modified it using another tool, such as Administration Services.
If you have created an Essbase application and database using another tool, such as Oracle Essbase Administration Services.