IBM Support

When running DataStage jobs, the status stayed in compiled status and nothing was written to the job log

Troubleshooting


Problem

When running DataStage jobs, they stayed in a compiled state, instead of showing running, and nothing was written to the detailed job log. This was happening for all the jobs in one project, but other projects were working successfully.

Symptom

When run the DataStage jobs, they stay in compiled status and nothing are written to the detail log.

Cause

Problem with the uvodbc.config file in the project directory.

Diagnosing The Problem

Check the files in &PH& for errors. The &PH& is a directory under the Project directory. If possible clear &PH& directory. See Technote: Commands to delete files in &PH& directories in IBM InfoSphere DataStage for more information. Otherwise you can run the job and the look at the timestamps to determine which file(s) is related to your job.

Looking at the files in the &PH& directory the following error was found:


DataStage/SQL: Failed to establish internal local connection.

Resolving The Problem

It was found that the localuv entry in the uvodbc.config file in the Project directory was incorrect.

  • The <localuv> entry is required and should look like:

    [ODBC DATA SOURCES]
    <localuv>
    DBMSTYPE = UNIVERSE
    network = TCP/IP
    service = uvserver
    host = 127.0.0.1

[{"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"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

swg21502454