Job completes successfully , but is showing ABORTED

[kumarjit]

We have migrated a couple of jobs from our DEV environment to a NEW STAGE environment. The Hardware configurations of these two environments are identical.
Post deployment, we are facing the following problems :

a) Jobs which used to complete within an hour, are taking close to 10-12 hours to complete
b)There are jobs which is showing in ABORTED state(in the DESIGNER), but while referring the JOB MONITOR window it is showing to have completed successfully. For these jobs, there are NO LOG files generated in the DS director.


Can someone throw some light on the root causes of these issues, and help us mitigate these problems ?

Thanks
Kumarjit.

[ArndW]

The Job Monitor sometimes shows all "green" even when the job has aborted and is not to be trusted to always show this value correctly.

Is the job log for the aborted job always empty or just empty after an abort event?

[kumarjit]

Appreciate your response.

There are quite a few jobs which were in ABORTED state, some of them had logs created in teh Director , but suprisingly there is ONE specific job which had Aborted and NO LOG was created for it.

We didnt change any of the Design settings while migrating the jobs to the new environment.

Even as I said before , the jobs are MASSIVELY SLOW in the new environment , compared with the time they ran in , in the earlier environment.

Are we missing something ?

Thanks
Kumarjit.

[ray.wurlod]

What's different about the new environment that might be causing slowness? (Clearly "nothing" is not the correct answer.)

[ArndW]

Sometimes multinstance jobs and director log display don't get along and an instance of such a job might show empty. Is the job in question a multi-instance one?

[venkateshrupineni]

check that job(not able to view job log) log filter propertis has somebody may be changed for that job..check the job log options is there any auto purge or some one cleard the log.