DSXchange

ArndW wrote:Those characters are not in the 7-bit US ASCII table and therefore are not displayable and changed to '?'.

It seems reasonable. I don't know how these data are inserted into the database but I've to transfer it even it was a rubbish data.

Any Ideas?

ray.wurlod wrote:Please look as your destination with something other than View Data.

Ray, It also loaded as question marks (?) at the destination when querying the Oracle 10g destination.

How about a NUMBER(x,y) with appropriate X and Y values? The maximum scale I currently have is 6. Converting REAL to NUMBER(x,y) seems to be a good idea but my main concern if the scale of the upcoming data in the future exceeds the identified scale even it was 10 which is the maximum scale I can a...

Okay, I will contact them. But if I need to get rid of the FLOAT datatype, what datatype you recommend to be the replacement without losing any data?

Thanks for the reply.

Any Suggestions?

Thank you for your replies, Basically the error appears when using my datastage Designer Client 8.1 to create a new parallel routine. I have no problem with my c++ code compilation and its deployment on the datastage server. but, i just could not link the '.o' file to the routine, because as i menti...

Also you can uncheck the APT_SORT_INSERTION environment variable.

Thanks ArndW.
Sreenivasulu, RCP is enabled but no warning

Regards.

ArndW,
my purpose is not to reject these truncated string records, I only want to generate a log warning if they're truncated to pay attention. Finally can I find a project level solution not on the level of transformer stage or job level because I currently have more than one thousand jobs.

Regards.

ArndW,
my purpose is not to reject these truncated string records, I only want to generate a log warning if they're truncated to pay attention. Finally can I find a project level solution not on the level of transformer stage or job level because I currently have more than one thousand jobs.

Regards.

Dears, I need to generate a custom warning from the transformer stage if the length of a certain column has been minimized by mistake. For example, if the column at the data source is Varchar with length 50 and at it's transferred through transformer stage as Varchar with length 10. I found out that...

[quote="Sreenivasulu"]If you want the exact precision as source the store as 'varchar'. This is done for some 'critical' fields

U mean changing the column's datatype into VARCHAR instead of FLOAT? and what do you mean by 'critical'?


Regards.

It's a simple move and the source's scale sometimes is more than 2.

Dears, I have a problem loading values with 'float' data types into the oracle 10G database, although the DataStage can read it right, but it loads it in a wrong way as follows: Source Column Data type: Real (7,0) Source Value: 5555.49 Oracle Ent. Stage Viewer: 5555.49 Destination Column data type: ...

Thanks for your reply.
I'm using the same job pattern for many jobs. Only few jobs introduced this error, so I don't know why SIGSEGV happened?

Regards.