is rid in ml_database related to IdentitySignature?

[Baron]

I have a 2 tire installation (2 DBs synchronizing against each other with Mobilink) (1 Cons. + 1 Remote).

I need now to add a new Remote, so I have copied the first Remote and prepared it to be a new client for the Cons. with following steps:

1. DROP SYNCHRONIZATION SUBSCRIPTION TO "MyPub" FOR "DB1_User";
2. DROP SYNCHRONIZATION USER "DB1_User";
3. CREATE SYNCHRONIZATION USER "DB2_User";
4. CREATE SYNCHRONIZATION SUBSCRIPTION TO "MyPub" FOR "DB2_User";

Then I added new mobilink User DB2_User on my Cons. and tried to synchronize.

I have now problem with the table ml_database since it recognizes both database as one, and as a result I get the same rid for both databases in the table ml_subscription!!

Is this is because both Remotes are originating from the same database? (they both have the same IdentitySignature)?

How can I solve this problem?

[regdomaratzki · Accepted solution]

The ml_remote_id database option in the database is used to uniquely identify a remote database in a synchronizing environment. If you copy a remote database that has already synchronized, you need to change this value. Note that if the ml_remote_id value is not set (or set to the empty string) and you run a synchronization, the ml_remote_id value will be set to a UUID value automatically.

After copying the remote databsae, I'd suggest running the following command so that a new ml_remote_id value is defined for this remote database on the next synchronization.

SET OPTION PUBLIC.ml_remote_id = '';

Reg

[Baron · Accepted solution]

OK, thank you. For my remote database I have this value: 19d5edb8-a4be-49ce-b5d8-883f97e68dd4

Which value should I write here? Anything? Or the places and the hyphens should be respeceted?

[regdomaratzki · Accepted solution]

As I stated in my last message, I would suggest setting the value to the empty string after copying the remote database and before the first synchronizing. This will result in the value being set to a UUID value (i.e. guaranteed to be unique) when the first synchronization is performed.

[Baron · Accepted solution]

OK, thank you.

I got it!