DSXchange

You haven't answered the question as to what the value was rounded to. From Oracle Docs: FLOAT data type The FLOAT data type is an alias for a REAL or DOUBLE PRECISION data type, depending on the precision you specify. Syntax FLOAT [ (precision) ] The default precision for FLOAT is 53 and is equival...

How about in the Designer. Go to "Stage Types" and do a find of where-used to get a list of all jobs that use that stage type.

Oracle redefines a "float" as a number(n,p) internally. Please see what your precision is set to and what your number is being rounded to. I would guess that you would want a double-float here and you should be aware that floating point numbers are always rounded somewhere and are imprecis...

Could you post the director log entries for this new job to the thread so we can see warnings, errors and informational messages?

I try to remove excess data as early as possible in a job. In this case the distinct at the database level will save overhead, particularly if the DB is remote.

At first look it would seem that the userid/password used to connect are incorrect. How certain are you that you have entered the correct ids and passwords in the installation and can you connect to xmeta from db2connect using them?

If you write a simple job with just the DRS stage reading data as in your original job and writing to a PEEK stage, does the error still occur?

What confuses me is that you mentioned SQL-Server initially and now it is Teradata.

Umm, but your original post stated

one of the jobs is to read a table from SQLSERVER DB using DRS stage.

is "TERT_ML_S04_DEL" your DRS Stage?

... main_program: APT_PMsectionLeader(1, node1), player 1 - Unexpected termination by Unix signal 9(SIGKILL)... It looks a bit like another process issued a signal to the aborted one to terminate. Could you add the parameter "APT_DISABLE_COMBINATION" and set it to "true" and re-...

Not with the sparse error information given. Are there no more messages or entries in the log?

My code that I posted is free, I did a quick test on my machine here to make sure it works. It assumes a character input and will generate a character output, i.e. it won't work for numeric fields but will work for numeric values. It sticks to the lower 0-255 characters so will also work for multiby...

The output will be in the DataStage log file and the ulimit is generally not changed during a job run, so it will be just one value.

If you want to write this in a routine, try this, a routine called AWCrypt with 2 parameters, "Seed" and "SourceString". Seed is an integer and SourceString is what you are obfuscating: WorkSeed = IF (Seed>256) THEN MOD(Seed,256) ELSE Seed Ans = '' SourceLength = LEN(SourceString...