Archives of the TeradataForum

Message Posted: Fri, 19 Jun 2009 @ 11:45:00 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

You do not necessarily need to restart the database for channel errors (most times). You do however need to restart the channels (vary them online) and then restart the TDP to pickup the new channels. This still causes active jobs to fail and you need to have an operational plan to quiesce the jobs streams coming in to correct the problem.

Our shop has redundancy built-in to the channels multiple channels per mainframe spread across multiple 5550 channel nodes. Even if we loose a channel, the other channels attached to different channel nodes survive and continue to be utilized. We can then schedule a maintenance window to correct the channels and bring them back into the TDP and run at full capacity.

We use control-m schedule and have a resource definition that governs how many parallel executions of jobs requiring Teradata resources. We can set that to resource definition to zero and keep other jobs from spawning. That does not help ad hoc jobs however.

Kyle Prescott

	<Prev	Next>		<<First	<Prev	Next>	Last>>