Skip to Main Content
Forums

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ORA-36836 about cube dimensionality ???

664948Oct 13 2008 — edited Nov 24 2008
Hi there,

I've been trying lately to use AWM to build an OLAP cube based on some sample data I have related to phone communications. Up to now I've been able although painfuly to build four dimensions (date/time, a-number, b-number, exit cause) and a cube with measures "number of calls" and "total call duration". Currently everything seems to load correctly (dimensions and cube), however when I try to view the cube data I get the following message :

ORA-36836: The dimensionality of object OLAP.TRAFFIC is different than the view token

This doesn't make any sense to me, and I've not been able to find any explanation on the web, except for those two lines :

Cause: The dimensionality of the cube does not match the view token
Action: Check view token for unrelated hierarchies clauses

Well the remedy looks even worse than the disease, since this is even less understandable than the former.
Does anyone has a clue about what might be wrong here, or what to do to go forward ?

I'm using the free Oracle 11g on CentOS, I guess this must be the XE edition, and AWM was part of Oracle Client on Windows XP. This piece of software seems to be riddle with bugs, data not updating properly after changes, objects only partly deleted after a delete command, lots of "uncommitable" and java exceptions of all kinds... I've had several times to totally delete the whole aw and restart from scratch because AWM would not finish deleting some dimension of attribute. A real pain in the neck. Is this related to the fact that I'm using a free version and don't have access to patches ? Well I really wonder how can anyone do some serious development with this tool. Or am I missing something ?

Thanks for your help,
Christian

Comments

Stuart Bunby-Oracle
Hi Christian,

Did you know that Oracle OLAP is only supported on Enterprise Edition of the Oracle Database?

I'm really surprised that you have been able to get any OLAP functionality to work on any other edition.

As far as 11g OLAP is concerned, I would recommend you use the recently released [11.1.0.7 database patch|http://oracleolap.blogspot.com/2008/10/more-11107-ports-now-available.html] along with [11.1.0.7A release of AWM|http://oracleolap.blogspot.com/2008/10/analytic-workspace-manager-11107a.html] - but on Enterprise Edition only!

Stuart
664948
Hi Stuart,

thank you for your quick answer. Here is the welcome message I get when connecting with SQL*Plus :

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

So it looks like there is some OLAP option evaluation available, although it does seem somewhat of an alpha version.

When you say "Enterprise Edition" do you mean I need to get a license ? If that's the case that's too bad because what I'm trying to do is to develop a small demo of an OLAP application to my fellow teammates and I was hoping Oracle would allow me out of the development hell I'm in with open source tools. However getting a license for this is simply out of the question, so this basically means I'm over with Oracle. Really too bad.

Thanks for your help anyway,
Christian
Stuart Bunby-Oracle
If you are working with 11.1.0.6 then you really should apply the patches listed here. Without any 11.1.0.6 patches, I am not surprised that you are experiencing lots of errors.

There is no escaping the fact that if you want to implement Oracle OLAP then you would ultimately need to license the Enterprise Edition of the database and the OLAP option itself. However, if you are simply trying to build a demo then I would recommend downloading Oracle Enterprise Edition from OTN and working within the terms and conditions of the OTN License Agreement (you will have to accept these prior to downloading the software). I **believe**_ that you are able to work without a license for the purposes of evaluation, but if you have any doubts then you really should contact your Oracle account manager.

Stuart
664948
Hi again Stuart,

in fact I realized right after posting the previous post that the welcome message did say that I'm using Enterprise Edition. My bad. From the terms of the license it seems very clear that these free downloads are precisely intended at that, i.e., developing and prototyping. However the current 11.1.0.6 version of the OLAP option looks essentially unusable, so I'll try to get my hands on the patch you mention. Hope someone at my company will be able to find me a Metalink ID.

Thanks a lot for your help !
Christian
Stuart Bunby-Oracle
Given the choice, you should go to 11.1.0.7.

Good luck,

Stuart
chris_here
Hi again Stuart and all,

I'm back after some patching... :-) I've applied the following patches to my installation :

On the server side patches 7375639 (Oracle Critical Patch Update October 2008) and 6992921 (OLAP B PATCH FOR 11.1.0.6).
On the client side I've upgraded to AWM 11.1.0.7.0A

And ... tadadam ... I still have the same error message after recreating the whole workspace from scratch :-(

Here is a transcript of the error message I get :

------------------------------------------------------------------------------------------------------------------
[edit many similar lines]

oracle.dss.dataSource.common.OLAPException: BIB-9009 Oracle OLAP could not create cursor.
oracle.express.idl.util.OlapiException: java.sql.SQLException: ORA-36836: The dimensionality of object OLAP.TRAFFIC is different than the view token
ORA-06512: at "SYS.GENCURSORMANAGERINTERFACE", line 42
ORA-06512: at line 1

oracle.express.idl.util.OlapiException: java.sql.SQLException: ORA-36836: The dimensionality of object OLAP.TRAFFIC is different than the view token
ORA-06512: at "SYS.GENCURSORMANAGERINTERFACE", line 42
ORA-06512: at line 1

at oracle.dss.dataSource.common.QueryDataDirector.addDataDirectorListener(QueryDataDirector.java:795)
at oracle.dss.dataView.ModelAdapter.setDataDirector(ModelAdapter.java:173)
at oracle.dss.crosstab.CrosstabModelAdapter.setDataSource(CrosstabModelAdapter.java:54)
at oracle.dss.dataView.Dataview.setDataSource(Dataview.java:396)
at oracle.olap.awm.dataobject.dialog.olapi.UBiBeanUtil.getCrosstab(Unknown Source)
at oracle.olap.awm.dataobject.dialog.olapi.UBiBeanUtil.showCrosstab(Unknown Source)
at oracle.olap.awm.dataobject.dialog.olapi.UBiBeanUtil.showData(Unknown Source)

[edit many similar lines]
------------------------------------------------------------------------------------------------------------------

I'm able to display the dimension views and the cube view and they "look" ok, but I get this error when I right-click to "View data <MY CUBE>..." or "View data <ONE OF THE MEASURES>..."

So it looks like there's something in the way my data is wrapped up that really bothers the Oracle OLAP engine. What I'm trying to do is to migrate a cube that works on Mondrian to Oracle OLAP, so it means the problem is probably related to some specific requirement that the Oracle OLAP engine imposes on the way the data is presented.

In any case the error messages are totally meaningless to me. Does anyone has an idea what the "view token" is ?

Thanks a lot for your help,
Christian
You will probably need to file an SR to get this resolved. In the meantime I have two questions.

(1) Can you access the cube data via the generated views? The 'View Data' option in AWM goes through a related, but different code path, so knowing if both fail or only one should help us isolate the problem.

(2) Are you running the data viewer as the owner of the cube? If not, then it is possible that this is a permissions issue.
chris_here
Hi David,

this is really the strangest part: everything seems to work perfectly ok when I create the cube, the loading of data (Maintain cube...) goes smoothy, I can view the dimensions data and also the cube data through the generated view Cubes -> TRAFFIC -> Views -> TRAFFIC_VIEW. The data looks fine, it's a simple fact table with PK (A_NUMBER, B_NUMBER, CAUSES, DATE_TIME) -> CALLS. I only get the error message when I right click on "View data TRAFFIC...". Right-clicking on "View data A_NUMBER" for instance works.

Here is the worst part: after quite a large number of attempts using the simplest possible cube model and all or only part of the 4 dimensions, I'm able sometimes to see and navigate the cube data, i.e., not having the error message. I'm totally incapable of saying why some particular attempt will work though. All I have been able to figure out up to now is that once I get the error message I'm going to be stuck with it for quite some times, I mean I will get it even after deleting the cubes, disconnecting awm, even restarting the whole database system. Then after carefully creating some cubes, trying to modify as little options as possible... suddently I'm able to view and navigate the cube data (although with a very simple cube with no hierarchies). So currently as I'm typing this I'm able to navigate several of my cubes, but I don't dare to touch anything for fear of encountering the dreaded red arrow again :-)

Also to answer your second question, since the error is intermittent this obvisouly isn't be related to permissions. All the work with AWM is done using a dedicated OLAP user.

I'm ok to fill a Support Request or bug description, however since I've never done that it would be nice if you could put me on the way about how to do it.

Also I'm going to not touch AWM anymore for a little while now that I have one working cube in order to be able to use the subsequent tools. I'm pretty confident from my earlier attempts that as soon as I will request my original cube data again the error message will come back to stay, even for the cubes that now work. This behaviour should help to determine what causes the error.

Thanks for your help,
Christian
chris_here
Hi there again,

does nobody have any more advice regarding this issue ? What I've tried lately is to install a whole fresh new instance of Oracle 11g 11.1.0.6 then apply the OALP & Oct08 CPU patches before doing anything. I still have this bug when I try to use in a cube a dimension that has at least one hiererchy it seems. However sometimes, seemingly depending on the alignement of the stars, I'm able to get the cube completed and view the data. I don't have the slightest clue about what might cause the pb and why it sometimes works. Am I really the only one to get this error ? I find it hard to believe, as the steps to reproduce are really simple:

1 . Install Oracle 11g 11.1.0.6 Enterprise Edition on Linux (in fact CentOS 5)
2. Apply any patch you like or none, doesn't seem to make the slighest difference
3. Create a dimension with a hierarchy
4. Create a cube based on that dimension, load it, watch the views, everything's ok
5. Ask for "View cube data..." and you're stuck with "Cube dimensionality blah blah blah".

Then I get error messages in the Oracle logs like "Internal error (ORA-600[kglrls-bad-lock]) detected in log.xml"

This is driving me crazy. Unfortunately I'm currently not able to post a SR because the ID my company gave me doesn't seem to allow it, and all this internal stuff is very heavy to make move. Does anyone has any clue about what to do from here ?

Please help if you can, this is really making me waste a lot of time while I should really be preparing this demo instead.

Again any help will be greatly appreciated,
Christian
Stuart Bunby-Oracle
Hi there,

Were you able to verify whether the error occurs with the 11.1.0.7 database patch applied?

Stuart
chris_here
Hi Stuart,

what I did lately was this :

1 - Install Oracle 11G Enterprise Edition v11.1.0.6 from OTN
2 - Apply patch 6880880 : OPatch v11.1.0.6.4 upgrade
3 - Apply patch 6992921 : OLAP B PATCH FOR 11.1.0.6
4 - Apply patch 7375639 : Critical Patch Update October 2008 (CPUOct2008)
5 - Download AWM 11.1.0.7.0.A standalone from OTN

I get fewer errors with AWM except for the ORA-36836 above, which keeps coming. However I swear I've been able to use my data model at least once, I've even been able to view and play with it in Oracle Answers... However today I tried to restart from scratch (there were just too many test tables etc) and I'm facing this error message again. :-(

Thanks for your help!
Christian
Stuart Bunby-Oracle
So you still haven't tried the [11.1.0.7 database patch|https://updates.oracle.com/ARULink/PatchDetails/process_form?patch_num=6890831] ?

Whereas I cannot be sure that applying this will fix your problem, I would recommend trying it as I understand that many important fixes were added in this release.

Stuart
chris_here
A few additional remarks about this crazy thing:

1) I have been able to create and use a dimension that contains a hierarchy, namely DATETIME.CALENDAR = (ALLDATE, YEAR, MONTH, DAY, HOUR, HALFHOUR). I have a cube T1 with two dimensions, DATETIME and EXITCAUSE and I can play with it as much as I want, no error.

2) If now I create a cube T2 that contains the hierarchical dimension BNUMBER.BLOCKS = (ALLNUMS, SHORT, CODE, BLOCK) I get the error message, even when I try to view the previous cube T1 above. If I delete T2 I can view T1's data again...

3) While writing this message I thought this might be due to some reserved keyword in the level names, like SHORT possibly, so I duplicated the dimension using labels like AAA, BBB, CCC, etc. I created a new cube T3 with that dimension and now not only does this new cube T3 work, but T2 and T1 also. I don't have the error message at all anymore. Well this is drivin me totally nuts.

At least it seems I have a workaround, just create a few random cubes with random element names and eventually the bug seems to go away. But still this is incredebly annoying. I really whish I could reach one of the AWM developpers to get this known at least.

I'm willing to provide any test case if anyone is interested, only I won't be able to fill an SR I guess.

Regards,
Christian

PS: I'll try the patch you indicate and keep you posted. Regards. Chris
Stuart Bunby-Oracle
I think we have all experienced unexplained errors in the past and can associate with your frustration.

I will make sure that someone from development takes a look at this thread but the only way you can guarantee a formal response would be to capture your experiences on Metalink in an SR (if your Oracle Support access code does not work then call Oracle and find out why)

Let me know how you get on with the 11.1.0.7 database patch - irrespective of this particular issue, you really should be using this anyway

Thanks

Stuart
Hi there, I work in OLAP Dev. Please can you upgrade to 11.1.0.7. to try it with AWM 11.1.0.7A? And/or do you get this error when you use 11.1.0.6 with appropriate patches and AWM 11.1.06A?

Please turn sql trace on at the database level, execute your operation, detach from AWM and send me the resulting sql trace. Do this with one of the above combinations of AWM/db (11.1.0.7 is best) and send me the sql trace while you sort out your CSI number.. I can progress the issue while a SR is being opened.

My email is laura.j.mckechnie@oracle.com.

Thanks, Laura
Quite by accident we have just stumbled across this same problem in development against an 11.1.0.7 instance. As in the reported case, changing the name of a level (in this case from VALUE to CUSTOMER_VALUE) made the cube viewer work again. I hope we will be able to track this down in house and explain what is happening.
chris_here
Hi there again,

I've just upgraded to 11.1.0.7.0 and I still get the same error message. However it is clear now that the issue is due to a conflict between level names and some reserved words, since the error doesn't appear when I use meaningless identifiers instead of 'CODE', 'BLOCK' and 'SHORT'. So the issue is not really serious, at least if it's known !

I've send some trace files to Laura so hopefully the issue will be identified more precisely soon.

Anyway the big relief now is that the problem has nothing to do with cube dimensionality because that was making me feel real bad :-)

Thanks to all for your support,
Christian
438862
Christian,

There's a bug in the a parser which is exposed when using the Data Viewer. Not to bore you with the details, but this layer of code is going throw an old code path that uses a parser that is sensitive to certain keyword names (base, short, long, integer, dimension, etc...). To work around the issue add a simple prefix or postfix to cube, dimension and hierarchy names. For example, instead of a dimension PRODUCT, hierarchy BASE and cube SALES create a dimension PRODUCT_DIM and a hierarchy BASE_HIER and a cube SALES_CUBE. It's a bit of a pain but you won't hit the issue anymore.

A bug will be created and the issue will be resolved in a future release.

Christopher
chris_here
Hi Christopher,

thanks a lot for this information. I think it's good to have this information on the thread, as now if someone stumbles on the same issue they'll be able to google it and immediately get the answer.

Regards,
Christian
1 - 19
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Dec 22 2008
Added on Oct 13 2008
#11g, #data-warehousing, #error, #olap
19 comments
3,565 views