DSXchange

Try something else to escape the quotes, like a back-slash.

eostic wrote:It won't.

To me a question would be: where do you want to maintain this history? Separate from or incorporated into the target?

Nothing in uvconfig will affect "fail to open project". I know there are specific error messages that should also be reported, but wouldn't running out of certain resources also cause the 'fail to open project' message? I've got nothing to refer to and just working from memory, thinking a...

See if this helps.

You have to not mention a column in your DML for the default value to be used, setting it to null will cause it to be null regardless of the default. That's true for Oracle and I'm assuming other databases as well.

Why not test that theory yourself? Sounds all kinds of wrong to me.

Jayanto wrote:is first giving the fatal error "Issuing abort after 50 warnings logged." But I am running the job, with NoLimits for warnings....

Apparently not.

Why not fix the jobs so they don't log those warnings?

As would I... perhaps something needs to be tweaked in uvconfig?

Server job aborts report an active stage, which typically means the transformer but the error could be anywhere. And without the clue from doing a Reset, they can be difficult to track down.

So let it be written, so let it be done.

A quick google for "argument list too long" (which is what I assume your issue is) should help with alternatives to the ls you are doing.

So... resolved?

Are you doing Type2 updates? If so then yes, they absolutely require a new "dimid" for the updated row.

Show us the 'trim functions' you are using. That and examples of values that load correctly and ones that ended up zero.

There is no 'loop logic' in 7.5, you'll need at least 8.5 for that. Search here for horizontal pivot for thoughts on how to handle your issue.