Unable to save or import DataStage jobs into new project

Problem(Abstract)

Unable to save or import DataStage jobs into new project because of a locked folder. Received the following error:

Error: The Folder ‘\Jobs’ is locked by user ‘DataStageSystemUser’ (SessionId ‘#########’)

Symptom

Unable to save or import DataStage jobs into new project because of a locked folder. Received the following error:

Error: The Folder ‘\Jobs’ is locked by user ‘DataStageSystemUser’ (SessionId ‘#########’)

Users may also see the following error dialog when importing job:
Line 25536: The folder \Jobs\Base does not exist..
Object=ROOT..

Cause

Entries remain in XMETALOCKINFO table from when the project was created.

 

Diagnosing the problem

Log on to the XMETA Database to view the contents of the XMETALOCKINFO table using SQL*Plus, DB2 Client, Query Analyzer or another utility that allows you to execute SQL statements at command line.
SCHEMA: The schema of your install by default this is XMETA
SESSION_ID: The session ID reported in the error message.

  1. Check to see if specific lock still exists for the session_ID in error message by executing the following query:
    Select count(*) from SCHEMA.XMETALOCKINFO where LOCKED_BY_SESSION=’SESSION_ID
  2. Check total number of all locks in table, grouped by user by executing the following query:Select distinct LOCKED_BY_USER,count(*) from SCHEMA.XMETALOCKINFO group by LOCKED_BY_USER

Resolving the problem

 

  1. First try to clear the locks by running the script cleanup_abandoned_locks as a Suite Administrative user. The script can be found in the following location:Unix/Linux: <Install location>/ASBServer/bin/cleanup_abandoned_locks.sh
    Windows: <Install location>\ASBServer\bin\cleanup_abandoned_locks.bat
  2. If this is not successful delete the entries in the XMETALOCKINFO table by executing the following command:Delete * from SCHEMA.XMETALOCKINFO where LOCKED_BY_SESSION=’SESSION_ID
  3. Or you may also stop and restart WebSphere.