Processing OLAP Cube causes OLAP and SQL to shut down

Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to th
e
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would fai
l
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before, bu
t
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.Yes! Resource contention. If you are trying to run 6 instances of SQL
Server and at least 1 Analysis Services server on only a two node cluster,
you most assuradely have resource contention and it is called MEMORY, which,
too, is most assuradely used during the building of the cube.
How much memory are you running on those two nodes? What is the MAX SERVER
MEMORY configuration set to on each of the instances? What is the setting
for the source of the OLAP cube? Anything short of about 512 MB to 1 GB for
each instances, plus about 1 GB for the Analysis Services, is under capacity
for any real use production system.
Do you have 6 to 12 or so GB on EACH node?
Sincerely,
Anthony Thomas
"TX_KniveS" <TX_KniveS@.discussions.microsoft.com> wrote in message
news:9C541BA2-E1B4-46C8-8F1D-3D1D145A622C@.microsoft.com...
Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to
the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would
fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before,
but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.

Processing OLAP Cube causes OLAP and SQL to shut down

Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before, but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.Yes! Resource contention. If you are trying to run 6 instances of SQL
Server and at least 1 Analysis Services server on only a two node cluster,
you most assuradely have resource contention and it is called MEMORY, which,
too, is most assuradely used during the building of the cube.
How much memory are you running on those two nodes? What is the MAX SERVER
MEMORY configuration set to on each of the instances? What is the setting
for the source of the OLAP cube? Anything short of about 512 MB to 1 GB for
each instances, plus about 1 GB for the Analysis Services, is under capacity
for any real use production system.
Do you have 6 to 12 or so GB on EACH node?
Sincerely,
Anthony Thomas
"TX_KniveS" <TX_KniveS@.discussions.microsoft.com> wrote in message
news:9C541BA2-E1B4-46C8-8F1D-3D1D145A622C@.microsoft.com...
Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to
the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would
fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before,
but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.

Processing of cube created via DSO in AS 2005 fails

We are testing an application originaly written for AS 2000 with AS

2005.
This application uses DSO from VB to create and process cubes. I have

gotten
over the major hurdles of getting DSO to work with AS 2005. However,

upon
creating of the cubes, I get errors processing it (even from

Management
Studio). Here's the code (abridged to remove error handling) that

we use to
create a cube:

Dim dsoCube As DSO.MDStore
Set

dsoCube = m_dsoDatabase.MDStores.AddNew(cubeName)

' set the cube's

description
dsoCube.Description = sCubeDesc

' set the cube's

datasource
dsoCube.DataSources.Add

m_dsoDatabase.DataSources(mvarDBName)

Dim dboStr As String

dboStr = sLQuote & "dbo" & sRQuote & "."
' set the source

table (fact table) for the cube
dsoCube.SourceTable = dboStr &

sLQuote & FACT_TABLE & sRQuote

dsoCube.EstimatedRows =

164558
' specify access permissions to the cube by adding roles to the

cube
Dim dsoCubeRole As DSO.role
Set dsoCubeRole =

dsoCube.Roles.AddNew("BSA Role")
dsoCubeRole.SetPermissions "Access",

"RW"

' create cube's measures
'
Dim dsoMeasure As

DSO.Measure
Set dsoCube = m_dsoDatabase.MDStores.Item(cubeName)

Set dsoMeasure = dsoCube.Measures.AddNew("BaseAmt")

' set the

measure's source column, data type and the formatting

dsoMeasure.SourceColumn = dsoCube.SourceTable & "." &

_
sLQuote & "baseamt" & sRQuote

dsoMeasure.SourceColumnType = adDouble
dsoMeasure.FormatString =

"Currency"
' this measure will be aggregated by summation

dsoMeasure.AggregateFunction = aggSum

Set dsoMeasure =

dsoCube.Measures.AddNew("Count")

' set the measure's source column,

data type and the formatting
dsoMeasure.SourceColumn =

dsoCube.SourceTable & "." & _
sLQuote

& "baseamt" & sRQuote
dsoMeasure.SourceColumnType =

adInteger
' this measure will be aggregated by summation

dsoMeasure.AggregateFunction = aggCount
Set dsoMeasure =

dsoCube.Measures.AddNew("TranNo")

' set the measure's source column,

data type and the formatting
dsoMeasure.SourceColumn =

dsoCube.SourceTable & "." & _
sLQuote

& "TranNo" & sRQuote
dsoMeasure.SourceColumnType =

adInteger

' this measure will be aggregated by summation

dsoMeasure.AggregateFunction = aggMax

' Create Calculated

members
Dim dsoCalculatedMember As DSO.Command
Set

dsoCalculatedMember = dsoCube.Commands.AddNew("CustAvgAmt")

' set the

command type
dsoCalculatedMember.CommandType = cmdCreateMember
'

set the MDX statement that defines the calculated member

dsoCalculatedMember.Statement = _
"Create Member Measures.[CustAvgAmt] As

" & _
"'avg({LastPeriods(3 ,

[bookdate].&[2003].&[4].&[10])},
measures.[baseamt])'"

Set dsoCalculatedMember = dsoCube.Commands.AddNew("CustAvgCnt")
' set the

command type
dsoCalculatedMember.CommandType = cmdCreateMember

' set the MDX statement that defines the calculated member

dsoCalculatedMember.Statement = _
"Create Member Measures.[CustAvgCnt] As

" & _
"'avg({LastPeriods(3 ,

[bookdate].&[2003].&[4].&[10])},
measures.[Count])'"

'

add the BookDate dimension
Dim dsoBookDateDim As DSO.Dimension
Set

dsoBookDateDim = dsoCube.Dimensions.AddNew("BookDate")

' add the

RecvPay dimension
Dim dsoRecvPayDim As DSO.Dimension
Set

dsoRecvPayDim = dsoCube.Dimensions.AddNew("RecvPay")

' get the list

of all tables used in this cube
' this list includes the fact table and

the dimension tables
' Note: Make sure that you do not repeat the same

table name twice.
dsoCube.FromClause = dsoCube.SourceTable & ", "

&
dsoBookDateDim.FromClause

dsoCube.joinClause =

dsoCube.joinClause & _
"(" & _
dboStr

& sLQuote & FACT_TABLE & sRQuote & "." & sLQuote

&
"bookdate" & sRQuote & _
" = " &

_
dboStr & sLQuote & "TblBookDate" & sRQuote &

"." & sLQuote &
"bookdate" & sRQuote & _

")"

dsoCube.SourceTableFilter = mvarFactTableFilter
' save the

cube definition in the metadata repository
dsoCube.Update

This

code runs fine, but during processing of the selected cube from
Management

Studio, the following error is displayed:
The Measures cube either does

not exist or has not been processed

There is no Measures cube, nor was

there ever. This does not happen when
processing cubes in AS 2000 or even in

AS 2005 if the cube was migrated from
AS 2000.

Can anybody help with

this?

Thanks in advance,
Boris Zakharin, MCAD
Metavante Risk and

Compliance

Hi Boris,

the problem is in the following line, which creates a calculated member. In AS2005 (as well as in AS2000) the member created in the cube scope should be prefixed with the cube name or CurrentCube, since Measures is the first name detected AS2005 treats it as a cube name. Pehaps AS2000 did not detected this error during the prosessing, but the calc member was disabled pr may be I'm wrong and CurrentCube was optional, but anyway, if you add CurrentCube to all calculated members it should start to process.

"Create Member Measures.[CustAvgAmt] As " & _
"'avg({LastPeriods(3 , [bookdate].&[2003].&[4].&[10])},
measures.[baseamt])'"

|||Thanks a lot, that worked

Processing of AS2005 cube from Integration Services package: Operation completed with 882 proble

Hi!

I did not now if I should post it in the Integration Services forum, but I believe this post is more AS related. Anyway, I am processing my cubes in SSIS after some loading of data. I use the SSIS log provider for SQL Server to log errors, and I get the following error message in the message column of a row in sysdtslog90:

"Server: Operation completed with 882 problems logged."

I wonder, where can I find this log? Is there some default location in AS or do I have to enable another log event than OnError or OnWarning in SSIS?

Thanks!

I'm guessing I'm looking for the Dimension key error log path when it is set for (default).

I found something here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1284202&SiteID=1

Seems like you have to set the location in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config\msmdsrv.ini. Now I get a key error logfile, but it is empty =/. I've restarted the AS service and set the ErrorLog elements in the ini to:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4</ErrorLogFileSize>
<KeyErrorAction>0</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>0</KeyErrorLimit>
<KeyErrorLimitAction>0</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>0</KeyDuplicate>
<NullKeyConvertedToUnknown>0</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

I've also tested the following without success:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4000000</ErrorLogFileSize>
<KeyErrorAction>1</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>1</KeyErrorLimit>
<KeyErrorLimitAction>1</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>1</KeyDuplicate>
<NullKeyConvertedToUnknown>1</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

More info here, but it does not get you that much wiser: http://technet.microsoft.com/en-us/library/ms174827.aspx

Seems like you do have to set the ErrorLog properties manually for each cube (Process > Change Settings > Use custom error configuration).

Processing measure groups together using same dimensions

Hi,

2 separate measure groups of a cube are being processed with 2 separate SSIS packages and these measure groups use same dimensions of the cube. SSIS packages are used to handle the partitions. Would there be a conflict if the SSIS packages both attempt to Process the same dimensions (update/full process) at the same time?

How does Analysis Services 2005 handle this? Does one wait for the other and then the 2nd package skips the Dim process or reprocesses it?

In such cases, is there a need to have a SSIS package that processes only the dimensions 1st and then the other 2 packages start off parallely to process the 2 measure groups without touching the dims.

Regards

You can process the dimension first in one step and after this processing have succeded you can process the two measure groups partitions in parallell.

Your last alternative sounds correct.

Regards

Thomas Ivarsson.

processing cube with partitions

Hi,

I have a cube with 2 partitions. Are these 2 partitions being processed everytime I have a ProcessData and Process Index? Coz i worry that if it's just processing 1 partition every time, i might have new data in one extraction that should reside in Partition 1 and another set of data (also in the same extraction) that reside on Partition 2.

cherriesh

If you are issuing your ProcessData and ProcessIndex commands against the cube, then it will cascade down and process all the partitions in that cube.|||

ic... but is there an option which partition i will just process?

cherriesh

|||Sure, you can process just one partition at a time (or multiple in parallel). There are multiple ways to do this. You can right click on a partition in SSMS and process it or you can build an XMLA command to process one or more partitions, you can do it from the partitions screen in BIDS.|||

is it a standard to just process only a partition of a cube every time (mine is partitioned based on This Year and Previous Years...) or by using Process Data and Process Index instead (meaning, process all)? What do you usually do?

|||

Usually you try to only process the smallest amount of data possible. I have done both extremes, sometimes I have to process the entire cube everytime, other times I only do a recent partition. It depends on the nature of the data and the source systems.

Note: ProcessData and ProcessIndex can be done at a partition level too. In fact when you do a process operation at the cube level, all that happens is that SSAS performs the specified processing command on each partition in the cube.

|||

Hi,

How to do it in the partition level?

thanks a lot!

cherriesh

|||

I don't have access to an Adventure Works database at the moment, so I don't know if the object Id's below are valid, but the basic structure of the XMLA command to process a partition would look like the following.

<Batch 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

xmlnsdl2=http://schemas.microsoft.com/analysisservices/2003/engine/2

xmlnsdl2_2=http://schemas.microsoft.com/analysisservices/2003/engine/2/2>

<Object>

<DatabaseID>Adventure Works DW</DatabaseID>

<CubeID>Adventure Works</CubeID>

<MeasureGroupID>Sales</MeasureGroupID>

<PartitionID>Sales 2003</PartitionID>

</Object>

<Type>ProcessFull</Type>

<WriteBackTableCreation>UseExisting</WriteBackTableCreation>

</Process>

</Parallel>

</Batch>

You can also navigate to the partition in the object browser in SSMS, right click on one and process it and you should be able to use the processing task in SSIS to do just a single partition. There are probably a couple of other methods of doing this too, essentially the all end up sending an XMLA command to the SSAS server. In my example I am using ProcessFull, but ProcessData and ProcessIndex will work at the partition level.

processing cube with partitions

Hi,

I have a cube with 2 partitions. Are these 2 partitions being processed everytime I have a ProcessData and Process Index? Coz i worry that if it's just processing 1 partition every time, i might have new data in one extraction that should reside in Partition 1 and another set of data (also in the same extraction) that reside on Partition 2.

cherriesh

If you are issuing your ProcessData and ProcessIndex commands against the cube, then it will cascade down and process all the partitions in that cube.|||

ic... but is there an option which partition i will just process?

cherriesh

|||Sure, you can process just one partition at a time (or multiple in parallel). There are multiple ways to do this. You can right click on a partition in SSMS and process it or you can build an XMLA command to process one or more partitions, you can do it from the partitions screen in BIDS.|||

is it a standard to just process only a partition of a cube every time (mine is partitioned based on This Year and Previous Years...) or by using Process Data and Process Index instead (meaning, process all)? What do you usually do?

|||

Usually you try to only process the smallest amount of data possible. I have done both extremes, sometimes I have to process the entire cube everytime, other times I only do a recent partition. It depends on the nature of the data and the source systems.

Note: ProcessData and ProcessIndex can be done at a partition level too. In fact when you do a process operation at the cube level, all that happens is that SSAS performs the specified processing command on each partition in the cube.

|||

Hi,

How to do it in the partition level?

thanks a lot!

cherriesh

|||

I don't have access to an Adventure Works database at the moment, so I don't know if the object Id's below are valid, but the basic structure of the XMLA command to process a partition would look like the following.

<Batch 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

xmlnsdl2=http://schemas.microsoft.com/analysisservices/2003/engine/2

xmlnsdl2_2=http://schemas.microsoft.com/analysisservices/2003/engine/2/2>

<Object>

<DatabaseID>Adventure Works DW</DatabaseID>

<CubeID>Adventure Works</CubeID>

<MeasureGroupID>Sales</MeasureGroupID>

<PartitionID>Sales 2003</PartitionID>

</Object>

<Type>ProcessFull</Type>

<WriteBackTableCreation>UseExisting</WriteBackTableCreation>

</Process>

</Parallel>

</Batch>

You can also navigate to the partition in the object browser in SSMS, right click on one and process it and you should be able to use the processing task in SSIS to do just a single partition. There are probably a couple of other methods of doing this too, essentially the all end up sending an XMLA command to the SSAS server. In my example I am using ProcessFull, but ProcessData and ProcessIndex will work at the partition level.

Processing Cube hangs

Hi,

I have a problem with processing my cube. My fact table (with telephone data) contains about 400,000 records... which is increasing rapidly (400,000 records is about 8 months of data)...
I have a few dimensions:
Dimension User: about 200 records
Dimension Line: about 200 records
Dimension Direction: 4 records
Dimension Date: 365 records for each year
Dimension TimeInterval: with 24 intervals

So far so good... when I process this dimension I have no problem....
However, when I add a dimension (CalledNumber, with exactly 101 records) the processing hangs as soon as it starts...

The SQL performed when processing the cube looks like this:
[CODE]
SELECT field1, field2,... fieldn
FROM table1, table2,.... tablem
WHERE
(table1.id=table2.table1id)
AND
(table2.id=table3.table2id)
...
[/CODE]

When I execute above SQL in the Query Analyser from SQL Server Enterprise Manager, it ALSO hangs...

I am not really suprised by that, because this SQL first create a huge table of 400,000 x 200 x 200 x 4 x 365 x 24 x 101 records and after that works through the WHERE statements to filter out the appropriate records.

for me it would be more logical to use the following code to process the cube, but that cannot be changed in Analysis Manager:
[CODE]
SELECT field1, field2,... fieldn
FROM table1
LEFT JOIN table2 ON (table1.id=table2.table1id)
....
LEFT JOIN tablem ON (tablem.id = tablem-1.tablemid)
[/CODE]

When I execute above SQL in the Query Analyser from SQL Servel Enterprise Manager, it does NOT hang, but performs the query in about 35 seconds....
But Analysis Manager does not allow me to change the SQL used for processing the cube...

What can I do to add more dimensions to my cube... (It will be more anyway after adding the CalledNumber dimension)?
any suggestions?

PS. forgot to mention: I use Sql Server 2000

For people who have the same problem... on another forum I got an answer (Thanks Darren Gosbell) which gave me the solution:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/olapdmad/agoptimizing_1qr7.asp

Processing cube from SSAS - OLE DB error

I have made a new dimension and setup the reference in dimension usage. Every time I process the cube i got the following message

Error 1 OLE DB error: OLE DB or ODBC error: Invalid column name 'PReference'.; 42S22. 0 0

The value in this column is 0,1 or 2. I have set the value in all rows to 1 and still get the same error.

I have tried to create a new column - updated value to 1 and refreshed the datasource and changed the dimension and dimension usage and I still got the same error processing the cube.

I have tried to use another integer field in dimension usage and this works fine.

Maybe it is something on the table - i have tried almost all but I can't solve this problem.

Leo Pedersen

The error message "Invalid column name 'PReference'" is saying that an invalid column name was specified in the SQL query that AS generated. Run Profiler on the AS server and capture the SQL query. It should point you to the problem.

Processing Cube error message?

Sorry about this "too stupid to live" type question, but I'm processing my first cube and I get the following error message: MdxScript(Manufacturing DM) (18,5) Parser: The syntax for "," is incorrect.

Dimensions are processed, it is working on a fact table. Where do I go to find a file that I might look for a bad comma?

(SQL Svr 2005 32bit w/sp 2, Vista Ultimate 32bit, Visual Studio w/ sp1)

Sorry, posted too soon....found my problem.....error in calculation code.....D'oh!!!

Processing cube error

Hi,
I have a small problem when trying to process the cubes in AS. We have a
datawarehouse and have done couple of cubes also. In the beginning the cubes
processed fine, but after a while I have begin to get lots of errors. The
error message is "The attribute key cannot be foun. The record was skipped
because the attribute key was not found". Its a clear message, but the
problem is that the key it gives can be found and exists in the database...
Could there be other reasons for this message?
Any ideas? Thanks in advance!are you processing your dimensions?
"beatmasta" <beatmasta@.discussions.microsoft.com> wrote in message
news:2731F26C-2DB8-40D0-B791-A4478D9F0813@.microsoft.com...
> Hi,
> I have a small problem when trying to process the cubes in AS. We have a
> datawarehouse and have done couple of cubes also. In the beginning the
> cubes
> processed fine, but after a while I have begin to get lots of errors. The
> error message is "The attribute key cannot be foun. The record was skipped
> because the attribute key was not found". Its a clear message, but the
> problem is that the key it gives can be found and exists in the
> database...
> Could there be other reasons for this message?
> Any ideas? Thanks in advance!|||Nope...
And yes, that was the problem! Thanks a lot for helping the noobie!

Processing cube automatically after ETL ends

Hi all,

We have an ETL process running at night and ending at the morning.

We want the system to automatically process a cube after ETL ends.

The ETL program is Infromatica and the server is Linux (Someone told me to use ascmd but it runs on windows server only so it won't work).

I really need a solution for this i order to automate our process.

Thanks in advance,

Ariel.

Could you create a wrapper web service for ascmd, and call it from Informatica?|||

If you are using the Enterprise edition you could also look at using proactive caching to detect when there have been changes to the underlying source data. It also has a silence interval parameter that allows SSAS to wait for a certain amount of silence (ie the ETL has finished) before commencing processing.

If you have HTTP connectivity enabled you could issue a direct xmla command to SSAS. There are some examples of using XMLA from javascript at http://www.activeinterface.com/thinolap.html

Otherwise John's idea of creating a web service wrapper is a good one.

Processing Cube

Hi,

Everyday I have a schedule job to processing the cubes, but I always receive the same error and then the Analysis Service will be stop. Here is the error msg from the Event Viewer:

Event Type: Error
Event Source: MSSQLServerOLAPService
Event Category: (256)
Event ID: 22
Date: 9/18/2007
Time: 5:03:38 AM
User: N/A
Computer: HODB04
Description:
The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: The following error occurred during a file operation: The process cannot access the file because it is being used by another process. . (\\?\z:\OLAP\data\DM_POS_V2.0.db\POS DM.558.cub\Fact Sales.591.det\FACT SALES F2008 P2.7.prt\55.agg.flex.data)..

Thanks,

I would reccomend you to investigate the storage subsystem (RAID).

I have almost the same problem - the source of it was in the configurationof the RAID controller.

|||

What modifications did you made to the raid config to make it run? Whe are just running two mirrored disks on a HP so there's not much to modify.

Processing after new data

I'm trying to build a cube in the "real world" for the first time. I had my fact table populated with one day's worth of data, set up my time dimension using named calculations based on a datetime within the DS View of the fact table (a la the Larsen book), then built and deployed and everything worked great.

However, when I added the next day's worth of data into the fact table and tried to get it to process incrementally (and then fully), the processing fails and it looks like it's complaining about those named calculations that worked so well on day one. Any thoughts on what I might be missing here? Thanks

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_fact_ALI, Column: YearOfBid, Value: 2006; Table: dbo_fact_ALI, Column: QuarterOfBid, Value: 2006Q2; Table: dbo_fact_ALI, Column: MonthOfBid, Value: 200607; Table: dbo_fact_ALI, Column: DayOfBid, Value: 20060702; Table: dbo_fact_ALI, Column: HourOfBid, Value: 00:00. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Time Key of Dimension: Dim Time from Database: ALI DM 2, Cube: ALI DM 2, Measure Group: Fact ALI, Partition: Fact ALI, Record: 577. 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. Errors in the OLAP storage engine: An error occurred while processing the 'Fact ALI' partition of the 'Fact ALI' measure group for the 'ALI DM 2' cube from the ALI DM 2 database.

You must process each dimension before the cube if you have updated your source system since the last day.

HTH

Thomas Ivarsson

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie

Processing a cube on SQL server 2005 from a dts package on SQL server 2000

We just started migrating some cubes to the 2005 platform. Still there are some DTS packages running on the 2000 platform that needs some recoding to fit the 2005 enviroment. Therefore we have some solutions where we have DTS packages running on SQL Server 2000 and their "related" cubes running on the 2005 platform.

My question is therefore: Is there an easy way to initiate a processing of a cube on the 2005 platform from a Sql server 2000 DTS package ?

Hmm seems that there are no easy way|||

Hello cgpl,

I think this may be of help to you: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=265208&SiteID=1

-Jamie

Processing a cube dimension

I am trying to process a time dimension on a cube and get the following error. Can some one please help. How can I fix this error?

Error 1 Errors related to feature availability and configuration: Exceeded the maximum number of partitions in a measure group. The installed server editions allows not more than 3 partitions and not more than 1 writeback partition. 0 0

That is the error if you try to use Standard Edition and partitioning.

Partitioning is an EE-only feature.

_-_-_ Dave

Processing a CUBE

Hi,

I have one doubt in my mind. If I build a cube on dt.st Oct. next time when in 1st Dec. I want to see the same cube with effect upto 1st Dec. do I need to process the cube in order to get effect till 1st Dec.?

Nilkanth Desai

If you have to add new data then yes have to prossess the cube, you can do a incremental process|||

Thanks for your reply.

Nilkanth

Processed Date for a Cube

Hi

I want to be able to display to the users the date/time a cube was last processed. We have SSAS 2005 and presenting the cube through Excel 2003 (with the SSAS 9 OLAP driver).

Thanks

LastProcessed is a property on the object avaliable only through AMO. Dont think Excel will show you this property.

You can possible wirte a AMO code yourself and use Excel programming model to show it.

Another way is to create a dimension with a single memeber based on the column in the relational database where you would keep the current date and during processing you update this dimension to pickup a new value.

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

|||

Thanks for the suggestions.

I created a table with the current date and use this.