Essbase Studio drill thru report error

Hi All,
Essbase studio drill thru report is producing the below error: Unable to retrieve drill thru result.
Error in the select statement. Line = 2466.
Error in query execution. Please review the query and try again.
Cannot execute a SQL query
ORA-01791: not a SELECTed expression
Any idea... i am able to test for some of the dimensions but this error is coming for a few dimensiosns .... i verified all the joins between dimensions and facts.. everything is fine.
Thanks,
Praveen

Hi Glenn,
This is a test report executed with in Studio console. Yes, i did verify the generated sql by studio server and was able to drill down to the detail. I dont find any information in the logs when testing this. Probably, i would need to increase logging level. Will do that and update here if i dont find much help there.
Thanks,
Praveen

Similar Messages

Essbase studio drill thru report Test error

Hi All,
Essbase studio drill thru report is producing the below error: Unable to retrieve drill thru result.
Error in the select statement. Line = 2466.
Error in query execution. Please review the query and try again.
Cannot execute a SQL query
ORA-01791: not a SELECTed expression
Any idea... i am able to test for some of the dimensions but this error is coming for a few dimensiosns .... i verified all the joins between dimensions and facts.. everything is fine.
Thanks,
Praveen

Hi Glenn,
This is a test report executed with in Studio console. Yes, i did verify the generated sql by studio server and was able to drill down to the detail. I dont find any information in the logs when testing this. Probably, i would need to increase logging level. Will do that and update here if i dont find much help there.
Thanks,
Praveen

Essbase Studio Drill-Through Report

Is it possible to run an Essbase Studio drill-through report in a SmartView spreadsheet that is connected to a cube that was not deployed by Essbase Studio? If so, how do you associate the drill-through report with the cube?

You have to trick Studio into thinking the cube was built from Studio. In my session on Advanced Studio Tips and Tricks at the KScope conference at the end of June I detail a couple of ways to do this. It is too detailed to put into a post here

Essbase Studio Drill-thru security

I applied a filter in Essbase so a user had filtered access. In Smartview I retrieve data and properly gett the NoAccess message, so far so good. If I do a drill-thru. It drills to the data in my report. I would think IT should prevent drill-thru from occuring. Am I doing something wrong? I don't think it should work this way.

Hi Glenn,
This is a test report executed with in Studio console. Yes, i did verify the generated sql by studio server and was able to drill down to the detail. I dont find any information in the logs when testing this. Probably, i would need to increase logging level. Will do that and update here if i dont find much help there.
Thanks,
Praveen

Excel is not showing multiple Drill thru report selection option

We have created 3 drill thru reports in EIS, excel is not showing Select Drill-Through Report Dialog Box when tying to acess drill thru reports. It defaultly executes the first drill thru report, we want it to list the available reports so that we can select accordingly after view/launch is selected.
essbase 7.1.6 version SQl server 2000

Hi,
This Prompt message would have been set in WAD(XHTML Coding section) in your old project. Now , you cross check your Web template for the same. Your issue will be resolved.
Regards,
Suman

Filters for Drill thru reports

Can we make the filter available for all users in a drill thru report?
Thanks
Kannan.

Maaguiar,We have Analyzer 6.1.1 installed within WebSphere Unix running AIX 4.3.3 We have been told by Hyperion support that this is a bug. No confirmation has been made yet as to whether this will be fixed in version 6.2 which has a RMF date of late October

Essbase Studio Drill-through for Recursive Hierarchy - Generation 1

I'm using Essbase Studio 11.1.2.3 to build an ASO cube. All my hierarchies are recursive (parent-child). I would like to define a drill-through report and I understand that I have to use the Advanced Settings option to specify my intersections. Now one of my dimensions is optional for the users - they don't have to specify a member (they can leave it at the highest level - dimension name on the spreadsheet). Under 'Advanced Settings' for DT report in Studio I have to specify a Generation value of 2 or greater than 2. How do I enable drill through in cells where one of the dimension is at Gen1 ? Specifying the level number didn't work. I think if you specify Level in 'Advanced Settings', drill through is allowed only if that specified level of the dimension is chosen, if Gen 2 is specified, then drill through is allowed as long as the dimension-members specified are at or above Gen2. But what about Gen1?

Yep, this is a limitation. I suggest you create two reports one that takes your "optional" dimension out and a second one that has it in. if they don't need the dimension, select the first report and if they need the filter then the second. I m always a little leery with recursive hierarchies and Gen 2 or 3 sine they create a list of level 0 members under the selection in the query and there are limits to the number of members in an in clause and at high levels in the hierarchy it is easy to surpass it (In Oracle it is 1000 members)

Essbase Studio Deployment Dimension Build Errors

I have a ASO cube used to handle Subsidiary financial reporting to parent. Rather than alternate hierarchies, we use attribute dimensions for yearly differentiation. The ASO cube typically holds information for Current year + 3 prior years. This is the first year that we will achieve this as this cube was created near the beginning of 2010. Therefore, with the cube already having attribute dimension for 2010 & 2011, with the beginning of 2013 it is necessary to create the 2012 attribute dimensions. The cube has 13 anchor dimensions. Typically only 4 of these dimensions have attribute dimensions derived from them. Nonetheless, the following is the build list of the dimensions in the essbase model:
1: Financials Standard, Dynamic, Sparse
2: GL Date Time, Stored, Sparse
3: Incident Date Standard, Stored, Sparse
4: View Standard, Dynamic, Dense
5: Company Standard, Multiple-hierarchy, Sparce
6: Well location Standard, Stored, Sparse
7: Depletion Code Standard, Stored, Sparse
8: Vendor Standard, Stored, Sparse
9: Entity Standard, Stored, Sparse
10: Profit Center Standard, Stored, Sparse
11: Curr Yr Cost Obj Standard, Stored, Sparse
12: Past Yr Cost Obj Standard, Stored, Sparse
13: Measures Accounts, Dynamic, Existing
Attribute dimensions are mainly created in 4 of the Defined Hierarchies with in the cube; 1:FINANCIALS, 5:COMPANY, 6:WELL Location, & 10:PROFIT CENTER.
According to the Essbase Server log, upon deployment, the FINANCIALS Hierarchy generates 19 Dimension Build rule files with the associated SQL to pull members from our SQL Dimension Build tables obviously based on the way the Hierarchy is built as well as the joins created in the MiniSchema in the referenced Data Source. The COMPANY Hierarchy generates 5 Dimension Build rule files, WELL LOCATION generates only 1 Dimension Build rule file (this is mainly due to the fact that all the attributes generated from WELL LOCATION are built from the same table), and PROFIT CENTER Generates 3 Dimension build rule files. At this point for comparison purposes I want to include excerpts from the Server Deployment Log file depicting the dimension build rule files generated from the PROFIT CENTER Hierarchy:
Rule 1 Labeled XXXX_PRO.rul
… FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center] cp_319 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 ON (cp_319.[profit_center_code]=cp_328.[profit_center_code]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 2 Labeled XXXX_PR1.rul
… FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2010] cp_275 ON (cp_275.[profit_center_code]=cp_328.[profit_center_code_2010]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 3 Labeled XXXX_PR2.rul
FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2011] cp_276 ON (cp_276.[profit_center_code]=cp_328.[profit_center_code_2011]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
These Dimension Build rule files are recreated nightly on 4 different production servers, each one successfully redeploying nightly with zero errors.
So now I need to add the new 2012 tables to the Data Source/MiniSchema, create the joins in the MiniSchema mimicking the joins for the 2010 & 2011 Attribute Dimensions. It would be difficult to demonstrate the joins in the MiniSchema but trust me they are there and this is proven by the additional Dimension Build rule files from the appropriate Hierarchies.
So on our test server, which is configured exactly like all 4 of our production servers, I have begun the creation of the 2012 attribute dimensions. I begin with the FINANCIALS Hierarchy adding 7 new attribute dimensions, 6 that are cross table and one that is inter-table.
At this point no changes have been made to any of the other 3 Hierarchies that contain Attribute dimensions; COMPANY, WELL LOCATION, or PROFIT CENTER. They still look exactly as they did in the current state discussed above. Upon deployment, the FINANCIALS Hierarchy generates , as expected 25 Dimension Build rule files, 6 additional because only 6 were cross table attributes, the 7th was within the anchor table and therefore would be included in the first dimension build rule file. COMPANY still generates 5 Dimension Build rule files, again as expected. WELL LOCATION still generates only the 1 Dimension rule file also as expected. Lastly, PROFIT CENTER also again only generates the 3 Dimension Rule files, however, one has materially changed as noted below:
Rule 1 Labeled XXXX_PRO.rul
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center] cp_319 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 ON ((cp_319.[profit_center_code]=cp_328.[profit_center_code]) AND (cp_328.[profit_center_code]=cp_319.[profit_center_code])) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 2 Labeled XXXX_PR1.rul (This one did not change)
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2010] cp_275 ON (cp_275.[profit_center_code]=cp_328.[profit_center_code_2010]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 3 Labeled XXXX_PR2.rul (This one did not change)
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2011] cp_276 ON (cp_328.[profit_center_code_2011]=cp_276.[profit_center_code]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
The change in Rule 1 above appears to now require something different from the previous deployment and when we run the deployment now it runs forever and ultimately fails, yet no changes have been made to the Hierarchy, no changes have been made to the MiniSchema involving joins to the tables used in the building of the Hierarchy, and no new tables have been added to the data source that would affect this Hierarchy.
Additionally, I have also run each of these incrementally, and the PROFIT CENTER even incrementally still makes the change to the SQL statement shown above.
So finally, to my question, Why and What caused this Dimension Build Rule file to change and ultimately led to deployment failure? Has anyone ever encountered this in Essbase Studio Deployments?

Gurus, anybody anything on this one??
I haave done a small adjustment in the dimension order by which I have eliminated the following error:
Record #40 - Error adding Dynamic calc property to member xxxxxxxxx (3320)
Record #40 - No time dimension defined
But, I have the following new error/warning (cube build successfull in this case) when I made this adjustment:
Record #427 - Error adding Attribute to member PATB4_ADJ-PDA (3320)
The adjustment I made is... I moved TIME dimension up and ACCOUNT dimension below that...so the order I have now is TIME,ACCOUNT,SCENATRIO,XXX,XXXX instead of ACCOUNT,TIME,SCENARIO,XXX,XXXXX ..*would this create any performance issues?*

Essbase Studio & Drill-through

Hello All,
Can I still create a drill-through report in Essbase Studio & update a previously built [by EPMA] Essbase cube? Please consider this urgent...
Thanks,
Cheryl

Cheryl,
One of the draw backs right now of using EPMA to load Essbase cubes is that any changes that are made to your Essbase cube in EAS, etc. post a EPMA Essbase Cube deployment will be overwritten and vice-versa. EPMA is best for working with HFM and Planning right now and is not best suited for Essbase deployment right now even though it can handle simple Essbase cube deployment. If you cannot do what you need with EPMA alone then you will need to deploy using Essbase Studio, EIS, or EAS.
However, other options would be to utilize partitioning or something similar to get the drill-through capability from another "Reporting" cube. That would be the immediate solution I believe.
http://www.artofbi.com
Edited by: Christian Screen on Nov 17, 2009 9:10 AM
Edited by: Christian Screen on Nov 25, 2009 12:30 PM

EPMA Essbase Studio Drill-through

If I deploy a Planning application via EPMA is it possible to configure drill-through from Planning via Essbase Studio?
Thanks,
Jz

The drill-through path from Planning is from a web-form to FDM.
Can this hack drill through from a Planning web-form or would I need to created reports in Planning to drill-through?
The Studio documentation only talks about Reports...
Thanks,
Jz

Essbase Studio Alternate Hierarchy Creation error

Hi All,
I'm using Essbase Studio to create an alternate hierarchy. I have a dim which has shared members and I'm getting the following error msg during cube deployment:
1. Record #1- Member Name (SKU) already used i.e. the member for which I m trying to create shared member
     I m following the same procedure mentioned in the user guide i.e.
        Step1: create a copy of the dimension element that you want to designate as a shared member(Renamed SKU_copy with SKU_Diet). By making a copy, the binding expression for this element is the same as the original dimension element (SKU_Diet).
       Step2: when you create the second hierarchy in the chain, which is the alternate hierarchy, add a user-defined membas the parent and add the new dimension element (SKU_Diet) as the child, which will be the shared member.
     Even I m able to see the shared members (SKU_Diet) under user defined member "Diet" under the preview window (both by key binding and caption binding) as wel..
     But I m unable to see the shared members in EAS console after deploying the cube from Essbase Studio to EAS Console.
I m not able to understand what I m missing exactly,.and suggest me other ways as well for creating alternate hierarchies in Essbase Studio.
Thanks in advance..!!

looks like similar issue..
https://forums.oracle.com/thread/1555956
It will work in genaration 2 not in genration 1.
Thanks,
mady

*****EIS : Drill through Report Error while excel data retre

Dear All,
could you please help me in the below error . When i tried to get the drill through reports in excel add-in ,
i am getting the below error . When i had look into EIS log, its generating dynamic query for this drill through reports .
[NCR][ODBC Teradata][Teradata Database] Syntax error- expected something between the word '<<Databasename>>' and the word 'ai'.Unable to get catalog string.
Thanks in advance .
M

You are saying the dynamic query was generated, did you copy the query and tried to execute it in the database client. Check the SQl for any errors and also in the did you see any SQL errors?

Need Help with Essbase Studio TBC cube deployment errors

Hello Everyone,
I am trying my hands on Essbase studio. I am using TBC example which comes with Essbase Studio installation. I am getting the following errors.
How can I troubleshoot these errors. Since it comes with Essbase studio I supposed the data to be clean.
In the essbase studio i defined the TIME dimension, but it stills give me that error.
Please click the Details button for more information
The error file is located on the server at: C:\temp\TBC.TBC_08-04-10_15-54-09.err
Failed to deploy Essbase cube Caused by: Cannot end incremental build. Analytic Server Error(1007151): Wrong incremental dimension build sequence
\\Record #3 - Error adding Label Only Attribute to member Inventory (3320)
\\Record #3 - No time dimension defined
\\Record #3 - Shared member cannot have a formula
Measures ~ O Inventory ~ O
\\Record #14 - Error adding Label Only Attribute to member Ratios (3320)
\\Record #14 - Shared member cannot have a formula
Measures ~ O Ratios ~ O
\\Outline verification errors:
\\When a single child member {Measures} is Dynamic Calc or Dynamic Calc and Store, the parent must also be Dynamic Calc or Dynamic Calc and Store

Hi,
Were you able to resolve that error with TBC db?
I am running in to the exact same error...
thanks

Essbase Studio - SmartView - Drill Through Error

Hello!
I'm creating a drill through report using Essbase Studio 11.1.1.2. Built the Context, the Report Content and Associations. Perform an ad-hoc analysis via SmartView. Perform a Hyperion | Drill Through Reports and the follow error occurs:
Unable to list Essbase Studio Drill Through Reports : Error in the statement interpret. Line = 1109
Anyone know what causes this and how to resolve it?
Thanks,
Bob

The issue was due to using transformations to prefix characters to ids. The drill through couldn't resolve the cube member name to the data in the tables.
For example, if your source data for your accounts table has an member id of 1, 2, 3 etc. But you use a prefix of A in transformation to build the member in Essbase (A1, A2, A3, etc.), drill through can't resolve it. Drill through is going back to the table and searching for A1, A2 or A3. The table has 1, 2, or 3. A string is not a number, that's the error that basically occurs.
Solution - I updated my tables to have the prefixes (and data types) and removed the transformations. That way when drilling, the Essbase member matches up with the table id.
Thanks,
Bob

Issue with Oracle Essbase Studio

Everytime I startup Essbase Studio Console, it report error retrieving children for root. How to solve it.
[http://photos.bravenet.com/389/104/449/4/6359232B64.jpg]

increasing the memory have a read of section "Configuring Virtual Memory" - http://download.oracle.com/docs/cd/E17236_01/epm.1112/est_user.pdf
Cheers
John
http://john-goodwin.blogspot.com/

Essbase Studio drill thru report error

Similar Messages

Maybe you are looking for