If an NLO file is missing on one system and that document is replicated, the replicator will report this error. This will cause the replicator to continue to ATTEMPT to replicate this document on every replication. If this error is encountered three times in a row the replicator will ABORT replicating the database. This can be AVOIDED by setting DEBUG_REPL_TOLERATE_ERRORS but does not resolve the problem. 

There are two ways to resolve this problem:

Restore the NLO file.

Run 'fixup -j -D' to delete the document REFERENCING the missing NLO.

If an NLO file is missing on one system and that document is replicated, the replicator will report this error. This will cause the replicator to continue to attempt to replicate this document on every replication. If this error is encountered three times in a row the replicator will abort replicating the database. This can be avoided by setting DEBUG_REPL_TOLERATE_ERRORS but does not resolve the problem. 

There are two ways to resolve this problem:

Restore the NLO file.

Run 'fixup -j -D' to delete the document referencing the missing NLO.