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.

Similar Messages

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/

Tutorial required for performing Dimension Build using Maxl

Hi all,
Can you please suggest me a Tutorial for performing Dimension Build using Maxl?
Best Regards

From the tech ref Samples
Exampleimport database sample.basic dimensions
from data_file '/data/calcdat.txt'
using rules_file '/data/rulesfile.rul'
on error append to '/logs/dimbuild.log';
Deferred-Restructure Examples
For Data File Sources:
import database sample.basic dimensions
from server text data_file 'genref' using server rules_file 'genref' suppress verification,
from server text data_file 'level' using server rules_file 'level' suppress verification,
from server text data_file 'time' using server rules_file 'time'
preserve input data on error append to 'C:\Hyperion\products\eas\client\dataload.err';
For SQL Sources:
import database sample.basic dimensions
connect as 'usrname1' identified by 'password1' using server rules_file 'genref',
connect as 'usrname2' identified by 'password2' using server rules_file 'level',
connect as 'usrname3' identified by 'password3' using server rules_file 'time'
on error append to 'C:\Hyperion\products\eas\client\dataload.err';
For Data and SQL Sources:
import database sample.basic dimensions
from server text data_file 'genref' using server rules_file 'genref',
from server text data_file 'level' using server rules_file 'level',
connect as 'usrname1' identified by 'password1' using server rules_file 'genref',
connect as 'usrname2' identified by 'password2' using server rules_file 'genref'
on error append to 'C:\Hyperion\products\eas\client\dataload.errr';>
Try it and post back if you have errors
Regards
Celvin
http://www.orahyplabs.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;

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

Error: 1030001 while Dimension Building using MaxL

Hi, I am bulding dimesions using MaxL import statement. My script builds the diemsions properly. But in Logfile, It shows this error without generating any error files. ...... ..... OK/INFO - 1021000 - Connection With SQL Database Server is Established. OK/INFO - 1021002 - SQL Connection is Freed. OK/INFO - 1007132 - Building Dimensions Elapsed Time : [0.781] seconds. ERROR - 1241101 - Unexpected Essbase error 1030001. OK/INFO - 1019017 - Reading Parameters For Database [Drxxxxxx]. OK/INFO - 1019012 - Reading Outline For Database [Drxxxxxx]. ...... ... Can anybody can help me out with it? I know that Error: 1030001 is geneated due to API or path problems, I checked all paths, all is good. Thanks in advance, Marma

We are getting this error too. I believe that the error occurs because Essbase tries to evaluate outline before you finish building all of your dimensions. To me, it should be a Warning, not an Error. But my experience with Essbase is that anything that has to do with GUI or presentation of information to its developers (non-scrollable text boxes, log info, etc.) is lousy, so this is not a surprise. I had to build a logic in my batch programs to ignore this error when parsing log file for errors in execution. Hope you can do the same.

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.

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.

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

Export outline to xml_file ... from EAS- MaxL editor, where is the export file

Hi
version 11.1.2.3.x
EAS is called from IE via the valid url and opens with no error.
When I run an outline xml extract from EAS (MaxL editor) there are errors.
e.g. as mentioned in the docu
https://docs.oracle.com/cd/E17236_01/epm.1112/esb_tech_ref/frameset.htm?maxl_expotl.html
->export outline sample.basic all dimensions to xml_file "c:/temp/basic.xml";
The error says unable to create objekt. However, the given path c:/temp exists on my client box.
When I run the same from a maxl shell it works like a charme... the otl-xml-export file is created on my box in the given directory.
Only when I run the command in EAS WITHOUT any path like "basic.xml" it works without any error, however I cannot find the file on my box. Where could it be ? Why the error when a valid path is given?
I have no clue.
Can someone explain wether I'm doing wrong something, or is there someone having faced the same issue?
Thanks in advance!
Andre

Hello John,
At first: thank you for your quick reply!
Indeed it's created on the Application server.
That's terrible! I was even able to write to c:/Windows/.
I have never tried this before. And what I see makes my very concerned about this.
Anyone who can run such an export can write anywhere on the Appliaction server!
Give me some minutes to realize what this means regarding security concerns.
Oracle! please explain what you have to say.
Best regards!
Andre

Urgent - Dimension Build Error - Maxl Editor

Similar Messages

Maybe you are looking for