SSAS DB Synch job hanged - Profiler shows 'Lock Acquired' but no 'Lock released' -where is the problem?

Question

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.

Answer 1

Hi,

I went through the trace file in you previous post , the lock was release in that file and process. But still the synchronization went to time out issue.
So I tend to think the lock issue would not be the root cause for this hanging .
Could you post the whole trc file for this time ?

I would suggest you to open a ticket at MS support, who has more diagnose methods and more experience dealing with this kind of issue.

Regards,
Lukas

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

At the beginning of the file, the DB Object get locked and released 2 times. But in the end , suddenly no trace any more. I'm sorry, I could not find any clue of the hanging in the log.