DSXchange

This is possible in a px sort stage with unique option selected.

If your using AT then check at.allow and at.deny
If your using crong then it will be cron.allow and cron.deny.

chitravallivenkat wrote:I think the file got locked.

If the file was never created how can it get locked. And if the file was, infact, locked by some other process, you will get a different error message. This is clearly a permissions issue as other have noticed. Look into the permissions through and through.

Its synonymous to multiple threads. Using Multiple Instance Jobs, one can incorporate massive parallism in a server job. Huge performance gains can be noticed for high volumes of data.

If you can get your work done with the tools you have, dont need to invent a new one. So yes, for simple tasks as trim and renaming you can use transformer and modify stage. You dont need to build an extra stage for that. As Kumar noted, utilize buildops for functionlity not readily available from t...

Great. Time to mark your post as "Resolved" now.

The tools that Ken has mentioned are to check for network traffic and load, in a general sense. You dont need admin rights to run them. Just go to your unix prompt and type top. You will see what I mean.

What is the error/warning message you get in the log? Copy paste it here.

For your second question, you will go into the exentended properties and specify an null_value for the nullable column. Or you can do an explicit null check inside the transformer and set a default value.

What solved your problem?

Do an exact search on key words 'does not appear to be a synonym'.

trobinson wrote:What is everybody on vacation today? Where's Kumar?

We wish. No vacation. Yea, Kumar, where were you !!!
Just playing with you

Just the password, what about the other info. like server name and user name ? Is'nt it funny, when you say the same thing they need proof and if 'they' say it, its accepted blindly

Never use kill. Even more, kill -9 should be a big no no and should be the last resort. Always try to stop the job from director as advised. And if your job was accessing a database, it can leave live zombie threads to the database. Beware of the wrath of DBA's

Guess I always banked on organizing the jobs in different categories and sub categories and never ran into sucha problem. But if I do, Ill know what to do