 | |
Processing of Cubes/Dimension hangs
microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Processing of Cubes/Dimension hangs -
08-06-2004
, 07:26 PM
#2
| |||
| |||
|
|
Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup |
#3
| |||
| |||
|
|
-----Original Message----- No, that is called a "shadow" file. If your system already has a dimension or partition processed, then the new work is done in a shadow file (so the existing object is not effected while processing is happening). Then at commit time the old data is deleted and renaming is done. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:181401c47c15$33556b50$a301280a (AT) phx (DOT) gbl... Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup . |
#4
| |||
| |||
|
|
Hello Dave, My problem is not creation of the shadow files but the fact that during a process of the dimensions or cubes it stops after creating these shadow files. It does not move them into the actual files. In the processing window correpondingly i get a processing complete message , but do not get a transaction committed message, which i think is the last step. So why is it failing at this particular stage. It hangs there indefinitely with no changes to file system, no usage of cpu or memory. Could this be bcoz someone is accessing the actual dimn/cube ? Regards Anup -----Original Message----- No, that is called a "shadow" file. If your system already has a dimension or partition processed, then the new work is done in a shadow file (so the existing object is not effected while processing is happening). Then at commit time the old data is deleted and renaming is done. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:181401c47c15$33556b50$a301280a (AT) phx (DOT) gbl... Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup . |
#5
| |||
| |||
|
|
-----Original Message----- Yes. If you have an outstanding long-running query, then Analysis Services will wait for it to finish before it can commit. It is waiting for a quiet point to get an exclusive lock on the database. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:2c5801c47e29$d8076a20$a501280a (AT) phx (DOT) gbl... Hello Dave, My problem is not creation of the shadow files but the fact that during a process of the dimensions or cubes it stops after creating these shadow files. It does not move them into the actual files. In the processing window correpondingly i get a processing complete message , but do not get a transaction committed message, which i think is the last step. So why is it failing at this particular stage. It hangs there indefinitely with no changes to file system, no usage of cpu or memory. Could this be bcoz someone is accessing the actual dimn/cube ? Regards Anup -----Original Message----- No, that is called a "shadow" file. If your system already has a dimension or partition processed, then the new work is done in a shadow file (so the existing object is not effected while processing is happening). Then at commit time the old data is deleted and renaming is done. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:181401c47c15$33556b50$a301280a (AT) phx (DOT) gbl... Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup . . |
#6
| |||
| |||
|
|
Hi Dave, thanks for the info. I am facing this problem on a regular basis and as a result i am not able to finish processing my cubes. Where can i see the queries running on the db? on which db would it need an exclusive lock. the data source db? Well when i check in the enterprise mngr there r no processes running on that particular db. Also during processing, it processes for 4-5 dimensions and then it stops at the next one and hangs there indefinitely. Then i have to stop the analysis server. delete all the files created for that cube, start the service again and then process. This time it will process and may or may not get stuck again. How do i know the exact reason it is getting stuck. Could you suggest any logging methods, or something which i should be monitoring. Thanks Anup -----Original Message----- Yes. If you have an outstanding long-running query, then Analysis Services will wait for it to finish before it can commit. It is waiting for a quiet point to get an exclusive lock on the database. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:2c5801c47e29$d8076a20$a501280a (AT) phx (DOT) gbl... Hello Dave, My problem is not creation of the shadow files but the fact that during a process of the dimensions or cubes it stops after creating these shadow files. It does not move them into the actual files. In the processing window correpondingly i get a processing complete message , but do not get a transaction committed message, which i think is the last step. So why is it failing at this particular stage. It hangs there indefinitely with no changes to file system, no usage of cpu or memory. Could this be bcoz someone is accessing the actual dimn/cube ? Regards Anup -----Original Message----- No, that is called a "shadow" file. If your system already has a dimension or partition processed, then the new work is done in a shadow file (so the existing object is not effected while processing is happening). Then at commit time the old data is deleted and renaming is done. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:181401c47c15$33556b50$a301280a (AT) phx (DOT) gbl... Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup . . |
#7
| |||
| |||
|
|
-----Original Message----- Oh.. that is something different. I thought you said that it hangs all of the way at the end. So you have something like 5 dimensions which are being processed in the same transaction and it processes 3 OK and then hangs? Is it at random or always at the same spot/same dimension/ etc.? -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:52a801c480b5$b4fb71f0$a501280a (AT) phx (DOT) gbl... Hi Dave, thanks for the info. I am facing this problem on a regular basis and as a result i am not able to finish processing my cubes. Where can i see the queries running on the db? on which db would it need an exclusive lock. the data source db? Well when i check in the enterprise mngr there r no processes running on that particular db. Also during processing, it processes for 4-5 dimensions and then it stops at the next one and hangs there indefinitely. Then i have to stop the analysis server. delete all the files created for that cube, start the service again and then process. This time it will process and may or may not get stuck again. How do i know the exact reason it is getting stuck. Could you suggest any logging methods, or something which i should be monitoring. Thanks Anup -----Original Message----- Yes. If you have an outstanding long-running query, then Analysis Services will wait for it to finish before it can commit. It is waiting for a quiet point to get an exclusive lock on the database. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:2c5801c47e29$d8076a20$a501280a (AT) phx (DOT) gbl... Hello Dave, My problem is not creation of the shadow files but the fact that during a process of the dimensions or cubes it stops after creating these shadow files. It does not move them into the actual files. In the processing window correpondingly i get a processing complete message , but do not get a transaction committed message, which i think is the last step. So why is it failing at this particular stage. It hangs there indefinitely with no changes to file system, no usage of cpu or memory. Could this be bcoz someone is accessing the actual dimn/cube ? Regards Anup -----Original Message----- No, that is called a "shadow" file. If your system already has a dimension or partition processed, then the new work is done in a shadow file (so the existing object is not effected while processing is happening). Then at commit time the old data is deleted and renaming is done. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:181401c47c15$33556b50$a301280a (AT) phx (DOT) gbl... Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup . . . |
#8
| |||
| |||
|
|
Yes if a OLAP db has 5 cubes and 20 odd dimensions then it can hang for any of the dimensions or cubes. and the problem seems to be progressively getting worse and more regular. I earlier had this problem a month back, i dropped the entire olap db and recreated it, the problem did not surface. Now for the same db i am getting it on multiple dimensions and cubes. Deletion and recreation of the olap db does not seem to solve the problem. It can fail at the same dimension or a different one. Also one more thing i noticed is that it does not hang for a dimension which has few records (single digit records in the dimension table) but for those which have abt a thousand or more records. I have tried everything from reinstalling deletion and recreation of dimensions , cubes , olap dbs, to reinstalling ms sql analysis server.. No respite. can u tell em what happens during the commit transaction phase. why could it hang there ? Anup -----Original Message----- Oh.. that is something different. I thought you said that it hangs all of the way at the end. So you have something like 5 dimensions which are being processed in the same transaction and it processes 3 OK and then hangs? Is it at random or always at the same spot/same dimension/ etc.? -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:52a801c480b5$b4fb71f0$a501280a (AT) phx (DOT) gbl... Hi Dave, thanks for the info. I am facing this problem on a regular basis and as a result i am not able to finish processing my cubes. Where can i see the queries running on the db? on which db would it need an exclusive lock. the data source db? Well when i check in the enterprise mngr there r no processes running on that particular db. Also during processing, it processes for 4-5 dimensions and then it stops at the next one and hangs there indefinitely. Then i have to stop the analysis server. delete all the files created for that cube, start the service again and then process. This time it will process and may or may not get stuck again. How do i know the exact reason it is getting stuck. Could you suggest any logging methods, or something which i should be monitoring. Thanks Anup -----Original Message----- Yes. If you have an outstanding long-running query, then Analysis Services will wait for it to finish before it can commit. It is waiting for a quiet point to get an exclusive lock on the database. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:2c5801c47e29$d8076a20$a501280a (AT) phx (DOT) gbl... Hello Dave, My problem is not creation of the shadow files but the fact that during a process of the dimensions or cubes it stops after creating these shadow files. It does not move them into the actual files. In the processing window correpondingly i get a processing complete message , but do not get a transaction committed message, which i think is the last step. So why is it failing at this particular stage. It hangs there indefinitely with no changes to file system, no usage of cpu or memory. Could this be bcoz someone is accessing the actual dimn/cube ? Regards Anup -----Original Message----- No, that is called a "shadow" file. If your system already has a dimension or partition processed, then the new work is done in a shadow file (so the existing object is not effected while processing is happening). Then at commit time the old data is deleted and renaming is done. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:181401c47c15$33556b50$a301280a (AT) phx (DOT) gbl... Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup . . . |
#9
| |||
| |||
|
|
-----Original Message----- I thought you said that it *didn't* hang all of the way at the end. That it hung at random on one of the intermediate dimensions and/or cubes. I am confused. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:550601c480e9$303d5e40$a501280a (AT) phx (DOT) gbl... Yes if a OLAP db has 5 cubes and 20 odd dimensions then it can hang for any of the dimensions or cubes. and the problem seems to be progressively getting worse and more regular. I earlier had this problem a month back, i dropped the entire olap db and recreated it, the problem did not surface. Now for the same db i am getting it on multiple dimensions and cubes. Deletion and recreation of the olap db does not seem to solve the problem. It can fail at the same dimension or a different one. Also one more thing i noticed is that it does not hang for a dimension which has few records (single digit records in the dimension table) but for those which have abt a thousand or more records. I have tried everything from reinstalling deletion and recreation of dimensions , cubes , olap dbs, to reinstalling ms sql analysis server.. No respite. can u tell em what happens during the commit transaction phase. why could it hang there ? Anup -----Original Message----- Oh.. that is something different. I thought you said that it hangs all of the way at the end. So you have something like 5 dimensions which are being processed in the same transaction and it processes 3 OK and then hangs? Is it at random or always at the same spot/same dimension/ etc.? -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:52a801c480b5$b4fb71f0$a501280a (AT) phx (DOT) gbl... Hi Dave, thanks for the info. I am facing this problem on a regular basis and as a result i am not able to finish processing my cubes. Where can i see the queries running on the db? on which db would it need an exclusive lock. the data source db? Well when i check in the enterprise mngr there r no processes running on that particular db. Also during processing, it processes for 4-5 dimensions and then it stops at the next one and hangs there indefinitely. Then i have to stop the analysis server. delete all the files created for that cube, start the service again and then process. This time it will process and may or may not get stuck again. How do i know the exact reason it is getting stuck. Could you suggest any logging methods, or something which i should be monitoring. Thanks Anup -----Original Message----- Yes. If you have an outstanding long-running query, then Analysis Services will wait for it to finish before it can commit. It is waiting for a quiet point to get an exclusive lock on the database. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:2c5801c47e29$d8076a20$a501280a (AT) phx (DOT) gbl... Hello Dave, My problem is not creation of the shadow files but the fact that during a process of the dimensions or cubes it stops after creating these shadow files. It does not move them into the actual files. In the processing window correpondingly i get a processing complete message , but do not get a transaction committed message, which i think is the last step. So why is it failing at this particular stage. It hangs there indefinitely with no changes to file system, no usage of cpu or memory. Could this be bcoz someone is accessing the actual dimn/cube ? Regards Anup -----Original Message----- No, that is called a "shadow" file. If your system already has a dimension or partition processed, then the new work is done in a shadow file (so the existing object is not effected while processing is happening). Then at commit time the old data is deleted and renaming is done. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com wrote in message news:181401c47c15$33556b50$a301280a (AT) phx (DOT) gbl... Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup . . . . |
#10
| |||
| |||
|
|
It hangs any place anytime. The problem has been resolved now. It seems it was a memory issue. I had many cubes with many dimensions on that particular server. So the analysis service was using up all the allocated memory at startup and then it did not have memory left to process new dimensions. When only this particular cube is present on the server , the processing finishes in few minutes. So could u advice in a situation where i have many cubes and many dimensions (approx 6 olap dbs with 50 cubes per db and 30 shared dimensions per db) how best should i configure my system. Would using ROLAP instead of MOLAP be a better idea? The server has 2.6 GB of ram and the applications running are Analysis service and MS SQL server. Anup -----Original Message----- I thought you said that it *didn't* hang all of the way at the end. That it hung at random on one of the intermediate dimensions and/or cubes. I am confused. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:550601c480e9$303d5e40$a501280a (AT) phx (DOT) gbl... Yes if a OLAP db has 5 cubes and 20 odd dimensions then it can hang for any of the dimensions or cubes. and the problem seems to be progressively getting worse and more regular. I earlier had this problem a month back, i dropped the entire olap db and recreated it, the problem did not surface. Now for the same db i am getting it on multiple dimensions and cubes. Deletion and recreation of the olap db does not seem to solve the problem. It can fail at the same dimension or a different one. Also one more thing i noticed is that it does not hang for a dimension which has few records (single digit records in the dimension table) but for those which have abt a thousand or more records. I have tried everything from reinstalling deletion and recreation of dimensions , cubes , olap dbs, to reinstalling ms sql analysis server.. No respite. can u tell em what happens during the commit transaction phase. why could it hang there ? Anup -----Original Message----- Oh.. that is something different. I thought you said that it hangs all of the way at the end. So you have something like 5 dimensions which are being processed in the same transaction and it processes 3 OK and then hangs? Is it at random or always at the same spot/same dimension/ etc.? -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:52a801c480b5$b4fb71f0$a501280a (AT) phx (DOT) gbl... Hi Dave, thanks for the info. I am facing this problem on a regular basis and as a result i am not able to finish processing my cubes. Where can i see the queries running on the db? on which db would it need an exclusive lock. the data source db? Well when i check in the enterprise mngr there r no processes running on that particular db. Also during processing, it processes for 4-5 dimensions and then it stops at the next one and hangs there indefinitely. Then i have to stop the analysis server. delete all the files created for that cube, start the service again and then process. This time it will process and may or may not get stuck again. How do i know the exact reason it is getting stuck. Could you suggest any logging methods, or something which i should be monitoring. Thanks Anup -----Original Message----- Yes. If you have an outstanding long-running query, then Analysis Services will wait for it to finish before it can commit. It is waiting for a quiet point to get an exclusive lock on the database. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:2c5801c47e29$d8076a20$a501280a (AT) phx (DOT) gbl... Hello Dave, My problem is not creation of the shadow files but the fact that during a process of the dimensions or cubes it stops after creating these shadow files. It does not move them into the actual files. In the processing window correpondingly i get a processing complete message , but do not get a transaction committed message, which i think is the last step. So why is it failing at this particular stage. It hangs there indefinitely with no changes to file system, no usage of cpu or memory. Could this be bcoz someone is accessing the actual dimn/cube ? Regards Anup -----Original Message----- No, that is called a "shadow" file. If your system already has a dimension or partition processed, then the new work is done in a shadow file (so the existing object is not effected while processing is happening). Then at commit time the old data is deleted and renaming is done. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI SystemsTeam SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "Anup" <anonymous (AT) discussions (DOT) microsoft.com wrote in message news:181401c47c15$33556b50$a301280a (AT) phx (DOT) gbl... Sometimes when i process my cube/dimension it gives me the message processing completed successfully in the small window which opens and it hangs there. In a normal operation it should give this message and the next statement would be committing transaction in database successul and it would end. But in this case it does not commit the transaction and it hangs at the above state. This does not exit even after long time. At this time the stop button also does not work. Then i have to stop the analysis service an restart it. Sometimes if i again re process the same cubes/dimension the process completes otherwise i get the same problem. Deleting and recreating the cubes/dimensions does not seem to solve the problem. Now i noticed that the dimension for which the processing had hanged the .dim* files had a "'S" in front of it. for eg if the normal dimension file should have been time.dim* in this case it was time'S.dim* What could be the reason for this? Is this a bug? Anup . . . . |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.