cancel
Showing results for 
Search instead for 
Did you mean: 

HANA model (Analytic view) is locked

prafful_agrawal
Explorer
0 Kudos

Hi All,

I am unable to edit HANA analytic view as it belongs to another user as per information messgae .Also i tried to take over the model back from user but no sucess.

Kindly suggest how to edit the model again.

Regards

PA

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member184768
Active Contributor
0 Kudos

Hi Prafful,

Can you please post the screenshot of the error message. Can you also check if the model is being edited by other user, if so ask the other user to close it. Many a times, closing the Analytic view and opening it again for editing helps.

Regards,

Ravi

prafful_agrawal
Explorer
0 Kudos

Hi Ravi,

Thanks for your response .

This model is locked from last couple of weeks & the user is locked out already. We have opened & close several times the hana studio but didn't get any sucess.

Please find the view snapshot

I am not able to take over the model back from user (318) because it is showing greyed

Is there any way to kill the entry in HANA like BW through t-code (sm12).

Kindly suggest.

Regards

PA

henrique_pinto
Active Contributor
0 Kudos

You can see existing locks (table, record, metadata) if you double click on the system (administration view) and go to the System Information tab, or look for the particular monitor view (http://help.sap.com/hana/html/monitor_views.html).

You cannot kill them, though, like in SM12, since it's merely a result set view from an internal control table. You'll need to find which is the process (thread) locking that particular object and kill the process, for example, using either one of these commands:

http://help.sap.com/hana/html/sql_alter_system_cancel_work.html (to kill a particular process in a particular session or the whole session)

or

http://help.sap.com/hana/html/sql_alter_system_disconnect.html (to kill the whole session)

But, back to your original problem, it does not seem to be a lock issue, but rather an object ownership issue. Apparently, the user had an inactive version (work in progress) prior to it being locked. I suppose you'll need to unlock that user and delete/activate any inactive versions (or try to take ownership again).