DSXchange

The input looks like Julian date to me. Try



ICONV/OCONV is not present in parallel jobs unless you use a basic transformer.

Everything looks ok to me. What is your result? Also try it in sequential order to see if the data is really getting joined or not? You might be having a leading trailing spaces.

Search for it. It has been discussed time and again with different methods.

Because your just ICONV'ing the date. This will give you internal date, which is what you got. Now you need to OCONV it with conversion code "DJ" I think, double check it, to get the Julian Date.

Bad design. Load in different jobs. You are loading 15 tables with data size ~ 30 Million. Restartability will be a problem. If a record fails in any one of the tables and the job aborts, its going to affect the other loads as well.

At the server end. In your Project directory.

Search for it. Vincent also has the comparisons in his blog. Click on the signature of vmcburney.

Due to the reason MKS Toolkit is shipped with the product and hence unix commands can be executed.

Your understanding of my implication is correct. Whatever id you are using, should be in dstage group, which is default. Or whatever group you have specified for your DataStage users.

Your target database might not be partitioned. Multiple inserts to a table should be fine too. Did you try commit level of 1?

Clear the &PH& folder and see if that helps.

A project for each user, wow thats an expensive playground.

kumar_s wrote:Oh my.... Thanks for fixing it.

No worries, I got your back

I left some work for the OP
Was'nt being hasty this time...

The quick DSGuru2B jumped over ahead of himself, yet again. But why?