DSXchange

Hopefully there are no nulls in any of the values you are concatenating together...

The Job Activity stage runs a job and then waits for it to complete, that functionality cannot be changed. You'd have to "roll your own", say something like a routine does all of the same steps except the DSWaitForJob() call or a script that leverages dsjob without either of the wait optio...

Look at the dsenv file on your old server and make any corresponding changes on the new server. I would imagine your "shared library" path is not set correctly.

Have you reported this to your official support provider?

Is that the complete error message? If not, can you post it unedited plus any other associated errors/warnings you are getting.

Put the value in a flat file. In a Sequence job, read the file for that value and pass it as a job parameter to the job that needs it. Use it in your where clause enclosed in hash tags. Or use a Server job for the first task, save the value in USERSTATUS and then use that mechanism to pass the value...

Server Jobs always have this disadvange , it will never point out to a specific error. Try deleting the transformer and introduce a new transformer. I beg to differ on general principal, never mind the fact that they posted a very specific error. If you search the forum for "Fault type is 4&qu...

Really? That doesn't make much sense to me but I guess we'll see!

Yes Craig!! The version controller is only accessible by the admin. I am planning to do this and give to developers so that they can import themselves. Is this an approved activity? I would counsel that this may not be the best idea in the world. Anywhere I've been had a someone (or a small group o...

There are many causes for that 3113 error as noted out in the wild, including here. If you can't get any joy from your DBAs or there's no sign of "defunct processes" then I'd suggest you contact your official support provider. Could be a bug in the stage or perhaps even in the Oracle clien...

For any kind of "starts with" check, all you need to do is substring.

Any particular reason you're not using Version Control?

Maybe... but a definite issue back in the 7.x version.

Hmmm... so the VOC records did exist. Not sure what the next step is, time to wait for El Queso Grande it would seem.

I would think you should be able to create it manually (all you'll have is an empty directory) and then do the two VOC steps Ray mentioned. You could then export the job from Production and import it back into this project, the "fix" will allow this 6487 version of the job to be successful...