DSXchange

I design a parallel job with change capture, and my stage properties setting as follow:

exclude values: some fields I don't want to compare
change keys: fields as keys
options:
change mode=Explicit Keys, All Values
other settings as default.

I absolutely assure that I pick up the right fields as the keys, and I check the "key" option of these fields in the columns list.
But when I run the job, I get the error:
Change_Capture: A field cannot be both a key and a value.

If I set

change mode= Explicit Keys & Values

, and explicit the key fields and values fields, it works out.

How could that happen? I've spent nearly all day on that problem. Please help!

Welcome.

I've not used the stage in years so just going by the documentation that says:

Change mode
This mode determines how keys and values are specified. Choose Explicit Keys & Values to specify the keys and values yourself. Choose All keys, Explicit values to specify that value columns must be defined, but all other columns are key columns unless excluded. Choose Explicit Keys, All Values to specify that key columns must be defined but all other columns are value columns unless they are excluded.

I'm wondering if your problem with that last option was the "unless" phrase, was there any overlap between your key and exclude choices?

Edit: after sitting here and staring at my answer while the site slowly attempts to move elsewhere, I'm not sure how helpful it is. Normally I would ask if you've engaged support but if you're really still rocking version 8 of the product, that's not an option for you. Hopefully someone with actual hands-on experience will wander by today.

chulett wrote:...after sitting here and staring at my answer while the site slowly attempts to move elsewhere...

Just got them to reboot the server. MUCH better now...

Thanks Andy!



<makes me wonder if there's a memory leak gumming up the works>

Jason, did you work this out, have a resolution?

there is not any overlap between the keys and the values. I've checked
that for several times.
I asked this question on stackoverflow too, but not get a solution until now

Have you involved your official support provider as well?

the official support expired