DSXchange

"I tried Server Job as well....to vain"..... The answer may be there --- Server Job certainly can't generate "osh" type errors......but I've seen cases where Server will yield a decipherable error when EE blows up because of a datatype/syntax/memory constraint type of problem. Wh...

hard to say...if this is the first time using the stage, it "could" be something really screwy, or a config/install type of issue...... ....but another thing to check is size...how big is the document. Various strange symptoms will occur if the doc is greater than 200 or 300 Meg.... ....an...

Check out exactly what release you are on....since 8.1 with FP1 applied, I've seen much more consistent behavior with namespaces...prior to FP1 there were numerous issues. If the XML is small, I've resorted to just passing it thru a transformer and zapping out the namespace details in the header and...

What Operating System are you on? What database are you using for xmeta? I haven't seen performance issues on Connector import, so I haven't analyzed that, but I've done a lot with analyzing things like Automated Services.....so this may be meaningless for your scenario, but it would be interesting ...

Test a Server Job's Oracle Stage and see if it can write to your particular column type, and then use a Folder Stage in Server to read the xml. If that fails, you could "experiment" with Folder inside of a Server side Shared Container, but passing long strings across the server/ee boundary...

it's by default....the MQ stage as a source will keep the job "always on"....immediately processing the message when it arrives. You can certainly "start" the job initially using a trigger mechanism, but once it is running it will just "be there" waiting for a new messa...

Anybody's guess. I wonder if it ran out of memory trying to do the work. Are you familiar with WAS and how to check the available heap size? Again, just a guess -- I wouldn't change anything at this point, but it might be something to look at. Sounds like an interesting application. What's your goal...

Certainly "2" shouldn't cause any problems, and I haven't heard of performance issues in this area. I will assume you are doing this from inside of DataStage using the Shared Table Creation wizard..... This one is news to me, but perhaps (this is just a guess) it has something to do with t...

Hard to say....there are a lot of things going on. For starters though, I would question the need to have a 1000 Jobs collecting Operational Metadata.....you may have a great reason, but it is something to think carefully about. The biggest value for OMD is for validating that target systems are wri...

There are several ways to map shared tables to a DataStage Job for data lineage purposes. Operational Metadata (OMD) is only one of them, and has the most complex steps. I suggest that you first start with the other two methods --- get those working, and then move on from there to OMD. I'm working o...

Very nice! That's great! I haven't seen a use case that demanded it (usually the variety is very low, or else dramatic and impacting downstream stages making a separate path of stages a requirement). Can you describe how #JPass1# changes? Does it ever include multiple nodes (slashes embedded in its ...

In this example, that is only likely to happen if you had a "blank" value coming in for one of your rows.... meaning that one row had an attendee value of "John" and another row had an attendee value of " ". It's unlikely that you would get two attendees here unless the...

In my last posting, I had you check "replace NULLS with empty values" so that you would be sure to see the results of your test...... When you uncheck this, NULLS "do not appear" (meaning...no tag comes out at all...) ....that is the default behavior and sounds like what your ven...

ok...good thread. This is a valuable, albeit less common scenario. I'd like to dig into it a bit further, as there may be others that are like it depending on Stage, Job type, data format, etc.... What exactly do you mean by: "a bunch of Table Defs that accurately reflect exactly what's in the ...

It's a big topic. Not sure exactly where to start --- certainly be sure to read thru the workbench users guide...it has good info there. But here are some things to think about initially.... -- consider learning how data lineage works by using a single large job that you are very familiar with. Sele...