job activities in a sequence being invoked AFTER DELAY

chulett · Post by **chulett** » Tue Jul 14, 2009 8:34 am

That makes no sense. Are you sure there's nothing else between the two or a before/after routine that is skewing the results?

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Tue Jul 14, 2009 8:55 am

Can you cut and paste the sequence log.

Even if your PH is almost full, waiting for hours is bit too much.

Include a dummy echo statement between J1 and J2 to see when it is triggered. It will give you an indication of which activity is taking time.

I guess either J1 has some post-job script or J2 uses database extract - which takes significant time.

Or it is possible that there are some other events between J1 and J2 which is not recorded in the log.

sureshdsx1001 · Post by **sureshdsx1001** » Tue Jul 14, 2009 10:27 am

Sainath.Srinivasan wrote:Can you cut and paste the sequence log.

Even if your PH is almost full, waiting for hours is bit too much.

Include a dummy echo statement between J1 and J2 to see when it is triggered. It will ...

Dear All....

The snaphshot of director log looks like below-
7/14/2009 8:11:35 AM seq_Extract_dsd_CBJ -> (jb_Extract_dsd01_CBJ.TN): Job run requested
7/14/2009 8:11:35 AM seq_Extract_dsd_CBJ.DSD_CBJ.JobControl (DSRunJob): Waiting for job jb_Extract_dsd01_CBJ.TN to start
7/14/2009 8:11:38 AM seq_Extract_dsd_CBJ.DSD_CBJ.JobControl (DSWaitForJob): Waiting for job jb_Extract_dsd01_CBJ.TN to finish
7/14/2009 8:12:26 AM seq_Extract_dsd_CBJ.DSD_CBJ.JobControl (DSWaitForJob): Job jb_Extract_dsd01_CBJ.TN has finished, status = 2 (Finished with warnings)
7/14/2009 10:40:10 AM seq_Extract_dsd_CBJ -> (jb_GetLOV_dsd.TN): Job run requested
7/14/2009 10:40:10 AM seq_Extract_dsd_CBJ.DSD_CBJ.JobControl (DSRunJob): Waiting for job jb_GetLOV_dsd.TN to start
7/14/2009 10:40:12 AM seq_Extract_dsd_CBJ.DSD_CBJ.JobControl (DSWaitForJob): Waiting for job jb_GetLOV_dsd.TN to finish

Please see the time difference between invocations [7/14/2009 8:12:26 AM and 7/14/2009 10:40:10 AM] between 2 jobs.

Also I have observed that there are huge Director logs which has not been purged for long time, will this be an potential issue leading to this delay of invocation.

Your response is appreciated

Regards,
Suresh

chulett · Post by **chulett** » Tue Jul 14, 2009 10:31 am

Yes, definitely. The job may technically finish but could be writing records to their logs for all that time. Simple enough to check - purge them and let us know.

sureshdsx1001 · Post by **sureshdsx1001** » Tue Jul 14, 2009 10:34 am

chulett wrote:Yes, definitely. The job may technically finish but could be writing records to their logs for all that time. Simple enough to check - purge them and let us know. ...

Thanks, will do the purging and keep you guys informed
However can you please provide some information on how DataStage upon completion , writes into DS - logs. Is there any process with DS Engine which does this activity

Regards,
Suresh

ray.wurlod · Post by **ray.wurlod** » Tue Jul 14, 2009 4:20 pm

No process. The millions of warnings returned from the database or operator are simply queued to be written to the log file. That buffering is largely under the control of the operating system. Sure there will be a DataStage process involved, but it will mainly be waiting for the buffered writes to complete.

sureshdsx1001 · Post by **sureshdsx1001** » Thu Jul 23, 2009 2:47 am

Hi Guys

Thanks

After clearing huge DataStage logs, main sequence finished execution quicker on time

Regards,
Suresh

chulett · Post by **chulett** » Thu Jul 23, 2009 7:34 am

Time to mark this as Resolved using the button at the top of the screen!