Dynamic Dimension Building Problem

Hi I am trying to build dimensions dynamicaly, I am getting a warning stating " your outline has generated warnings indicating possible erroneous calculations...."The member is defined as a Dynamic Calc member and has more than 100 children"My question is there any limit for the no. of children to any dynamic calc members. Is there any way to increase that number.Thanks

And somewhere along the way, Hyperion changed the way this was handled.. At one point, this would cause a data load to be considered partially successful by Essbase. Then Essbase was changed so that this error was ignored by the dimbuild process. I don't remember the version.. probably somewhere around version 6.0 or 6.1..?

Similar Messages

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 ?

Dimension Build Problems

Even the simplest dimension build rules files are not working for me. For example, I set up a test cube and tried to load 2 lines to a product dimension and it would not work. Is it possible that something is enabled/disabled that would cause this? I am at a loss, as the dimbuild.err file is not working either so I cant got there for guidance.

HI Dan,
1. When you say not working , what error do you get and when you start your build process( you need to set the file location for the .err file).
2. Can you give more details like the data file and your current outline,along with build information too.
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

Dimension Build problem - Child Memeber with no Parent???

Seems so obvious but I can't see what I'm missing...
LEVEL0,Product!ALIAS0,Product!LEVEL1,Product!ALIAS1,Product!LEVEL2,Product!ALIAS2,Product!LEVEL3,Product!ALIAS3,Product!LEVEL4,Product!ALIAS4,Product
*05HC!!NONE!!Product!!!!!*
Generates the following error...
*\\Record #2 - Child Member with no parent (3331)*
*05HC!!NONE!!Product!!!!!*
What am I missing?

SR wrote:
You can extract in XML format using Maxl.you can Use other outline extraction tools.
Check here
http://www.appliedolap.com/free-tools/outline-extractor
That is currently the utility I'm using, I was hoping there was a way to extract using MAXL??
are you using dimension load option? (by default data load) - yes
did you selected products dimension while setting " use level reference"? - yes
Did you selected "remove unspecified" in dimension build setting? If yes, "None" parent record exist before child record in source file? - "remove unspecified", does this remove items in the dimension not specific to the load?

Dynamic Dimension Build - Quotes

I have an ASCII data file that has some of the member names enclosed in double quotes. The file is imported twice: First, to dynamically add new members (using ?Add as Child of?) and a second time to load the data.Both imports use the same load rule file.The dimension load fails because of the quotes. The data load works fine.Is this a bug?Harold

Consider the below things when you are building dimensions.
Cannot build Generation 1(dimension name)
Secondary fields (member properties) must immediately follow primary field
To share members generation and level methods require a “dupgen” or “duplevel” column.
Parent /Child shares automatically
Generation method can’t share members at different generations
Level method can share members at different generations
Parent/Child method is easiest to share and easiest to change granularity

Dynamic Dimension Build...which is suitable..

Hi, Experts
i am new to implementation..I collected the members in the each dimension from the source team and next job is to build the hierarchy with all the members available in the flat files...
Just before starting, willing to know,which technique will be flexible to build...(ge,parent,lev refererence)?
Regards,
Vishnu.M

Consider the below things when you are building dimensions.
Cannot build Generation 1(dimension name)
Secondary fields (member properties) must immediately follow primary field
To share members generation and level methods require a “dupgen” or “duplevel” column.
Parent /Child shares automatically
Generation method can’t share members at different generations
Level method can share members at different generations
Parent/Child method is easiest to share and easiest to change granularity

Essbase 11.1.2.1 - Dimension build problem, OCI and SQL...

When retrieving SQL data in Data Prep editor, field names are replaced with SQL View field names.
From what I can find this was supposed to be fixed in the patch for 11.1.2, can anyone confirm or deny that...
Is this only a problem with OCI and ODBC connections?
Any help would be appreciated.
Adam,

We are experiencing all of the defects:
Defects Fixed in this Patch
· 13398150 – When you use the Migration Wizard in Administration Services to migrate an Essbase application, an incorrect error message is returned: "Failed to migrate the application. Please see message panel for details." However, the application is migrated. Refresh the Essbase server application node to see the migrated application.
· 13398160 – Selecting the OK/Retrieve button to populate data from SQL causes previously defined column headers to be changed.
· 13398169 - Joining two or more data fields in Data Prep Editor, when one or more of the fields is empty, causes Administration Server to terminate abnormally.
I think the patch would work if it weren't for the limited processors supported... were running Intel Zeons. How do we get ORACLE to compile patches for them... ???
Supported Platforms
· Microsoft Windows (32-bit) (console)
· Microsoft Windows x64 (64-bit) (server)
· Linux AMD (64-bit) (server)
Edited by: Adam M on May 18, 2012 2:52 PM

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!

Dynamic dimention building failed

Hi essbase experts,
I am trying to build dimension using rules file.
My outline is -
Product
A
B
C
D
SALE
Price
STOCK
Quantity
YEAR
2007
jan2007
feb2007
mar2007
I created a rules file . in the field "product" I unchecked the option" ignore field during dimension build", "ignore field during data load" .
by this rules file i am able to load the data. but i am not able to build dimension .
in the rules file the fields are - product , year , quantity , price
is there any thing I am missing out ?
the data which i am trying to load is -
"A" , "Jan2007", 375,0
note - the same rules file is able to load data but when i try to build dimension
it gives the error
"dimension build failed"
Can you guys tell me what am I actually missing ????

Kyle,
I have the same problem. All of this functionality worked before (at least about 130 days ago), but there have been at least two updates to Pr since that time.
Here are a few more data points. (Win 7 x64 Ultimate on HP Z820 32 GB RAM, Quadro 4000 CS6 Master Collection)
(1) Exporting using Queue in Pr CS6 to batch in AME creates the project file in a TEMP directory, and launches AME and adds the file to the Queue. When I press start, it sits a LONG time, then finally in the Encoding panel, I get the "Connecting to Dynamic Link Server...", until it fails with the error "Can't read source file..."
(2) Exporting directly from Pr works fine (so headless AME is working)
(3) Importing a Pr Sequence within AME does not work, I get an error from the Import Premiere Pro Sequence dialog (after a long wait “Connecting to Dynamic Link server…”) that “Connecting to Dynamic Link server failed”.
I suspect this is a dynamic link issue, but don't know where. I've tried the 'create a new Premiere shortcut in dynamicilnk folder' solution, but it didn't work. When I first tried that, I did find two shortcuts already there, one for Pr and one for Ae, but BOTH of them pointed to a CS4 folder! I've never owned CS4, and went from CS3 Design Professional to CS6 Master Collection. I also suspect this issue was caused by one of the updates to Pr that occurred within the last 130 days (since the last time I know this functionality worked). I've made not changes to my system during that time.
I do not use Windows Firewall, and all of this happens on a single machine, so there should be no TCP traffic across the wire (unless it is communicating with Adobe?). I use Webroot Endpoint Protection, but have received no indication that anything is suspect or has been blocked. Any help from the Adobe engineers would be greatly appreciated.

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

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

Automated BSO / ASO Outline Dimension Build

Hi,
I am trying to dynamically build an BSO cube outline using RULE file and DATA files.
But am experiencing challenges.
Does the cube have to intial dimensions in the outline(ie PRODUCT)? Or any dimensions?
I am speciifying the PRODUCT dimension only in the DATA file, and in the RULE file specifying it as a PARENT, and the second row as CHILD.
But it errors.
Can this same methodology be used to build ASO cube outlines as well?
Can anyone assists in overcoming this frustrating hiccup.
Thanks
Reg
Edited by: user13022116 on 18-Jun-2010 09:00
Edited by: user13022116 on 18-Jun-2010 09:03

The easiest way to do this is to have the dimension at least specified in advance, but if you can't do that, then you can define the dimension in the load rule. Select Dimension build settings, then go to the tab Dimension Definition. In the bottom half, you can define a dimension

Dimension Build File - Member Property Codes

I am building a Dimension Build File.
What is the code to create a Shared Member?
I know the following codes:
Code
N Never Share
O Label Only
S Stored
V Dynamic Calc and Store
X Dynamic Calc
Or is there a different way to specify a member as a Shared Member in the dimension build file?
Thanks,
Dave

There is no property for a shared member. If you are using a parent/child build method it will automatically load shared members unless you specify don't share. To do a load as a level or generation build, you have to have the file in a particular order and use the dimension build tab of field properties. There is a section in the admin guide that shows you how to do it.
But for using level builds it would be something like
Lev 0, Product Lev 1, product Lev 2, Product Lev 1, product
100-20 100 Products Diet Colas
Notice how the second lev1 defines the alternate rollup and it would cause a shared member to be created

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.

MAXL - using multiple Dimension build rules in single script...

I seem to be having problems running multiple Dimension build rules in a single MAXL script, is this a known problem or just an issue that I'm having? The build rules independently work as designed but when joined into a single script the script hangs...
So, this is a 2 part question...
1) Does MAXL not play nice when using multiple Dimension load rules in a single script?
2) Do I need to run the build rules independent of each other?
Also, is there some type of refresh/update on the cube that you can use in the script and would it be necessary...?
Thanks for any light you can shed on the issue.
Adam,

I've written multiple dimension build statements as a part of 1 long MaxL statement. I'm executing this MaxL via a shell script (that replaces the variables such as username, password, servername, file path etc.) I've not seen any issues doing so.
However, I've noted that, number of imports statements in 1 single MaxL command does not bode well for more than *60* import statements at once. So, if you're using more than 60 source files to build your dimensions, please consider breaking up your MaxL into multiple statements.
Note: All but last of the import statements have 'deferred' re-structure specified. It speeds up the build process.

Dynamic Dimension Building Problem

Similar Messages

Maybe you are looking for