Well, isn't the most likely explanation that the backup also contains the duplicate?
Either way you should contact support if you want to dig into the problem more. If there's a bug involved, they will want to know about it. -- Mike On 26 Jun 2013, at 10:41 , Florent Georges <[email protected]> wrote: > Michael Blakeley wrote: > > Hi, > >> In this situation I would probably use xdmp:node-delete. That way >> you can select which of the two documents to keep, and which to >> delete. > > Thank you, Michael. Yes, that's what I thought as well. But before > doing anything, I just wanted to check if anyone had experienced this, > as this could have side-effects even only by calling xdmp:node-delete > (when there is some corruption, you never know, and this is on a live > system). > > Basically, we were able to reproduce the problem on a new MarkLogic > instance by restoring a backup. Then what happened is that one of the > documents disappeared after a re-indexing, without any damage (and we > don't really care which one is remove in this case). So we are > probably going to do a re-index on the live system as well tomorrow > morning. > > So more than solving the problem (which is most likely to be fixed > tomorrow), we still have the backup and can reproduce the problem, so > it might be worth trying to find out what happened and how to prevent > it? > > Regards, > > -- > Florent Georges > http://fgeorges.org/ > http://h2oconsulting.be/ > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
