User is getting error " b-tree structure is invalid" . How do I use file replica to replace existing file?

ASKER

Bill,
Thanks for your quick, detailed reply. I have a few questions.

(1) How do I check for Manager access to the database (meaning the single dm.nsf database)
(2) How do I check for access to delete/create databases function on the server
(3) I am not sure I understand what you mean by "from the server copy". I am using Lotus Administrator to view the mailbox databases. I can right click on the database and I have the create replica function available. I am logged in as administrator.
(4) When the replica is complete, delete the server database. Using Lotus Administrator do I just right-cllick on the database and select the delete function?
(5) "From your temporary local replica, choose "File - Replication - New Replica". Select the server name then click OK to create the new replica on your server." I assume the replica (the one that I created on local computer (which is the notes server)) will be visible in Lotus Administrator.

I am a little confused on the steps here. I want to certain that I do not make the problem worse by some error on my part. I want to understand exactly what and why I am taking each step.

I would not do this via the Admin tool since BILL GAVE AN EXCELLENT explanation but may have left out one important thing.
You need to do this and also in the options tell it to use a 4 GB maximum size if you are doing this using an R5 client.
R6 and above do not have these issues.

Another option is to use the server console and to run

Compact -M dm.nsf which if I remember correctly, should rebuild it and allow the 4 GB max size for R5.

I hope this helps !

see

https://www.experts-exchange.com/questions/20677500/B-tree-structure-is-invalid.html

for what to do.

Load compact databasepath -M ( maybe ncompact on windows ) should work if the DB is < 4 GB size.

otherwise see the updall option above.

Bill-Hanson

SysExpert has posted some ideas that do not require re-creating the database, so I would try those sugesstions first. If that does not work, we can walk you through replacing the database.

ASKER

Sorry about the late response. I got caught in some other issues today. I tried the compact command from server console and got the following results. Looks like I will have to replace the database.
load compact -M d:\data\notes\data\mail\dm.nsf
08/16/2007 05:53:10 PM Compacting database d:\data\notes\data\mail\dm.nsf (Dawn B Moore)
08/16/2007 05:53:11 PM Searching Administration Requests database.
08/16/2007 05:53:22 PM Error compacting database
d:\data\notes\data\mail\dm.nsf: Document has invalid structure
08/16/2007 05:53:22 PM Database compact process shutdown

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Oh, and try FIXUP

ASKER

tried the -D parameter with the following results. (is the fixup command load fixup database name?)

load compact -D d:\data\notes\data\mail\dm.nsf
08/16/2007 07:41:38 PM Compacting database d:\data\notes\data\mail\dm.nsf (Dawn B Moore)
08/16/2007 07:41:50 PM Error compacting database
d:\data\notes\data\mail\dm.nsf: Document has invalid structure
08/16/2007 07:41:50 PM Database compact process shutdown

ASKER

I have a question about copy-style compacting. I reading the help documentation it states that it creates a new database and then deletes the original database after compacting completes. Does it then rename the new database to the old database name? If so, is this not the same thing as creating a replica, deleting the database, and then replacing with the replica? With copy-style compacting, will the user be able to access the database after the compaction is complete?
Thanks for everyone's help. I have limited experience with this level of Notes administration.

Yes, it acts very similarly to creating a new replica, then swapping file names.

FIxup might be able to reove the corrupt "document," whatever it is. I would try it plain, or with the ofllowing options:
-F full scan
-J if you are using transaction loggin

ASKER

Ran fixup and got this message. Does this mean the database is dead? Can I restore from tape? If so, do I just replace the existing database with the database from the tape?

load fixup -F d:\data\notes\data\mail\dm.nsf
08/16/2007 11:11:14 PM Database fixup process started
08/16/2007 11:11:14 PM Performing consistency check on mail\dm.nsf...
08/16/2007 11:11:18 PM Completed consistency check on mail\dm.nsf
08/16/2007 11:11:18 PM Unable to fixup database
d:\data\notes\data\mail\dm.nsf: Database is damaged and can't be repaired (UNID index)
08/16/2007 11:11:18 PM Database fixup process shutdown

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Yeah, using a different version might allow you to open and copy. or, if you can open it locally even using an R5 client, you might be able to do the same.

If R5, R6, R7, and R8 clients can't open it, then kiss it goodbye.