AS2005 September CTP Errors when Processing Cube

I have a cube which was originally created in the June 2005 CTP.

I have made no changes. I am just attempting to process it in the AS2005 September CTP.

I get random messages like this:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_PolicyFact, Column: PolicyDimKey, Value: 3135. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Policy Number of Dimension: PolicyA from Database: CDEV15D1, Cube: Cube, Measure Group: Policy Fact, Partition: Policy Fact, Record: 2920.

While trying to process various fact tables. Any ideas? I checked and the key relationships in the source store are all good.

Thanks,

ChrisI had the same problem. The cube processed fine on June CTP but would not process on the September CTP. I discovered my problem was due to the way dimension key errors were handled.

For the "key not found" option on the dimension key errors tab of the processing box, change the default setting from "Report and continue" to "Ignore".|||

Hi guys,

Thanks a ton for that input. Can you believe it! I am working on the Adventure works sample db and get the same error when processing a simple cube metioned in the tutorial.

I think this option was set to "Ignore" in the CTPs and then it gor switched back in the final release.

Thanks once again! Keep up the good work!!

AS2005 September CTP Errors when Processing Cube

I have a cube which was originally created in the June 2005 CTP.

I have made no changes. I am just attempting to process it in the AS2005 September CTP.

I get random messages like this:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_PolicyFact, Column: PolicyDimKey, Value: 3135. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Policy Number of Dimension: PolicyA from Database: CDEV15D1, Cube: Cube, Measure Group: Policy Fact, Partition: Policy Fact, Record: 2920.

While trying to process various fact tables. Any ideas? I checked and the key relationships in the source store are all good.

Thanks,

ChrisI had the same problem. The cube processed fine on June CTP but would not process on the September CTP. I discovered my problem was due to the way dimension key errors were handled.

For the "key not found" option on the dimension key errors tab of the processing box, change the default setting from "Report and continue" to "Ignore".|||

Hi guys,

Thanks a ton for that input. Can you believe it! I am working on the Adventure works sample db and get the same error when processing a simple cube metioned in the tutorial.

I think this option was set to "Ignore" in the CTPs and then it gor switched back in the final release.

Thanks once again! Keep up the good work!!

AS2005 September CTP Errors when Processing Cube

I have a cube which was originally created in the June 2005 CTP.

I have made no changes. I am just attempting to process it in the AS2005 September CTP.

I get random messages like this:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_PolicyFact, Column: PolicyDimKey, Value: 3135. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Policy Number of Dimension: PolicyA from Database: CDEV15D1, Cube: Cube, Measure Group: Policy Fact, Partition: Policy Fact, Record: 2920.

While trying to process various fact tables. Any ideas? I checked and the key relationships in the source store are all good.

Thanks,

ChrisI had the same problem. The cube processed fine on June CTP but would not process on the September CTP. I discovered my problem was due to the way dimension key errors were handled.

For the "key not found" option on the dimension key errors tab of the processing box, change the default setting from "Report and continue" to "Ignore".|||

Hi guys,

Thanks a ton for that input. Can you believe it! I am working on the Adventure works sample db and get the same error when processing a simple cube metioned in the tutorial.

I think this option was set to "Ignore" in the CTPs and then it gor switched back in the final release.

Thanks once again! Keep up the good work!!

AS2005 Redistributable DLLs

I am referencing Microsoft.AnalysisServices.dll in my C# project to get to the sweet AS2005 object model for automated cube processing among other things but know I need to start getting the deployment of these DLLs figured out for client releases. Currently our installs are deployed to relative paths on the client machines and we have avoided any GAC installations. So my questions revolve around - Are we free to redistribute the Microsoft.AnalysisServices.dll? What other dependencies does it have or redistribution requirements Microsoft may have for it

Thanks in advance for any help or if someone could point me into the correct direction

PS - I have been extremely impressed with the programmability and ease of deployment of AS2005 databases in these latest revs - well done, I am a huge fan of the toolset and the exposed technology.

Brad Osterloo

Probably Microsoft.AnalysisServices.XmlaClient.dll will be enough.|||

1. Microsoft.AnalysisServices.dll does't depends on Microsoft.AnalysisServices.XmlaClient.dll

2. If you want to have a compression in XMLA over TCP, your schould have msasxpress.dll

in %PROGRAMFILES%\Microsoft SQL Server\90\shared\

|||

It took me a bit while before I looked at your thread.

I would try and explan the general policy for redistibuting Analysis Services components:

You cannot redistibute any single file, or group of files with your application. It is going to create huge mess of files with different versions copied all over on user's machine. Also known as: "dll hell".

To redistribute Analysis Services functionlity you should use Redstributable packages found on http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

The one you need in this particular case is "Microsoft SQL Server 2005 Management Objects Collection "

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||OK, Thank you Edward for your response. Much appreciated.

AS2005 Cube Processing

I have problems with processing cubes on AS2005. I get this error message while processing:

Memory error: Allocation failure: Not enough storage is available to process this command. Error in the OLAP storage engine.

This machine has 6GB of memory and once it hits 3.5GB the processing stops. AWE is turned on.

I would appreciate, if anyone can help on this.

Thanks,

Gopal

Analysis Services is not AWE aware. So it can only use 2GB on a 32bit box (3GB if you have /3GB switch in boot.ini). Looks like the processing operation is running out of memory.

What are the number and sizes of dimension and partition tables? Do you have aggregations? Look at the processing log (in the process dialog) and find out what is the operation that causes out of memory - dimension processing, partition processing, building aggregations, etc.

This could also happen due to excessive parallelism. Try processing the dimensions and partitions individually.

|||

Thanks for your reply.

I managed to process the partitions and dimensions individually. That worked.

Gopal

|||

Hi.

Just a short question:

Is it really true that SSAS can use only 2GB RAM on a 32bit system? The technical reference for SQL Server 2005 Standard and Enterprise states that SQL Server can use the amount of RAM supported by the operating system which is 4GB for a Server 2003 Standard edition and 32GB for a Server 2003 Enterprise edition, both on 32bit systems. Does this apply only to the SQL Server Database Engine then and not the Analysis Services Server?

Regards

Kjetil

T.K. Anand wrote:

Analysis Services is not AWE aware. So it can only use 2GB on a 32bit box (3GB if you have /3GB switch in boot.ini). Looks like the processing operation is running out of memory.

What are the number and sizes of dimension and partition tables? Do you have aggregations? Look at the processing log (in the process dialog) and find out what is the operation that causes out of memory - dimension processing, partition processing, building aggregations, etc.

This could also happen due to excessive parallelism. Try processing the dimensions and partitions individually.

|||

In the 64-bit versions of Analysis Services...has this memory use limit been removed?

...cordell...

|||Yes - 64bit version doesn't have these limitations.

AS2005 Cube Processed "Successfully", But Data Not Refreshed

We process the cube automatically every night but the data isn't up-to-date despite a "successful" processing.

However, if I go onto the server and process the cube directly there through the BI Dev Studio, the data will finally get updated.

Similarly, if I try to process the cube from a client using Management Studio, it processes "successfully" as well, but the data is not updated.

I have to do it on the server itself. I've noticed this behavior the last few weeks, but it could very well have been going on for quite some time.

Any ideas or thoughts on this behavior?

What method you use in your processing automation?
Are you using SSIS processing Task?

Try and run SQL Server Profiler trace to capture Command Begin/End requests only and try to see if one is issued during your nightly processing job.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||I was told that we do indeed using SSIS Processing Task for the nightly cube processing automation.

I just ran a profile trace and I don't think I see any real difference in the Command Events whether I process the cube in the BI Dev Studio directly on the server or from SQL Management Studio from a client. However, the data is usually only updated if I do it on the server directly (and I always use the BI Dev Studio).

What should I be looking for in the trace?
|||I think I know what's going on. When I do it in the BI Dev Studio on the server, I'm essentially processing the solution as a whole. As a result, when the process screen comes up, the Type is database. If I processed the cube and not necessarily the entire solution, the Type is Cube.

I hope that make sense.

Which "should" be the correct one to use and what's the difference? It appears in our case, the "Database" type is correct.

|||

Can you connect using MDX Sample application?

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

AS2000. How to organize pocessing?

In AS 2000 I made update processing off all dimension and full processing of the last partition in every cube. I was made in a transaction. Duering processing the old version of data was available for the MDX querying.

If I do the same in AS 2000, the database seem to be locked.

What I make wrong?

Hiere is the xmla batch what I send to the AS2005.

<Batch Transaction="true" ProcessAffectedObjects="true" xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">

<Parallel>

<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<Object>

<DatabaseID>MW</DatabaseID>

<DimensionID>Abteilung</DimensionID>

</Object>

<Type>ProcessUpdate</Type>

</Process>

<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<Object>

<DatabaseID>MW</DatabaseID>

<DimensionID>Adm</DimensionID>

</Object>

<Type>ProcessUpdate</Type>

</Process>

<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<Object>

<DatabaseID>MW</DatabaseID>

<DimensionID>Artikel</DimensionID>

</Object>

<Type>ProcessUpdate</Type>

</Process>

<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<Object>

<DatabaseID>MW</DatabaseID>

<CubeID>Verkauf</CubeID>

<MeasureGroupID>Verkauf</MeasureGroupID>

<PartitionID>Verkauf_2006</PartitionID>

</Object>

<Type>ProcessFull</Type>

</Process>

<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<Object>

<DatabaseID>MW</DatabaseID>

<CubeID>Verkauf</CubeID>

<MeasureGroupID>VerkaufAuftrag</MeasureGroupID>

<PartitionID>VerkaufAuftrag_2006</PartitionID>

</Object>

<Type>ProcessFull</Type>

</Process>

<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<Object>

<DatabaseID>MW</DatabaseID>

<CubeID>Verkauf</CubeID>

<MeasureGroupID>VerkaufRechnung</MeasureGroupID>

<PartitionID>VerkaufRechnung_2006</PartitionID>

</Object>

<Type>ProcessFull</Type>

</Process>

<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">

<Object>

<DatabaseID>MW</DatabaseID>

<CubeID>Verkauf</CubeID>

<MeasureGroupID>VerkaufArtikel</MeasureGroupID>

<PartitionID>VerkaufArtikel_2006</PartitionID>

</Object>

<Type>ProcessFull</Type>

</Process>

</Parallel>

</Batch>

Do you mean "If I do the same in AS 2005, the database seem to be locked" ?

If this is related to Analysis Services 2005 behvior, this is strange. I think you should have access to product support. Please report this problem.

Thanks.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

AS2000 problem!

We are developing a As 2000 solution and when processing the cube we get an Eventlog message 'The memory conversation threshold was exceeded by more then 12,5% for an extended period'!

Does anyone have any idea about this problem/issue?

Larra

Try upgrading to Service Pack 4. There was a similar issue reported against AS2000 SP3 that was fixed in SP4.

http://www.microsoft.com/downloads/info.aspx?na=22&p=1&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFamilyID%3d8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5%26DisplayLang%3den

Hope that helps.

AS Processing Task

When using the AS processing task with a connection to "an Analysis Services project in this solution", only some processing options are available for processing dimensions. For instance, it is not possible to select "Process Update". Once I change the connection manager to point to the deployed cube database, I can choose from all the options. Is this by design?I have searched the documentation and the net for information on this. I have not been able to find an explanation. Anyone? At all?