Cube hang up is happening during Dimension Build process

Question

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

Answer 1

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.