datastage job having high start up time
Moderators: chulett, rschirm, roy
datastage job having high start up time
Hi,
There is a datastage job with Teradata Enterprise stage and Teradata API stages as the source. Data is being loaded to Oracle. All the stages in this job are running in sequential mode.
The start up time of this job is low most of the times. Sometimes the start up time is very high(approx 15 min, once it was approx 45min ).
What could be the reason for such high start up time. Why is the job having inconsistent start up times? Is there any environment variable/setting in the DB stage to control the start up time?
Could anyone please help on this?
There is a datastage job with Teradata Enterprise stage and Teradata API stages as the source. Data is being loaded to Oracle. All the stages in this job are running in sequential mode.
The start up time of this job is low most of the times. Sometimes the start up time is very high(approx 15 min, once it was approx 45min ).
What could be the reason for such high start up time. Why is the job having inconsistent start up times? Is there any environment variable/setting in the DB stage to control the start up time?
Could anyone please help on this?
It's not just before SQL that appears to get captured as Startup time.
From what I've observed, it appears to be a catch-all bucket for any time not specifically measured elsewhere.
Overhead would probably be a better name for it.
Before SQL, after SQL, time spent computing database statistics are all things I've seen captured as "Startup" time.
Mike
From what I've observed, it appears to be a catch-all bucket for any time not specifically measured elsewhere.
Overhead would probably be a better name for it.
Before SQL, after SQL, time spent computing database statistics are all things I've seen captured as "Startup" time.
Mike
-
- Participant
- Posts: 10
- Joined: Sun Aug 11, 2013 10:46 pm
- Location: Dalian