SSAS DB synchronization job (using xmla via ssis) usually takes 30 minutes to complete, but is getting hanged for indefinite time until I terminate it forcefully. Even I terminate it, it do not release physical memory and also can not restart a manual synchronization ( via synchronization wizard). Only after ssas service restart, it releases the memory and I can initiate manual ssas DB synch and then it gets complete in normal time(30 min).
This issue was happening intermittently, but last 3 days it is occurring daily.
SQL profiler traces are showing that a 'Lock Acquired' statement (as below) to ssas DB object is there but NO corresponding 'Lock released' statement. I am not able to figure out why it is not there or it is not releasing the DB object. Below is 3 different lock I found exactly at the same time in profiler.
<LockList>
<Lock>
<Type>Write</Type>
<LockStatus>Acquired</LockStatus>
<Object>
<DatabaseID>ESS MOLAP ISSJMT</DatabaseID>
</Object>
<ObjectID>A1062EDC-A77B-45B9-B0E3-71873E820BBF</ObjectID>
</Lock>
</LockList>
------------------------------------------------------------------------------
<LockList>
<Lock>
<Type>Commit Write</Type>
<LockStatus>Acquired</LockStatus>
<Object>
<DatabaseID>ESS MOLAP ISSJMT</DatabaseID>
</Object>
<ObjectID>3BD7BEC7-B0E0-488C-AB8A-383434AD0DCB</ObjectID>
</Lock>
</LockList>
------------------------------------------------------------------------------
<LockList>
<Lock>
<Type>Write</Type>
<LockStatus>Acquired</LockStatus>
<Object>
<DatabaseID>ESS MOLAP ISSJMT</DatabaseID>
</Object>
<ObjectID>3BD7BEC7-B0E0-488C-AB8A-383434AD0DCB</ObjectID>
</Lock>
</LockList>
------------------------------------------------------------------------------
Can you please please help me to get what may be reason/solution?
Any comment will be helpful.