We are using Ascential to pump bidirectional data between SAP ERP and warehouse. While a job that inserts replies to Oracle 9i DBMS, it gives warning message first then gets aborted, and I get the message :
Job XXXXXXXX must be reset before it can run.
and after that :
Attempting to Cleanup after ABORT raised in stage XXXXXXXX..AfterJob
where XXXXXXXX stands for the job name and that's all the info I can get.
Thank you for your concern,
Yours sincerely,
Job aborts after warning with no reason
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 8
- Joined: Thu Aug 16, 2007 12:52 am
Job aborts after warning with no reason
Kayhan YUKSEL
Re: ASCENTIAL DATASTAGE- JOB ABORTS AFTER WARNING WITH NO RE
That's because your job failed in the previous run. In order to run a again, the job must be in a runnable state. So, either you re-compile the job, or reset the job before you run it again.kayhanyuksel wrote: Job XXXXXXXX must be reset before it can run.
And BTW, welcome to the forum.
gateleys
-
- Premium Member
- Posts: 99
- Joined: Mon Sep 03, 2007 7:49 am
- Location: Stockholm, Sweden
In the log there will be a short message after you reset saying from previous run ... doubleclick on it and paste the response here. It may contain the reason for failure. Maybe you are using some pre-job routine or custom made code in jobcontrol....
-------------------------------------
http://it.toolbox.com/blogs/bi-aj
my blog on delivering business intelligence using agile principles
http://it.toolbox.com/blogs/bi-aj
my blog on delivering business intelligence using agile principles
-
- Participant
- Posts: 8
- Joined: Thu Aug 16, 2007 12:52 am
Re: ASCENTIAL DATASTAGE- JOB ABORTS AFTER WARNING WITH NO RE
First of all thank you, it is nice to be heard. I do reset & run but I am looking forward to find out a pattern , a reason for this problem and I want to fix it once forever, because of this problem I always have to keep an eye on Ascential, pushing my development jobs away.. IMHO, a successful system wouldn't need that.It should work like a charm.gateleys wrote:That's because your job failed in the previous run. In order to run a again, the job must be in a runnable state. So, either you re-compile the job, or reset the job before you run it again.kayhanyuksel wrote: Job XXXXXXXX must be reset before it can run.
And BTW, welcome to the forum.
Again thanks a lot for the quick response and warm welcome,
Yours sincerely,
Kayhan YUKSEL
Re: ASCENTIAL DATASTAGE- JOB ABORTS AFTER WARNING WITH NO RE
We could attempt to help you if you would provide the actual log for the job's failure. What you have posted is the log of an attempted run for a job that is in an aborted state. Now, just as stefanfrost1 suggested, can you first reset your job and provide us with the log from previous run?kayhanyuksel wrote: but I am looking forward to find out a pattern , a reason for this problem and I want to fix it once forever
gateleys
-
- Participant
- Posts: 8
- Joined: Thu Aug 16, 2007 12:52 am
Here is the line before the warning at the log : XXXXXXXX.YYYYYYY.DOCNUM_TO_HASHED: Write caching disabledstefanfrost1 wrote:In the log there will be a short message after you reset saying from previous run ... doubleclick on it and paste the response here. It may contain the reason for failure. Maybe you are using some pre-job routine or custom made code in jobcontrol....
and here is the line before the second warning :
XXXXXXXX.IDoc_XYVZ: Total rows read: 30 Total rows processed: 24
(there were massages regarding to SMTP etc. for mailing errors to people related to Ascential, I just skipped that)
pre-job routine is EXEC_DOS which is a built-in routine. It deletes a an empty file which works as a manually implamented lock mechanism. Other controls check if that file exists to proceed or not.
Jobcontrol tab was empty,
Yours sincerely,
Kayhan YUKSEL
-
- Participant
- Posts: 8
- Joined: Thu Aug 16, 2007 12:52 am
Re: ASCENTIAL DATASTAGE- JOB ABORTS AFTER WARNING WITH NO RE
The job that I am providing info is running now, I am just copy-pasting the log-info regarding to aborted run. Any other log info needed? I would like to provide any information you needed to resolve this.gateleys wrote:Now, just as stefanfrost1 suggested, can you first reset your job and provide us with the log from previous run?
Thanks a lot,
Kayhan YUKSEL