Hello Forum,
Is it possible to use the same load job to load multiple load files with different columns and delimiters to different target tables.
My idea was to use parameterized schema files to handle/parse the load file, and parameters for the rest of the connectivity information. I've done such things with normal ETL processing before, but was wondering if there is something special about the load stages that might make using schema files not work.
Thanks,
Greg
Reusing same job to load multiple tables of different DDL.
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 210
- Joined: Wed Feb 16, 2005 7:17 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's possible; it's not best practice.
Parameterized schema files for the source files, and rely on RCP and parameterized table names for the loads.
No guarantees - you may need to tweak some other aspects.
Parameterized schema files for the source files, and rely on RCP and parameterized table names for the loads.
No guarantees - you may need to tweak some other aspects.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
gsherry1 wrote :"multiple load files with different columns and delimiters to different target tables".
Different columns can be handled by using RCP. Different tables using parameters. But different delimiters? can that be handled? i have a similar requirement and i am using a multi instance job. But the source files are all DataSets. So not sure if different delimiters can be handled?
Different columns can be handled by using RCP. Different tables using parameters. But different delimiters? can that be handled? i have a similar requirement and i am using a multi instance job. But the source files are all DataSets. So not sure if different delimiters can be handled?