DSXchange

That doesn't mean you couldn't build something clever to work around this issue. I'm thinking a job parameter, probably of a List type with two simple values, yes or no. Add a new routine that you write to the job flow and branch around it for normal runs since it defaults to 'No'. On a reset run, f...

Verify the bottleneck. Replace the DB2 target with a sequential file and note the speed. If no significant change then remove the XML Input stage and put the sequential file target there. After that, you'll now which part is the actual bottleneck.

adasgupta123 wrote:Have any of the nodes that /u/InfoServ/PROJECT_PLUS/QA_GRS_R2_SIT_V1/datasets/USWMT_DC_FW_RWBFST.ds lives on been removed
from the configuration file since /u/InfoServ/PROJECT_PLUS/QA_GRS_R2_SIT_V1/datasets/USWMT_DC_FW_RWBFST.ds was created?

Have they?

DSGetLinkMetaData may be a new 8.x function that is not available in your 7.x version. I do not really believe this.. Recognize the fact that I said may since I had no way to check. :? Now that I'm home, I too can find it in my old 7.5.x documentation so it should indeed exist - but someone with ac...

suse_dk wrote:Can't you problem be solved by setting the execution action to "Reset if required, then run" for all sub sequencers? Then it should only be necessary for support to reset the top sequencer...

Only if you never want to be able to do a checkpoint restart.

No, not that I've ever seen.

DSGetLinkMetaData may be a new 8.x function that is not available in your 7.x version.

I'm assuming you ran on two nodes and got the 20th record on each node. Disregarding partitioning for the moment, what you need is @INROWNUM <= 20.

We've seen this posted before - fatal in the log, job doesn't abort - but I don't recall ever seeing a good reason for it. Me, I'd ping your official support provider and let us know what they say.

True, there's always something controlling the "century pivot" aspect of conversions of two-digit to four-digit years. Of course, you can easily do your own simple if-then-else check and stick the century on yourself.

I don't know if there is something more "official" but I'd probably look at using StringToDate & DateToString to convert this. Add something like "-01-01" to the two-digit year, convert to date and then back to string using only "%yyyy" for the format.

Ah... good catch.

No clue, as noted double-check with your support provider. The 8.5 documentation for Oracle doesn't note any version restrictions in it that I can see but I do see snippets like this: This predicate is only available when you are building an Oracle 8i query with an 'old style' join expression. Which...

Where the PX Engine lives... PX as in what drives Parallel jobs. I'm guessing yours is fairly empty? Or does everything get installed and it's just not active as it's not licensed?

Found this today, interesting stuffs.

Version 8.7 introduces new features and functions that affect existing Version 8.5 jobs. In some cases, you can set environment variables to retain the Version 8.5 behavior.

Information Server Version 8.7 Compatibility