DSXchange

The options for a date column are different in the row generator.

And what happens if you run this query in mysql? Note that column 4 would be "crdate" - what type is that in mysql and what is your DataStage definition?

Well - I guess I asked for it.... but if you look at the file you will see that you didn't actually add any information; the first section is the base configuration and nothing is specified. At a minimum you need to specify a real relay, perhaps "mail.yourdomain.com"

It is unlikely that this is a bug.
Are you letting DataStage generate the insert and update statements? If so, have you correctly marked your key column(s)?

Scratch is there to be used - how much data are you processing in parallel and are you doing things like multiple sorts or several joins on different keys (which imply sorts)? Are many jobs running in parallel?

You need to compare the columns in the schema shown in the log with those you defined and you will see a discrepancy.

I checked Google for the MySQL Cast() syntax and it would seem that one needs to use "signed" rather than "int".

Do you have RCP enable in on or more of the input links to the stage?
Turn on the $OSH_PRINT_SCHEMAS in your job parameters and see what the schemas going into the stage are.

The CDC package is part of the standard delivery, nothing additional needs to be installed or purchased.

I assume that "srvpprodinfsrv.pronaca.com" is the datastage server, correct?
That tells me that the sendmail doesn't have a correct address to the smtp gateway/server for mail.

Can you post the "/etc/sendmail.cf" contents?

You'll always see the first part of the message regarding process metadata, so don't worry about that.
If you do a "cast( original_column_nameAS int) as 'original_column_name'" and declare the column as integer in datastage what is the result?

I am afraid that I don't quite follow the first question, but unfortunately the schema does not contain information on whether or not the first line contains the column names, therefore there is no way to set this in a schema file.

There is no command and no option to let you do so.

What exactly is your question? You posted a schema that does null handling for "REQ_SUBM_TS", i.e. when read it replaces '1900-01-01 00:00:00' with a null value. p.s. I would have answered the question yesterday, but since you posted "ASAP" despite warnings not to do so I opted t...

I didn't get that error with tinyint but if your SQL Server tabel contains a column of type "image" and you try to read that column you will get DataStage aborting on you.
Can you reproduce your error in a job where you read ONLY that one column from your table?