Hello:
The ETL job even after completion shows the status as "running" (in Datastage director client tool) instead of "finished" status? What is the reason for this?
Thanks in advance,
T.Vijay
ETL job status shows "running" after completion
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The client tool is accessing a record in a table into which the DataStage job records the status of the job and of the active stages in the job (the stage status can be viewed using the monitor).
If the job never got the opportunity to update this table (for example an after-job subroutine returned a non-zero ErrorCode, or the job aborted), then the status is never updated to Finished.
What evidence do you have to assert that the job has finished?
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
If the job never got the opportunity to update this table (for example an after-job subroutine returned a non-zero ErrorCode, or the job aborted), then the status is never updated to Finished.
What evidence do you have to assert that the job has finished?
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Beware that you can also have a long-running after-stage or after-jon subroutine that can cause the job finish to occur well after the final row has been processed.
Even DataStage itself can take a while to clean up, for example if you've been using write cache for large quantities of data in hashed files.
If you know none of these is the case, then you can check for processes running on the server. If the job process has finished you can reset or recompile the job or, as a last resort, clear its status file.
Even DataStage itself can take a while to clean up, for example if you've been using write cache for large quantities of data in hashed files.
If you know none of these is the case, then you can check for processes running on the server. If the job process has finished you can reset or recompile the job or, as a last resort, clear its status file.
A high volume of &PH& entries will cause jobs to take a long time to cleanup after completion. Back on releases 3.5 and 4 this could be quite lengthy, where a 20 second job could take 5-10 minutes to remove it's &PH& entry from a really full &PH& file.
Not knowing the release of DataStage, or the platform, makes it frustrating for the rest of us to troubleshoot questions, folks.
I'd suggest looking in the projects &PH& directory to see if there's a lot of old entries that have never been cleaned out.
Kenneth Bland
Not knowing the release of DataStage, or the platform, makes it frustrating for the rest of us to troubleshoot questions, folks.
I'd suggest looking in the projects &PH& directory to see if there's a lot of old entries that have never been cleaned out.
Kenneth Bland
T.Vijay
Kenneth is right even on Ds6 if a system is overloaded then it can take a few seconds or minutes to cleanup. May have to remove some temp files especially on a large number of rows. The database takes a long time to commit that amount of data. If it is a small process then you may have an issue or a bug.
Kim.
Kim Duke
DsWebMon - Monitor over the web
www.Duke-Consulting.com
Kenneth is right even on Ds6 if a system is overloaded then it can take a few seconds or minutes to cleanup. May have to remove some temp files especially on a large number of rows. The database takes a long time to commit that amount of data. If it is a small process then you may have an issue or a bug.
Kim.
Kim Duke
DsWebMon - Monitor over the web
www.Duke-Consulting.com