Page 1 of 1

ORCH_WORK_<hexvalue>

Posted: Sun Jan 25, 2009 7:27 am
by nishadkapadia
At times there are ORCH_WORK_<hexvalue> tables left behind in the database.
Is this <hex value> stored somewhere which could be used to identify the tables.

Currently Information available:
Possibly through the Director
ORCH_WORK_<hexvalue> tables get auto dropped on re-execution of DS Jobs. Alternatively, these tables are created specifically to indicate a failure, hence they are not dropped auto.

However, would like to know where this <hexvalue> number are stored somewhere.

Posted: Tue Jan 27, 2009 6:05 am
by keshav0307
when you re execute the job, a new ORCH_WORK_<hexvalue> table will be created. and this is probably because the <hexvalue> is not stored anywhere.
unlike the MLOAD stage there is no option to define ORCH_WORK and ORCH_ERR table in teradata enterprise stage.

Posted: Tue Jan 27, 2009 1:04 pm
by nishadkapadia
Thanks keshav on confirmation