 |
|
 |
Subject: View design not replicating properly ( also agents and docs ) |
 |
 |
 |
Product Area: Domino Server |
 |
Technical Area: Application Development |
 |
Platform: Windows |
 |
Release: 8.5.2 |
 |
Reproducible: Intermittent |
 |
 |
 |
 |
Replication does not appear to be working as reliably as it has for the last decade or so.
I've been having this problem for some time now with documents in one particular database. A change is made on a document in one server, and it does not replicate back to the hub server. No changes to this document will now replicate.
If I cut and paste the document ( to get a new ID), it replicates fine.
However, today something similar happened with views and also with an agent.
I made some design changes to some views on my development server( just selection formula changes ), and then removed the design elements from live, and copied in the changed elements manually. The majority of the views(not all) promptly disappeared of every other server ( all 15 of them ) and refused to come back despite, signing, resaving, cutting and pasting.
I checked the server versions, it seemed a global issue regardless of version. I checked the design documents in the special design element view, there didn't appear to be any replication conflicts.
I deleted all the views from live again and copied them back in. A different subset of views appeared.
The solution in the end was to rename all the views in dev ( I just added an alias ), and then copy them back in. Then they all reappeared in the other servers.
It is behaving as if there are deletion stubs for these design elements, and instead of just checking the document ID, it is also checking the Title of the Design element before assuming I want the NEW one instead of the deleted one to take precedence.
Obviously this solution is at best a temporary work around, I can't continue to rename design elements every time I want to update them, and templates are not practical in this environment.
As it is, for now, I will have to check every design change I make to make sure it is getting sent out to other servers.
Has anyone seen this before?
The massive problem with this was, that I didn't know it had happened and when the database replicated out to the other servers, without its default view, it caused one of the SERVERS to crash.....
That's a separate issue however.
 
Feedback number WEBB8RB2UJ created by ~Zach Bubtumisternivu on 02/09/2012

Status: Open
Comments:

View design not replicating properl... (~Zach Bubtumist... 9.Feb.12)
. . It sounds like the sending server h... (~Bill Frokimari... 9.Feb.12)
. . Finger print & work around (~Delores Bubfre... 10.Feb.12) |
|  |
|