why to import table definitions by Orchestrate Schema def.

ajmore · Post by **ajmore** » Thu Sep 07, 2006 4:29 am

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

Luciana · Post by **Luciana** » Thu Sep 07, 2006 6:02 am

Importing Table Definitions:
Can import using ODBC or using Orchestrate schema definitions
- Orchestrate schema imports are better because the data types are more accurate

kumar_s · Post by **kumar_s** » Thu Sep 07, 2006 6:07 pm

You can use plug in metadata as well.

vmcburney · Post by **vmcburney** » Thu Sep 07, 2006 6:49 pm

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.

ajmore · Post by **ajmore** » Fri Sep 08, 2006 12:07 am

Thanks all of u for the Information....
Can u also specify where can i get additional information about these minute details

ray.wurlod · Post by **ray.wurlod** » Sun Sep 10, 2006 2:36 am

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).