DSXchange

What triggers the generation of the sequence number? If it's every row, just add @INROWNUM to the starting value.

What you attempted seems OK. Can you tell us precisely what you did, what you expected to get, and what you actually got?

If you're prepared to use a BASIC Transformer stage or server job, you could have which would answer all three questions.

Is the stage running in sequential mode or in parallel mode?

Let us know if any of that will make a difference. I predict that it won't make much difference at all.

You could use istool command with a -datastage option specifying "server/project/*/*.tbd"

You could export all the table definitions using any of the DataStage export utilities.

Read my response again carefully.

There is always some performance hit in server jobs on version 8 over version 7.5 because of the new environment in which things are operating. I've posted about this in the past. In short, though, everything executes in a service-oriented architecture running on a parallel execution engine. To comm...

SAMPLE is applied first because it is documented as being applied first.

Could you use nested SQL? For example

Could this data type require FOUR fractional second digits (making a total of 27 characters in the timestamp)? You'd need "%ss.4" in the format string as well as only four zeroes in the constructed data.

If a column can have an extended property possible values are available in a drop-down list. For example a string data type might have "Unicode" as an extended property. It is also possible to edit the row in the Columns grid. Double click on the row number or right click on the row and ch...

I'm planning an installation of Information Server 8.7 on Windows Server 2008 (64-bit). Has anyone done this yet and, if so, which version of the Microsoft Windows SDK did you use? This one (for example) has three different ISOs to download, but none of them appears to relate to 64-bit operating sys...

SYSDATE yes.
JobName yes.

But only if you use user-defined SQL in the database stage, with SYSDATE specified explicitly and the JOBNAME hard-coded from the job that it's run from.

No.

For exactly the reason you specified.

There is a problem in the data your job is sending to Oracle. Somewhere a non-numeric value is being supplied where a numeric value is required You have to do some detective work. Note that "numeric" includes dates and times in this context.