DSXchange

Never seen a situation where a constraint was 'ignored'. Show us your actual constraint expression. Also, have you included the counter on the output link or are you just counting?

Which this, exactly? The "advisable to delete" question? If so - yes.

hargun wrote:and in output taking as varchar.

This is causing your warning. Why a varchar? As noted, output is a double and I believe you can override that to a decimal but any conversion to a string should happen explicitly after the stage.

The only way would be to take the issue to your official support provider. Let them tell us if it is problematic (and perhaps patched) or is 'working as designed'.

http://ss64.com/nt/regsvr32.html

The only thing the full client install might bring is that registration. [shrug] Let us know what happens in your secret home lab!

If the stage is doing that then (IMHO) it is broken. There is no situation in which Type2 changes should generate "an update only" meaning an update to an existing row without end-dating it and inserting a new current version of that record. Unless you are saying that it updates the record...

Obviously, I don't have experience with this on newer systems but have done this on older ones. Have they tried to run it? Were the dlls registered?

One of two questions answered...

Note that I honestly don't know the answer here, just trying to get past the obvious issues and hoping that someone who's actually done this shows up and lends a hand.

And what happened - you got the exact same error? You mentioned it where exactly?

Your issue and solution are detailed in the message you posted. "Bulk load" in Oracle means sqlldr and that utility has the option to capture rejects to an exceptions table rather than failing. In order for it to do that you must tell it the name of the exceptions table to write to. I don'...

The USERSTATUS of any job can be fetched at any time but is typically done after the job has completed. It is preserved until the next time the job is run or it is reset / recompiled. Typically some mechanism (say, via the API) would be used to fetch it from one job and pass it as a job parameter to...

Do an exact search here for "century pivot", this has been asked and answered before and that will turn the discussions up.

Seems to me that should recognize it has already been loaded and do nothing. Speaking strictly from a type 2 load perspective rather than what the SCD stage actually does.

Not sure... have you double-checked the constraints / indexes on the table to ensure they are all there and in a USABLE state?

Do you have a way to determine exactly what the character in question is? For Oracle you would use the DUMP() function in the SQL, not sure what the DB2 equivalent would be.