Since we upgraded our server (AS/400) to 5.08 last week-end we have a serious problem with both the full-text indexer and the domain indexer (they worked fine before). Both of them have been destroyed and can't be rebuild again. The database affected is a document library (1GByte without Index) that contains about 43000 documents with various attachments (word, excel, Zip etc.). Compact, update and fixup didn't help. We also tried to replicate locally, delete the server copy and then replicate backwards, but to no avail. The ACL of the database is correct (Indexing Server is manager)
Problem full-text: Once you try to rebuild the following error messages are logged:
02.12.2001 12.11.52 Periodic full text indexer starting, performing hourly full text indexing
02.12.2001 12.12.33 Periodic full text indexer terminating
02.12.2001 12.14.11 Message C1256A14.004C4170 was not converted successfully
02.12.2001 12.14.11 Error full text indexing document NT0001FA2A in database /Chicago/Allgem/Dach041/kunden.ft: File does not exist
02.12.2001 12.14.13 Error full text indexing Dach041/kunden.nsf: Bad document ID/key
We identified the document, deleted it from the database and rebuilt the index: same error message, but with a different document ID. After the error the full-text-index drops to a 0-KByte-size.
Problem domain-index: Basically the same problem (see error log below).
03.12.2001 00.31.23 Error full text indexing document NT0001FA2A for database Dach041/kunden.nsf in domain index /LNT04110/ftdomain.di/NotesDB/37010.0088855324: File does not exist on remote server
03.12.2001 00.31.25 Domain Indexer finished indexing Database 'LNT04101/SRV/DACH041/DACHSER/DE Dach041\kunden.nsf': Bad document ID/key
Does anyone have an idea? - We can't just continue deleting the 'bad documents' from the database (first of all we don't have a clue how many of them are 'hidden' there, and apart from that I am not that weary of life yet that I'll call the database users and tell them that maybe thousands of their customer documents have been destroyed). Please help!!!
Problem full-text: Once you try to rebuild the following error messages are logged:
02.12.2001 12.11.52 Periodic full text indexer starting, performing hourly full text indexing
02.12.2001 12.12.33 Periodic full text indexer terminating
02.12.2001 12.14.11 Message C1256A14.004C4170 was not converted successfully
02.12.2001 12.14.11 Error full text indexing document NT0001FA2A in database /Chicago/Allgem/Dach041/kunden.ft: File does not exist
02.12.2001 12.14.13 Error full text indexing Dach041/kunden.nsf: Bad document ID/key
We identified the document, deleted it from the database and rebuilt the index: same error message, but with a different document ID. After the error the full-text-index drops to a 0-KByte-size.
Problem domain-index: Basically the same problem (see error log below).
03.12.2001 00.31.23 Error full text indexing document NT0001FA2A for database Dach041/kunden.nsf in domain index /LNT04110/ftdomain.di/NotesDB/37010.0088855324: File does not exist on remote server
03.12.2001 00.31.25 Domain Indexer finished indexing Database 'LNT04101/SRV/DACH041/DACHSER/DE Dach041\kunden.nsf': Bad document ID/key
Does anyone have an idea? - We can't just continue deleting the 'bad documents' from the database (first of all we don't have a clue how many of them are 'hidden' there, and apart from that I am not that weary of life yet that I'll call the database users and tell them that maybe thousands of their customer documents have been destroyed). Please help!!!
