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/

Similar Messages

Urgent - Dimension Build Error - Maxl Editor

I have the following Statement import database 'ASOmkv5'.'ASOmkv5' dimensions from data_file timedim using rules_file ASOmkv5 on error write to 'ASOmkv5_logfile'; I get the following Errors Object [ASOmkv5] is locked by user [jtest] Object [57774682] is locked by user [jtest] Cannot access object: ASOmkv5.rul Object [57774682] is unlocked by user [jtest] Unexpected Essbase error 1030200 Object [ASOmkv5] is unlocked by user [jtest] 

I suspect that it is not finding your rules file. Try modifying the line to add "server" as in using server rules_file 'ASOmkv5' , also, single quoting the filename is probably a good practice. I'm always careful about using the "server" keyword when using any file from a source in the database directory. I work on a Windows server and have found that MAXL is sometimes a little erratic in parsing filenames. Escaping backslashes can be a particular problem. In your example, I'd try the server file location first.

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 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/

Ignore dimension build error Incorrect Parent For Member (3307)

Hello,
Is it possible to ignore the following error:
Incorrect Parent [XYZ] For Member ABC (3307)
The error appears because the member is in outline already. Is there a way to ignore that error?
Thanks in advance

The reason for the error is you have multiple rows in your dimension build file with conflicting information. One row says to associate the member with parent A and another row says to associate it with Parent B. TimG's suggestion to set them ember to allow moves would get rid of the error, but the member will be associated with the last row in your data. If you do not allow moves (as it appears you have) there is no way to turn off the error. In your case it is what I call a soft error, you know about it, but don't want to do anything about it. I would suggest you clean up your data so it does not cause this issue. It is troublesome to me when the incoming data has this type of inconsistency and the solution is to ignore it

Essbase Dimension build error and Unable to Stop/Start Application

Hi All,
I am trying to build the dimendion in the ASO application it is throwing the Error meaasage " Dimension Biuld failed , ther may be problem in allocating memory".
While i am trying to and Start/Stop my respective Application it is throwing the below error meaasge
I tried to debug this issue by checking the Locked objects, and asked my Admin to close my sessions forcebully if any running and also checking all rules files . But i didn't get any clue/solution from them.
Please help me out from this issue
***ess-dev.ASOAPP     Stop application     April 15, 2009 4:15:08 PM IST     Failed***
***Error: 1013018 Cannot unload database [Sample] while user [ASDF] is performing database operation. Wait for user [ASDF] to complete the operation, or ask the user to abort it. Log out all users and then unload the database.***
***     MaxL Command     April 15, 2009 4:40:52 PM IST***
***Error: 1053012: Object [Sample] is locked by user [ASDF]***
***Error: 1013100: User [ASDF] is Active on Database [Sample]***
***Error: 1013132: Cannot build dimensions. There are other active users on database [Sample]***
***Error: 1241101: Unexpected Essbase error 1013132***
***Error: 1053013: Object [Sample] unlocked by user [ASDF]***
***     MaxL Command     April 15, 2009 4:43:28 PM IST***
***Error: 1270040: Data load buffer [2] does not exist***
Regards

Hi,
Thanks for your answer friend. My admin has successfully killed my session forcebully. And he doubted that i may not have enough rights to Stop/Start application and he provided me the required rights. After that also the error is repeating as below. we two are not getting where we went wrong.
ss-dev.ASOAPP     Stop application     April 15, 2009 8:19:35 PM IST     Failed
Error: 1013018 Cannot unload database [Sample] while user [ASDF] is performing database operation. Wait for user [ASDF] to complete the operation, or ask the user to abort it. Log out all users and then unload the database.
Help me out from this issue

Dimension build error codes

Does anyone have a list or know where I can find a list?
I'm seeing 3307 and 3315 and need to figure out what that is causing them
Thanks!

Hi,
There isn't a list for the dimbuild error codes that I know of. They don't even appear in the message.txt file that comes with the API install.
Maybe if you paste the whole line of the error we might be able to help a bit more.
Google found a couple of examples which might steer you in the right direction:
\Record #234 - Property [FAC: Unknown | AMER] changes for member [FAC-1234 | AMER] not allowed (3315)
\\Record #2 - Incorrect Parent [600-20] For Member [600] (3307)
Gee

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!

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.

How to use Dimension Build to change member property?

Hello,
I have researched online on how to do this and I think i have an understanding but I cannot get it to work. My dimension build rules file is of type Parent Child. The fields are Parent, Child, Alias. I am looking to add a Property field to change the consolidation property to - for one member. I have checked off all the options required and tried several different ways but always come with the following error on that line.
\\Record #95 - Child Member - with no parent (3331)
P&L - ACC OPERATING Operating Expenses -
order is:
Parent Child Alias Property
What i want to do is assign the - subtraction for consolidation on the OPERATING member. Can this be done with the Parent Child type dimension build? Could this be achieved automatically in another way?
Thanks
Alex

Hey guys, thanks for the tips. The source file is tab delimited. I made sure there was a tab between Operating Expenses and the - for subtractions. The lines look like so.
REV_PROJ PS100001 - ACC PS100001 - ACC_PS-M9 Revenue Settlement
REV_PROJ SC100000 - ACC SC100000 - ACC_SCS Revenue Settlement
P&L - ACC OPERATING Operating Expenses -
OPERATING LABOR Labour
LABOR PAYROLL Payroll related
I know they don't show the tab but it's there. I have the field set to Property for Account_Desc (Dimension im updating in the outline) with a value of 0. I have also checked off "Delete when the field is empty" as to not change the consolidation on the other lines. i guess i need to figure out why it's treating the final "-" as a member and not as a part of the same line holding it's property. Is there a EOL delimiter i should be setting?
thanks again

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

Dim Build Error

There isn't any keywords or reserved words for dimensions, are there?
I'm building dimensions from a sql call, it creates all of them except for "OTHER" which gives the following error:
\\Record #10 - Incorrect Dimension (Region) for Member OTHER (3308) OTHER

This is a common problem in the essbase world and a reason many cubes have prefixing. Unless you are working in system 9.3 and have elected to allow duplicate names, you have simply used the name other twice in two different dimensions.
This is confusing to those with a relational database background because Other Region should be different from Other Product and Other Customer. You need to remember that the labels such as Othe can be used by an end user at anytime in any position. So you need to make each label in your database unique. The time tested process is to prefix (or suffix) all the members within a dimension. So all of your products could be prefixed with a P and all of your regions with an R. Or you could prefix with Prod or Product. As the moment you are only having the issue with Other, but it could happen when you have a saleman named West and a region West, etc. So the prefix solution allows you to have things run on autopilot.
Two other options, in the dimension build rule, you could change Other to Other Region. This is the easiest solution for a business owned application.
The other choice is to change your ETL so Other Region comes in your file as Other Region.

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;

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

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.

Urgent: dimension build error.

Similar Messages

Maybe you are looking for