June 23, 2009 at 11:31 pm
Hi All
I had migrated from SSAS 2000 to SSAS 2005.
SSAS 2000 had 1 virtual cube (vir_cube1) which was using 2 physical cube.
Now ,I had made few new dimension in SSAS 2005 but I'm not able to add the dimension in one of the cube (vir_cube1) while in other cubes it lets me add these new dimension.
How can I add these dimension to this cube?
Again to overcome this problem I added linked dimension based on these newly created dimension. Now the virtual cube (vir_cube1) lets me add the linked dimension and everything works fine.
But after reboot I cannot connect to SSAS 2005.
It goes in endless loop.
Event viewer has no warning/errors. The error fom SSAS log file is
Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.4\OLAP\Data\Flexlab1.2.db\Analyses all.5.dim.xml'. (Source: \\?\C:\Program Files\Microsoft SQL Server\MSSQL.4\OLAP\Log\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210012)
Message: Errors in the metadata manager. An error occurred when loading the Arrival times 1 dimension, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.4\OLAP\Data\Flexlab_try.4.db\Arrival times 1.1.dim.xml'. (Source: \\?\C:\Program Files\Microsoft SQL Server\MSSQL.4\OLAP\Log\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210013)
Message: Errors in the metadata manager. An error occurred when loading the FlexLab_Production cube, from the file, '\\?\C:\Program Files\Microsoft SQL Server\MSSQL.4\OLAP\Data\Flexlab_try.4.db\vir_cube1.89.cub.xml'. (Source: \\?\C:\Program Files\Microsoft SQL Server\MSSQL.4\OLAP\Log\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210013)
Then I have to delete the data file .. And do the process again.
This error only comes when I add the linked dimension.
Please help to resolve this error
SSAS 2005 SP2
June 24, 2009 at 9:36 am
Not a direct answer but more of a general question - why would you not simply create the 'virtual' cube as a physical one now in SSAS 2005? That is, the primary reason for virtuals in 2k was to get around the limitation of a single fact table per cube. Now that AS2K5 supports multiple facts, why wouldn't you bring in all of the tables required, build a single cube that 'links' the two (or more) facts together via conformed dimensions (ie the ones that you were using as linkage points previously). AS2K5 is a better platform than 2K was, with enhancements like support for many-to-many.
You could still present the single cube as 3 cubes to your users as/if required, simply sue perspectives to limit the visibility of dimensions and measure groups.
Steve.
June 24, 2009 at 11:48 pm
Hi
Thanks for the input.
I have tried making new cube. But while processing I get an error
Errors in the high-level relational engine. The 'dbo_v_Pr_fact' table that is required for a join cannot be reached based on the relationships in the data source view.
The relationship has been defined in data source view but still keep getting this error for one dimension and hence for the cube.
Please help to overcome this error
June 25, 2009 at 8:27 am
Check the 'direction' of the relationship, this is done from the datasource view, right click on the rel and then select edit. Make sure the 'primary key' of the relationship is set correctly.
Also, check your dimension usage, ensure that the dimensions that should 'link' all measure groups (ie are shared between facts) are displayed that way.
Steve.
June 25, 2009 at 10:05 pm
Hi
The direction of the keys are set correctly.
Could you please try and explain "check your dimension usage, ensure that the dimensions that should 'link' all measure groups (ie are shared between facts) are displayed that way."
also, the dimension which passes error works fine on other SSAS 2005 db which was migrated from SSAS 2000.
It only gives this error for the new created cube. and then it passing error for all other cubes also.
what might be the reason for this.
June 25, 2009 at 10:20 pm
Hi
The direction of the keys are set correctly.
Could you please try and explain "check your dimension usage, ensure that the dimensions that should 'link' all measure groups (ie are shared between facts) are displayed that way."
also, the dimension which passes error works fine on other SSAS 2005 db which was migrated from SSAS 2000.
It only gives this error for the new created cube. and then it passing error for all other cubes also.
what might be the reason for this.
June 26, 2009 at 1:14 pm
Hi,
It's hard to tell exactly what the issue may be without some further detail. Prior to pushing that up here, you may want to take a look at the (roughly 3) different solutions people ahve used to solve this in the past (found here), these are (short-form):
- The direction of the relationship in the DSV
- the dimension usage (go to the dimension usage tab and review)
- the key and/or name fields (for the PK) in the dimension itself.
HTH,
Steve.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply