DD unique constrain

cmcdieck

Hi,

we have a strange problem since we moved to TS 6 (6.1 SP2 on solaris, DD in DAS mode) if using more than one Workarea.

After creating a new DCR and save+submitting it, DD puts the tuple in the Staging Table and also creates a delta tuple in the second Workarea. So far, so good. But after editing the DCR again and finally submitting it, DD tries to insert the tuple in the delta table again (instead of doing an update). This is leading to the unique constrain error:

Excluding propagation to current delta...
Checking if _MAIN_YOUNGMISS_WORKAREA_DEVELOP exists in the exclude propagate list. PropagateRowsFromBaseToDeltas:INSERT INTO IWT_2047D40F2355 SELECT * FROM IWT_1B2F366E28CF WHERE Path = 'templatedata/YM_Content/Artikel/ data/reise_events/reisen/geschichten/auswahl.dcr'

*******************************************************
SQLException occured in TDbSchemaCfg
Exception Message: ORA-00001: unique constraint (PTSCMS.IWT_2047D40F2355_KEY) violated

Vendor Error Code: 1
SQL state: 23000
*******************************************************

*******STACK TRACE*************
java.sql.SQLException: ORA-00001: unique constraint (PTSCMS.IWT_2047D40F2355_KEY) violated ...


Is there anyone with the same problem?

Steffen

iwovGraduate

Theres a attribute in the configuration which allows you to specify DD to do update instead of delete + insert. (If thats the problem you are having).
If my memory serves me right, its called something like realupdates=true or yes.
Check the documentation.