DSXchange

That's not an "ODBC error" and as noted, for OCI it would be the tnsnames entry. Have "you" used OCI from DataStage before this successfully or is this your first time trying this? I'm asking to see if DataStage has been properly configured for Oracle yet and this is an overall p...

What stage are we talking about here? What error are you getting? For ODBC the 'DSN' should be the name of the ODBC connection you defined, for OCI it would be the tnsnames entry for the instance.

Exactly, I too would assume that is the issue. That special 7.5x2 version is the only "pre-8" version that will run PX jobs on Windows.

Ah... never mind then. There are several free file hosting sites out there, you could upload it to one and then link to it from here.

Chuck Smith has some tools that would help. For this, specifically the 'List all files and tables' one - I've tweaked my copy to load the results into a database table so it can be easily queried.

Found 8 other posts that mention "The view adapter has a binding for the non-existent destination field", see if any of them help.

Right, know about the DOS record delimiter, just forgot about the field delimiter string as an option. Am I missing something with the Column Import stage as well, does it have the same 'delimiter string' option? Not somewhere where I can check tonight.

How are you attempting this sqlplus connection? Manually? Give us some details around what you are doing and the sqlplus syntax you are attempting to use.

Interesting, indeed. That would seem to imply that a manual edit should still work. Perhaps there's more to it in 8.x, meaning there are more "sections" in the DSParams files where critical information is stored?

The NOTFOUND Link Variable is only valid for hashed file reference lookups, it is way too inconsistent when used with a direct DB reference lookup to use and maintain your sanity. Stick with a null check. That being said... How did you setup the OCI lookup, meaning is the SQL custom or generated by ...

D'oh! I looked at the "Delimiter" property and it had as an option "<other> => A single ASCII character". I didn't see the "Delimiter String" property.

Yes.

They would except for the fact that multi-character delimiters are not supported.

The Field function works fine but it does require a single character delimiter, just like the way the Column Import stage does. So you have at least two choices that comes to my mind. 1. Pre-process the file to change all occurrences of those two characters to a single character that you are certain...

How big is it? Meaning, why not just post the contents here?