DSXchange

It's logged as a Warning only because it's an "unusual" event. And, as Arnd stated, you won't see it again in the current project, unless you delete the hashed file SDKSequences (not recommended).

Functions in DataStage BASIC are implemented as subroutines. Either of the following will work. Call DSGetLinkMetaData(Result, JobName, StageName, LinkName) or Result = DSGetLinkMetaData(JobName, StageName, LinkName) Of course, you will need a DEFFUN in the second case, so will need ...

There is no out-of-the-box function.

Search the forum as Arnd suggested; yours is far from a unique problem.

It means you have version 7.0.0 of the parallel engine and version 7.0.1 of the server engine. Every stage type also has its own version, for example you're probably running version 1.3 of the ORABULK stage. You posted in the server forum and specified "Server" as your job style, which is why you go...

This message can arise when the name of the link from the parent job to the container is not the same as the link connection within the container to the container input or output. If you make the link names the same, this problem willl go away. Otherwise, you need to right click on the container in ...

There is no limit on the number of columns in a row in DataStage.

However, you may encounter limits elsewhere. For example, the default limit via ODBC is 400 (which can be overridden by MAXROWCOLS in uvodbc.config). The maximum number of columns supported by MS Access is 256. And so on.

We trust that by "broken" you mean split over the available processing nodes, not "damaged"!

Did you undertake the official Ascential training? The case study therein is quite comprehensive, with some good examples of bad data.

As far as I am aware there are no other case studies extant. For some reason most people are unwilling to publish examples of their bad data.

Did you extract "GRAYT" does not have the privilege to perform operation "IMPLICIT CREATE SCHEMA" from the first error? Check with your DBA.

In either case also check that your Oracle environment variables are correctly set (in the $DSHOME/dsenv script) and that tnsnames.ora is properly populated.

If you want N comma-delimited values into N separate columns in one row (the OP specification used the word "columns"), the output side of a Transformer stage must have Max(N) columns defined, and the Field function used to separate into separate columns. This design should also be used if N separat...

Try or

Scheduled for release very soon (July?) is an active dashboard which may help with this requirement. Currently it's called "Sorcerer". Don't know whether it will work with version 6 - why not ask the vendor, at Ascential Developer Net?

It might help also to post the generated SQL and how many columns there are in the Columns grid.

Looks like you still need to add the DSN into .odbc.ini.