Hi to all,
we are very often troubleshooting on the problem that old and deleted documents are replicated back to the server replica from a local user replica.
There are many descriptions of this circumstance on ibm.com , notes.net (cut-off date, purge intervals,…) and help with workarounds.
I never find a real solution.
All workarounds such as
database/replication script events
manupulating cut off date
replication formular (ggrrr)
disabling editor-rights (!)
-…
are no solutions and do not support a stable business plattform.
I do not understand why IBM do not want to change this to a real solution.
We more and more get trouble with obsolete data.
A big argument for lotus Notes WERE the replication and local security functions. This is gone.
Many of our key users agree to the statement: Probably Notes is not the plattform for business data any longer…
In my mind:
To solve this it is necessary NOT to remove deletion stubs
AND/OR
avoiding reliably replication with a datebase which is not up to date (not replicated in the last 30 days).
Please, IBM/Lotus or other “answer-ready” professional circles:
When will it or an other solution be implemented?
Thanks for any good answers to get back to a stable plattform…
Subject: purging deletion stubs is business critical; when will it be solved?
I am not sure from you description if you used database replication setting “Do not send deletions made in this replica to other replicas” ?
hcl-bot
October 17, 2007, 11:40am
5
Subject: RE: here the known issue/description
thanks a lot.Unfortunately, it is a workaround and does not solve the problem.
It is very sad that several Customers must spend many time on troubleshooting and to find workarounds.
And the only answer from IBM is “works as designed”. When do they realize that the customer need a solution to get rid of this trouble?
hcl-bot
October 17, 2007, 12:54pm
6
Subject: RE: here the known issue/description
I feel your pain as well. Seems like an easy “feature” to implement a way to prevent local replicas that have not replicated within the purge interval from replicating at all.
hcl-bot
October 17, 2007, 11:48am
7
Subject: RE: here the known issue/description
It could be an idea
http://ideajam.net/ideaexchange/ie.nsf/product
What is the Idea Jam?
Idea Jam is a place where people can post and share their ideas on how to improve products from Lotus software. When an idea gets posted, others can help promote and/or demote the idea and provide comments. Popular ideas will bubble to the top.
JYR
hcl-bot
October 19, 2007, 12:32pm
8
Subject: RE: here the known issue/description
Hi,
From Dallas Gimpel
http://www.openntf.org/Projects/codebin/codebin.nsf/CodeByDate/FF93BAD7004C0F1B86257370004C2B83
'// USAGE NOTES:
'// Among other uses, this code can be used in the event of a “late replication” event in which a remote user reintroduces old (purged)
'// documents into a database by way of replication. This happens on occasion when a remote user waits more than than a database’s
'// purge interval (30 days by default) to replicate. The purge interval is the interval at which deletion stubs are purged from a database.
'// It is 1/3 of the cut off interval, which defaults to 90 days.
'//
'// Since the “getAddedToFileDate” function above takes an api handle to a Notes database as an argument, the example code below,
'// which excludes declarations for the two modules above for brevity, shows a functional example with all required declarations, etc.
'//
'// To try this code, just place the functions above and the sample code below in a button, agent, etc, and call “main”. The “REPLICA_ID”
'// constant below will also need to be replaced with a valid replica id for testing purposes.
JYR
Subject: purging deletion stubs is business critical; when will it be solved?
And what, exactly, is the problem with changing the default purge interval?
hcl-bot
October 17, 2007, 4:52pm
10
Subject: RE: purging deletion stubs is business critical; when will it be solved?
Maybe 27 years is not enough. People might replicate for the first time after 28 years …
hcl-bot
October 17, 2007, 4:54pm
11
Subject: RE: purging deletion stubs is business critical; when will it be solved?
Ah, but at that point the docs would become “Golden Oldies”, reminding them of simpler times…
hcl-bot
October 17, 2007, 4:59pm
12
Subject: RE: purging deletion stubs is business critical; when will it be solved?
Hey, I’m working for a company, where one employee had a “golden” jubilee last(?) year: Working for the same company for 50 years.
Maybe Claus is working for my company as well and we just didn’t meet yet?
Honestly: If there has ever been a valid case for IBM to refuse any action, because the product is “working as designed”, this is it.
hcl-bot
October 19, 2007, 12:42pm
13
