Essbase studio deploy cube failed

Hi,
I'm try to deploy my first cube in essbase studio
once I deploy the cube, I get the follwing error:
The error file is located on the server at: H:\Oracle_EPM\Middleware\EPMSystem11R1\products\Essbase\EssbaseStudio\Server\.\ess_japihome\data\MStudio.basic_02-13-13_17-21-18.err
Cannot join following sets of tables:
1. [connection : \'ME'::'MLNX.GL_DATA', connection : \'ME'::'MLNX.LOCATION', connection : \ME::'MLNX.DEPARTMENT', connection : \'ME'::'MLNX.INTERCOMPANY', connection : \'ME'::'MLNX.ACCOUNT', connection : \'ME'::'MLNX.COMPANY', connection : \'ME'::'MLNX.PRODUCT', connection : \'Mellanox_txt'::'Scenario_M.TXT']
2. [connection : \'Mellanox_txt'::'Version.txt']
\\Record #8 - Illegal Smartlist Text: -408.33 (3385)
-408.33
\\Record #9 - Illegal Smartlist Text: -1044.39 (3385)
-1044.39
\\Record #15 - Illegal Smartlist Text: -1987.96 (3385)
-1987.96
\\Record #18 - Illegal Smartlist Text: -1275.04 (3385)
however, I see on EAS the app with outline,
without data .
Thanks a lot
Messi

Are you trying to join to two text file data sources, if so I thought only self-joins were supported. Glenn will probably be able to confirm.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

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 Error(1021001): Failed to Establish Connection With SQL Data

Hi.
I have trying to deploy a cube with Essbase Studio but I get the error: "*Error(1021001): Failed to Establish Connection With SQL Database Server*"
My environment is Linux 5, Oracle 11g and EPM 11.1.1.2. Oracle database and Essbase was installed with diferent users. In the .bash_profile of hypadmin user (that install Essbase) I have set the following variables
ORACLE_BASE=/u01/app/oracledb/product/11.1.0
ORACLE_HOME=$ORACLE_BASE/db_1
LD_LIBRARY_PATH=/usr/X11R6/lib:$ORACLE_HOME/lib:$LD_LIBRARY_PATH
ORACLE_HOSTNAME=devbi.sigfe2
PATH=$ORACLE_HOME/bin:$ORACLE_HOME/jdk/bin:$ORACLE_HOME/bin:/sbin:$ORACLE_HOME/opmn/bin:$PATH
ORACLE_SID=orcl
JAVA_HOME=/u01/app/installfiles/jdk1.5.0_19
In my pc (windows xp) I can open Essbase Studio console, do the connection to Oracle database, get tables and create minischema, mesures and hierarchies (I can see the preview of hierarchies). Also I can create cubes with EAS and can connect with MAXSHELL to essbase.
When I try to deploy the cube from Essbaes Studio y get the error "Error(1021001): Failed to Establish Connection With SQL Database Server".
The Essbase Studio Log File say:
+12:40:16 07/24/09 (admin-1) INFO Start creating outline in database "5.4.0.41:1423.POC_ESS.POC_ESS1"...+
+12:40:16 07/24/09 (admin-1) FINA Sign on Essbase by CSS token "5.4.0.41:1423" successfully...+
+12:40:16 07/24/09 (admin-1) INFO Start building dimension "DM_CIUDADES" ...+
+12:40:16 07/24/09 (admin-1) MÁS FINA Start creating rule file ...+
+12:40:16 07/24/09 (admin-1) INFO SQL statement has been created and put into rule file "/home/hypadmin/hyperion/products/Essbase/EssbaseStudio/Server/./ess_japihome/data/DM_CIU.rul"+
+12:40:16 07/24/09 (admin-1) INFO The query is "SELECT (CONCAT('reg_',CAST(cp_105."ID_REGIONPADRE" AS VARCHAR2(1000)))) as "REGION_PADRE", (CONCAT('reg_',CAST(cp_105."ID_REGION" AS VARCHAR2(1000)))) as "REGION_HIJO", cp_105."DE_REGION" as "REGION_HIJO.Default" FROM "POC"."DM_REGIONES_ESS3" cp_105 ORDER BY cp_105."DE_NIVEL" ASC, cp_105."ID_REGIONPADRE" ASC, cp_105."ID_REGION" ASC"+
+12:40:16 07/24/09 (admin-1) INFO Rule file has been created and saved as "/home/hypadmin/hyperion/products/Essbase/EssbaseStudio/Server/./ess_japihome/data/DM_CIU.rul"+
+12:40:16 07/24/09 (admin-1) FINA Essbase starts to add members to DM_CIUDADES dimensioin based on the rules file.+
+12:40:16 07/24/09 (admin-1) ADVERTENCIA (1021001): Error al establecer conexión con el servidor de bases de datos SQL. Consulte el registro para obtener más información.+
+12:40:16 07/24/09 (admin-1) ADVERTENCIA essbaseDriver.FailedToBuildDimensionException+
+12:40:16 07/24/09 (admin-1) GRAVE Unexpected exception in EssbaseExport prevented cube from being deployed+
-------------- Exception --------------
com.hyperion.cp.datasources.export.essbase.EssbaseDriverException: Failed to deploy Essbase cube
Thanks in advance to all that have any idea to help me to solve this issue.
A.S.

Hi,
If you type database SID in lowercase, try to reenter iot in uppercase. Strange, but I and my colleagues encounter this behaviour many times.

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 deployment errors

I am getting the following error message when I try to deploy a BSO cube:
\\Record #40 - Error adding Dynamic calc property to member xxxxxxxxx (3320)
\\Record #40 - No time dimension defined
I have a TIME dimension which is assigned to TIME property in essbase model properties. I do have a 'X' in the source column of the above member xxxxxxxxxx. And xxxxxxx is a ACCOUNT dimension member. Both ACCOUNT and TIME dimensions have been assigned with DENSE dimension property.
Please help me on how to proceed.
Essbase Studio version : 11.1.2.1.00

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 - Create Cube Schema without a Measure or Measures Hierarchy

Using Essbase Studio V 11.1.2.1 I'm trying to create a cube schema. The wizard needs a measures or measures hierarchy in order to proceed. My cube doesn't have a dimension that falls under this category. All dimensions are under the Hierarchies. Is there a way to skip adding anything in the Measures/Measures Hierarchies in order to continue building the cube schema/Model? Any work around?

Hi GlennS, I that I need atleast one measure and thats the dollar amount field from the fact table. So I have done that now...
I'm trying to recreate a cube using Essbase Studio. I'm using EIS from an older essbase version as a template.
While doing a member load In EIS, in the olapisvr.log file, I could see the individual select statements for every dimension/member load. Something like "Member load SQL statement (for dimension CURRENCY_CD) has been generated, start adding member to outline". I cannot locate where I specified this sql or how EIS generates this. The sql is very specific so looks like the EIS generated sql for Member load is being overridden.
Once I figure that out, I need to replicate that in Essbase Studio. Any ideas?

Essbase Studio - Failed to Establish Connection With SQL Database Server

Hi all,
I am new to Hyperion and am having trouble deploying what seems a simple cube in Essbase Studio.
My environment is Windows 2003, EPM 11.1.1.2, SQL Server 2000.
I have the following two issues which may be related.
1. The EPM System Diagnostic tool says that Hyperion Foundation cannot connect to the SQL database.
Error:
Failed: Connection to database
Error: java.net.UnknownHostException: <server name: <server name>
Recommended Action:
Every other EPM application is able to connect to the database. I have tried re-configuring Foundation Services and checking the config files and nothing looks wrong. I would appreciate advice on how to fix this.
2 In Essbase Studio, I was able to connect to the database where the source data is, build the minischema and create dimensions and measures. But when I run the cube deployment wizard I get the error:
Message: Failed to deploy Essbase cube
Caused By: Failed to build Essbase cube dimension: (Time)
Caused By: Cannot incremental build. Essbase Error(1021001): Failed to Establish Connection With SQL Database Server. See log for more information
…ODBC Layer Error: [08001] ==> [[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.]
I have checked the DSN as well as the connections set up within Studio, and they are all able to connect to the database. I am using the admin user for the Essbase server and have created a different user for the databases where the data resides and the shared services database. I tried using the same user all the way through and this didn’t help.
Can you please advise what else I can check or change to resolve this issue.
Also, can you work in EAS with cubes that are created in Studio? I tried looking at it and I got an error that the rule file couldn’t be accessed because it was created in Studio.
After the above failures, I tried creating a cube in EIS, with mixed success. I have been able to load the members and data without errors. But when I try to view the data in the cube, I am seeing field names for the measures instead of the data itself.
...Definitely more questions than answers at this stage of my learning.
Regards
Michelle

Michelle,
I don't know if you found an answer to you question after so many months but I was hoping I could be helpful.
The issue you are experience happens often when the dimension that you are getting an error on, in this case TIME, is built from a snowflake lineage and there is a bad foreign key reference. This dimension is most like high-up in your outline build process for Essbase Studio and this prevents the build from happening usually early on.
Check your logs also. They are in Hyperion > Products > logs > essbase > essbasestudio.
You can also make your logs more verbose by setting a configuration variable in the essbase studio server.properties file but that should only be used for debugging as it really saps performance.
And, yes, you can of course edit an Essbase Studio deployed cube in EAS. However, any changes you make to the cube in EAS are subject to being wiped-out upon the next Essbase Studio deployment of that Applicaion/Database combo.
If you want to provide more detail, screenshots, etc. I would be glad to help where I can.
Cheers,
Christian
http://www.artofbi.com

Essbase Studio: Failed to deploy Essbase cube

Hi
I have started working with Essbase studio sometime back and I am able to deploy BSO cube with success using the TBCSample Database which comes along with Essbase. Now I wanted to deploy ASO cube, as no sample database is available I thought to create one, I extracted ASOSamp using ODI to CSV files. Then I bulk inserted the csv extracts into MSSQL 2003 server which created 11 tables (Age, Geography, IncomeLevel, Measures, PaymentType, Product, Stores, Time TransactionType, Year). The above mentioned table does not have any keys(Primary, Foreign) as it is an Essbase export.
I then successful created ASO Cube Schema using the newly created sample database in MSSQL, validated cube schema without any errors.
Essbase Property Setting:
Measures Hierarchy is tagged as Dynamic Compression at dimension level
Time, Product and Year Hierarchy is tagged as Multiple Hierarchies Enabled, Year does not have multiple hierarchies but it has formulas for Variance and Variance % member. Is there a way to tag Year as Dynamic hierarchy?
But when I try to deploy the cube to Essbase I receive following errors:
Failed to deploy Essbase cube
Caused By: Cannot end incremental build. Essbase Error(1060053): Outline has errors
\\Record #1 - Member name (Time) already used
+ S Time + S
\\Record #6 - Member name (1st Half) already used
MTD + S 1st Half + S
\\Record #7 - Member name (2nd Half) already used
MTD + S 2nd Half + S
\\Record #21 - Member name (Qtr1) already used
Qtr1 + S Feb + S
\\Record #22 - Member name (Qtr1) already used
Qtr1 + S Jan + S
\\Record #23 - Member name (Qtr1) already used
Qtr1 + S Mar + S
\\Record #24 - Member name (Qtr2) already used
Qtr2 + S Apr + S
\\Record #25 - Member name (Qtr2) already used
Qtr2 + S Jun + S
\\Record #26 - Member name (Qtr2) already used
Qtr2 + S May + S
\\Record #27 - Member name (Qtr3) already used
Qtr3 + S Aug + S
\\Record #28 - Member name (Qtr3) already used
Qtr3 + S Jul + S
\\Record #29 - Member name (Qtr3) already used
Qtr3 + S Sep + S
\\Record #30 - Member name (Qtr4) already used
Qtr4 + S Dec + S
\\Record #31 - Member name (Qtr4) already used
Qtr4 + S Nov + S
\\Record #32 - Member name (Qtr4) already used
Qtr4 + S Oct + S
\\Record #33 - Member name (Time) already used
Time + S MTD + S
\\Record #34 - Member name (Time) already used
Time ~ S QTD ~ S
\\Record #35 - Member name (Time) already used
Time ~ S YTD ~ S
\\Record #9 - Error adding Attribute to member QTD(Jan) (3320)
\\Record #9 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD + S QTD(Jan) + S [Jan]
\\Record #10 - Error adding Attribute to member QTD(Apr) (3320)
\\Record #10 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Apr) ~ S [Apr]
\\Record #11 - Error adding Attribute to member QTD(Aug) (3320)
\\Record #11 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Aug) ~ S [Jul]+[Aug]
\\Record #12 - Error adding Attribute to member QTD(Dec) (3320)
\\Record #12 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Dec) ~ S [Oct]+[Nov]+[Dec]
\\Record #13 - Error adding Attribute to member QTD(Feb) (3320)
\\Record #13 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Feb) ~ S [Jan]+[Feb]
\\Record #14 - Error adding Attribute to member QTD(Jul) (3320)
\\Record #14 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Jul) ~ S [Jul]
\\Record #15 - Error adding Attribute to member QTD(Jun) (3320)
\\Record #15 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Jun) ~ S [Apr]+[May]+[Jun]
\\Record #16 - Error adding Attribute to member QTD(Mar) (3320)
\\Record #16 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Mar) ~ S [Jan]+[Feb]+[Mar]
\\Record #17 - Error adding Attribute to member QTD(May) (3320)
\\Record #17 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(May) ~ S [Apr]+[May]
\\Record #18 - Error adding Attribute to member QTD(Nov) (3320)
\\Record #18 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Nov) ~ S [Oct]+[Nov]
\\Record #19 - Error adding Attribute to member QTD(Oct) (3320)
\\Record #19 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Oct) ~ S [Oct]
\\Record #20 - Error adding Attribute to member QTD(Sep) (3320)
\\Record #20 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Sep) ~ S [Jul]+[Aug]+[Sep]
\\Record #36 - Error adding Attribute to member YTD(Jan) (3320)
\\Record #36 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD + S YTD(Jan) + S [Jan]
\\Record #37 - Error adding Attribute to member YTD(Apr) (3320)
\\Record #37 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Apr) ~ S [Qtr1]+[Apr]
\\Record #38 - Error adding Attribute to member YTD(Aug) (3320)
\\Record #38 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Aug) ~ S [1st Half]+[Jul]+[Aug]
\\Record #39 - Error adding Attribute to member YTD(Dec) (3320)
\\Record #39 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Dec) ~ S [1st Half]+[Qtr3]+[Qtr4]
\\Record #40 - Error adding Attribute to member YTD(Feb) (3320)
\\Record #40 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Feb) ~ S [Jan]+[Feb]
\\Record #41 - Error adding Attribute to member YTD(Jul) (3320)
\\Record #41 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Jul) ~ S [1st Half]+[Jul]
\\Record #42 - Error adding Attribute to member YTD(Jun) (3320)
\\Record #42 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Jun) ~ S [1st Half]
\\Record #43 - Error adding Attribute to member YTD(Mar) (3320)
\\Record #43 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Mar) ~ S [Qtr1]
\\Record #44 - Error adding Attribute to member YTD(May) (3320)
\\Record #44 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(May) ~ S [Qtr1]+[Apr]+[May]
\\Record #45 - Error adding Attribute to member YTD(Nov) (3320)
\\Record #45 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Nov) ~ S [1st Half]+[Qtr3]+[Oct]+[Nov]
\\Record #46 - Error adding Attribute to member YTD(Oct) (3320)
\\Record #46 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Oct) ~ S [1st Half]+[Qtr3]+[Oct]
\\Record #47 - Error adding Attribute to member YTD(Sep) (3320)
\\Record #47 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Sep) ~ S [1st Half]+[Qtr3]
\\Record #2 - Incorrect Dimension [Year] For Member [ParentName] (3308)
ParentName Consolidation DataStorage MemberName Consolidation DataStorage Formula
\\Record #1 - Member name (Promotions) already used
S Promotions S
\\Record #2 - Incorrect Dimension [Promotions] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #3 - Member name (Promotions) already used
Promotions S Coupon S
\\Record #4 - Member name (Promotions) already used
Promotions S Newspaper Ad S
\\Record #5 - Member name (Promotions) already used
Promotions S No Promotion S
\\Record #6 - Member name (Promotions) already used
Promotions S Temporary Price Reduction S
\\Record #7 - Member name (Promotions) already used
Promotions S Year End Sale S
\\Record #2 - Incorrect Dimension [Payment Type] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #2 - Incorrect Dimension [Transation Type] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #22 - Member name (Home Entertainment) already used
Home Entertainment + S Home Audio/Video + S
\\Record #23 - Member name (Home Entertainment) already used
Home Entertainment + S Televisions + S
\\Record #24 - Member name (Other) already used
Other + S Computers and Peripherals + S
\\Record #25 - Incorrect Dimension [Product] For Member [ParentName] (3308)
ParentName Consolidation DataStorage MemberName Consolidation DataStorage
\\Record #26 - Member name (Personal Electronics) already used
Personal Electronics + S Digital Cameras/Camcorders + S
\\Record #27 - Member name (Personal Electronics) already used
Personal Electronics + S Handhelds/PDAs + S
\\Record #28 - Member name (Personal Electronics) already used
Personal Electronics + S Portable Audio + S
\\Record #31 - Member name (All Merchandise) already used
Products + S All Merchandise + S
\\Record #32 - Member name (High End Merchandise) already used
Products ~ S High End Merchandise ~ S
\\Record #33 - Member name (Systems) already used
Systems + S Desktops + S
\\Record #34 - Member name (Systems) already used
Systems + S Notebooks + S
\\Record #18 - Error adding Attribute to member Digital Recorders (3320)
Home Audio/Video + S Digital Recorders + S
\\Record #36 - Error adding Attribute to member Flat Panel (3320)
Televisions + S Flat Panel + S
\\Record #37 - Error adding Attribute to member HDTV (3320)
Televisions + S HDTV + S
\\Record #8 - Incorrect Dimension [Income Level] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #1 - Member name (Geography) already used
S Geography S
\\Record #2 - Error adding member 27425 (3317)
\\Record #2 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
A M F GREENSBORO - NC S 27425 S 336
\\Record #3 - Error adding member 36310 (3317)
\\Record #3 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBEVILLE - AL S 36310 S 334
\\Record #4 - Error adding member 29620 (3317)
\\Record #4 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBEVILLE - SC S 29620 S 864
\\Record #5 - Error adding member 67510 (3317)
\\Record #5 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBYVILLE - KS S 67510 S 316
\\Record #6 - Error adding member 58001 (3317)
\\Record #6 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERCROMBIE - ND S 58001 S 701
\\Record #7 - Error adding member 42201 (3317)
\\Record #7 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - KY S 42201 S 502
\\Record #8 - Error adding member 21001 (3317)
\\Record #8 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - MD S 21001 S 410
\\Record #9 - Error adding member 39730 (3317)
\\Record #9 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - MS S 39730 S 601
\\Record #10 - Error adding member 28315 (3317)
\\Record #10 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - NC S 28315 S 910
\\Record #11 - Error adding member 79311 (3317)
\\Record #11 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERNATHY - TX S 79311 S 806
\\Record #12 - Error adding member 79601 (3317)
\\Record #12 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABILENE - TX S 79601 S 915
\\Record #13 - Error adding member 79608 (3317)
\\Record #13 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABILENE - TX S 79608 S 915
\\Record #14 - Error adding member 79698 (3317)
\\Record #14 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
Are these errors due to data source, if yes what could be possible work around?
Is there any problem with Essbase properties which I have set if so then when I validate cube schema why I dn't get any errors?
Please help me, I am stuck here not able to deploy ASO Cube.
Thanks in advance

Hii
I have the same problem , you have.
did you manage to solve it ??
Thanks in advance

Error in deploying the cubes in Essbase Studio

I am getting below error when I try to depoly ASO cubes in Essbase Studio.
***Failed to deploy Essbase cube***
***Caused By: Error when retrieving data from SQL source***
***Caused By: Error when retrieving data from SQL source***
***Caused By: [Hyperion][DB2 JDBC Driver]SQLDIAGGRP was specified and not null.***
I also checked the error log generated in the applications asking to increase the NETDELAY and NETRETRY COUNTS in ESSBASE.CFG, the config file. I made those changes, restarted the services and deployed again but in vain.

There have been a number of MaxL bugs with encryption that produce 'Parse error near...' messages. If you login to Oracle Support and search the Knowledge Base on 'Parse error near' you will find them. I can't see anything specifically relating to 11.1.2.1 or a known defect in the release notes... ...I'd get a support ticket raised, if you haven't already.
You don't mention platform, but I've also run into a bug running 'deploy' in 11.1.2.1 on a 64-bit Windows environment and there was a Unix bug too, but they both caused crashes so probably aren't your problem.

Essbase Studio Cube Deployment SQL Connection Error

Hello,
Has anyone seen this error in studio.
Failed to deploy Essbase cube
Caused By: Failed to build Essbase cube dimension: (Accounts)
Caused By: Cannot incremental build. Essbase Error(1021001): Failed to Establish Connection With SQL Database Server. See log for more information
I connected to the SQL database without issue creating the data source and I can view the sample data on the dimension element. The only time I have a connection issue is during cube deployment. The log is no help.
Thanks

Hi Celvin
Thanks for your reply.
I can connect from the same Essbase Server from the data source connection used in the Essbase Studio console.
I am not using any encrypted passwords.
I can log into MaxL with no issues, but running trying to execute the following command is where I get the error.
deploy all from model 'GL_Analysis' in cube schema '\ANALYSIS\Schema\Schema' with option delete_members login $1 identified by $2 on host 'server1' to application 'test1' database 'test1' overwrite values using connection 'essbaseserver' keep 200 errors on error ignore dataload write to default;
It allows me to connect and deploy sucessfully using the Maxl installed from the Essbase client version 11.1.2.2. However running the MaxL installed from the Essbase client MaxL version 11.1.2.3 seems to provide me with the connection issue. I am trying to determine if it is a bug or something that was missed during upgrade process.
Currently we need to deploy via the Studio.
Thanks.

Essbase Studio Cube Deployment Error

Hi,
I am trying to deploy a cube using essbase studio 11.1.1.3.00. I am getting this error.
\\Record #1203 - Unable to write smartlist 801990, error code 1060301
Any ideas what the issue is? I can't find anything on the error and I don't have any idea what smartlist would have to do with the deployment.
Thanks in advance

Hi,
I assume that the Essbase studio version is 11.1.2 and above.
The error is caused by the Essbase Studio Server failing to establish a connection with the SQL Database Server and you can try the following:
1) Back up the server.properties file and alter it in the following manner:
Change the server.essbase.streamingCubeBuilding=true to server.essbase.streamingCubeBuilding=false (use Essbase drivers)
2) Set the ODBCINST variable to point directly to odbcinst.ini
3) Then, the BPMS service should be restarted.
The file is named:
startBPMS_bpms1_Server.bat on Windows;
startBPMS_bpms1_Server.sh on UNIX.
Note:
The Essbase Studio Server startup file contains the commands necessary to start Essbase Studio Server. During the configuration process , the EPM System Configurator writes information to the startup file about the computer on which Essbase Studio is installed so that Essbase Studio Server can start properly. Oracle recommends that you do not manually edit the startup file.
The start up file is installed by default in:
MIDDLEWARE_HOME/user_projects/epmsystem1BPMS/bpms1/bin
KosuruS

Deploying Cube from Essbase Studio

Hi,
I am fresher and I am a student and I am trying to study Oracle Hyperion Essbase Studio. I have a problem when I am trying to Build outline and load data from Essbase studio ->Cube Deployment option.
Failed to deploy Essbase cube.
Caused by: Cannot end incremental build. Essbase Error(1007072): Member [keyboard] tagged as <REFER does not have a member to refer to
\\Record #1 - (3345) Error setting ID (#~@12#0#196#0@#~@3#0#562#0@#~karnataka) to member (karnataka)
karnataka karnataka banglore banglore 457787 457787
\\Record #2 - (3345) Error setting ID (#~@12#0#196#0@#~@3#0#562#0@#~Maharashtra) to member (Maharashtra)
Maharashtra Maharashtra Pune Pune 411043 411043
\\Record #4 - (3345) Error setting ID (#~@12#0#196#0@#~@3#0#562#0@#~Maharashtra) to member (Maharashtra)
Maharashtra Maharashtra Pune Pune
\\Record #5 - (3345) Error setting ID (#~@12#0#196#0@#~@3#0#562#0@#~maharashtra) to member (maharashtra)
maharashtra maharashtra pune pune
\\Record #6 - (3345) Error setting ID (#~@12#0#196#0@#~@3#0#562#0@#~Maharashtra) to member (Maharashtra)
Maharashtra Maharashtra pune pune 441205 441205
\\Record #7 - (3345) Error setting ID (#~@12#0#196#0@#~@3#0#545#0@#~Gujrat) to member (Gujrat)
Gujrat Gujrat 123456 123456
\\Record #8 - (3345) Error setting ID (#~@12#0#196#0@#~@3#0#562#0@#~maharashtra) to member (maharashtra)
maharashtra maharashtra mumbai mumbai 433653 433653
Edited by: 980685 on Jan 8, 2013 11:30 PM
Edited by: 980685 on Jan 8, 2013 11:31 PM

Hi All,
Towards this error if we are talking about Hyperion Essbase - Version 11.1.2.1.000 and later.
So mostly we are facing this issue has been verified as unpublished Bug 12967639.
As documented in KM:
Unable to Save ASO Outline After Renaming Members, "Error(1007072) Member [xxx] tagged as <REFER does not have a member to refer to" [ID 1465850.1]
Also towards ASO there is another document having all there as:
Oracle Hyperion Essbase and Aggregate Storage (ASO) [ID 1291202.1]
Thanks,
Shaker

Cube Deployment Essbase Studio maxl

Hi,
I created an Essbase Cube with Essbase Studio. Everything works fine.
Now I want to schedule the cube deployment (build the outline and load data). I tried to use the maxl deploy statement like it is explained it the Essbase Technical Reference.
I used the following statement to delete the database and to build the outline:
deploy outline from model MyModelName with option delete_database login admin identified by password on host localhost;
But all I got is this error messages: "BPM error: Parse error near ;"
The syntax of my statement should be the same as in the documentation... but I think there missing some points like application name and database name?!?
Thanks for any advice!

Hi,
I also had issues with this. The documentation isnt' what it should be for this command. The follownig example should work:
deploy outline from model 'TbcStudioModel' with option incremental_load update all preserve no data login 'admin' identified by 'password' on host 'epmv11112' to application 'TcbStudi' database 'Studio' using connection 'epmv11112';
Gee

MaxL script deploy essbase studio cube

Hi There,
I am testing my MaxL script deploying cube from essbase studio, here is result from my cmd windows:
BPM connect status: success
BPM maxL deployment ... succeeded with warning.
How do I find out the detail about the warning? I assume it is essbase studio log at C:\Hyperion\logs\esbstudio
But I did not see any warning message.
Thanks

Thanks John and Glenn, I just check my app log, the warning I found is:
Warning(1013254)
Hybrid Analysis spanning cannot be enabled on database [test] in application [test]. Check if the database has Hybrid Analysis and if span into relational source is enabled.
I am not sure I understand this.

Unable to load data into Essbase cube using Essbase Studio

Hi
We are creating an essbase cube using Essbase Studio using flat files as data sources.
We have taken different hierarchies into different flat files and created one fact file having dimension intersection along with data.
We are able to create the cube and the hierarchy but not able to load any data.
We are getting the following error
Failed to deploy Essbase cube.
Caused by: Unable to perform dataload from more than one flat file.
Could anyone please help on this?

Oh this was killing me, so I did this test in 11.1.1.3:
1) Excel 2007 format -- no go, Essbase didn't see it
2) Excel 2003 format, three sheets -- only the first sheet was read into an empty rule
3) Excel 2003 format, one sheet -- the first sheet was read into an empty rule
4) Excel 95 format, one sheet -- the first sheet was read into an empty rule
The lesson?
1) Excel 2007/2010 sheets don't work (no surprise there as the .xlsx format isn't supported).
2) Excel 2003 and lower (hey, if you have Excel 4, I'll bet that works as well) work, but only the first sheet is recognized.
Regards,
Cameron Lackpour

Essbase studio deploy cube failed

Similar Messages

Maybe you are looking for