Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

OLAP full cube processing error

2,247 views
Skip to first unread message

Neeraj

unread,
Jun 1, 2010, 12:56:01 PM6/1/10
to
Hi,

I am getting the following error while processing full cube in production.
It is a SQL Server 2008 Enterprise edition on Windows 2008 R2 with 64 GB RAM.
The strange thing is that this error occurs randomly and the job completes
successfully after I restarting immediately. I have monitored memory usage
using PerfMon and there is always around 8-10 GB memory available. The
process is always failing on one particular dimension.

Please help.

Executed as user: DC\SQLServer. ...results
xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root
xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Exception
xmlns="urn:schemas-microsoft-com:xml-analysis:exception" /><Messages
xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Error
ErrorCode="3238002695" Description="Internal error: The operation terminated
unsuccessfully." Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" /><Error ErrorCode="3238133838" Description="File system error:
While attempting to read information from disk, a read error occurred for
physical file:
\\?\K:\MSAS10.MSSQLSERVER\OLAP\Temp\MSMDCacheRowset_1712_2ab8_jgw53.tmp,
logical file: ." Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP
storage engine: An error occurred while the 'Minutes To Complete' attribute
of the 'Lead' dimension from the 'Datamine OLAP' database was being
processed." Source="Microsoft SQL Server 2008 Analysis Services" HelpFile=""
/><Error ErrorCode="3240034310" Description="Errors in the OLAP storage
engine: The process operation ended because the number of errors encountered
during processing reached the defined limit of allowable errors for the
operation." Source="Microsoft SQL Server 2008 Analysis Services" HelpFile=""
/><Error ErrorCode="3239837698" Description="Server: The operation has been
cancelled." Source="Microsoft SQL Server 2008 Analysis Services" HelpFile=""
/><Error ErrorCode="3240034317" Description="Errors in the OLAP storage
engine: An error occurred while the 'Ip Address' attribute of the 'User
Session' dimension from the 'Datamine OLAP' database was being processed."
Source="Microsoft SQL Server 2008 Analysis Services" HelpFile="" /><Error
ErrorCode="3240034310" Description="Errors in the OLAP storage engine: The
process operation ended because the number of errors encountered during
processing reached the defined limit of allowable errors for the operation."
Source="Microsoft SQL Server 2008 Analysis Services" HelpFile="" /><Error
ErrorCode="3238002695" Description="Internal error: The operation terminated
unsuccessfully." Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" /><Error ErrorCode="3238002695" Description="Internal error: The
operation terminated unsuccessfully." Source="Microsoft SQL Server 2008
Analysis Services" HelpFile="" /><Error ErrorCode="3240034317"
Description="Errors in the OLAP storage engine: An error occurred while the
'Lead Sale Id' attribute of the 'Lead Assignment' dimension from the
'Datamine OLAP' database was being processed." Source="Microsoft SQL Server
2008 Analysis Services" HelpFile="" /><Error ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended
because the number of errors encountered during processing reached the
defined limit of allowable errors for the operation." Source="Microsoft SQL
Server 2008 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317"
Description="Errors in the OLAP storage engine: An error occurred while the
'Keyword Path' attribute of the 'PPC Keyword' dimension from the 'Datamine
OLAP' database was being processed." Source="Microsoft SQL Server 2008
Analysis Services" HelpFile="" /><Error ErrorCode="3240034310"
Description="Errors in the OLAP storage engine: The process operation ended
because the number of errors encountered during processing reached the
defined limit of allowable errors for the operation." Source="Microsoft SQL
Server 2008 Analysis Services" HelpFile="" /><Error ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services" HelpFile="" /><Error
ErrorCode="3238002695" Description="Internal error: The operation terminated
unsuccessfully." Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" /><Error Err... The step failed.


bha...@gmail.com

unread,
Jun 1, 2010, 2:39:38 PM6/1/10
to
I have had similar issues with SSAS 2005 & 2008 when running on the
same server, especially when the cube is large and the disk I/O is
saturated

In the data sources there is a "Maximum number of connections:" set by
default to 10 - Try reducing this to 1 or 2. It will slow the
processing down some, but make the processing more predictable.

I'm not sure if this is your issue, but it's an easy thing to try.

Bill

epdAaronK

unread,
Jun 1, 2010, 5:46:58 PM6/1/10
to
you should give more room to olap dude, I've had soooooo many failures
that just are an indication that I was starving analysis services for
physical memory.

I'd reccomend changing your SQL RDB to have 32gb limit while you're
processing cubes (and give 32gb to SSAS)

but it really depends on your cubes, your granularities, etc

Neeraj

unread,
Jun 4, 2010, 3:17:30 PM6/4/10
to
Thanks for your response.

Changing maximum number of connections to 2 did not work. I am sure that
server has around 10-12 GB RAM available all the time during cube processing.

Any other suggestions?


"bha...@gmail.com" wrote:

> .
>

bha...@gmail.com

unread,
Jun 7, 2010, 8:53:44 AM6/7/10
to
How much disk space do you have available?

Remember that the cube processing uses shadow copying and disk space
can get pinched before the cube finishes processing You should have
additional space for a complete processed cube free.

Bill

> > .- Hide quoted text -
>
> - Show quoted text -

Neeraj

unread,
Jun 7, 2010, 5:03:56 PM6/7/10
to
Thanks for your response again, Bill.
I suspect that to be the case. So I moved OLAP temp files to separate LUN of
approx. 140 GB disk space. But this change didn't help either.

Any other suggestions?

"bha...@gmail.com" wrote:

> .
>

bha...@gmail.com

unread,
Jun 9, 2010, 4:18:11 PM6/9/10
to
I think I'm out of ideas

Perhaps a hardware issue. It was a read error on:


\\?\K:\MSAS10.MSSQLSERVER\OLAP\Temp
\MSMDCacheRowset_1712_2ab8_jgw53.tmp,

Sorry I couldnt help.

Bill

grzegorz_s

unread,
Jul 9, 2010, 8:41:43 AM7/9/10
to
Hi!
I had similar problem.
I rebuilt problematic dimension. I used GUID as a key. Then I replaced
this key with integer identity column.

best regards
Grzegorz
[SQL Server MVP]

0 new messages