Datastage Job xxx is being accessed by another user

-

DataStage Error:  Job xxx is being accessed by another user  

Take below steps to get rid of locks in datastage --

  • In web console check active sessions and if job is listed disconnect session.

    To view all active sessions:

    In the Web console, click the Administration tab.
    In the Navigation pane, select Session Management > Active Sessions

    The Active Sessions pane shows the users that are currently connected to the server.

  •  Check for and clear any Universe locks:
    From the DataStage (DS) Administrator:
    1. Launch DS Director
    2. Select Job > Cleanup Resources (if Cleanup Resources is disabled, go to step 10 below)
    3. In the Processes pane, click Show All
    4. In the Locks pane, click Show All
    5. In the Locks pane, scroll to the job name in the Item ID field
    6. Note the PID/User # associated with the job
    7. Click on the PID # in the upper pane (Processes)
    8. Click Show by process (Locks pane)
    9. Click Release All (Locks pane)
    10. Launch DS Administrator
    11. In the Projects tab, highlight the job
    12. Click Properties
    13. Check Enable job administration in Director
    14. Click OK
    15. Click Close
    16. Exit DS Director and relaunch
    17. Perform steps 3 - 9 above.

    From Unix/Linux:
    1. Log into the server using the dsadm user.
    2. cd to the DSEngine directory
    3. Enter . ./dsenv to source the dsenv file
    4. Enter ./bin/uvsh to get into DataStage prompt
    5. At ">" DataStage engine prompt, enter LOGTO project name
    6. Run LIST.READU EVERY to list all the locks
    7. Check active record locks under "Item Id" column for job name or RT_CONFIG# or RT_LOG# (# matches the job description number
    8. Write down the Inode numbers and user numbers associated with these locks.
    9. Enter LOGTO UV

      If the LOGTO command is disabled, enter this command

      "CHDIR <path_to_the_DSEngine_folder>"

      (with <path_to_the_DSEngine_folder>=cat /.dshome under a telnet session on the DataStage server).

      The UNLOCK command lives in UV account.
    10. Enter UNLOCK INODE inode# USER user# ALL
    11. You can use Q to get out of DataStage engine
    1. Use cleanup_abandoned_locks utility to clear any abandoned locks. The cleanup_abandoned_locks utility deletes session locks from the Information Server repository that were left over from some usage of an Information Server suite application (e.g. DataStage).

      Login to domain layer using either root or Administrator user (for Windows)

      cd /opt/IBM/InformationServer/ASBServer/bin

      ./cleanup_abandoned_locks.sh (on Unix/Linux)
      ./cleanup_abandoned_locks.bat (on Windows)

      usage: cleanup_abandoned_locks
      -P,--password Password
      -U,--user User name
      -h,--help Print this message.

    Popular posts from this blog

    cognos content store database tables

    -
    CMSYSPROPS This table has the Content Store Version. CMOBJNAMES This table has the names of all the objects in the content store. CMOBJPROPS1 Users, Roles \ Group Distribution list and contact information such as Email, phone number, Fax Given name etc are stored in this table. CMOBJPROPS2 Report scheduling information is stored. This table has fields like hour, day week etc CMOBJPROPS3 Stores Screen Tip and Object description provided while creating the objects are stored here CMOBJPROPS4 Stores the printer paper setting details like height and width of A3 , A4 , letter and 11X17 paper orientations CMOBJPROPS6 Has the details of the all packages which were published using the FM. CMOBJPROPS7 This table stores the XML of all reports and models. This is basically to maintain the metadata about the structure of the reports and models. CMOBJPROPS10 Contact information is stored in this table. This table has columns like Contact Email and C...
    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

    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