DSXchange

I'm sorry but I don't remember whether/if the xmlpack2 stages could be installed separately....it's been too long since I've been on 7.5... I recall strange times when I needed to re-register the gui side of it (at the client, if you get the little "plug" boxes instead of the xml icons...b...

You are doing it correctly. The only time that lineage should stop at the column level is if the output column is derived from a Stage variable that doesn't use any input link cols.......if it does, then lineage should continue thru the Stage. There is apparently dual patch for this..one for DataSta...

New smells bring new experiences. Metadata Workbench alone is worth holding your nose.

Ernie

Why? It really should be no concern. The metadata store is laid down for you and may as well just be a "black box." Like the Universe metadata store before it, it keeps all your ETL design metadata, plus a whole lot more. Universe is still there to support the run time engine and execution...

I don't know if it's exactly the issue that you are having, but there is a patch to 8.1.2 that may help you....it fixed another site I know of who was experiencing the same symptom. The patch became available about a week ago.

Ernie

What's wrong with the &amp hexcode? Any tool reading the xml should work fine with that too.

DS should obey the OS security rules. Having another layer in a tool like DS opens doors to other problems.

What are you trying to pass into it? Does a test job with a string like "hello" passed to the MQ Connector from a Transformer work ok?

Ernie

Take a look at the encoding that you are using....there was a thread in here a week or so ago where we were talking about the copyright symbol. In there I posted the results of some research with the various encodings. That might help. Worst case, you'll need to convert it an put in its escaped hex ...

Ok. I'll bite. It is vastly more than just "another piece of middleware." It's often the core of the entire data integration infrastructure for thousands of companies. And as that "core," represents the lion's share of intellectual capital about "the" data and metrics t...

Assumng that your job is just a simple source...copy...transformer...xmlOutput...Sequential, then start looking at other things...compare the properties in your xmlOutput in "this" job to the jobs where it works.... How is this one different from any of your others? Try different sources.....

Time to start breaking it down.... It looks like both the xml output link and the other primarily link are fed into the lookup? Create another Job and remove the whole top path..... just write the xml output in a straight line...does it still fail? This is probably a problem of stages in some sort o...

ok...so following on Craig's note, tell us more about "that" Job...what makes it unique?

Ernie

Not sure....obviously it is impacting memory somewhere. Still...even if you get around it for now...it's possible it will get bigger and blow up tomorrow.....start looking for alternative methods to indicate how many rows you want....in this call, and then successive calls, etc....

Ernie

It's probably nothing to do with your xml "in particular"....that's pretty generic. Can you get "any" XML to work? What release are you upgrading from/to? Do you have other Jobs with xml that are working? What is the size of the xml that you are moving around on the links? It cou...