DSXchange

Kind of surprised as - unless something has changed - you are only allowed to have one key checked as the Repetition Element.

Salegueule wrote:The DS engine put quotes on all columns.

Because you defined them as string (VARCHAR) fields in the Sequential File target stage.

Perhaps drive the sources from a table or file, read from that to dynamically drive your loop.

You should also be able to confirm what was or wasn't installed by your Admin or whomever did the actual install. Plus I believe there may be a manifest file (XML perhaps) on the server showing the installed components and their versions. May be.

Looks like this is the relevant bit:

Caused by: com.ibm.e2.util.logging.E2LoggerCreationException: java.io.FileNotFoundException: /var/tmp/XMLStage_org.apache.http.wire_0.log (Permission denied)

Just to expand on that 'nothing fancy' comment, I just meant it's a SQL query to SELECT MAX(whatever) from the target. The wrinkle is how you get that into the job and like most things in a tool like this, there are many ways to skin the proverbial cat. A separate step could run the query and write ...

Welcome. Without dwelling much on your design, one typical approach is to gather the highest surrogate value from the target just before the load and you don't need anything fancy for that, then you should be able to seed a Surrogate Key Generator state file to use that as the starting value. It wil...

qt_ky wrote:I probably wouldn't worry about it unless you're seeing jobs run unusually slow or jobs or other processes abort due to out of memory errors or the like.

Agree. Why spend money on perfectly good memory and then not use it?

Please clarify, "items" here means... ?

You're better off taking a full export daily rather than an incremental, trying to cherry pick just the updated objects and then wondering where they actually ended up. IMHO

That document is hosted at Ray's site.

I'm assuming (can't turn it up in the docs at the moment) it is related to defining your multiple record types, as in the field to check and the values to identify (tag) each row type. It sounds like it found two things there that you didn't account for... which also sounds like they are not setup c...

How many jobs were running?

Anthony, have you been through the documentation on that option? Have an issue or specific question?

I don't believe there's any way for us to tell you the "why" of this, probably only the "what". A "BP.O" file is a BASIC Object file from what I recall and is created by the compiler rather than something generated at runtime. I've seen files like that disappear ("...

Sorry, just had to LOL at the classic "Let's eat grandpa!". For want of a comma...