DSXchange

9(14) indicates 14 digits to the left of the decimal place, and V99 indicates two digits to the right. Therefore there is a total of 16 significant digits, from which you can deduce that the equivalent data type is Decimal(16,2), because precision is the total number of significant digits.

You should be able to override.
dsjob -run -param $MYPARAM=value project job

The default date format should be YYYY-MM-DD
dsjob -run -param $MYDATEPARAM=2007-12-09 project job

Or maybe it has to be quoted
dsjob -run -param $MYDATEPARAM='2007-12-09' project job

Experiment.

WHERE is this Sequential File stage? What's on the other side of the Transformer stage? You really are not helping us to help you here.

It would appear that DSParams is updated by a child process of dsrpcd (which I find a little surprising). Or is your user ID credentialled in Information Server as a DataStage Administrator?

Have you been able to get as far as creating a profile? Is there any else to this message, or any other message? Do you have the DataStage xpsp2 patch installed?

Surely you would need Char(14) (or VarChar(14)) to allow for the sign character and the decimal place holder?

Did the vendor ever respond with an answer about the Decimal data type?

Did you import the table definition using orchdbutil or via the plug-in or ODBC stage?

I doubt it very much. You didn't even bother to define "performance" in an ETL context, much less what your indicators of performance were (recall that rows/sec is meaningless), so how can you state that partitioning your data solved something you have not even been able to define?

Welome aboard. Etiquette Notes 1. Do not hijack threads. This thread was resolved six months ago. 2. Ask a question. You didn't. Therefore we can't even determine whether you problem is the same as that resolved in this thread. Therefore please start a new thread, in the parallel forum, and ask your...

What's different between the old server and the new server? "Nothing" is not the correct answer.

Were the warnings being suppressed by a local message handler on the old server? If so there will be events in the job log informing you that a message handler was used.

I know of no advantages or disadvantages except that the Stored Procedure stage will more readily adapt once the smooth-talking IBM sales person has convinced the IT department to scrap Oracle in favour of DB2 which is, so we are informed, the only database you'll ever need.

How much physical memory do you have? Monitor with vmstat while this job is running.

You could, for the extraction part, use any of Lookup, Join or Merge stage - with an appropriate database-accessing stage feeding the secondary input. Multiple SQL statements - well, it depends. Can you give some idea of what these do? It may be easier to advise after that. For example, running the ...

It's the stage that does not permit updates, while your Write Method is set to use direct writes - effectively bulk load. Experiment with other values of Write Method and Write Mode properties, and you will probably encounter some form of Upsert being available. I also have not used this stage type ...

Where are you measuring rows/sec? The intermediate Sequential File stage is performing a blocking operation - its output can not be opened until its input is closed. Meanwhile the clock is still running, so the rows/sec reported is reducing. This is one of the many reasons rows/sec is a meaningless ...

Don't forget February 29th.

There is a set of date arithmetic functions downloadable from here which includes AddYearsToTimestamp() function.