Skip to Content
0
Feb 20, 2009 at 07:56 AM

MAM3.0 purpose SYNC_KEY

19 Views

Hi,

We are using MAM3.0. Sometimes we get an error on frontend. If I look in the trace file, I see there is following error while inserting a row in MAM30_030_110 (order history of functional location): java.sql.SQLException: [SQLState:23505, error code:-803]

This probably means there would be a duplicate key while inserting this row in DB. Correct? If I look at the rows he want to insert, I see he has 2 items of MAM30_030_110 that he wants to insert which are linked to the same MAM30_030 syncbo instance. Both these items have the same value for sync_key, syncbokey and state. I was wondering, is it okay he uses two times the same sync_key? That is actually my question, what is the logic behind sync_key? When should a different sync_key be used? Can it be that one syncbo with different items all refer to the same sync_key?

If i look at other MAM30_030 syncbo's which doesn't trigger an error on frontend, i see he uses a different sync_key for every MAM30_030_110 item.

Please advise,

thx in advance

Peter