DSXchange

How many columns? how many records ? is the data format fixed and always like A:B^~C:M^~E:F ?? that is two charcter_1:character_2^~charcter_3:character_4. If you have fixed columns you can use the substring to extarct the data and concatenate them at the end. if the data is hefty why not write a rou...

in which error tables are the record going in ? i think its error table one which means you have data issues. if its going in error table 2 then they are duplicates.

are the smiles coming through in your data too ?

I know i just replied to one of them

i had such issues in DB2 to TD migration. if its ending up in seven characters then Ray is right that the last three are respresting the day number i.e. 102nd day of the year. in TD we have Sys_calender.Calender to check if its mapping to the right date in this case 102nd day = 22nd of december. tho...

which column is it giving the error on . i am sure you got some warnings etc before this ?

did u replace them from DS or changed the job code at the backend to do it ?

if you want to run them in parallel then the only way is putting them in the sequence as you mentioned. if you want to try the sequential run, this may sound a bit daft but you can store the names of the jobs in a file and then use the exec command stage to run the jobs through a command line "...

Can only tell if i had some sample rows and what metadata is defined in your oracle stage

p.s. i think this can also be ignored by using StringToUstring and UstringToString functions in DS

Correct me if i am wrong here people . but ustring is a unicode string in UTF 8 character or UTF 16 or even UTF 32 format and looking at this alert it seems like the project is set to ISO-8859-1 character set which is defined at a project level. so i guess DS is trying to convert the data from its p...

guess almost a similar problem as this
viewtopic.php?t=93587&highlight=Unicode+character

i have done thing manually and its not that complicated. just make sample jobs and the only thing that will differ would be the TD stage from the DB2 one. what ever opotions you want in that target TD stage should be in your sample job. then replace that bit with the DB2 bit keeping in view the VS0 ...

The date in TD is internally stored as an integer so its o.k to use char(10) in the API stage to pull the data out.
P.S you can keep it as in the DS internal format. TD will convert it automatically when you insert it so no need of doing an oconv before

i would have made one job to read 70 files...........