DSXchange

Which is it, fixed or variable? Can't really be both.

Probably. In earlier versions it would have said "RTI Enabled" and that option would only have shown up if the job was multi-instance and the RTI Agent was running.

Does the help mention it? Not something I can check myself or I would.

Hmmm... as noted, that's why the quotes are there - they are needed for a Windows "Long Filename" when it has spaces in it. The workaround of renaming any directories to remove the spaces was pretty obvious and one that I didn't really see the need to mention, thinking that you'd want to w...

That DOS 22 error is more of a "bug" error than a user type error, in my opinion. You may need to take this up with your official support provider if nothing comes of it here.

Yah... it seems like you could do this in Seq2 to make sure Seq1 has completed before it "start starts", if that makes sense.

kiran259 wrote:After some search,I found that some clients do not accept VARCHAR>31.I am using Oracle 10g version.

If this is true, then perhaps you need to install an updated Oracle client.

I would never do such a thing. Continuously? :? I would schedule it at a regular time every day and run it up to just before that same time the next day, letting it stop just before it gets started up again. Actually, that's exactly what we did the last time one had to run "continuously" a...

Here is why Arnd is asking that:

http://stanislavs.org/helppc/dos_error_codes.html

I think you may need one or two supporting ddls as well, but ya that's about it.

If you know there will always be a header record, you could just subtract 1 from the line count of the file before you use it.

dsinfo wrote:Currently my xml test file have 4 transactions but my target tables showing only 2 transaction data.

Which two and what's different about them from the two that did not load?

Join on itself?

Have you tried this outside of DataStage, say using Toad?

You mean to loading data via DataStage? Pretty straight-forward but it does add some extra wrinkles over a relatively straight-foward extract job: bulk or conventional loads, update versus insert, data integrity, referential integrity, etc etc. You'll see.

I don't believe that the Stored Procedure stage supports procedures without at least one parameter. Probably more appropriate to use an ODBC stage for that.

What did you find when you googled for that ORA error? I found that it is a known Oracle issue, so it sounds like you should upgrade the client version you are using.