Oracle Business Intelligence supports session variables that are populated from multiple data sources.
These multi-source session variables can be used in logical queries or in repository data filters, and contain the union of values from the different data sources.
There is no restriction on the number of values that the multi-source session variable can hold. To create a multi-source session variable, you first create row-wise initialization blocks for each source.
Then, you explicitly define session variables for each source. The format for the session variable names must be:
<ms_variable_name>
____<source>
where the separator must be exactly four underscore characters.
This automatically creates a single multi-source session variable, named:
<ms_variable_name>
The component session variable names (<ms_variable_name>____<source>) appear separately in the Variable Manager in the Administration Tool, but the Expression Builder displays only the single multi-source session variable name (<ms_variable_name>).
Note:
While the main focus of this section is on the definition and usage of multi-source session variables, you may also select the VALUEOF the component session variables in logical queries and data filters.
If any of the row-wise initialization blocks returns null results, this is logged in the Oracle BI Server log, nqserver.log
. Values can still be added to the multi-source session variable from other component initialization blocks that succeed in returning values. The multi-source session variable will fail only if all of the component initialization blocks return null values.
You can set execution precedence and deferred execution with multi-source session variables, similar to regular session variables.
Use these examples to learn how to create a multi-source session variable.
The following example illustrates how to create and use a multi-source session variable:
In the Variable Manager in the Administration Tool, select Action > New > Session > Initialization Block.
Create a row-wise initialization block called mvcountry_sebl_init
with the following SQL for Default initialization string:
select distinct 'MVCOUNTRY____SEBL', country from siebel_table
Create a second row-wise initialization block called mvcountry_orcl_init
with the following SQL for Default initialization string:
select distinct 'MVCOUNTRY____ORCL', country from oracle_table
Still in the Variable Manager, select Action > New > Session > Variable.
Create a session variable called MVCOUNTRY____SEBL, making sure to include four underscores between the variable name and the source name. For Initialization Block, select mvcountry_sebl_init
.
Create a second session variable called MVCOUNTRY____ORCL, making sure to include four underscores between the variable name and the source name. For Initialization Block, select mvcountry_orcl_init
.
While the component session variables appear in the Variable Manager, the MVCOUNTRY multi-source session variable that has been created appears in Expression Builder.
Using the Multi-Source Session Variable in a Logical Query
You can now use the MVCOUNTRY multi-source session variable in a logical query.
For example:
select lastName, firstName, country from employee where country=VALUEOF(NQ_SESSION.MVCOUNTRY)
Using the Multi-Source Session Variable in a Data Filter
Perform the following steps to use the MVCOUNTRY multi-source session variable in a data filter:
Tthe Expression Builder, as shown in the image that follows, displays only the MVCOUNTRY multi-source session variable, and not the regular session variables that were used during the creation of the multi-source session variable.