I have two types of problem in datastage
job hangs and job locked
Some times the job hangs with out any reason.
Some times the the job control job hangs because the
called job has got exclusive lock
(cannot get exclusive access to job ).
what could be the possible solution for this?
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
Job Hangs and Job Lock
Sudhir
To be of any help, we are going to need more information.
What version of DataStage are you using?
Can you supply the message from the log file for the lock?
In the case of the hang, what does a monitor of the job show?
What kind of server are you running on?
-----Original Message-----
From: sudhir.mahendru@db.com [SMTP:sudhir.mahendru@db.com]
Sent: Thursday, 10 August 2000 12:12
To: informix-datastage@oliver.com
Subject: Job Hangs and Job Lock
I have two types of problem in datastage
job hangs and job locked
Some times the job hangs with out any reason.
Some times the the job control job hangs because the
called job has got exclusive lock
(cannot get exclusive access to job ).
what could be the possible solution for this?
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
To be of any help, we are going to need more information.
What version of DataStage are you using?
Can you supply the message from the log file for the lock?
In the case of the hang, what does a monitor of the job show?
What kind of server are you running on?
-----Original Message-----
From: sudhir.mahendru@db.com [SMTP:sudhir.mahendru@db.com]
Sent: Thursday, 10 August 2000 12:12
To: informix-datastage@oliver.com
Subject: Job Hangs and Job Lock
I have two types of problem in datastage
job hangs and job locked
Some times the job hangs with out any reason.
Some times the the job control job hangs because the
called job has got exclusive lock
(cannot get exclusive access to job ).
what could be the possible solution for this?
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
In this case will CLEAR.FILE DATA &PH& help
if i do it on regular basis does it have any impact on jobs please clarify
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
---------------------------------------- Message History ----------------------------------------
From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
Please respond to informix-datastage@oliver.com
To: informix-datastage@oliver.com
cc:
Subject: RE: Job Hangs and Job Lock
Job Hangs
As David pointed out, you can get more information about the actual status of each active stage in a job by using the Monitor. Choosing "show links" can provide more information. Double clicking on any line in the Monitor view will reveal the process ID associated with that active stage, which can be helpful when using the Job > Cleanup Resources option in Director. Occasionally a child process (e.g. active stage running DSD.StageRun) is unable to notify its parent (e.g. job running DSD.RUN) that it, the child process, has finished, leaving the job process awaiting notification. This will be clear from the Monitor, as all the active stages will have a status of Finished, but the jobs status will still be Running. In this case, you can clear the jobs status file reasonably safely.
Job Locks
Usually "cannot get exclusive access to job" indicates that another process, such as a DataStage client, has the job open in some kind of editor. For example, the Manager may have the job properties open, or the job may be open in Designer, or the job may be being monitored. What are your DataStage developers doing?
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 12:12
> To: informix-datastage@oliver.com
> Subject: Job Hangs and Job Lock
>
> I have two types of problem in datastage
> job hangs and job locked
> Some times the job hangs with out any reason.
> Some times the the job control job hangs because the
> called job has got exclusive lock
> (cannot get exclusive access to job ).
>
> what could be the possible solution for this?
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
if i do it on regular basis does it have any impact on jobs please clarify
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
---------------------------------------- Message History ----------------------------------------
From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
Please respond to informix-datastage@oliver.com
To: informix-datastage@oliver.com
cc:
Subject: RE: Job Hangs and Job Lock
Job Hangs
As David pointed out, you can get more information about the actual status of each active stage in a job by using the Monitor. Choosing "show links" can provide more information. Double clicking on any line in the Monitor view will reveal the process ID associated with that active stage, which can be helpful when using the Job > Cleanup Resources option in Director. Occasionally a child process (e.g. active stage running DSD.StageRun) is unable to notify its parent (e.g. job running DSD.RUN) that it, the child process, has finished, leaving the job process awaiting notification. This will be clear from the Monitor, as all the active stages will have a status of Finished, but the jobs status will still be Running. In this case, you can clear the jobs status file reasonably safely.
Job Locks
Usually "cannot get exclusive access to job" indicates that another process, such as a DataStage client, has the job open in some kind of editor. For example, the Manager may have the job properties open, or the job may be open in Designer, or the job may be being monitored. What are your DataStage developers doing?
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 12:12
> To: informix-datastage@oliver.com
> Subject: Job Hangs and Job Lock
>
> I have two types of problem in datastage
> job hangs and job locked
> Some times the job hangs with out any reason.
> Some times the the job control job hangs because the
> called job has got exclusive lock
> (cannot get exclusive access to job ).
>
> what could be the possible solution for this?
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
Job Hangs
As David pointed out, you can get more information about the actual status of each active stage in a job by using the Monitor. Choosing "show links" can provide more information. Double clicking on any line in the Monitor view will reveal the process ID associated with that active stage, which can be helpful when using the Job > Cleanup Resources option in Director. Occasionally a child process (e.g. active stage running DSD.StageRun) is unable to notify its parent (e.g. job running DSD.RUN) that it, the child process, has finished, leaving the job process awaiting notification. This will be clear from the Monitor, as all the active stages will have a status of Finished, but the jobs status will still be Running. In this case, you can clear the jobs status file reasonably safely.
Job Locks
Usually "cannot get exclusive access to job" indicates that another process, such as a DataStage client, has the job open in some kind of editor. For example, the Manager may have the job properties open, or the job may be open in Designer, or the job may be being monitored. What are your DataStage developers doing?
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 12:12
> To: informix-datastage@oliver.com
> Subject: Job Hangs and Job Lock
>
> I have two types of problem in datastage
> job hangs and job locked
> Some times the job hangs with out any reason.
> Some times the the job control job hangs because the
> called job has got exclusive lock
> (cannot get exclusive access to job ).
>
> what could be the possible solution for this?
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
As David pointed out, you can get more information about the actual status of each active stage in a job by using the Monitor. Choosing "show links" can provide more information. Double clicking on any line in the Monitor view will reveal the process ID associated with that active stage, which can be helpful when using the Job > Cleanup Resources option in Director. Occasionally a child process (e.g. active stage running DSD.StageRun) is unable to notify its parent (e.g. job running DSD.RUN) that it, the child process, has finished, leaving the job process awaiting notification. This will be clear from the Monitor, as all the active stages will have a status of Finished, but the jobs status will still be Running. In this case, you can clear the jobs status file reasonably safely.
Job Locks
Usually "cannot get exclusive access to job" indicates that another process, such as a DataStage client, has the job open in some kind of editor. For example, the Manager may have the job properties open, or the job may be open in Designer, or the job may be being monitored. What are your DataStage developers doing?
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 12:12
> To: informix-datastage@oliver.com
> Subject: Job Hangs and Job Lock
>
> I have two types of problem in datastage
> job hangs and job locked
> Some times the job hangs with out any reason.
> Some times the the job control job hangs because the
> called job has got exclusive lock
> (cannot get exclusive access to job ).
>
> what could be the possible solution for this?
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
CLEAR.FILE DATA &PH& is good maintenance practice, and will positively impact on performance, but will have no impact on locking/hanging processes.
&PH& contains the output logs for each phantom (background) process. Each job runs as a background process (executing the DSD.RUN program) and each independent active stage runs as a background process. Each keeps a record of its activities in &PH&. These are automatically cleaned up if the previous run was successful, but not otherwise. This means that, when you reset a job, you may get warning messages logged from phantom processes that were running stages that aborted. The message typically relates to the fact that the phantom process is cleaning up after an abort situation occurred.
In later releases of DataStage, a record is kept of the PID of each phantom process so that cleanup can be more comprehensive.
To determine exactly what is locked, you need to use the Cleanup Resources option in Director to identify which records/tables are locked in the
(Repository) database. This will provide the evidence that permits you to focus more closely on the cause of the locking problem that you have reported.
Have you involved Informix technical support? I am aware that they are sparsely staffed in Singapore where you are, but they can escalate to a regional support centre if needs be.
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 14:46
> To: informix-datastage@oliver.com
> Subject: RE: Job Hangs and Job Lock
>
> In this case will CLEAR.FILE DATA &PH& help
> if i do it on regular basis does it have any impact on jobs please
> clarify
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
> ---------------------------------------- Message History
> ----------------------------------------
>
>
> From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
>
> Please respond to informix-datastage@oliver.com
>
> To: informix-datastage@oliver.com
> cc:
> Subject: RE: Job Hangs and Job Lock
>
>
>
> Job Hangs
> As David pointed out, you can get more information about the actual
> status of each active stage in a job by using the Monitor. Choosing
> "show links" can provide more information. Double clicking on any
> line in the Monitor view will reveal the process ID associated with
> that active stage, which can be helpful when using the Job > Cleanup
> Resources option in Director. Occasionally a child process (e.g.
> active stage running DSD.StageRun) is unable to notify its parent
> (e.g. job running DSD.RUN) that it, the child process, has finished,
> leaving the job process awaiting notification. This
> will be clear from the Monitor, as all the active stages will have a
> status
> of Finished, but the jobs status will still be Running. In this case,
> you
> can clear the jobs status file reasonably safely.
>
> Job Locks
> Usually "cannot get exclusive access to job" indicates that another
> process, such as a DataStage client, has the job open in some kind of
> editor. For example, the Manager may have the job properties open, or
> the job may be
> open in Designer, or the job may be being monitored. What are your
> DataStage developers doing?
>
> > ----------
> > From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> > Reply To: informix-datastage@oliver.com
> > Sent: Thursday, 10 August 2000 12:12
> > To: informix-datastage@oliver.com
> > Subject: Job Hangs and Job Lock
> >
> > I have two types of problem in datastage
> > job hangs and job locked
> > Some times the job hangs with out any reason.
> > Some times the the job control job hangs because the
> > called job has got exclusive lock
> > (cannot get exclusive access to job ).
> >
> > what could be the possible solution for this?
> >
> > thanks and regards
> > Sudhir
> > APHOIT/CA$H Datawarehouse Team
> > (65) 423-7449
> >
> >
>
>
>
>
&PH& contains the output logs for each phantom (background) process. Each job runs as a background process (executing the DSD.RUN program) and each independent active stage runs as a background process. Each keeps a record of its activities in &PH&. These are automatically cleaned up if the previous run was successful, but not otherwise. This means that, when you reset a job, you may get warning messages logged from phantom processes that were running stages that aborted. The message typically relates to the fact that the phantom process is cleaning up after an abort situation occurred.
In later releases of DataStage, a record is kept of the PID of each phantom process so that cleanup can be more comprehensive.
To determine exactly what is locked, you need to use the Cleanup Resources option in Director to identify which records/tables are locked in the
(Repository) database. This will provide the evidence that permits you to focus more closely on the cause of the locking problem that you have reported.
Have you involved Informix technical support? I am aware that they are sparsely staffed in Singapore where you are, but they can escalate to a regional support centre if needs be.
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 14:46
> To: informix-datastage@oliver.com
> Subject: RE: Job Hangs and Job Lock
>
> In this case will CLEAR.FILE DATA &PH& help
> if i do it on regular basis does it have any impact on jobs please
> clarify
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
> ---------------------------------------- Message History
> ----------------------------------------
>
>
> From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
>
> Please respond to informix-datastage@oliver.com
>
> To: informix-datastage@oliver.com
> cc:
> Subject: RE: Job Hangs and Job Lock
>
>
>
> Job Hangs
> As David pointed out, you can get more information about the actual
> status of each active stage in a job by using the Monitor. Choosing
> "show links" can provide more information. Double clicking on any
> line in the Monitor view will reveal the process ID associated with
> that active stage, which can be helpful when using the Job > Cleanup
> Resources option in Director. Occasionally a child process (e.g.
> active stage running DSD.StageRun) is unable to notify its parent
> (e.g. job running DSD.RUN) that it, the child process, has finished,
> leaving the job process awaiting notification. This
> will be clear from the Monitor, as all the active stages will have a
> status
> of Finished, but the jobs status will still be Running. In this case,
> you
> can clear the jobs status file reasonably safely.
>
> Job Locks
> Usually "cannot get exclusive access to job" indicates that another
> process, such as a DataStage client, has the job open in some kind of
> editor. For example, the Manager may have the job properties open, or
> the job may be
> open in Designer, or the job may be being monitored. What are your
> DataStage developers doing?
>
> > ----------
> > From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> > Reply To: informix-datastage@oliver.com
> > Sent: Thursday, 10 August 2000 12:12
> > To: informix-datastage@oliver.com
> > Subject: Job Hangs and Job Lock
> >
> > I have two types of problem in datastage
> > job hangs and job locked
> > Some times the job hangs with out any reason.
> > Some times the the job control job hangs because the
> > called job has got exclusive lock
> > (cannot get exclusive access to job ).
> >
> > what could be the possible solution for this?
> >
> > thanks and regards
> > Sudhir
> > APHOIT/CA$H Datawarehouse Team
> > (65) 423-7449
> >
> >
>
>
>
>
Sudhir,
In my references to the &PH& directory, I wasnt suggesting that there is a problem here that needs addressing, but rather, that these work files might contain a clue as to what is wrong with your job that keeps hanging.
Are you able to tell from Unix if the hanging job is using CPU (eg endless
loop) or not (eg waiting on something)?
David
-----Original Message-----
From: sudhir.mahendru@db.com [SMTP:sudhir.mahendru@db.com]
Sent: Thursday, 10 August 2000 14:47
To: informix-datastage@oliver.com
Subject: RE: Job Hangs and Job Lock
In this case will CLEAR.FILE DATA &PH& help
if i do it on regular basis does it have any impact on jobs
please clarify
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
---------------------------------------- Message History
----------------------------------------
From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
Please respond to informix-datastage@oliver.com
To: informix-datastage@oliver.com
cc:
Subject: RE: Job Hangs and Job Lock
Job Hangs
As David pointed out, you can get more information about the actual status
of each active stage in a job by using the Monitor. Choosing "show links"
can provide more information. Double clicking on any line in the Monitor
view will reveal the process ID associated with that active stage, which can
be helpful when using the Job > Cleanup Resources option in Director.
Occasionally a child process (e.g. active stage running
DSD.StageRun) is
unable to notify its parent (e.g. job running DSD.RUN) that it, the child
process, has finished, leaving the job process awaiting notification. This
will be clear from the Monitor, as all the active stages will have a status
of Finished, but the jobs status will still be Running. In this case, you
can clear the jobs status file reasonably safely.
Job Locks
Usually "cannot get exclusive access to job" indicates that another process,
such as a DataStage client, has the job open in some kind of editor.
For example, the Manager may have the job properties open, or the job may be
open in Designer, or the job may be being monitored. What are your
DataStage developers doing?
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 12:12
> To: informix-datastage@oliver.com
> Subject: Job Hangs and Job Lock
>
> I have two types of problem in datastage
> job hangs and job locked
> Some times the job hangs with out any reason.
> Some times the the job control job hangs because the
> called job has got exclusive lock
> (cannot get exclusive access to job ).
>
> what could be the possible solution for this?
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
In my references to the &PH& directory, I wasnt suggesting that there is a problem here that needs addressing, but rather, that these work files might contain a clue as to what is wrong with your job that keeps hanging.
Are you able to tell from Unix if the hanging job is using CPU (eg endless
loop) or not (eg waiting on something)?
David
-----Original Message-----
From: sudhir.mahendru@db.com [SMTP:sudhir.mahendru@db.com]
Sent: Thursday, 10 August 2000 14:47
To: informix-datastage@oliver.com
Subject: RE: Job Hangs and Job Lock
In this case will CLEAR.FILE DATA &PH& help
if i do it on regular basis does it have any impact on jobs
please clarify
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
---------------------------------------- Message History
----------------------------------------
From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
Please respond to informix-datastage@oliver.com
To: informix-datastage@oliver.com
cc:
Subject: RE: Job Hangs and Job Lock
Job Hangs
As David pointed out, you can get more information about the actual status
of each active stage in a job by using the Monitor. Choosing "show links"
can provide more information. Double clicking on any line in the Monitor
view will reveal the process ID associated with that active stage, which can
be helpful when using the Job > Cleanup Resources option in Director.
Occasionally a child process (e.g. active stage running
DSD.StageRun) is
unable to notify its parent (e.g. job running DSD.RUN) that it, the child
process, has finished, leaving the job process awaiting notification. This
will be clear from the Monitor, as all the active stages will have a status
of Finished, but the jobs status will still be Running. In this case, you
can clear the jobs status file reasonably safely.
Job Locks
Usually "cannot get exclusive access to job" indicates that another process,
such as a DataStage client, has the job open in some kind of editor.
For example, the Manager may have the job properties open, or the job may be
open in Designer, or the job may be being monitored. What are your
DataStage developers doing?
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 12:12
> To: informix-datastage@oliver.com
> Subject: Job Hangs and Job Lock
>
> I have two types of problem in datastage
> job hangs and job locked
> Some times the job hangs with out any reason.
> Some times the the job control job hangs because the
> called job has got exclusive lock
> (cannot get exclusive access to job ).
>
> what could be the possible solution for this?
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in
error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
I have found following observation in &PH&, for all the jobs which complete successfull I get this kind of message message.
DataStage Job 701 Phantom 26099
Program "DSD.RUN": Line 274, Nonnumeric data when numeric required. Zero used. DataStage Phantom Finished
( the middle line is coming in all the logs )
and the job which hangs have the message as
DataStage Job 996 Phantom 21258
Program "DSD.RUN": Line 274, Nonnumeric data when numeric required. Zero used.
please advice as early as possible.
regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
---------------------------------------- Message History ----------------------------------------
From: David.Barham@anglocoal.com.au on 10/08/2000 05:32 GMT
Please respond to informix-datastage@oliver.com
To: informix-datastage@oliver.com
cc:
Subject: RE: Job Hangs and Job Lock
Sudhir,
In my references to the &PH& directory, I wasnt suggesting that there is a problem here that needs addressing, but rather, that these work files might contain a clue as to what is wrong with your job that keeps hanging.
Are you able to tell from Unix if the hanging job is using CPU (eg endless
loop) or not (eg waiting on something)?
David
-----Original Message-----
From: sudhir.mahendru@db.com [SMTP:sudhir.mahendru@db.com]
Sent: Thursday, 10 August 2000 14:47
To: informix-datastage@oliver.com
Subject: RE: Job Hangs and Job Lock
In this case will CLEAR.FILE DATA &PH& help
if i do it on regular basis does it have any impact on jobs
please clarify
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
---------------------------------------- Message History
----------------------------------------
From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
Please respond to informix-datastage@oliver.com
To: informix-datastage@oliver.com
cc:
Subject: RE: Job Hangs and Job Lock
Job Hangs
As David pointed out, you can get more information about the actual status
of each active stage in a job by using the Monitor. Choosing "show links"
can provide more information. Double clicking on any line in the Monitor
view will reveal the process ID associated with that active stage, which can
be helpful when using the Job > Cleanup Resources option in Director.
Occasionally a child process (e.g. active stage running
DSD.StageRun) is
unable to notify its parent (e.g. job running DSD.RUN) that it, the child
process, has finished, leaving the job process awaiting notification. This
will be clear from the Monitor, as all the active stages will have a status
of Finished, but the jobs status will still be Running. In this case, you
can clear the jobs status file reasonably safely.
Job Locks
Usually "cannot get exclusive access to job" indicates that another process,
such as a DataStage client, has the job open in some kind of editor.
For example, the Manager may have the job properties open, or the job may be
open in Designer, or the job may be being monitored. What are your
DataStage developers doing?
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 12:12
> To: informix-datastage@oliver.com
> Subject: Job Hangs and Job Lock
>
> I have two types of problem in datastage
> job hangs and job locked
> Some times the job hangs with out any reason.
> Some times the the job control job hangs because the
> called job has got exclusive lock
> (cannot get exclusive access to job ).
>
> what could be the possible solution for this?
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************
DataStage Job 701 Phantom 26099
Program "DSD.RUN": Line 274, Nonnumeric data when numeric required. Zero used. DataStage Phantom Finished
( the middle line is coming in all the logs )
and the job which hangs have the message as
DataStage Job 996 Phantom 21258
Program "DSD.RUN": Line 274, Nonnumeric data when numeric required. Zero used.
please advice as early as possible.
regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
---------------------------------------- Message History ----------------------------------------
From: David.Barham@anglocoal.com.au on 10/08/2000 05:32 GMT
Please respond to informix-datastage@oliver.com
To: informix-datastage@oliver.com
cc:
Subject: RE: Job Hangs and Job Lock
Sudhir,
In my references to the &PH& directory, I wasnt suggesting that there is a problem here that needs addressing, but rather, that these work files might contain a clue as to what is wrong with your job that keeps hanging.
Are you able to tell from Unix if the hanging job is using CPU (eg endless
loop) or not (eg waiting on something)?
David
-----Original Message-----
From: sudhir.mahendru@db.com [SMTP:sudhir.mahendru@db.com]
Sent: Thursday, 10 August 2000 14:47
To: informix-datastage@oliver.com
Subject: RE: Job Hangs and Job Lock
In this case will CLEAR.FILE DATA &PH& help
if i do it on regular basis does it have any impact on jobs
please clarify
thanks and regards
Sudhir
APHOIT/CA$H Datawarehouse Team
(65) 423-7449
---------------------------------------- Message History
----------------------------------------
From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
Please respond to informix-datastage@oliver.com
To: informix-datastage@oliver.com
cc:
Subject: RE: Job Hangs and Job Lock
Job Hangs
As David pointed out, you can get more information about the actual status
of each active stage in a job by using the Monitor. Choosing "show links"
can provide more information. Double clicking on any line in the Monitor
view will reveal the process ID associated with that active stage, which can
be helpful when using the Job > Cleanup Resources option in Director.
Occasionally a child process (e.g. active stage running
DSD.StageRun) is
unable to notify its parent (e.g. job running DSD.RUN) that it, the child
process, has finished, leaving the job process awaiting notification. This
will be clear from the Monitor, as all the active stages will have a status
of Finished, but the jobs status will still be Running. In this case, you
can clear the jobs status file reasonably safely.
Job Locks
Usually "cannot get exclusive access to job" indicates that another process,
such as a DataStage client, has the job open in some kind of editor.
For example, the Manager may have the job properties open, or the job may be
open in Designer, or the job may be being monitored. What are your
DataStage developers doing?
> ----------
> From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> Reply To: informix-datastage@oliver.com
> Sent: Thursday, 10 August 2000 12:12
> To: informix-datastage@oliver.com
> Subject: Job Hangs and Job Lock
>
> I have two types of problem in datastage
> job hangs and job locked
> Some times the job hangs with out any reason.
> Some times the the job control job hangs because the
> called job has got exclusive lock
> (cannot get exclusive access to job ).
>
> what could be the possible solution for this?
>
> thanks and regards
> Sudhir
> APHOIT/CA$H Datawarehouse Team
> (65) 423-7449
>
>
*************************************************************************
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else
*************************************************************************