Tag Archives: obiee bug

Values In OBIEE 10g Multiselect Prompt Are Not Sorting in Alpha-Numeric Order In Large LOVs

Symptoms
When running an Oracle Business Intelligence Enterprise Edition (OBIEE) Dashboard with multi-select prompts that contain many values, the values in the list are not consistently alpha-numerically sorted.

The initial retrieval in the multi-select dialog box shows the values alpha-numerically sorted.  When the next set of values are retrieved, the values lose their sort order and are no longer alpha-numerically sorted.
Cause
This issue is described in the following known bugs:

Bug 8995183 – SORTING IN MULTISELECT PROMPT NOT WORKING AS EXPECTED
Bug 9787610, MULTISELECT PROMPT NOT SORTING PROPERLY WHEN CONTAINS MORE THAN 256 ITEMS
Solution
This issue is fixed in OBIEE 10.1.3.4.2.
If you are encountering this issue, you are urged to upgrade to version 10.1.3.4.2 to obtain the fix
for this bug and many other bugs.
For information on upgrading to this version, please see Note 1357872.1 How To Upgrade to
Oracle Business Intelligence Enterprise Edition (OBIEE) 10.1.3.4.2

If you are currently unable to upgrade to OBIEE 10.1.3.4.2, and require the fix in OBIEE 10.1.3.4.1, please do the following:
1.    Open a Service Request (SR) with Oracle Support and request the password for
Patch 9787610.

2.    Follow instructions for installing the patch as described in patch readme.txt file.
Oracle Support recommends that you first test this patch on a development or test server.
Once you are satisfied that the patch corrects the issue, you may promote the patch to
your production environment.

NOTE: If you are using any web server other than IIS, you will need to recreate and redeploy the
Analytics.war file after installing the patch.

For detailed instructions on how to do this in an OC4J environment, please see:

Note 1075754.1 Create and Deploy A New BIEE 10.1.3.4/10.1.3.4.1 ANALYTICS.WAR File.

References
BUG:8995183 – SORTING IN MULTISELECT PROMPT NOT WORKING AS EXPECTED
BUG:9787610 – MULTISELECT PROMPT NOT SORTING PROPERLY WHEN CONTAINS MORE THAN 256 ITEMS
NOTE:1075754.1 – How To Create And Deploy A New OBIEE 10.1.3.4.X ‘analytics.war’ File (for OC4J)
PATCH:9787610 – MULTISELECT PROMPT NOT SORTING PROPERLY WHEN CONTAINS MORE THAN 256 ITEMS

Applies to:
Business Intelligence Suite Enterprise Edition – Version: 10.1.3.4.1 [1900] to 10.1.3.4.1 [1900] – Release: to 10g
Business Intelligence Server Enterprise Edition – Version: 10.1.3.4.1 [1900] to 10.1.3.4.1 [1900]   [Release: 10g to 10g]
Business Intelligence Answers Option – Version: 10.1.3.4.1 [1900] to 10.1.3.4.1 [1900]   [Release: 10g to 10g]
Information in this document applies to any platform.
This knowledge document is a replacement for 952833.1 which has been deleted.

Parameter For Max Number Of Rows Not Taken Into Account

This is probably helpful for someone who migrated from OBIEE 10G to 11G and need to retain the same settings. I’m still wondering who needs to see reports with 500k rows, but still.

In OBIEE 10g the ResultRowLimit was working with a value of 5,000,000 (65,000 is the default value).

We have tried to do the same in 11g through EM > BI > Core application > Capacity Management >

Performance > Maximal number of rows in a tabular view set from 65,000 to 5,000,000.

The Servers have been restarted and the report is still not running.

The SQL query fetches less than 200,000 rows. i.e. one of our reports is 172,310 rows.

Impact on Business:
This problem impacts a lot of reports through the National Healthcare agency.
These reports used to work in 10g.

View Display Error

Exceeded configured maximum number of allowed input records.
Error Details
Error Codes: EKMT3FK5:OI2DL65P
Location: saw.httpserver.processrequest, saw.rpc.server.responder, saw.rpc.server,

saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool, saw.threadpool, saw.threads
SQL Issued: 858~k1vsg0egoo7i60qhn13qv8lj52

Moreover, the same matter occurs in a report with 49220 lines fetched from Database.

Could it be linked to the fact that these reports use a pivot table to perform a second aggregation phase?

The final Pivot view is about 10 columns by 10 lines.
Cause
The Number of Rows setting was verified within OBIEE 11.1.1.5.

Capacity Management > Performance

Maximum Number of Rows Processed when Rendering a Table View

This setting limits how much data is retrieved from the BI Server and processed. The default value is 65000.

Reducing the maximum number of rows processed can significantly improve performance by reducing the system resources that can be consumed by a given user session.

Number of Rows 65000

It was found that the cause was the Pivot Table (which generally have more performance overheads when compared to a standard Table).
Solution
Within the instanceconfig.xml file in 10g you would have had to adjust the limits in your file for the parameters below.



In OBIEE 11g, these values below are discussed in the following Guides.

Oracle Fusion Middleware System Administrator’s Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1) E10541-02

18.3.1 Manually Configuring for Data in Views

If changes are made to the instanceconfig.xml file please carefully refer to the section stated below:
(Section 3.4, “Using a Text Editor to Update Configuration Settings.”)

When the following changes were made to the instanceconfig.xml file, this fixed the issue.





1000000
5000000



Oracle suggests that “These values were specific to this environment and the reports being run by that organisation. Other readers should note that increasing these values to too high a level may have an impact on performance (which is hardware dependent).”

Few recent Knowledge-based updates

I’ve found the following items to be very interesting as I’m very much interested in running OBIEE in a cloud.
Question someone asked on OS:
Q:How to cluster OBIEE that is installed on two virtual machines?
And their response was:
A:It is not currently possible to use Virtual machine names for OBIEE within a Cluster. The following Enhancement Request exists:
BUG#7576055
VIRTUAL MACHINE NAME FOR CLUSTERED OBI SERVER

This one is interesting, because it’s not just applicable to headers, but to some other elements that may contain HTML:
Q:Is it possible to add HTML code into a Column Header in OBIEE?

A:In order to render HTML in OBIEE (i.e. Answers, Dashboards, etc) please ensure you have set the following parameter “HardenXSS” to FALSE in the instanceconfig.xml file.

Example:


[ServerInstance]
[HardenXSS]false[/HardenXSS]
[/ServerInstance]

Last one is related to using external methods to get in to OBIEE.

Goal
1) Customer has a JSP and java application running on web sphere application server which uses OAM for single-sign-on.
2) In the same JSP application they have embeded a report which gets the data from OBIEE webservices. The actual report is deployed on OBIEE presentation server and uses OAM for authentication. When the user logs in to java application and clicks on the page which invokes a report from OBIEE customer doesn’t want to prompt for authentication again.
3) Customer does not see any OBIEE login webservices which takes as input parameter the authentication token or cookie generated in JSP application.
A:
There is currently no mechanism within the OBI Web Services to use Single Sign-on (SSO).

There are some methods that may assist further with customer requirement (i.e. impersonate() Method and impersonateex() Method). These methods should allow the users to logon and impersonate another user when customer only have the Administrators Login and Password.

However, these methods are not SSO as customer would still need to provide a username and password for the SOAP client (i.e. Administrator/Administrator) from within their J2EE application.

In order to overcome the fact the OBI Web Services does not use SSO, customer may want to install a new Presentation Server. The dedicated Presentation Server can then have the SSO disabled and can be used solely for the WEB Services application and nothing else.

I wonder what are security implications of such arrangement.

Have a good day!

Oracle Business Intelligence is not supported on this Windows version

When trying to install Oracle Business Intelligence Suite Enterprise Edition, v. 10.1.3.4.0 for Microsoft Windows in Windows XP and getting the following error message.

“Oracle Business Intelligence is not supported on this Windows version. Oracle Business Intelligence is only supported on Windows XP x86, Windows 2003 x86, Windows 2003 AMD64, Windows 2003 EM64T, Windows Vista x86, Windows Vista AMD64, Windows Vista EM64T, and Windows 2000 x86.”

Installer uses systeminfo.exe command to get information on the architecture of the machine. If this command will cause any error, then there is a need to check and fix that error first.

Run the following command and see if any errors. In our case we had the following error.

The command systeminfo.exe is run from command line.

***
C:>\windows\system32\systeminfo.exe

Error:-

Back with error for Network Card
Information???????..Error:Provider Load failures.

***********

Since installer use the same command to get information on the architecture of the machine. In this case because of the above error installer was not able to drive the machine detail and as a result installation failed.

The errors from the above command systeminfo.exe (if any) needs to be fixed first.  In our case after we fixed the Network Card issue, installation went fine.

Several new bugs

Happy New Year! It’s been a busy time, however, I’m back with some new posts. I wish the readers the best of the best of the best :-) I wish that your repository always stays consistent, that your physical layer is a true star, and your users never have problems with BI Answers.  I’ve digged up a few things that might be interesting:

Issue 1

Duplicate records are being eliminated from the Answers request results, when the desired results would be to include all rows, including duplicates.

The duplicate rows can have both the same case or different case.  Setting the case sensitivity parameter has no impact.

Example:

One row may be:
Dinner

Another row may be:
dinner or Dinner

The second row is not included in the Answers results.  Running the same SQL directly on the server does return all rows, including duplicates.  Analytic server is removing the duplicates.

Cause

Analytic Server issues the distinct clause.

Solution

Include the table key column in the request.  Hide the column so it is not actually seen in the request results.  This will make each row unique and thus each row, including what would be considered duplicate, is included in the results.

=======

Item 2

How to configure External Db Authentication that supports OBIS Impersonation (i.e. Delivers, BI Publisher)

Solution

To implement external DB authentication (i.e., authentication via a user/pw record in a database), you should NOT use AUTHENTICATION_TYPE = DATABASE. Instead, define it exactly like the Siebel Integrated setup in SiebelAnalytics.rpd’s/EnterpriseBusinessAnalytics.rpd’s Authentication init block. That is:
Use the default NQS Authentication type in NQSConfig.ini by commenting out all authentication types.
Define a separate physical database in the rpd which has a connection pool configured to hit the external database used which has the defined OBI users.
Enable Shared logon for this connection pool; set User name to :USER and Password to :PASSWORD.
Only the connection pool configuration is required for this physical database – no table/column objects are required.
Define an Authentication Session initialization block to set the session system security variable ‘USER’ to be used for OBIS External DB Authentication.
Point the initialization block to the connection pool defined in step 2.
Use an initialization string like “Select ‘:USER’ from external_table WHERE USERID=':USER’.
Define the ‘Edit Data Target’ to use system security variable ‘USER’ – this will make this initialization block the defacto OBIS authentication init block.
Define all connection pools used for backend data access to use ‘Shared logon’ with an explicit database user/password with at least read access to all backend tables.
This configuration supports OBIS Impersonation (i.e. Delivers). Database Authentication will be done via the connection pool defined in the Authentication init block. The user / password entered in an OBIPS client browser session will be passed to OBIS via the :USER / :PASSWORD system session variables. These values will then be passed to the database for user validation – if a database session is established using this user/password combo, the user will be considered authenticated to OBI.

Also, it does not require all OBI users to be defined in the rpd. In fact, remove all the OBI users from the rpd that will be authenticated via a database user entry. If you require OBIS Group Security assignments for users, you should use a separate external table (either existing or new) that stores the user-to-OBIS group associations, and make the associations via a session initialization block. Again, similar to the SiebelAnalytics.rpd’s/EnterpriseBusinessAnalytics.rpd’s Autherization initialization block.