A Troubleshooting

This appendix contains the following topics:

• Section A.1, "Oracle Business Intelligence Data Warehouse Administration Console Task Fails due to Missing Parameter File"

• Section A.2, "Sorting and Displaying Null Values in Reports"

• Section A.3, "Aborting a Workflow"

A.1 Oracle Business Intelligence Data Warehouse Administration Console Task Fails due to Missing Parameter File

In DAC 10.1.3.4.1 + patch (***) command_infa.xml uses -paramfile as the default option for the parameter file. The DAC tasks will fail if DAC and Informatica servers are on different machines.

To fix the problem, perform the following steps:

1. Navigate to <DAC>\conf folder and edit the file infa_commands.xml.

2. Edit the block START_WORKFLOW_7 or START_WORKFLOW_8 and change the content as follows:

   • For START_WORKFLOW_7 replace the following line:

     pmcmd startworkflow -sv %SERVER -d %DOMAIN -u %USER -p %PASSWORD -f %FOLDER -paramfile %PARAMFILE %WORKFLOW

     with

     pmcmd startworkflow -sv %SERVER -d %DOMAIN -u %USER -p %PASSWORD -f %FOLDER -lpf %PARAMFILE %WORKFLOW

   • For START_WORKFLOW_8 replace the following line:

     pmcmd startworkflow -sv %SERVER -d %DOMAIN -u %USER -p %PASSWORD -f %FOLDER -paramfile %PARAMFILE %WORKFLOW

     with

     pmcmd startworkflow -sv %SERVER -d %DOMAIN -u %USER -p %PASSWORD -f %FOLDER -lpf %PARAMFILE %WORKFLOW

     Note:

     These modifications should be done both on the DAC client and the server machines.

3. After you modify this file, restart the DAC server and client for the changes to take effect.

A.2 Sorting and Displaying Null Values in Reports

In order to understand results shown in OBIEE reports, it may be necessary to understand how null values are sorted and displayed in reports.

Oracle uses NULL as a pseudo-value for a table cell when there is no actual value. For example, if the number of documents awaiting completion for a site is unknown, the column containing that attribute of the site will be set to null in the database.

As null values can appear in among data, OBIEE has rules that determine how to display the null values. And as OBIEE supports sorting of data in a column, it has rules for how nulls should be sorted.

The following are the rules:

• Oracle's sorting order cause a null value to be treated as greater than any non-null value.

• In table views, OBIEE generally displays null values as empty cells.

  The exception is when the request designer has specified that the user can navigate to a different request by clicking on a value in the column that contains null. In that case, in order to give the user something to click on, OBIEE displays the null value as a zero.

These rules can produce unexpected results. This following section describes how to interpret such unexpected results. It also describes actions you can take in creating OBIEE requests to override OBIEE's default rules.

The results of these rules are:

• If the data in a column contain nulls and non-nulls, and the column is sorted, and navigation is not enabled from cells in the column, then:

  • Nulls will display as blank cells

  • Blank cells will sort as larger than the largest non-null value

• If the data in a column contain nulls and non-nulls, and the column is sorted, and navigation is enabled from cells in the column, then:

  • Nulls will display as zeros

  • Cells representing nulls (but now displaying as zeros) will sort as larger than the largest non-null value. If there are actual zeros in the column as well, they will sort as smaller than the smallest positive value in the column. So, if you have both real zero values and null values, and cell-based navigation is enabled, and you sort the column, you will get two clumps of zeros - one representing the nulls, the other representing the actual zeros - separated by the non-negative actual values.

• OBIEE does have a capability that can be used to make it easier to identify null values. In requests, you can use the IFNULL function to specify that NULL should be replaced by a large negative value that could not be a real value for the column. For instance, if "# Documents Outstanding" could be null in your data, and you want to include it in a request, you could change the functional definition of the column in the request from "# DocumentsOutstanding" to IFNULL("# Documents Outstanding", -99). This would cause nulls to sort and display as if their value was -99.

If you use IFNULL, it is important that you:

• Choose a value that could not also be a legitimate value (this may vary from column to column, though it is preferable to use the same IFNULL replacement across all columns).

• Communicate to your end users the meaning of the IFNULL values.

A.3 Aborting a Workflow

A workflow can be aborted by the following two methods:

Method 1

Perform the following steps in DAC to abort a workflow:

1. Navigate to Execute > Execution Plan sub tab.

2. Click the Execution Plan you want to abort.

3. Click Abort.

Method 2

Perform the following steps in Informatica PowerCenter to abort a workflow:

1. Open the Informatica PowerCenter Workflow Monitor.

2. In the Repositories tree, navigate to the particular folder that contains the Informatica job.

3. In the Workflow Run pane, select and right-click the workflow, and click Abort.

See Also:

Informatica PowerCenter Online Help