Unlocking XMETA locks from jobs

-
How can I unlock an XMETA locked job?

The job cannot be exported and when attempting to open the job, the following error appears:

Unable to open the Job

The Job 'TestJob' is locked by user 'dsadm'
(SessionID '8F1B0326-4F7E-45A8-B8EC-EAA8C4780528')

Do you want to continue and open a read-only view of the Job?

Cause

This issue arises when a lock still remains in XMETA for the corresponding job. Information Server will lock the job to ensure that there is no indeterminancy regarding the editing and saving of a job.
The most common causes of this is when a user has closed a client window unexpectedly (e.g. Force Terminate).



Answer

To remove the lock on the job, the following steps need to be taken:
  • Check that another user has not left the job open accidentally. The same error appears if another user has opened the same job in a Designer or Director client.
  • Explore the following in Information Server web client (http://<server>:9080):
    1. Open Administration tab -> Session Management -> Active Sessions.
    2. Select the session with the same 'Session ID' as the message.
    3. Disconnect selected session.
  • Remove using cleanup_abandoned_locks.sh. This occurs if the session is no longer displayed but lock is remaining in the XMETALOCKINFO table in XMETA repository. To perform this:
    1. Login to domain layer using either root or Administrator user (for Windows)
    2. cd /opt/IBM/InformationServer/ASBServer/bin (C:\IBM\InformationServer\ASBServer\bin for Windowss)
    3. ./cleanup_abandoned_locks.sh -U <user> -P <password> (cleanup_abandoned_locks.bat -U <user> -P <password> for Windows)


    In this case, select a user with Suite Administrator privileges.

Source: http://www-01.ibm.com/support/docview.wss?uid=swg21469438

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more