DSXchange

I think you might be using auto transfer of columns, do it programatically in the loop logic.

Using a single job will not work. Infact, the best and cleanest way is to do a separate job that deletes all records from your table.

There's a trick way of doing this. In the job, do a read from the same database where the table to be deleted exists and do a 'select 1 from dual' and write your table truncate/delete copmmand in the open command there and then device a dummy lookup with the actual stream of data on this dummy colum...

You have to define multiple "pools" in your configuration file.

Check out the keychange columns generated in the sort stage. They will help you to identify when you move from one key record group to the next.

Ummm, okay, so what you can do is, for null value in the format settings in sequential file stage specify something like - null and then get rid of the "null".

In execute command activity, just define command as "ksh" and pass shell file space 6 as the parameters.

Yippie, that is what I do ALWAYS and it will SURELY work.

Well, that is the way in which datastage behaves when it writes to sequential files, it compulsorily puts the quotes if you chose so. What you can do is run a script after the file is created to get rid of all "" in the file.

Hmmm, I am running out of ideas, but let us do one thing. a> In the sequence where you pass the parameter value to the job, just hardcode the timestamp value and run, if this works then surely the problem is on the sequence side and do point b. If this failed do c. b> Check what is being sent to the...

If the data is finally landing into the database, just leave the datatype as the original one. Another approach could be, change the precision and scale in the source itself.

Do only a cat (the -n option will list with record numbers which you don't want). Use this:


and in ereplace, make sure there is no space between the single quotes.

Ok, please provide the following:

1> The contents of the file
2> The commands (exact) used in the execute command stage and while passing to the job

Give this a try, use this derivation in the sequence when passing the parameter to the job: