I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB running on Unix.
Is anyone aware of a issues with batches that never complete? I have a batch that was running a job that ran for way too long, but when the last job in the batch completed, the batch showed as still running. Attempts to stop the batch also failed. This happened once before, and the only way that I was able to kill the job (and do an export) was to do a "Save As" on the batch and delete the one that was running. Any ideas?
TIA,
jason
runaway batches
Hi Jason,
Ive had a similar experience with a never ending job run. What I do is select... clear job status for that particular job and then recompile it. Regards, Doris
Jason Mulvin wrote:
> I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB
> running on Unix.
>
> Is anyone aware of a issues with batches that never complete? I have
> a batch that was running a job that ran for way too long, but when the
> last job in the batch completed, the batch showed as still running.
> Attempts to stop the batch also failed. This happened once before,
> and the only way that I was able to kill the job (and do an export)
> was to do a "Save As" on the batch and delete the one that was
> running. Any ideas?
>
> TIA,
>
> jason
Ive had a similar experience with a never ending job run. What I do is select... clear job status for that particular job and then recompile it. Regards, Doris
Jason Mulvin wrote:
> I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB
> running on Unix.
>
> Is anyone aware of a issues with batches that never complete? I have
> a batch that was running a job that ran for way too long, but when the
> last job in the batch completed, the batch showed as still running.
> Attempts to stop the batch also failed. This happened once before,
> and the only way that I was able to kill the job (and do an export)
> was to do a "Save As" on the batch and delete the one that was
> running. Any ideas?
>
> TIA,
>
> jason
That worked.. Thanks!!!!
jason
-----Original Message-----
From: Doris Zammit [mailto:Doris.Zammit@oit.state.nj.us]
Sent: Tuesday, October 23, 2001 3:11 PM
To: datastage-users@oliver.com
Subject: Re: runaway batches
Hi Jason,
Ive had a similar experience with a never ending job run. What I do is select... clear job status for that particular job and then recompile it. Regards, Doris
Jason Mulvin wrote:
> I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB
> running on Unix.
>
> Is anyone aware of a issues with batches that never complete? I have
> a batch that was running a job that ran for way too long, but when the
> last job in the batch completed, the batch showed as still running.
> Attempts
to
> stop the batch also failed. This happened once before, and the only
> way that I was able to kill the job (and do an export) was to do a
> "Save As"
on
> the batch and delete the one that was running. Any ideas?
>
> TIA,
>
> jason
jason
-----Original Message-----
From: Doris Zammit [mailto:Doris.Zammit@oit.state.nj.us]
Sent: Tuesday, October 23, 2001 3:11 PM
To: datastage-users@oliver.com
Subject: Re: runaway batches
Hi Jason,
Ive had a similar experience with a never ending job run. What I do is select... clear job status for that particular job and then recompile it. Regards, Doris
Jason Mulvin wrote:
> I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB
> running on Unix.
>
> Is anyone aware of a issues with batches that never complete? I have
> a batch that was running a job that ran for way too long, but when the
> last job in the batch completed, the batch showed as still running.
> Attempts
to
> stop the batch also failed. This happened once before, and the only
> way that I was able to kill the job (and do an export) was to do a
> "Save As"
on
> the batch and delete the one that was running. Any ideas?
>
> TIA,
>
> jason
It now behoves you to analyse WHY your batches "never end". Do all the controlled jobs complete successfully? What else does your batch do? Can you code a timeout check near the end of the batch, that checks the status of all controlled jobs, and ends properly if they have all finished? (That it doesnt suggests some problem with the controlled jobs - child processes of the batch - notifying their parent process upon exit.)
-----Original Message-----
From: Jason Mulvin [mailto:jmulvin@fuse.net]
Sent: Wednesday, 24 October 2001 06:12
To: datastage-users@oliver.com
Subject: RE: runaway batches
That worked.. Thanks!!!!
jason
-----Original Message-----
From: Doris Zammit [mailto:Doris.Zammit@oit.state.nj.us]
Sent: Tuesday, October 23, 2001 3:11 PM
To: datastage-users@oliver.com
Subject: Re: runaway batches
Hi Jason,
Ive had a similar experience with a never ending job run. What I do is select... clear job status for that particular job and then recompile it. Regards, Doris
Jason Mulvin wrote:
> I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB
> running on Unix.
>
> Is anyone aware of a issues with batches that never complete? I have
> a batch that was running a job that ran for way too long, but when the
> last job in the batch completed, the batch showed as still running.
> Attempts
to
> stop the batch also failed. This happened once before, and the only
> way that I was able to kill the job (and do an export) was to do a
> "Save As"
on
> the batch and delete the one that was running. Any ideas?
>
> TIA,
>
> jason
-----Original Message-----
From: Jason Mulvin [mailto:jmulvin@fuse.net]
Sent: Wednesday, 24 October 2001 06:12
To: datastage-users@oliver.com
Subject: RE: runaway batches
That worked.. Thanks!!!!
jason
-----Original Message-----
From: Doris Zammit [mailto:Doris.Zammit@oit.state.nj.us]
Sent: Tuesday, October 23, 2001 3:11 PM
To: datastage-users@oliver.com
Subject: Re: runaway batches
Hi Jason,
Ive had a similar experience with a never ending job run. What I do is select... clear job status for that particular job and then recompile it. Regards, Doris
Jason Mulvin wrote:
> I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB
> running on Unix.
>
> Is anyone aware of a issues with batches that never complete? I have
> a batch that was running a job that ran for way too long, but when the
> last job in the batch completed, the batch showed as still running.
> Attempts
to
> stop the batch also failed. This happened once before, and the only
> way that I was able to kill the job (and do an export) was to do a
> "Save As"
on
> the batch and delete the one that was running. Any ideas?
>
> TIA,
>
> jason
Im experiencing the same problem over here, and I also do what Doris suggested -
"select... clear job status for that particular job and then recompile it"
This morning I ran a job that seemed to get stuck. I reset the job and ran it again, and it ran without any problems the 2nd time - strange. We all (accept for the systems administrator) have a feeling there is something wrong with the network, but we cant prove anything.
This used to happen a lot with the jobs I schedule. I increased my temp space (in the dsenv file) and the problem seems to be a lot better now.
Dirk
-----Original Message-----
From: Jason Mulvin [mailto:jmulvin@fuse.net]
Sent: Tuesday, October 23, 2001 8:53 PM
To: datastage-users@oliver.com
Subject: runaway batches
I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB running on Unix.
Is anyone aware of a issues with batches that never complete? I have a batch that was running a job that ran for way too long, but when the last job in the batch completed, the batch showed as still running. Attempts to stop the batch also failed. This happened once before, and the only way that I was able to kill the job (and do an export) was to do a "Save As" on the batch and delete the one that was running. Any ideas?
TIA,
jason
==========================================================
This message contains information intended for the perusal, and/or use (if so stated), by the stated addressee(s) only. The information is confidential and privileged. If you are not an intended recipient, do not peruse, use, disseminate, distribute, copy or in any manner rely upon the information contained in this message (directly or indirectly). The sender and/or the entity represented by the sender shall not be held accountable in the event that this prohibition is disregarded. If you receive this message in error, notify the sender immediately by e-mail, fax or telephone representations contained in this message, whether express or implied, are those of the sender only, unless that sender expressly states them to be the views or representations of an entity or person, who shall be named by the sender and who the sender shall state to represent. No liability shall otherwise attach to any other entity or person. ==========================================================
"select... clear job status for that particular job and then recompile it"
This morning I ran a job that seemed to get stuck. I reset the job and ran it again, and it ran without any problems the 2nd time - strange. We all (accept for the systems administrator) have a feeling there is something wrong with the network, but we cant prove anything.
This used to happen a lot with the jobs I schedule. I increased my temp space (in the dsenv file) and the problem seems to be a lot better now.
Dirk
-----Original Message-----
From: Jason Mulvin [mailto:jmulvin@fuse.net]
Sent: Tuesday, October 23, 2001 8:53 PM
To: datastage-users@oliver.com
Subject: runaway batches
I am currently using DataStage v4.2 on NT 4.0 with an Oracle DB running on Unix.
Is anyone aware of a issues with batches that never complete? I have a batch that was running a job that ran for way too long, but when the last job in the batch completed, the batch showed as still running. Attempts to stop the batch also failed. This happened once before, and the only way that I was able to kill the job (and do an export) was to do a "Save As" on the batch and delete the one that was running. Any ideas?
TIA,
jason
==========================================================
This message contains information intended for the perusal, and/or use (if so stated), by the stated addressee(s) only. The information is confidential and privileged. If you are not an intended recipient, do not peruse, use, disseminate, distribute, copy or in any manner rely upon the information contained in this message (directly or indirectly). The sender and/or the entity represented by the sender shall not be held accountable in the event that this prohibition is disregarded. If you receive this message in error, notify the sender immediately by e-mail, fax or telephone representations contained in this message, whether express or implied, are those of the sender only, unless that sender expressly states them to be the views or representations of an entity or person, who shall be named by the sender and who the sender shall state to represent. No liability shall otherwise attach to any other entity or person. ==========================================================