Can anyOne Explain ..why it is so that you should import table definitions by Orchestrate Schema Definition in Parallel Framework and
not using definitions imported via ODBC
why to import table definitions by Orchestrate Schema def.
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
When they added Orchestrate to DataStage to give us parallel jobs they added the Orchestrate import. Most of the other imports are were originally designed for server jobs, not parallel jobs, so sometimes there is a minor metadata mismatch. This can result in some of the warnings you see when you run parallel jobs. I'm sure in future releases we will see more seamless importing, they are due to deliver what they call frictionless connectivity to simplify that side of things.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I don't know if "u" can (whoever "u" is), but I can. This information is in the manuals, which a thorough reading will reveal, and/or in the readme notes that ship with the product. The knowledge is also conveyed in the vendor's training classes; in this particular case DX434 (DataStage Essentials, Enterprise Edition).
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.