Generation numbers are out of order

[ToreTjøtta]

Hi,

We have an issue with replication in a disconneted environment. We're running ArcGis 10 sp3 on Oracle 11.2.0.3.0 We have multiple replicas set up that has been running for several months.

Our problem occures when we try to import a data change message. We can export the message perfectly ok, but when we try to import it again we get following message:

Import Changes failed.
Generation numbers are out of order

(and then a list of messages saying Version not found... (see attached screenshot))

There is no difference either we use xml or file geodatabase for the datachange message. The result is the same either way.

Any idea why this suddenly start to happen and how to fix it?

Also, we have synchronized this replica many many times before this started to be a problem, so something strange is going on here...

BR
Tore

[JeanetteBachand1]

I had this same issue and made a call to ESRI to ask them about what the problem was.  If you open the.xml document there is a line that indicates "[repllicaName]gen#".  Compare this number to the one found under the gdb the replica was created from under Distributed Geodatabases/Manage Replicas and double click on the repllica you're trying to import a message from to open the Replica Properties.  Under Relative Replica it will indicate it's generation number.

For instance in the Replica I am trying to import an .xml message to says the generation is 3 and the .xml message I tried to import has a generation of 6.  Therefore there should be two other .xml message files that were never imported/received on my side.

As for the version part, make sure the version you created when you first created the replica is present.  I always use DBO from our SDE so that other people in our company can import messages just in case I'm not around to do so and I guess that's just a better way to go.  If you didn't do that to begin with when you created the replica I'd think it's too late for that.  But just make sure the version is created with the same name and under the same account username as when you created the replica.

Hope this helps!

Jeanetta

[HeatherMcCracken]

Hi Tore,

Jeannette is correct - the "Generation out of order" message means that you are trying to import a new set of changes, but there are others that you are missing for one reason or another (maybe the file got lost, forgot to import, who knows). Replication can determine this because we keep track of what changes were sent and received using a series of generation numbers - which is one of the terms Jeannette referred to in her description. 

To fix this can you try the following:

1) Use the "Re-Export Unacknowledged Messages" to recreate the xml file (i.e NOT "Export Data Change Message").  Make sure to leave the default option to "Include all unacknowledged data changes".  This will ensure that all pending data changes will be included in this XML.
2) Import this into the target - this should succeed because it should now contain all the pending changes.

My guess is the "version not found" part of the error is extraneous.
Please try the steps above, and respond with how it goes.

Thanks,
Heather

[ToreTjøtta]

Hi, and thanks for your response on this issue.

When I try to perform step 1 and 2 on a replica we have issues on, it fails. It work fine to re-export unack'ed messages, but when we try to import this message on target, it fails with the same message: Generation numbers are out of order"

Any suggestions would be highly appreciated.