Name & Address Book corruption

HCL Domino Domino Forum
1

We have upgraded 4 hub servers and 2 mail servers to 6.0.1. Since the upgrade of the mail servers the following corruption occurs on all the servers upgraded to 6.0.1 (servers on 5x are not affected) This corruption did not appear on the hub servers before the mail servers were upgraded:

NIF: DETECTED STORAGE CORRUPTION ERROR ‘This database cannot be read due to an invalid on disk structure’

01/07/2003 09:41:00 NIF: in e:\notes\data\names.nsf collection “($Policies)”, ID=0 length 1024

Looking through the forum it has been mentioned that this corruption occurs after the designer task has shut down. The views that seem to be affected are $Policies, $ServerGroups and $InternetSites. Running a fixup, compact and updall fixes temporarily. Any idea how to stop this from happening permanently?

2

Subject: Name & Address Book corruption

No problems of that kind here.

Things to check.

  1. Is your backup software suitable for R6, this could cause a problem.

  2. Is your AV software suitable for R6, again a possible cause.

  3. Any other 3rd party add-ins?

  4. You mention the design task. Do you run this for any particular purpose. I disable it on all server build and run refresh/replace design on individual datebases as necessary.

Cheers,

Ben

3

Subject: RE: Name & Address Book corruption

Thanks for the quick response

Backup software is ok, No AV software on the mail or hub servers, no 3rd party add ins that I can think of. We have the design task in the ini of all servers. It runs at 1am. I wouldnt like to take this out permanently… might take it out for experimental purposes. But I dont understand why this error has just shown up now after upgrading the first mail servers. I didnt upgrade them differently to the other hubs

Thanks Joanna

4

Subject: Name & Address Book corruption

In our conversion we had problems with corruption showing up where it was not before.One thing I would do is take the NAB off line and run a compact -C -D -K -i, this will do a copy compact and drop all the view indexes. This has fixed most corruption we have seen and makes sure the database is on the new ODS (43) for R6. 601 seems to have some issues with the R5 ODS especially when running fixup.

5

Subject: RE: Name & Address Book corruption

Thanks for the response

A compact will fix it but the error comes back over night.

Joanna

6

Subject: RE: Name & Address Book corruption

I have taken the design task out of the ini for the time being and the corruption has stopped. This is not a suitable permanent fix though… anyone know if 6.0.2 has any fixes related to the design task?

Thanks Joanna