DSXchange

In a dataset, field_A is defined as Bigint and value is stored in dataset. In my next job, when i read field_A as Bigint, it is outputting as NULL . However, if I force the datatype as char while dataset read in my job, it is outputting the right value for the field_A. Does anyone know why this beha...

I had some issues similar to this. This could be a LOW VALUE with ASCII value less than 32. you can write a condition to see if the input ASCII value is less than CHAR(32) but that is bad data. By the way are you getting this from the source table?

try CASTING the field as NUMERIC(10) in the query and in the metadata change it to Integer(10). This will help you keep it as Integer and will not convert into Decimal.

if ur coversion is about just change in length...u dont have to use modify stage...just in any of the transformer stage you may be having in ur job...simply map Decimal[31,11] column to Decimal[15,2] column..u wont get any error or warning.. word of caution, if ur input value is really occupying al...

You have to get this alert, since what you are doing could result in loss of infomation. You can not shoehorn a 31 digit number into a 15 digit number. Therefore DataStage will not let you suppress ... I am doing this conversion as part of migration from DB2 to Oracle. In DB2 the field was defined ...

I am getting the following warning message while converting from Decimal[31,11] to Decimal[15,2] Source_Mdf: When checking operator: When binding output schema variable "outRec": When binding output interface field "source_column" to field "target_column": Conversion fr...

ray.wurlod wrote: How about marking the topic as resolved?

Ray,
I tried doing that yesterday but i was getting an error when i clicked on the button and new window with html script opens.

so i am not able to mark it resolved. would the admininstrator be able to do this?

Hi Meera..
this worked for me.. thanks for resolving the issue.

thanks everyone for their input and suggestion.

I am still getting warning messages though i converted the replacement string to 4 characters.. the specification looks like target_column:string[4]=Handle_Null(substring[0,4](source_column),"xxxx"). I am still getting the same warning message. Please suggest if there is any alternative Mo...

Hi Ray, I used a substring function and in the specification, i included target_column:string[4]=Handle_Null(substring[0,4](source_column),""). though the field is converted from length(10) to length(4), i am getting a warning message Modify_135: When checking operator: When binding output...

thank you.... ithink that is more efficient than using a transformer

thanks every one for their reply. i can use Left() function to get the required four characters from the source_column. is there any other way of doing the same... without using Left/Right functions

I am using a modify stage and in specification i specified

target_column:string = source_column

where target_column is specified as CHAR(4) and source column is defined as Varchar(10)

I am getting warning with possible trucation. how can i avoid this warning message.

ArndW wrote:It timed out after exactly 1 minute... Were the DataStage machine or the FTP target machine exceptionally busy when you tried this?

I don't think so. Since, the environment is UAT, i dont have an idea of that but at what ever part of day i run, the job fails. i ran this job at off-peak time.

Yes, it is a FTP stage to FTP the file. I don't have anywaitforFile event activated. But my FTP job will run once my extract job is completed which generates the file for FTP. so why do i require waitforFile activity. Trigger condition from extract job to Ftp job is unconditional. should i change it...