duplicate local sync_key in merep_111

[Former Member]

Hi,

we are having problems with the field of local sync_key in table merep_111.

The problem is that in the function MEREP_EXT_TO_INT_CON_FRM_KEYTB there are two select's (line 198 and 221)from table merep_111.This selects retrieve a single value and we have in data merep_111 two registers that have the same

idMobile, Sync_key and different SCENARIO.One of this two registers is marked to be deleted.But when we execute the merep_purge tool with runtime option according to delete this entries with action "D" if we set a number of days very small it delete entries of merep_111 that still are useful.

How can i know when this entries can be deleted??

Exist any relation between this entries and the entries of tables merep_10700 and merep_207??

thanks, regards

[Former Member · Accepted solution]

Hi Jose,

Exist any relation between this entries and the entries of tables merep_10700 and merep_207??

MEREP_207 is the middleware RDB and MEREP_10700 is the Client RDB...

Merep_207 is common table for all the mobile IDs and MEREP_10700 is the specific client RDB for that mobile ID.

Cheers,

Karthick

[Former Member]

the question is that if exists any relation between the entries of table MEREP_111 and the entries of tables ( MEREP_207 and MEREP_10700 )???

I

[Former Member]

But we have two entries in the table merep_11 with the same local_sync_key and different scenario.But one of this entries is marked with action "D" and the other no.

[AjithC]

Hi,

The local synckey is unique only to a particular mobile device. The global synckey will be unique across all devices.

The only chance of having duplicate local synckey for a device is during device reset.

The reason why this entry is kept as status 'D' is to help reprocesing the records if

required. The only way to delete the 'D' records is via purge tool.

Regards

Ajith Chandran