Regardnig the Cube Processing.

Hello Team,
When I tried to process the cube, am getting the folowing window, which shows the cube processing whch is in progress.
My Questions are
. What is the number which we can see as 9 of 13?. Why It is different for each partittion of one measure group?
. For few partitions, the Inprogress one's which we are getting as 9 or 13/12 or 13/7/200000?. What It doest meant for?

Hi,
This is the way that SSAS engine displays that Indexes are getting created.
Regards,
Venkata Koppula

Similar Messages

Regarding the tracking the live progress of the cube processing.

Hello,
Good Morning. As we are having multiple cube applicatons as part of our project, there are multiple cubes for which we need to evaluate the completion time for the cube processing.
By referencing one cube, the cube processing is taking one hour one day and some other day, It is taking an hour for completion. Beacuse of this reason, we could not be able to asses the time for completion of cube processing.
Is there any chance to track the live status of the cube processing?. Which means, the expected time for completion? How many measure group processing are completed and how many left?
Please provide your inputs on this.
Thanks in advance.
Regards,
Pradeep.

Hi Kumar,
According to your description, you want to monitor the progress of cube processing. Right?
In Analysis Services, there are several tools can help us monitor the processing performance, like SQL Profiler, AS Trace, Performance Monitor, etc. We can also use XMLA command or DMV to get the information. Please see:
Monitoring processing performance
Monitoring and Tuning Analysis Services with SQL Profiler
However, if you want to get the exact live data of the cube processing, Olaf's script can be an effective solution to get the current processing status for some measures or dimensions. But some information still can't be traced, like expected time for completion,
etc. So for your requirement, it can't be fully achieved.
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Is the cube processed after an OLS full optimization?

Version: OutlookSoft V4.2
Sometimes, the value in fact tables are not consistent with the values retrieved via Analysis Service. At this time, processing the cube in Analysis Service may solve the problem.
An OLS full optimization sum the data in 3 fact tables to one, and empty the other two. My question is if the cube is also processed in this operation.
Thanks,
Jason
Edited by: chaoloo on Apr 7, 2010 11:51 AM

HI,
This can happen when an administration process not finish properly. As you know the two of partions are MOLAP and those must be processed to see the data.
The optimization process is processing the partitions at the end.
Best regards,
Mihaela

SQL Server Profiler does not capture cube processing queries against the relational database

Hello, experts,
This my first attempt to use SQL Server Profiler to find out why my cube processing is so slow. Here is what I did:
My cube sources its data from a SQL Server database. While the cube processing is going, I launched the profiler connecting to the database engine (note: not the Analysis Services). I choose the "Tuning" template and started the trace. However,
I do not see any query activities (such as, SELECT DISTINCT ...) in the profiler trace window.
Did I do something wrong, or do I have the wrong expectation?
Thank you much in advance.

Hi QQFA,
Agree with Olaf.
Please make sure that you choose the appropriate events to monitor the cube processing queries when using SQL Server Profiler.
And I recommend you review the following links to get more information about tuning Analysis Services with SQL Profiler.
Monitoring and Tuning Analysis Services with SQL Profiler:
http://www.informit.com/articles/article.aspx?p=1745747
Analysis Services Trace Events:
http://msdn.microsoft.com/en-us/library/ms174867.aspx
Thanks,
Lydia Zhang

Is it mandatory to have OLAP cube processing feature in SCSM ??

Hi All,
We have SCSM 2012 R2 environment with SCSM DW component installed
can we disable the cube processing , if we are not using it ??
or by disabling it will it affect the reporting functionality
Thanks,
Kalai

Hi,
OLAP (Online Analytical Processing) cubes are a new feature in SCSM 2012 that leverage the existing Data Warehouse infrastructure to provide self-service Business Intelligence capabilities to the end user.
To get more details about OLAP cubes, you may go through the article below:
OLAP Cubes in the SCSM Data Warehouse: Introduction
http://blogs.technet.com/b/servicemanager/archive/2012/02/03/olap-cubes-in-the-scsm-data-warehouse-introduction.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Cube Processing - process Dimension before Measure Groups? How to?

Hi guys.
I noticed that when you choose "Process Cube", Measure groups are processed before Dimensions. Recently I ran into an issue caused by change in data that made the Process Cube job fail, - until I manually processed all Dimensions and then run the
"Process Cube" job again.
- Is there any way to configure it to process Dimensions before Measure Groups???
Cheers!

We use SSIS to automate the cube processing using XMLA scripts. We have a control table where we maintain the list of dimensions and measure group partitions which will be iterated upon and processed by SSIS. It will also log audit information like when
it was started, when it got ended and the process result.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Improve cube process time

Hi,
I am processing cube with process full. its taking around 15 mins. I planned to improve this by adding indexes to the database. I used SQL Trace while processing & later used the result to the database tuning advisor to get recommendations. I got the
recommendations & i have included those changes to the Database & then processed the cube but there is no improvement. I even tried to get the expensive queries from the trace & run in SSMS with Query execution plan but I am not able to figure
out. Please help.
Thanks
sush

Hi susheel1347,
According to your description, you want to improve the cube processing. Right?
In Analysis Services, cube processing is performed in Analysis Services by executing Analysis Services-generated SQL statements against the underlying relational database. Here we have some advices on improving the cube processing:
Use integer keys if at all possible
Use query binding to optimize processing
Partition measure groups if you have a lot of data
Use ProcessData and ProcessIndex instead of ProcessFull
For more information, please refer to links below:
SQL Server Best Practices Article
Improving cube processing time
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

Geeting an Collaxa Cube Exception while invoking the bpel process in 10g

Hi All,
While running my bpel process I'm getting an exception something like this. can anybody came across this type of exception. what it means
remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>when invoking locally the endpoint 'http://soclxs3ap19.localhost.com:7777/orabpel/default/CRMOnDemandEventProcessor/1.0', ; nested exception is:
     ORABPEL-00000
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "ORABPEL-09221
Cannot serialize DOM element.
Failed to serialize the DOM element "cd4f942ea8359f47:7f46d12c:136e194e429:2d1" to binary format. The exception reported is Cannot update document.
The process domain was unable to update/insert the document "cd4f942ea8359f47:7f46d12c:136e194e429:2d1" into the datastore. The exception reported is: ORA-01653: unable to extend table ORABPEL.XML_DOCUMENT by 8192 in tablespace ORABPEL
ORA-06512: at line 1
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
sql statement: BEGIN INSERT INTO xml_document ( dockey, domain_ref, bin_csize, bin_usize, bin_format, bin ) VALUES ( ?, ?, ?, ?, ?, empty_blob() ) RETURNING bin INTO ?; END;
     at com.collaxa.cube.xml.dom.SDOMHelper.saveNewNormalDocuments(SDOMHelper.java:329)
     at com.collaxa.cube.engine.delivery.DeliveryHelper.storeDocuments(DeliveryHelper.java:924)
     at com.collaxa.cube.engine.delivery.DeliveryHelper.storeHeaders(DeliveryHelper.java:960)
     at com.collaxa.cube.engine.adaptors.common.BaseDeliveryPersistenceAdaptor.storeInvoke(BaseDeliveryPersistenceAdaptor.java:1930)
     at com.collaxa.cube.engine.data.DeliveryPersistenceMgr.storeInvoke(DeliveryPersistenceMgr.java:467)
     at com.collaxa.cube.engine.delivery.DeliveryService.receiveInvoke(DeliveryService.java:463)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.receiveInvoke(CubeDeliveryBean.java:73)
     at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeDeliveryBean_LocalProxy_4bin6i8.receiveInvoke(Unknown Source)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialPostAnyType(DeliveryHandler.java:310)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialPost(DeliveryHandler.java:215)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.post(DeliveryHandler.java:87)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invokeLocalService(WSIFInvocationHandler.java:1338)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:287)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:528)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:285)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:829)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:412)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:199)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3714)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1657)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:317)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5787)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1089)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.__createAndInvoke(CubeEngineBean.java:127)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:170)
     at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:190)
     at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiresNewInterceptor.invoke(TxRequiresNewInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at CubeEngineBean_LocalProxy_4bin6i8.syncCreateAndInvoke(Unknown Source)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:549)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:465)
     at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:134)
     at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:95)
     at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
     at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:106)
     at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:69)
     at com.oracle.bpel.activation.SiebelActivationAgent.onHeartBeat(SiebelActivationAgent.java:173)
     at com.collaxa.cube.activation.HeartBeatListenerJob.execute(HeartBeatListenerJob.java:48)
     at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
     at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
Exception: ORABPEL-09221
Cannot serialize DOM element.
Failed to serialize the DOM element "cd4f942ea8359f47:7f46d12c:136e194e429:2d1" to binary format. The exception reported is Cannot update document.
The process domain was unable to update/insert the document "cd4f942ea8359f47:7f46d12c:136e194e429:2d1" into the datastore. The exception reported is: ORA-01653: unable to extend table ORABPEL.XML_DOCUMENT by 8192 in tablespace ORABPEL
ORA-06512: at line 1
In the BPEL process it looks everything is fine. Can anybody guide what should be done over here to get rid of this issue as it is very urgent.
Regards,
CH

CH,
The problem is with table space: "..unable to extend table ORABPEL.XML_DOCUMENT by 8192 in tablespace ORABPEL..."
Increase the table space for ORABPEL
Arik

Error in generating/deleting the index of the cube in Process chain

Hi All,
I am getting an error in the process chain during the deletion/generation of index in the cube....
error says: " Deleting/reconstructing indexes for InfoCube 0CSAL_C01 is not permitted "
Need your input for the same.....
Thanks & Regards,
Anup

Hi Anup,
Try to analyse the error in the manage tab of that cube, and try to do the reconstruction of indexes manually.
Good day!!!
Regards
Arun S

Error for the fact table while processing the cube - attribute key cannot be found when processing

Please help as I am new to SSAS and this is urgent requirement. This is a MOLAP cube and below is the error that I am receiving when processing the cube. The cube is set to Prrocess Full. Several similar errors are popped up for various dimensions.
"Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'Fact_Table', Column: 'ID', Value: '1'. The attribute is 'Id'. Errors in the OLAP storage engine: The attribute key was converted to an unknown member because
the attribute key was not found. Attribute Id of Dimension: 17 - Ves - PoC Cont from Database: DB, Cube: IPNCube, Measure Group: iSrvy, Partition: Partition1, Record: 1."
Thanks in advance.

Thanks for the recommendations David.
It will be really great if you can clear some of my doubts:
To my information, all the dimensions need to be processed first and then the fact table will be processed.
So if the ID's are not present in the dimension tables, then it should not be present in the Fact table either.
Here we found null values in the dimension table and the ID's were present in the Fact table. What might be the reasons causing such situation?
Also how frequently the cube needs to be processed? Currently the ETL which processes the cube, is scheduled in a SQL Job Agent on hourly basis everyday.
Is there any possibilty that the cube might be under processing state and the SQL job for the next run getting executed trying to access and process the cube while it was still processing?

Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.

Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.
I have dropped and recreated a fact table to refresh the data as the table is having identity columns. So not able to directly insert data. After that cube is throwing above error.
Please suggest.

Hi Md,
It hard to analyse the issue base on the limited information, Are there any error message on the log? Under C:\Program Files\Microsoft SQL Server\MSAS11.\OLAP\Log (this could be different for your server), there are 3 log files that are generated:
msmdrrv.log
FlightRecorderCurrent.trc
FightRecorderBack.trc
The msmdrrv.log simply points to the other two logs. There might be some detail information for this error. Please provide us the detail information about it, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Error occurred while processing the "sales" partition of the "sales" measure group in the cube

Hi
when i ran the job for processing the cube it showing the error like "error occurred while processing the sales partition of the sales measure group in the cube". but in log files no error massage was there. after get that error message we ran
the cube manually
at that time the cube executed successfully.
my aim when the job was run it will be process automatically but it is not like that.
can you suggest the solution.
thank you
satyak248

Hi Satyak248,
According to your description, you get the error when using Windows Task to process a cube on a schedule, however can process the cube on SSMS successful manually, right?
In your scenario, you can process the cube manually, the issue can be cause by Windows Task was not set correctly. So you can try to process the cube using SSIS package. The Analysis Services Processing Task in SQL Server Integration Services (SSIS) allows
for the processing of one to many to all Analysis Services objects in an SSIS package. Once the SSIS package is created, then a job can be created within the SQL Server Management Studio which will allow for scheduling.
http://www.mssqltips.com/sqlservertip/2994/configuring-the-analysis-services-processing-task-in-sql-server-2012-integration-services/
Regards,
Charlie Liao
TechNet Community Support

How to determine if in real time that the Cube is still processing by using DMV or MDX ?

Hi All,
I know that ther is no direct way of finding whether the cube is proceesing at the current instance with the help of MDX ot T-SQL(DMV).
Could any body please suggest alternatives for it for it.

Well, I put a measure in each measure group which is just getdate() on the sql side. This allows me to tell when a particular record was processed into the cube. I have aggregation set to max on this column as well. Not precisely
what you asked.
Are you processing using SSIS? You could always use the SSIS log tables.

"Transaction Errors : Aborting transaction on session " while processing the cube

HI Team,
Currently i have developed a cube and successfully deployed it in to the SSAS server.
But when i process the cube the measures in the cube got successfully processed. After that the process is still running and showing the status as "Transaction errors : aborting transaction on session XYZAB".
can you please guide me in solving this issue. The cube takes more than 6 hrs to process.
thanks in advance
baskar k

Hi,
I have Similar issue with 2005 and in 2005 I can't execute select * from $system.discover_sessions.
Do we have any other way to resolve it.
If I restart SSAS Server, It starts working fine and I cant restart at day time.
http://blogs.msdn.com/b/sql_pfe_blog/archive/2009/08/27/deadlock-troubleshooting-in-sql-server-analysis-services-ssas.aspx
Thanks Shiven:) If Answer is Helpful, Please Vote

Where is the subsequent processing of CUBE or DTP going to cube?

Hi guyz,
I'm looking for the subsequent process in the DTP or in the CUBE so that when a request or data is loaded in the cube an EVENT will be triggered.
Thank you!
Loed

Hi Loed
I assume you want to trigger an event once data is loaded to a cube/dso and other load should start after completion of this event.
For this you can first create one event from Tcode:SM64 (i.e ZTEST) in my case and use the same event in request tab of cube.
Click on Subsequent proc. below window will appear and mention same event name here. In this case once data load is complete for this cube then ZTEST event will be triggered on its own.
Use same event to triggere a process chain as below. In process chain start variant use ZTEST event.
Regards
Shabnam

Regardnig the Cube Processing.

Similar Messages

Maybe you are looking for