Essbase 11.1.2 dimension build slow

Hi All,
I wonder if anyone has had similar problems or ideas of how to solve the problem I have.
We've recently migrated to Essbase 11.1.2 running on some big SPARC 64 bit servers and everything is going well.
We have a problem with dimension builds though. They work, just very slowly taking sometimes over a minute to build a dimension with just 10-20 members in it. With 22 dimensions to build it is taking over 20 minutes to build our dimensions - much more time then loading the gigabytes of data after and this is making the overnight process slower.
The model was migrated from 11.1.1.2 and we converted the outline. The dimension builds on the old server were 4 minutes. The old rules files are still used but as a test I tried creating a new rules file in the same application to load the meta data from a text file instead of an Oracle SQL server but the same problem exists.
We use deferred restructure on an ASO model but the restructure is fine - just the 'BuildDimFile' session runs for over a minute and then starts again for over a minute for the next dim build. Number of members seems to make no difference be it 10 or so to 60,000.
Has anyone got any ideas why or seen similar? Or should I really move out of the dark ages and learn Essbase Studio!
Thanks for your help,
Dan

It seems to be related to the number of dimensions.
I tried creating a basic outline, two dimensions and loaded with a basic rules file. Took 8 seconds in total, no problem.
I then tried copying in one of the existing rules files that builds a dimension with four members. Still no problem.
I then went to the existing outline and deleted all but two dimensions and tried rebuilding with the rules file - it is still quick. I then added the dimensions back, by typing them, all as stored with no members underneath and it suddenly jumps to 40 seconds (of which 30 sec for the dimension build time, 10 sec for the restructure) using the same rules file and data. I'd expect the restructure time to go up, but not the build time.
Possibly unrelated - EAS often produces an error message when loading an outline stating that I have -1536 MB memory free and the outline is 0 MB do I still wish to load?
Dan

Similar Messages

ASO Dimension building slow

Hi all,
We just switched from BSO cubes to ASO cubes and found that building complete dimensions (parent child) takes much longer than building BSO dimensions.
We use the same loadrules as we used for the BSO cubes.
Is this normal?
Is there any way to speed up the dimension building?
Your help is much appreciated!
rgds,
Rudy

Thanks very much guys,
this info will definitely help us come to an optimized approach.
btw, since rebuilding all dimension in BSO wasn't any problem I'll now also spend some thoughts on rebuilding only those dimensions that have actually changed.
No reason to rebuild if nothing has changed, right...<@Cameron,
We went for this approach because we don't want the business users to manually change the outline.
So we created an dimension maintenance GUI on a sql table that can be maintained by the business users. That way we're able to load all dimension from sql.
It has its downside when it comes to e.g. member formulas, but as this more of an administrator task, it's no problem, as we're able to set which dimension should be fully rebuild/resorted.
Now we have one ODI scenario that's able to load to any essbase cube (ASO and BSO), fully parameterized. IT definitely works great!

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?*

Dimension Build in Essbase 9

Hi,
Can we build multiple dimensions using a single rule file and data source file? If we have 10 dimensions to build, then do we really need to build 10 separate rule files and data sources for that?
I've 10 dimensions parent-child tables in relational database. I'm not going to use EIS. Can you suggest me a better way to build the dimensions using sql interface without creating so many rule files and data sources?
Thanks!

Actually, it can be done.
One could certainly make an argument that this may not always be the best way to do things but that's a different matter. I can certainly appreciate that this approach would generally be unwieldy.
In my case, I wanted to reset dimensions to contain nothing but the dimension name before I reloaded the dimension. I could have created multiple dimension load rules and data files/sql tablse that contained a garbage member name and then load each one -- all doable.
However, GlennS2 suggested (hi, Glenn) a single record file and a single parent child rule. I don't remember exactly, but I want to say that there were five dimensions to be rebuilt, so it was a 10 field, one record file. The file had the dimension name, and a garbage member name that could never be in the database. It worked a treat. Dimension build rules with lots of lovely SQL (and different by dimension) followed, so this approach didn't make sense to load the real members into the dimensions.
Regards,
Cameron Lackpour

Urgent: dimension build error.

Hi folks,
While running dimensin build , i have got the below errors.
ERROR - 1007083 - Dimension build failed. Error code [1250029].
ERROR - 1241101 - Unexpected Essbase error 1007083.
Please let me know what could be the reason to create these errors.
I really appreciate your help on the same.
thanks,

Hi,
1. Request to let us know the whats in the log file.
2. Cant be sure about the error , but found a similar error code in other case .
http://businessintelligence.ittoolbox.com/groups/technical-functional/hyperion-bi-l/hyperion-essbase-error-code-1250029-3109331
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

Multiple Dimension Builds using MAXL

We currently use ESSCMND to perform multiple dimension builds and data loads. We have been using the "INCBUILDDIM" in Escmnd to update the outline with multiple files without restructuring until the last file. Is there an equivalent command for MAXL ??

Yes, you can mimic the BEGININCBUILDDIM command from ESSCMD in version 6.5. I've appended a sample script below to show that functionality. Until you upgrade to V6.5 you could shell to Esscmd and do your dim builds there. login 'xxx' 'PASSWORD' on 'LOCALHOST'; spool on to 'd:\ESSBASE\CLIENT\OUTPUT.LOG'; alter system load application 'SAMPTEST'; alter application 'SAMPTEST' load database 'BASIC'; import database 'SAMPTEST'.'BASIC' dimensions from server text data_file 'ACCTBLD1.TXT' using server rules_file 'ACTBLD.RUL', from server text data_file 'ACCTBLD2.TXT' using server rules_file 'ACTBLD.RUL' preserve all data on error append to 'ERR.OUT'; spool off; logout; exit;

Duplicate member names allowed dimension build

I have turned on allow duplicate members in a current ASO essbase cube to test how much rework this will require to allow duplicate aliases. After I switched the property on, I was recieving errors when attempting to associate an attribute to a dimension through a dimension build rule. I realized that I needed to use qualified member names in the load file. Here is an example of the file in Parent Child AttributeValue format
[Domestic-PD].[Test_Comm-PD]     [Test_Comm-PD].[0001-PD]      [Test_Attr-MD].[Test1-MD]
So I want to associate the attribue Test1-MD to product 0001-PD below.
Domestic-PD
     Test_Comm-PD
          0001-PD
What ends up happening is something like this
Domestic-PD
     Test_Comm-PD
          0001-PD( [Test_Attr-MD].[Test1-MD]
          [Test_Comm-PD].[0001-PD]
It attaches the attribute to the correct product but then adds an additional member. I don't want it to add the additional member. Any idea on what is happening?
Thanks for any help!

It ended up working in a different format. I changed the data file to like below. I also started over, recopying the outline, turning duplicate members on, so it is possible that there was just something off with the outline earlier.
Test_Comm-PD     0001-PD      [Test_Attr-MD].[Test1-MD]
It probably will have issues if there is a duplicate member but luckily I only will have duplicate aliases.

Dimension Building Error

Hi
While Dimension Building process in EPM 11 i am getting the below error:
ERROR - 1042012 - Network error [32]: Cannot Send Data.
ERROR - 1010003 - The data block size of database [Drxxxxxx] exceeds the limit [268435455].
ERROR - 1241101 - Unexpected Essbase error 1010003.
kindly suggest for above.

I think the error describes the issue very well, your block size is a monster and you need to tame the beast :)
Cheers
John
http://john-goodwin.blogspot.com/

Error during dimension building

Hi All,
Is there a way to move the members using alias names in outline using a load rule?
I have two dimesnion build process, one to create lev 0 members in a dimension and the other to move these members under proper rollups. The first dimension build process will build the members and it's aliases and in second dimemsion build source file, I have member aliases instead of orginal member names and when I am trying to do dimbuild (trying to move the members using alias names) I am getting error "Error moving member....".
Is there any way to move members in outline using alias names?
Any suggestions will be appreciated. I am using essbase version 7.1.5
Thanks
Maddy

How you are extracting both the dimension files.
if you are getting both from differant tables, you can genearte single file with all required fields by using alias name in the join criteria of the query.
Then you can build the entire dimension in one attempt.

Dimension build rule file (Sort member)

I am loading sorted data for one of the dimension. But its is not coming in sorted fashion in outline. New member which i am adding is always coming in The end.Even though that member is in sorted format in the file.
I am using generation method . I am putting member for only generation 2 and its alias.I tried using ascending option but it is giving me error
Can any body help me with this

As Glenn said, the build only builds new members. In order to have FULL control over the order of a resultant dimension's order, you need to blank out the dimension first and then build via the load rule. As Glenn mentioned, you can do "incremental dimension building". You can do this directly in EAS in an interactive manner by using outline/update outline in pull downs. Just do not save the outline until all your changes are done. You can also accomplish incremental builds via Esscmd or via MaxL, but I'll assume for right now you are still testing. The advantages of the incremental changes is that you can do a number of changes before Essbase commits to doing a restructure, which is time consuming, not to mention confusing if you are "deleting" (however temporary) the entire dimension's hierarchy.
Regarding setting ascending order
1) in the load rule's Dimension Build Settings prompt
2) Select Dimension Build Settings tab
3) highlight the dimension you are changing
4) select Ascending for sort order
This should work...I've never had it error out. However, I will say that it sorts the entire dimension...not just the siblings of a new member. Your upper level members will move as well. Because of this, the ascending sort in a load rule is undesirable. Give it a try. If you don't like the results, just don't save the outline.
Kevin

Incremental Dimension Build

Hi,
We have a BSO cube in Essbase in which we have a custom dimension "Product" which has around 30K members, depending on the requests from the business users we need to rebuild this hierarchy with the changes that come in the new files and they may contain
- New member
- Removed old members
- Members moved across different parents within the same dimension
Till now we have been deleting the whole dimension hierarchy manually and update the outline with the new file but due to this whole data needs to be reloaded, what can be the best possible option that we take in the rule file or any other option so that we don't need to delete the existing hierarchy manually and then reload the whole data.
I want to know if we have something like incremental dimension build which would take care of all the changes and we would be saved from the manual effort that we need to apply.
Any suggestions would be really helpful.
--XAT
Edited by: XAT on Dec 4, 2010 5:20 PM

Well you could test it to assure yourself and you should, but if the members are retained, then the data associated with it will be saved. One note, if you are moving members in hierarchies, then you will need to re-agg the database after the dim build

Problem with dimension build

I am trying to build dimensions for a bso cube using Maxl in version 11. I have both the rules file and the textfile in the server. But I am getting the following error.
import database 'CNFIN1'.'CNGL' dimensions from data_file 'G:\Hyperion\products\Essbase\EssbaseServer\bcpfiles\CNFIN1\CNMarket.txt' using rules_file 'G:\Hyperion\products\Essbase\EssbaseServer\app\CNFIN1\CNGL\GLMktD.rul' on error write to 'G:\Hyperion\products\Essbase\EssbaseServer\log\CNFIN1\CNGL\MktD.err';
OK/INFO - 1053012 - Object [CNGL] is locked by user [US0T4235].
OK/INFO - 1053012 - Object [93547618] is locked by user [US0T4235].
ERROR - 1007083 - Dimension build failed. Error code [1090037]. Check the server log file and the dimension build error file for possible additional info..
OK/INFO - 1053013 - Object [93547618] unlocked by user [US0T4235].
ERROR - 1241101 - Unexpected Essbase error 1007083.
OK/INFO - 1053013 - Object [CNGL] unlocked by user [US0T4235].
Guys can you help me..Thanks in advance

First, have you tested this build manually through EAS? Confirm that you can run the dim build manually to eliminate the load rule as a variable that is causing the problem.
Next, below is a new version of the mxl statement that should work. I altered the syntax to use a server rules_file because the load rule is store in the db directory and you do not need to reference the path or file extension. Also, the backslash is a special character in mxl and needs to be preceded by a backslash. Mxl interprets two backslashes as one.
import database 'CNFIN1'.'CNGL' dimensions from data_file 'G:\\Hyperion\\products\\Essbase\\EssbaseServer\\bcpfiles\\CNFIN1\\CNMarket.txt' using server rules_file 'GLMktD' on error write to 'G:\\Hyperion\\products\\Essbase\\EssbaseServer\\log\\CNFIN1\\CNGL\\MktD.err';
Good Luck!

Cube hang up is happening during Dimension Build process

We are using the Excel VBA tool for the Dimension build process.The tool will build the members in 3 applications(Atlaunch,ModeLife,Textcube).Most of the times cube hung up is happening at the Text cube. The dimension build process is described below
Dimension Build Process :-
The dimension build process is performed by the Calculation and Dimension Build Tool.
Before executing dimension build logging in to essbase server is required through the tool
Once logged in the particular region where dimension build is supposed to be carried out is selected from NML, NA, NE and NS.
Per region there are 3 applications namely <Region>LNCH, <Region>LIFE and <Region>TEXT and per application there is only 1 database namely AtLaunch, ModeLife and TextData respectively. The cube structure per region is given below:
NML Region:
NMLLNCH.AtLaunch
NMLLIFE.ModeLife
NMLTEXT.TextData
NA Region:
NALNCH.AtLaunch
NALIFE.ModeLife
NATEXT.TextData
NE Region:
NELNCH.AtLaunch
NELIFE.ModeLife
NETEXT.TextData
NS Region:
NSLNCH.AtLaunch
NSLIFE.ModeLife
NSTEXT.TextData
The Dimension Build Process is carried out in 2 steps:
1.     Project Master Code Build –
2.     Grades, Line Options, Project Description and Reference Currency Build –
Project Master Code Build:-
In the Project Master Code Build by the Calculation and Dimension Build Tool the following processes are involved
•     Some members are dynamically created in <Region>LNCH.AtLaunch, <Region>LIFE. ModeLife and <Region>TEXT. TextData cubes.
•     Some data is loaded in <Region>LNCH.AtLaunch Cube.
Grades, Line Option, Project Description and Reference Currency Build:-
Grades – Some members are dynamically created in <Region>LNCH.AtLaunch and <Region>LIFE. ModeLife cubes.
Line Options - Some members are dynamically created in <Region>LNCH.AtLaunch
Project Description - Some members are dynamically created in <Region>TEXT.TextData cube. After that some data is loaded in <Region>TEXT.TextData cube.
Reference Currency – UDA is updated in <Region>LNCH.AtLaunch, <Region>LIFE.ModeLife cube and UDA and Alias is updated in <Region>TEXT.TextData cube.
Note: Most of the times during Project Description Build we are experiencing cube hang up / no response for NMLTEXT.TextData, NATEXT.TextData, NETEXT.TextData and NSTEXT.TextData cubes.
Text cube dimension build process flow :-
1. Introduction
The Dimension Build process in CDB system is used for adding new project information in the cubes (AtLaunch, ModelLife and TextData). The text files which are needed for performing dimension build are generated from the child packages and stored in the local system of the user (<LocalDrive>:\GCEP4\Input\CDB_DimensionBuild). The Dimension Build process is carried out in 2 stages:
1.     Project Master Code Build
2.     Grades, Line Option, Project Description and Reference Currency Build
Project Master Code Build:-
In the Project Master Code Build by the Calculation and Dimension Build Tool the following processes are involved
•     MsPr_DIM rule is used for the text file F0P_<Project>-<Milestone>-<Version>.txt to build Project Master Code in AtLaunch, Model Life and Text Data Cubes.
•     MsPr_FLG rule is used to Load some data from the text file F0P_<Project>-<Milestone>-<Version>.txt in AtLaunch Cube.
Grades, Line Option, Project Description and Reference Currency Build:-
Dimension Build w.r.t. Grades and Line Options are carried out in AtLaunch and Model Life cubes which is not in scope of this document. Dimension Build w.r.t. Project Description and Reference Currency change are carried out in Text Data cube, so only those parts are discussed in this document.
2. Project Description Build (Detailed process flow)
The Project Description Build is carried out in the following steps:
•     First, any Lock on the particular PMV is checked. If not locked next operation is carried out.
•     Database availability is checked next (whether any other Dimension build is happening that time or not) and accordingly the availability flag is updated in TextData cube.
•     Next cache is set from high to low to carry out dimension build.
•     After cache setting, one rule file at a time is taken (as given in the cfgDL sheet) and dimension build is performed by using the Rule file and text file (created in local by input packages) on the intended cube.
•     For a particular Rule file “GCM_FDIM” which is used to build CCM information in TextData cube, the following steps are followed by the tool itself:
o     From the TextData cube all the child members under CCM member under Grades dimension are fetched by “GetMbrInfo” function (GetMbrInfo is used around 2000 to 3000 times).
o     The child members under CCM for that particular PMV combination are deleted (if previously build).
•     New child members under CCM are build based on the information provided in the text file F1G_<Project>-<Milestone>-<Version>.txt
•     Once CCM is build rest of the rule files are used to carry the dimension build operation.
•     The Dimension build process is carried out by building dimensions as well as updating some flags (loading data).
•     Reference Currency is updated (if required) at last.
Why this cube hang up is happening?
Thanks in advance

53 questions, all still open. Would you mind marking them as closed as without at least the "question is closed" tag, there's no way for future readers to know if your issues have been resolved or not. I know that I personally use this board for answers quite often and it really helps me when I see that a question has been adequately answered. Points assigned to those who helped you is a nice touch.
Now to your question: did you by any chance change from one Essbase server to another? You didn't state if this build issue happens all the time, or only if you do all three databases, or much of anything in your post as to the actual process of failure, so I'm kind of guessing wildly on this. If true, you might want to look at: http://timtows-hyperion-blog.blogspot.com/2007/12/essbase-api-error-fix-geeky.html
Regards,
Cameron Lackpour
P.S. MMIC, GlennS, and I were just discussing your kind of build-hierarchy-in-Excel approach last week and how infrequently it's seen nowadays. Not a criticism, I personally like these old-school approaches, probably because I've built one or two myself.

Dynamic dimension building

Hi
In our project we are using Essbase11.1.4 version.We have a 8 Dimensions.For one dimension we are loading new members ( some account numbers ) every month through informatica-Essbase connector ( Dynamic dimension building ) with rules.The new members are adding below the existing members.But for smartview reporting purpose client wants one member ( Accounts Total ) to be retained always at last.Can we do this ?Please help.
Version - Essbase 11.1.4
Thanks
Edited by: Palem on Dec 10, 2012 10:29 PM

Can some one help please ?

No valid Dimension Build Fields

Hi, could you guys give me a little help?
I'm running a load rule that execute a select on a view. The load rule has 4 columns, and the outline also has 4 columns.
Col1 - Pointer
Col2 - Pointer
Col3 - Pointer
Col4 - Data Field
I execute the load rule and the same returns the error "No valid Dimension Build Fields" at error file.
What could be happenning for Essbase return that error?
Thanks in advanced.

You mean Field Properties screen?
If yes, I checked each column for their equal at Data Load Properties tab.
And marking "Data field" at Data Load Properties tab for the column that have all the variables.
I don't know if it make any difference, I copied this load rule from another application. Both applications have the same outline. The only difference is that the select commands are in other tables.
App1
Rul1 -> select on table1
App2
Rul(the one I'm having problem) -> select on table2
Another detail, I'm running the load rule with "Update outline" at "Outline" menu in the "File bar".
Edited by: Rodpg on Dec 1, 2008 2:16 PM
Edited by: Rodpg on Dec 1, 2008 2:32 PM

Essbase 11.1.2 dimension build slow

Similar Messages

Maybe you are looking for