ORCH_WORK_<hexvalue>

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
nishadkapadia
Charter Member
Charter Member
Posts: 47
Joined: Fri Mar 18, 2005 5:59 am

ORCH_WORK_<hexvalue>

Post 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.
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post 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.
nishadkapadia
Charter Member
Charter Member
Posts: 47
Joined: Fri Mar 18, 2005 5:59 am

Post by nishadkapadia »

Thanks keshav on confirmation
Post Reply