DSXchange

Choice 1 - correct the warnings.
Choice 2 - Deprecate the warning to informational.

Choice #1 is by far the better choice.

Since your specifications are vague the answers are as well. All the information you need is present somewhere in the text portions of the director log records. A Job can have many stages that write records, each of these can have a distinct number of inserts, updates, deletes, success, errors and w...

Yes, that would be a good assumption and the likely cause.

1) According to the above post, XMETA and UniVerse databases both are being utilized to store DataStage information. Is there a way to make the tool use only XMETA? While the use of the switch RT/ORLOGGING will let the runtime logging information be written to either the XMETA or the old UniVerse d...

Can you see if changing it to CHAR makes a difference (You don't need to change the whole database, just your one table).

While the job shows as "not compiled" does that mean that the compile in the designer was successful and the can be run from the designer? Also, I wonder if there might be a refresh lag in the director - does the "not compiled" status remain after a Ctrl-R in the director? Also, ...

Is the Oracle instance a different one as well? I wonder if your tables/databases string types are declared as BYTE or CHAR based and if that might have an effect.

I agree that what you are seeing is wrong, i.e. returning something different than what is expected.

Sometimes the names can be confusing. Try this - close your designer, open the director. In the director click on the "not compiled" job to highlight that line. Then from the menu bar do a "Tools -> Run Designer". In the designer compile the job, then check the status again in th...

There is a bit of a problem here. A column of Char(10) will never contain just one or two or three blanks - it has a fixed length of 10, no more and no less. Are you certain that you are discussing Char(10) or perhaps VarChar(10)? What happens if you change your select to SELECT CAST('' AS Char(10))...

Very strange.

What about Stage -> NLS Map, are they the same?

oops, I see you want it the other way around. Put a user variable activity and generate "BigString" as "BigString:',':$Loop.Loopvariable"

A Variable holding "file1.sql,abc.sql,xyz.sql" outside the loop, then use a comma for the loop separator.

The error message refers to a failed attempt to read a dataset, not to write one. Please look at your job again, somewhere you are reading from a dataset (which cannot be located at runtime).

Just compare the attributes in both the and tabs, they need to be identical.

Have you defined this as a fixed-length file? Also, is your test file just one line, and if so, does it have a <lf> at the end? Just 2 columns in the file - is your DataStage sequential file also defined with 2 columns?