DSXchange

Did you go to the Advanced Tab of Workbench and review the "Database Alias" link?

Ernie

Ok....great. Just wanted to validate that you were doing things at the Stage Level. It sounds like you have a "Database Alias" established for ODBC, but not for Oracle..... Here's what to look at: a) Go to the Advanced Tab in the WB b) Click on Database Alias. c) Look thru the list.....you...

Sort of....it looks like you are building the header, adding the first element and the concatenation of the string as part of your derivation. It's only a subtle difference, but I would imagine that you have the "whole header" in your working WSClient Job. Copy that "as is" into ...

I'm being explicit because I want to be sure I know where you are "starting" your lineage. When you follow the steps above, it shouldn't show you a "job"...it should show a list of stages to select from.....(on the Create Report page).

Ernie

Did it show you a list of Stages?

....I often take the same dev/debugging approach as you, and test with WSClient and hard coding. Step two would then be to use the exact same hard coded header with a WSTransformer, before going on with something more dynamic. Have you cut/pasted the exact hard coded header from the job that works i...

Ok...great. Now its a bit more clear. There "could" be some stage issues...it depends on a couple of factors. First, let's be sure that lineage is working "at all" for your Job. I'm also not sure yet "where" you are starting lineage. Find the Job that fails in the "...

Another solution is to use Metadata Workbench and just run a query for the Job object and list the Last Modified Date and Last Modified By values.....

Ernie

I don't see a problem, although it's very unclear to me exactly what your goal is. XMLOutput "creates" XML...... if you are initially reading it, I'm not sure what value xmlOutput has for this entire solution or problem. But if it is working for what you need, it shouldn't be a problem. Er...

Sorry if I led you down the wrong track for awhile...the insertion of the sequential file was just for debugging purposes...not for your final solution......... Sounds like you have things working now...

Ernie

That's what makes this site so great. We all give something...and we all get something..... Nice to be "surrounded" by experts when you "walk" into a situation that needs a creative solution.....I'm sure we can all say that we've used the site to "gain confidence" when ...

Where is/was sequential stage in the picture? Absolutely...the sequential stage will have horrible problems with "random" CRLFs, as often occur with XML........thought you were flowing directly from MQ into XMLInput....

Ernie

Not sure.....please state exactly when (make exact note of your clicks, and exactly what you are clicking on) you get the error.

Thx.

Ernie

Well.... you probably don't want to choose a destructive read in this case. A DataSet is just a file on disk --- there is no ensured delivery for that. To be safe, "browse" your messages and don't remove them from the original queue until you are sure that things have been completed succes...

Start first with design lineage...it's important that you fully get to know the patterns that are used to link Jobs/Stages/Tables together.... Check out the "Getting started with Data Lineage" entries that I have at my blog (see url below).... As to your Jobs, I'm not sure what you are exp...