DSXchange

Also check for APT_BUFFER_MAXIMUM_MEMORY, APT_BUFFER_FREE_RUN, Buffering policies, Database parameters.

Install NLS. It should be prompted during installing server.

It is marked duplicate in other post. Hence I belive Moderater can move this one to Parallel and can delete the other post.

Raji - Try StringToDate() function. What is you input stage. If is sequential file, read the input data field as varchar and use StirngToDate in the transformer.

Try the bulk load untility. Or try to commit after all the rows got loaded. Also check whether you have any dupicated in the loaded data.

If number of process increased which may exceed the capacity of the section leader for that particular time to handle or may be even if communicaiton between the conductor and Section leader fails.

This error may occur randamly due to over load of the server. The job might be aborted at a peak load and when you rerun at a reduced load it might go through. Try to split the job with fewer lookup in a single job. If you have transformer and a heavy transformations try to split it. Also try to hav...

Dataset is stored in the native data type of Datastage. And hence it is more easily and effeciently read/written by datastage (and only by datastage.)

And this was the one among lot, written by Kim Duke. cd $DSHOME vi dsenv # add umask 007 vi sample/ds.rc # change umask to 007 chmod -R 777 catdir sql DS_LICENSE cd ../Projects chmod -R 4770 . chmod 4770 . cd NewProject chgrp -R dstage2 . vi .developer.adm .prodmgr.adm .operator.adm # add dstage2

Will it allow you to create new job and save in a new name?
Do you have a backup of you project.
Try to do a restart of the server and do a REINDEX as suggested.

After - Recompile all the jobs.

Are the two files in the same location?
Have you tried calling the two routines indivudually from datastage?

The same has been discussed several times.
May be you can avoid this warning by Clearing the partition in the previous stage output.

Yes, source the dsenv though .profile. But you can check the path being exported in the job log at the entry where Environtment Variable: is given. Will be at first few lines.

ashwin141 wrote:Hi Deepak

We had created an Estimation Tool based on different parameters for Datastage Project Estimation. I can guide you about the parameters, but I am sorry the Tool can't be shared.

Regards
Ashwin

Instead you can discuss the core and concept on which your tool has been built.

DSParam and DSParam.keep are the files which hold the whole variables and its values. Which can be promoted to the new project for one. Do a search or FAQ forum for the same.