DSXchange

This is not a problem with the timestamp unless UPDATE_TIMESTAMP has a string data type. Please verify that. Otherwise, it is one of your Char or VarChar fields that is throwing this error. (The error message specifies "string data right truncation".)

Add a reject link to the Sequential File stage and report back whether the row counts reconcile with this design. If they do, then you will need to perform some of your own detective work to figure out why the rejected rows do not match the record schema you have given in the Sequential File stage.

I believe your major concern is identifying the culprit who is deleting your local repository hashed files. It's good that you can recover them but you ought not to need to do so.

What size decimal?

There is information in the manuals about how decimal numbers are stored, but the number of bytes depends on both the precision and the scale.

How many records on the stream input? How many records on the reference input? How many records on the output of the Lookup stage?

There's an easy solution for either server or parallel jobs involving a mix of Left(), Index() and Right() functions - you can pass the string that is to be removed as a job parameter.

Use a freeware email client such as blat to send mail. Configure your email gateway with the ability to translate short emails into pager messages.

Look in the DataStage BASIC manual for IF statement and CASE statement.

Quickest solution?

Double the number of nodes, increasing the hardware and licensing commensurately.

And you have read and execute permissions to libgciudt6.so ? This error is really annoying, because the library contains functions used to access Unidata 6; an inability to load the library ought not to affect any job that does not access Unidata version 6. However, functions in this library are sta...

Check the NLSMODE setting in the uvconfig file. If NLSMODE is 0 then NLS is not available.

pandujoy wrote:plz help me out

Who, what or where is "plz"?

In server routines rounding can be performed using "MD" conversions in Oconv() and when using the Fmt() function. You will find more information about these in the DataStage BASIC manual.

No it won't. It will convert the string to a binary date. That's only half way to the required solution. You're also making an assumption about the century pivot year.