Skip to main content
This forum is closed to new posts and responses. New discussions are now taking place in the IBM Developer Answers forum.
 
developerWorks
AIX and UNIX
Information Mgmt
Lotus
New to Lotus
Products
How to buy
Downloads
Live demos
Technical library
Training
Support
Forums & community
Events
Rational
Tivoli
WebSphere
Java™ technology
Linux
Open source
SOA and Web services
Web development
XML
My developerWorks
About dW
Submit content
Feedback



developerWorks  >  Lotus  >  Forums & community  >  Notes/Domino 6 and 7 Forum

Notes/Domino 6 and 7 Forum

developerWorks

  

PreviousPrevious NextNext

RE: replication cutoff date
Andre Guirard 3.May.04 01:00 PM Lotus Notes
General All Releases All Platforms


It sounds like you're talking about a scenario where someone creates an update on a local replica and then fails to replicate that database for so long that it expires off the replication cutoff, and when they do replicate it doesn't go out. I hate to think how many updates they're not receiving during all that time. Isn't it just as serious a problem that they have lots of out-of-date information locally, of documents that they did not edit?

Simple answer is, if it's so critical that information be up to date, don't let people use local replicas. Design the application in such a way that it must be used on the server; that way you can control all replication. Or, have the local replica check a timestamp that would let it detect that replication has not happened recently in a local replica (I've described how to do that elsewhere in this forum). If the database is not sufficiently up to date, refuse to let the user open it. That would force them to keep it up to date.

If you are already faced with the situation you're talking about, and you want to make sure that all documents are equal in all server replicas, you could create your own consistency checker fairly easily. Create a server agent that opens a view in two replicas of the same database. The views should be sorted ascending by date modified, and then by document UNID or some other unique unchanging key.

Scan down the views in parallel and see whether they match -- if not, "touch" the more recent version to force it to replicate out again to all the servers. Scan until you are finding documents in both replicas that are more recently modified than the replication cutoff. And there you go!




replication cutoff date (Michael Peets 3.May.04)
. . RE: replication cutoff date (Andre Guirard 3.May.04)


Document Options






  Document options
Print this pagePrint this page

Search this forum

Forum views and search


  Forum views and search
Date (threaded)
Date (flat)
With excerpt
Author
Category
Platform
Release
Advanced search

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS
More Lotus RSS feeds

Resources

 Resources
Forum use and etiquette
Native Notes Access
Web site Feedback

Lotus Support

 Lotus Support
IBM Support Portal - Lotus software
Lotus Support documents
Lotus support by product
Lotus support downloads
Lotus support RSS feeds

Wikis

 Wikis
IBM Composite Applications
IBM Mashup Center
IBM Connections
IBM Connections Cloud Developers
IBM Docs
IBM Forms
IBM Mobile Connect
IBM Sametime
IBM SmartCloud for Social Business
IBM Web Experience Factory
Lotus Domino
Lotus Domino Designer
Lotus Expeditor
Lotus Foundations
Lotus iNotes
Lotus Instructor Community Courseware
Lotus Notes
Lotus Notes & Domino Application Development
Lotus Notes Traveler
Lotus Protector
Lotus Quickr
Lotus Symphony
IBM Web Content Manager
WebSphere Portal

Lotus Forums


 Lotus Forums
Notes/Domino 9.0
Notes/Domino 8.5 + Traveler
Notes/Domino XPages development forum
Notes/Domino 8
Notes/Domino 6 and 7
IBM Connections
IBM Mobile Connect
IBM Sametime
IBM SmartCloud Notes
Lotus Enterprise Integration
Lotus Protector
Lotus Quickr
Lotus SmartSuite