DSXchange

You don't pass output parameters. You receive them. They should then appear as two columns on the output link of the Stored Procedure stage.

Why do you think anything is missing? What do you think is missing?

Oracle has never been horribly consistent externally with numeric data types. Adjust your metadata to match what Oracle generates, and this ought to eliminate the warning. Adjust the data type explicitly in your job.

Clearly this is "vapourware" at this time. If there is enough interest then maybe there will be time found to put one together. Remember that developing training takes much longer than presenting it - depending on the delivery model the ratio may be up to 100:1.

Explain what you mean by "rejected". Maybe you need to rethink the design, to handled failed lookups correctly - not reject them, but insert them into the target database.

Can you please outline what you think this entry is doing?

Have you checked for "upper case o versus zero" and "upper case i versus lower case L" in the auth codes?

Add one extra parameter to the job properties. It doesn't have to do anything. Then recompile. This will force a new parameters collection to be built. Then remove the job from the Schedule (if indeed it is there), and re-schedule it. This process should prompt for job parameter values and, based on...

Stages, link ends (pins), jobs, annotations, containers...

You haven't looked hard enough - there ARE faults. But in general they do have adequate breadth of coverage, if not perhaps the desired depth. Would anyone be interested in (paying to take) a training class on derivations in parallel jobs? Probably two or three days, with lots of hands-on exercises.

Thanks for letting us know.

My reaction (yuk) is unchanged.

The data types in the result set of the UNION query should match those in the SELECT clause of the first SELECT statement in the UNION.

Parameters, my friends, and more parameters. Don't do ANYTHING platform-specific. The migration itself is quite straightforward; it is exactly the same technique you would use on homogenous platforms. You WILL need to recompile everything on the AIX machine, since it will use a different C++ compile...

There's nothing to install. All you have to do is license it. All the pieces are already in place.

Edit an export file, then re-import.