DSXchange

Already have. As noted, find the directory where that ".so" file lives and ensure its home is in that path variable. Simple as that.

OK, so your client shouldn't be the issue. You need to ensure the proper PXEngine/lib directory is in your LD_LIBARY_PATH, the one that contains the orchoracle.so file. Note that that 'proper directory' may be a symbolic link.

Ernie, were these "optional" stages in 7.x? I don't recall. If so, you'd need to repeat the Server installation, it will go into "Maintenance Mode" and allow you to add any missing optional plugins.

What stage are you using in your Server jobs to access Oracle?

Dang... knew I forget something! The whole "who really cares?" part.

They're not the "magic bullet" that some seem to believe they are. And I'm not sure what anyone can suggest if you can't make any changes to the jobs. I'm going to have to defer to some of the more smarter folks here as to what might be going on under the covers but it sure seems IPC relat...

You only have the option to use a single tag for "empty elements".

You're certain they're not there? They would be in the 'Real Time' category. Or in the Manager in the Stage Types / Server / Real Time branch.

What point do you think those IPC stages are serving in the job?

Remove them and then either run without row bufferring or enable it at the job level.

It doesn't matter where the compiler is, it matters where you run the compile command from. And I'm sure there's an option to create the output elsewhere. Or use "Docume~1" for the directory name.

It's important to tell us if you've ever been able to "access Oracle" and this is a new error or if this is your first time trying to access anything Oracle in this manner.

/* Errors generated by the DataStage server */ #define DSJE_NOERROR 0 /* No error */ #define DSJE_BADHANDLE -1 /* Invalid JobHandle. */ #define DSJE_BADSTATE -2 /* Job is not in the right state (must be compiled & not running). */ #define DSJE_BADPARAM -3 /* ParamName is not a parameter name in...

Which part is unclear? All the steps seem to be spelled out right there.

It's not that you can't do it in earlier versions, it's just that there's no automatic option in the Lookup stage for it. AFAIK you'd have to go more 'old school' and I'm sure others could share techniques if you like.

You need all jobs in the Sequence or all jobs that the Sequence actually ran? May not be the same list. For the former, the dssearch command. For the latter, the 'Summary of sequence run' log entry.