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

Similar Messages

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?

Reporting with Report Builder 3.0 and SQL Server 2008 R2

Hi everyone
I'm trying really hard to find books about Report Builder 3.0 or SQL Server 2008 R2
I found the following books on the "learn" site, sadly they do not cover Report Builder 3.0 or SQL Server 2008 R2 since there all too old.
Microsoft® SQL Server® 2008 Analysis Services Step by Step
Microsoft® SQL Server® 2008 MDX Step by Step
Microsoft® SQL Server® 2008 Reporting Services Step by Step
What are good books (like the ones above) for the newest system?

Hello wishmasterIN,
Thank you to post your question on TechNet forum.
Based on my experience, the books are always delayed to the new technology, since the author need time to summarize and analyze the new features in the new product or technology, write it down and publish it. If you want to have a quick learning about the
new technology, MSDN library is a good place. It can be a cookbook for you. It contains some detail steps for tools, such as Report Builder or BIDS. It also contains many new features introduction. It is always very useful for you to understand the new features.
In addition, it is based on web and many links make you can jump to the other technical point freely. The most important is all of these is free and all the information will be updated if the new feature is released.
In short, if you want to learn the latest technology about Microsoft product, MSDN is a good choice. I hope my introduction is helpful to you.
Regards,
Edward
Edward Zhu
TechNet Community Support

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

HELP: Reports Builder 9iDS Rel2 and SQL Server 2000

Hi,
I need to connect to a SQL Server 2000 database from within Report Builder (for a proof of concept) and I am getting error 62000-Failed to connect to datasource.
Can you help?
My OS is Windows Prof 2000.
I have Downloaded Oracle 9iDS Rel2 and Oracle 9i AS J2EE and Web Cache. They are installed in the same Oracle Home.
I have modified the REPORTS_CLASSPATH with the datadirect jar files and the j2ee oc4j.jar.
The oc4j.jar is in my system classpath.
I have added the classpath definition with jars to my rwserver.conf.
I start Report Builder select JDBC Query
enter my connect info:
Username: user
Passowrd: pwd
Database: dbname
and select the merant-sqlserver driver from the list.
What am I doing wrong?
I have been at this a week can anyone help?
Thanks.

Hi Jeanne
1. When you run the report to paper design from builder, you need to add the necessary jar file of driver to REPORTS_CLASSPATH env variable in registery.
2. To run the report from report server and to generate to file from report builder, you need to add the jar files via classPath attribute of engine element in server/builder conf file. It would be like this
<engine id="rwEng" .....classPath="<yr classpath>" >
3. Have a look at jdbcpds.conf file in OH/reports/conf dir. This file need to have the driver information for the driver you are using. The entry here also specifies the connect sting format which is required by the driver. You need to refer to driver doc for connect string format.
Once you have all this set up ready, run the report. You need to mention the connect string in same format as specified in driver info in jdbcpds.conf file.
Try this.
Thanks
Rohit

Reports Builder 9iDS Rel2 and SQL Server 2000

Hi,
I need to connect to a SQL Server 2000 database from within Report Builder (for a proof of concept) and I am getting error 62000-Failed to connect to datasource.
Can you help?
My OS is Windows Prof 2000.
I have Downloaded Oracle 9iDS Rel2 and Oracle 9i AS J2EE and Web Cache. They are installed in the sale Oracle Home.
I have modified the REPORTS_CLASSPATH with the datadirect jar files and the j2ee oc4j.jar.
I have added the classpath definition with jars to my rwserver.conf.
I start Report Builder select JDBC Query
enter my connect info:
Username: user
Passowrd: pwd
Database: dbname
and select the merant-sqlserver driver from the list.
What am I doing wrong?
I have been at this a week can anyone help?
Thanks.

You should ask this on the Reports discussion forum, you'll get a better answer there.
http://forums.oracle.com/forums/index.jsp?cat=19

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

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!

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

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!

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

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/

Dimension access problem

Hello there!
I've got a problem:
There is a user test_user, and there is a form test_form, test_user has an access to this form as write, and has an access directly to all lowest level dimensions used in this form. In pages there are two members: unit1 and unit2, both are marked as write for test_user, BUT at one time unit1 values could be modified, unit2 could be NOT.
Same form, same accesses for dimensions, but unit2 for any form it is used in somehow is read only.
Where should i search for this problem, maybe some solutions or it is just a bug-reason for Oracle SR?
I really need help people, please :)

when you say autogenerated currency conversion script , is it the calculation script CurrCo which get created from Administarion->Manage->Currency Conversion
Or you are talking about <Calculate Currencies> on dataform one.?
1)
If it is a calc script then you need to provide access to that user via EAS
Login to EAS- expand the Essbase server
Go to Security-> right click on User and display
Select the user and edit access then select the Calc Script from the Application-->Database
Then the user will able to see that script on the webform if it is attched to that.
2)if it is <Calculate Currencies> then no need to give separate access , it comes to all user having Planner access/Essbase Write access
-KP

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

Similar Messages

Maybe you are looking for