When you process the cube or partition, at the bottom there is a
"Settings..." button. In there you can request that the system log dimension
key errors to a file. You can also increase the number of errors. The
default is "one" so that processing halts immediately, but ou could increase
it to some larger number such as 1000, or disable the checking altogether...

--
Dave Wickert [MSFT]
dwickert@online.microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Frank Kearney" <frank@djrtour.com> wrote in message
news:%23dLozGubDHA.2544@TK2MSFTNGP09.phx.gbl...
> I have a cube with 5 partitions and a fact table with 8.9 million rows in
> the fact table. The first two partitions process just fine. When it hits
the
> 3rd partition, it gets through the select statement against the fact
table,
> returns the count of rows (8.9million), then proceeds to start throwing
> missing member key errors followed by an odd memory error. An example:
>
> 8/26/2003 3:40:00 PM 18084 A member with key '' was found in
the
> fact table but was not found in the level 'MYDIMLVL' of the dimension
> "MYDIM".; Time:8/26/2003 3:40:00 PM
> 8/26/2003 3:40:00 PM 18084 The maximum number of dimension key
> processing errors has been exceeded.; Time:8/26/2003 3:40:00 PM
> 8/26/2003 3:40:35 PM 18084 Analysis Server Error: Memory error
> [Failed to reallocate space] '' ; Time:8/26/2003 3:40:35 PM
> 8/26/2003 3:40:35 PM 18084 Analysis Server Error: Memory error
> [Failed to reallocate space] '' ; Time:8/26/2003 3:40:35 PM
>
> We have queried the fact table over and over and cannot find this empty
> string that AS is complaining about. I looked up the memory error online
and
> found KB article 303370 which directs you to increase the page file size
to
> resolve the issue. Prior to doing that, I decided to kick off the 3rd
> partition again just to see if it was an abnormality. Sure enough, it
> finished. So I started partition 4. Same amount of rows as part 3.
> Immedietly after the select statement was finished, I again got the same
> errors as above except this time I didn't get the memory error. ( I did
> increase page file before starting partition 4.
>
> What concerns me the most is the fact that we cannot find this empty
string
> ANYWHERE in the data. So, where is it coming from?
>
> Any thoguhts out there?
>
> Oh yea, forgot to tell you that the input data is being retrieved from
> Oracle 8.1.7.4l
>
> Thanks all and sorry for the novel
>
>