column is not a ColumnBinding type

[Flybridge]

I am new to SQL Server 2005. I have a cube that will process in full. But I have created a new partition and get an error message when I try to process it.

The message is 'Errors in the high-level relational engine. The binding for the 'XXX' column is not a ColumnBinding type.'

The column in question has no relevance to the partition.It exists in 2 dimensions but neither are relevant to the partition.

Any ideas what is causing this and, hopefully, how to fix it?

Thanks in advance.

Flybridge

'The world isn't round - it's bent!' Spike Milligan

 

[MDXer]

are the columns of the same datatype? Do you have a relationship between these columns and there dimensions defined in the DSV? If you don't use these columns in this particular partition you should remove them.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[Flybridge]

Thanks. The column in question does not even exist in the partition, so there is nothing to remove, which is why we are all scratching our heads.
A full cube process works. This only happens when we try to process the partition.

Flybridge

'The world isn't round - it's bent!' Spike Milligan

 

[MDXer]

How are your partitions set up?

Is each partition bound to a table or view that contains only that partitions data or are you using criteria within the partition to define the dtata returned? Making all partitions point to the same source object.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[MDXer]

Another thing you can do is expand the nodes in the Processing Status window to the actual SQL statement. From there you can "View Details" and then copy this query and put it directly into SSMS query window and look at what is happening.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck

 

[Flybridge]

The partition is based on a single transaction table, using a timestamp to partition the data by year.
The measure group that is fed by this table has a relationship to a dimension that uses the offending column (as per the Dimension Usage tab). Could that have some impact?

I can't expand the node to see any SQL. There is a statement saying the masure group processed ok but the lapsed time is 0, then get error messages from Response. So no SQL to view, unfortunately.

Flybridge

'The world isn't round - it's bent!' Spike Milligan

 

[MDXer]

Sounds like a good candidate. in your dimension USAGE tab you want the level to be the same as the relationship between the dim and the measure. If you don't have the relationship defined it won't work if you have the wrong level defined it probably will cause problems, but I've never tried.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck