IBM Support

DataStage jobs hung in a project in IBM InfoSphere DataStage

Troubleshooting


Problem

All DataStage jobs are hung in a project; they are running, but hung. The workaround is to reboot the server.

Cause

Possible causes include:

  • Excessive amount of files in &PH& directory for the project
  • Incorrect job status
  • Internal locks

Resolving The Problem

Check the following:

  • There is a &PH& directory in each DataStage project directory, which contains information about active stages that is used for diagnostic purposes. The &PH& directory is added to every time a job (both types: server and parallel/PX) is run, and needs periodic cleaning out.

    To clear the file from within DataStage:
    1. Ensure there are no DataStage jobs running anywhere on the system by running "ps -ef | grep DSD"
    2. From the DataStage Administrator, go to the Projects page, select the project whose file you want to clear and click the Command button. The Command Interface dialog box opens.
    3. Type the following into the command field: CLEAR.FILE &PH& (all uppercase)
    4. Click Execute to run the command and clear the file.

  • If the job processes have aborted, but the stattus indicates it is running this can be resolved by clearing the status of the job, check for locks, and then try running the job again.

    Clear Status file should be used only when the status of a job hangs in "running" status.

    To Clear the Status File of the job, from the DataStage Director, select the job and then click menu Job -> Clear Status File).

    If this menu is grayed out, you first need to "Enable job administration in Director" in your project from the DataStage Administrator, and restart your Director.

  • If you cannot clear the status file, please try checking/removing locks

    Here are two methods for checking/removing locks (you need only perform one method to remove the locks)

    From the DataStage (DS) clients:
    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 server:
    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. Run LIST.READU EVERY to list all the locks
    6. Check active record locks under "Item Id" column for job name or RT_CONFIG# or RT_LOG# (# matches the job description number)
    7. Write down the Inode numbers and user numbers associated with these locks
    8. Enter UNLOCK INODE inode# USER user# ALL
    9. You can use Q to get out of DataStage command line, e.g. ">" prompt

Related Information

Job administration

[{"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.1;8.7;8.5;8.1;8.0.1;7.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21390366

Page Feedback