Financial reporting rpd using obiee

Hi,
      Building RPD and Financial Reporting  by using multidimensional  essbase datasource in obiee

http://www.slideshare.net/alooa2/financial-reporting-rpd-using-obiee-7968605


Thanks and Regards,

Deva

Migrating Application Roles from Dev to UAT server and Production server.

Hi,

Reference:

To move Application Roles, please kindly review the following information:
Oracle Fusion Middleware Application Security Guide 11g Release 1 (11.1.1)
7.3.2 Migrating Policies with the Command migrateSecurityStorehttp://download.oracle.com/docs/cd/E14571_01/core.1111/e10043/cfgauthr.htm#JISEC2929


Thanks and Regards,

Deva

ODBC SQL Server Driver]Optional feature not implemented in RPD - Phesical layer feature

I came across an interesting error recently. I had a very simple data model with 1 fact table and 1 dimension, both coming from a SQL Server 2008 database. When querying the model through Answers I would get ODBC driver errors like the ones below.

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000]
[nQSError: 10058] A general error has occurred.
[nQSError: 43113] Message returned from OBIS.
[nQSError: 43119] Query Failed:
[nQSError: 16001] ODBC error state: 37000 code: 8180 message: [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared..
[nQSError: 16001] ODBC error state: 37000 code: 145 message: [Microsoft][ODBC SQL Server Driver][SQL Server]ORDER BY items must appear in the select list if SELECT DISTINCT is specified..
[nQSError: 16002] Cannot obtain number of columns for the query result. (HY000)

Below thing in addred in Physical layer feature then also it's not working:

Untick the checkbox for EXPRESSIONS_IN_ORDERBY_SUPPORTED in the features tab of the database properties in the physical layer.


However I did notice that from your error that you are using [Microsoft][ODBC SQL Server Driver] and not "[Microsoft][SQL Server Native Client 10.0]" as given by the Doc 1308545.1

Thanks and Regards,
Deva

nQSError: 60008

Hi,
    I came across an interesting error recently, as a admin (weblogic user)  able to see the o/p without any error dashboard page, if any one user/group loging that time they are getting attached screen short error message.

FYI,

SR 3-3888346391: Odbc driver returned an error (SQLExecDirectW) on obiee11g Dashboard page

Solution Statement:

In your OBIEE11g  --> RPD file---> Manage--> Identity -->Users/Application role --> increase the each user/group wise that maximum number of rows the user or group is allowed to retrieve from a database. then it will work.

Reference:

At the rpd level, you can Manage Query Execution Privileges to limit queries by number of rows received by a user or group with
the max rows parameter. It determines the number of rows that can be returned from the database. If the number of rows exceeds this limit, an ODBC error occurs.
From the Administration Tool menu bar, choose Manage > Security.
•In the Security Manager dialog box, in the tree pane, select Users or Groups.
•In the right pane, right-click the name that you want to change and select Properties.
•In the User or Group dialog box, click the Permissions tab.
•In the User/Group Permissions dialog box, click the Query Limits tab and expand the dialog box to view all columns.
•To specify or change the maximum number of rows each query can retrieve from a database, in the Query Limits tab, perform the following steps:
•In the Max Rows column, type the maximum number of rows.
•In the Status Max Rows field, select a status.
•Click OK twice to return to the Security Manager dialog box.
If a query exceeds the limit set by the Administrator, the end user will get the message:
[nQSError: 60008] The query for user 'user1'
exceeded the maximum query governing rows n from the database x
Status  Description 
Disable  When selected, disables any limits set in the Max Rows or Max Time fields 
Enable  This limits the number of rows or time to the value specified. If the number of rows exceeds the Max Rows value, the query is terminated. 
Ignore  Limits will be inherited from the parent group. If there is no row limit to inherit, no limit is enforced 

 

Thanks and Regards,

Deva