BR Execution Parameters - Example Usages
This page gives some examples on situations when the
BR Execution Parameters can be used, e.g.
parameters mainly affecting server side SQL statement execution generated by IFS
Business Reporter. The general execution parameters actually also affect
SQL statements generated by IFS Lobby when working with Information Sources.
Note: If the Published for BR Access Only check box is selected, then the report can only be executed via
IFS Business Reporter.
Contents
In this scenario we found that a published report takes a long time
to execute. Possible actions are:
- Open the BR Report Level Execution Parameters
form and populate the form with respect to the report identity that has the
experienced problem. Check the Duration (sec)
field to make sure that the report execution is really as bad as reported.
- Next use the Data Sets tab to find the
data set that consumes most of the execution time.
- Double click on the SQL Statement field
to open a read-only window where the complete statement can be copied from.
- Paste the statement into a tool like e.g.
PL/SQL Developer (or similar) to figure out what execution plan the Oracle optimizer is using.
To find parameters values used, use the
Go to Client Log... link in the form header
to navigate to the client log window where more details can be found.
However this requires that the BR
Execution Parameter LOG_DURING_EXECUTION
to be enabled.
- Try to figure out if any of the available execution parameter related
functionality that can be used to enhance the execution. See General
Tuning Advice.
- Make sure to open the BR Execution Parameters for
Data Set form for the data set to be handled.
- Apply execution parameters, Save and use
the Statement for Next Execution link to
open a read-only window where the SQL statement with respect to current
parameter settings will be presented. This is the statement that will be used in
the
next execution.
- Investigate that statement as described before or run the report again. This
time only the enabled data sets will be executed.
- Test different parameters in the same was as described in previous bullets.
- Also read about general
Tuning Advice.
In this scenario there is a published report that takes a very long time to
execute and the execution has been interrupted be the administrator or by a
backup job. If the report execution has been interrupted, there will not be
statistics available to find the data set or sets that takes most of the
execution time.
- Open the BR Report Level Execution Parameters
form and populate the form with respect to the report identity that has the
experienced problem
- Now use the Execute SQL Statements
check box to disable execution of SQL statements for all data sets in the
report.
- Make sure to enable server logging be enabling the
BR Execution Parameter
LOG_DURING_EXECUTION parameter.
- Run the report in Info Services or IFS
Business Reporter and go back to the report level parameter form to
find out how many data sets that have been executed.
- Use the Data Sets tab to copy some of the
data set statements into e.g. PL/SQL Developer
in order to evaluate the execution plan. By looking at estimated costs and
IO reads in might be possible to find out if a specific statement will take
long time to execute.
It is of course also possible to execute the copied statements one-by-one
and simply interrupt the execution if a statement takes really long time to
execute.
To find parameters values used, use the Go to
Client Log... link in the form header to navigate to the client log
window where more details can be found.
- Another way is to enable one or maybe a few of the available data sets by
using the Execute SQL Statement check box to
make sure that only the selected data sets will be executed. It is necessary to
first make sure that the Execute SQL Statements
check box in the BR Report Level Execution Parameters
form header has been enabled.
- Execute the report and go back to the report level parameter form and find
out how long time it took to execute the enabled data sets.
- If nothing unexpected is found, enable one or a few more data sets and
re-execute the report again. This is done until one or more statements are found
that take long time to execute.
Now these statements can be examined.
- Also read about general
Tuning Advice.
This scenario is related to a IFS Business Reporter designer that wants to test the performance of a newly
developed report before publishing it to Info Services for public use.
- Start by publishing the report for IFS
Business Reporter access only.
This action is handled in
IFS Business Reporter and it means that
the report is not available in Info Services but can be executed from End
User mode in IFS Business Reporter.
After the execution there will be information available in the execution
parameter forms.
- Start investigating number of statements and the time used for data set
execution.
- Try to find the statement or statements that take most of the time (see
previous cases).
- Perform actions like adding/modifying BR Execution
Parameters and then run the report again from IFS
Business Reporter.
It is not necessary that all data sets are enabled
for SQL execution, if the intention is to make sure that it so far works ok with
respect to performance when executed from IFS Business
Reporter. The report output and layout is later issue to address. If not
all data sets in the report has been examined, then continue the analysis as
described previously.
- Also read about general
Tuning Advice.