Left over ORCH_WORK_ tables in the database

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
kishorenvkb
Participant
Posts: 54
Joined: Mon Dec 24, 2007 9:27 am

Left over ORCH_WORK_ tables in the database

Post by kishorenvkb »

Hello,

We have been running our Datastage jobs for a while now with Teradata as the target database.

On a routine check... we saw that the work database on Teradata is growing in size.

When looked we have a lot of tables starting with ORCH_WORK_ followed by some numbers.

Does anyone know what these are and why they are left behind?

Thanks
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

The ORCH_WORK_XXXX table will not be dropped if the job abort.
similarly ORCH_ERR_XXXX will not be dropped if there are any error records.
shershahkhan
Participant
Posts: 64
Joined: Fri Jan 25, 2008 4:41 am

Post by shershahkhan »

ORCH_WRK_XXXX tables are working tables for Teradata Enterprise stage it use this table to load the load using fastload and then do insert select from this table to the final table, if the job aborts due to any reason these tables will not drop.
kishorenvkb
Participant
Posts: 54
Joined: Mon Dec 24, 2007 9:27 am

Post by kishorenvkb »

Makes sense. Thank you very much.
Post Reply