DSXchange

It looks like you are getting close! ....make one of the lowest level elements (that repeat at the innermost part of the document) a "key" and then be sure to use the "aggregate" option that you will see in the tabs at the output link.

Ernie

It would be interesting to know more about "where" it dies...just to be sure that it's not a problem un-related to volume. We know that 1k works....does 100M...does 200M ? does 500M.... does 1Gig? Perhaps you have a particular element or attribute at the 1Gig mark that it has trouble with....

The next thing is to understand exactly how you are implementing the 8.5 xml stage.... What method, in your 1k working example, are you using to pass the document or name of the document to the xml Stage ...there are many ways to do it..... Please describe the structure of your Job (stages and their...

I haven't tried it recently, but if you can't get an entirely blank attribute via the settings, it may require that you build the element yourself......build it upstream (concatenate the tags and things together, along with the value in the element, if there is one) and then experiment with the data...

First thing is the most critical --- does the job read the file perfectly with a test document that is 1k?

Ernie

...what do you mean by "removed the old xml out stage" and put in the new one? I "suspect", since you are saying you migrated from 6.x, that it means you originally were using the xmlWriter? If so, it's not as simple as moving in one for the other, unfortunately. You will have to...

commit = 1 with an rdbms target is a good way to see your messages.....it's likely also that they are being written to the file or dataset, but you can't get to them until the file is formally closed. Look in the doc for the "message type" support. You can specify a long integer message ty...

Not sure what you mean "unable to route it as output"...do you mean on an output link to a downstream stage? If so, just have a single column like "myXMLdocument" on the output link, with a long varchar as datatype and a single '/' in the Description property. As for the formatti...

You might consider looking at istool and its ability to invoke the MWB query and send its output to a csv file...then you could manipulate externally as necessary.

Ernie

Currently the MWB queries cannot be parameterized. Have you looked at using DSJob and its command language as a way to get results of your Jobs in an automated fashion?

Ernie

For testing purposes, remove your output link. Put the xml document to a file.

Ernie

Import the document you have below via the xml metadata importer. Click only the inner most boxes (with the "T"). There should be five of them. Indicate TransactionLineNumber as a key. Load that tabledef into your input link. Spend time searching thru other threads here concerning addition...

For Oracle? don't even bother with Java........the in-the-box Oracle Stages and Connectors are long proven for their operation, performance, stability and behavior. Those are the only recommended way to connect to Oracle unless you have some very special reason to do otherwise.

Ernie

If you "want" to.......the Stages that are there all try to use the native APIs, and usually via C++......unless you have a strange database that only supports JDBC, and hasn't ever provided an ODBC driver, there should be little reason to use JavaPack...... however, if you have the expert...

I doubt seriously if it will work. You need to install DataStage in order to get it's "pieces" of the underlying metadata model deployed into the Information Server (xmeta) in question.

Ernie