ETL jobs was in a running state & not changed to "F

tirumal_nit · Post by **tirumal_nit** » Tue Jun 16, 2009 12:37 am

Hi,

One of the ETL jobs was in a running state & not changed to "Finished" state even after completion of job. Due to this the job was not compiled in the batch & when it was triggered by the scheduler the batch job had failed.

Please suggest me what might be the reason caused this issue.

Thanks in advance.

ArndW · Post by **ArndW** » Tue Jun 16, 2009 1:51 am

Tirumal,

you need to supply more information and do some more diagnosis; it is impossible to guess what the cause might have been. Does this job use a database - if so, it could have been a lock & wait on the database.

chulett · Post by **chulett** » Tue Jun 16, 2009 5:24 am

Did you check at the O/S level for any processes associated with the job? Could it be the job was killed/died so hadn't reset the Status? If so, you'd need to use the Clear Status File option in the Director to 'fix' that.