DSXchange

First suggestion is to always do an Exact search here for your message and see if any of the people having the same problem posted anything that helps. If tried with:

call to OpenFileMapping() failed - The system cannot find the file specified

And got 20 matches.

Of course. That's where Standards come in. Mostly. The rest is handled with a Big Stick.

Depends on what stage we're talking about and exactly how it was setup to leverage parameters. Pretty typical, though, is to do something like: #p_Owner#TABLE_NAME To allow the owner to be dropped to leverage a local table or synonym without getting screwed by a hard-coded dot. Yes, that also means ...

So, no obvious problem jumps out at you?

Item #4 is an Info type and is marked with a green icon. Item #5 is Fatal and red. Item #6 is a Warning and yellow. So, start with the fatal error which says:

ORA-00942: table or view does not exist

That's all on you. Call the function (or a wrapper script) and pass it whatever it needs, either hard-coded or as Job Parameters wrapped in # pound/hash signs. Suggest the latter.

:? So, you checked the log of the child job that the controlling parent Sequence job reported as 'failed' as in Aborted, specifically: J_Stage_PS_BUS_UNIT_TBL_SF_CS_CS9_EPM9 And you don't see anything other than green Info messages in the log? Do you see messages from the job run in question? What i...

Clarify for us if this 'generated query in a file' is generated in the same job as the ODBC stage that will use it or in a previous job? Former bad, latter good.

I don't understand why people feel the need to come in and repeatedly speculate on what the answer might be without full disclosure of the issue from the original poster. I don't know about anyone else but I was planning on waiting for sreddy to come back before continuing this. Didn't quite work ou...

How about... hmmm... "ftp"?

Right, check your setting. What database / stage by the way?

Here's the rest of the sentence, don't think Ray will mind for this. You've got the meat of his reply regardless and need to realise that's how things work here, especially when it comes to Mr Wurlod.

ted" event and choosing "Related Log".

All stages have a General tab which is a perfectly good place for comments, even though some people may overlook them there. Stage Variables have a Description field in their setup screen where I always document their function. But no, as noted, there's no place for comments in code / derivations or...

That too.

I would think you should be reading it as one long varchar field and then parsing out the individual fields after you determine what record type you actually have. You could do this using Field() in a transformer, for example, or perhaps with the Column Import stage.