HenryKafeman |
Thanks, but I would like to be able to access the Database.
I have tried “NCOMPACT” which should update to current ODS and also “NCOMPACT -M” which should update ODS 20 to 4 GB.
Any other ideas to be able to access the Database? If I could access it, I could delete some content to make it smaller and also make sure that I have everyting I need in my other Replicas (which are ODS 41 or ODS 43)!
Brooklynegg |
There is a command and option for increasing the largest allowable size for the database. I will look for it and let you know. Is this a mail database?
HenryKafeman |
Yes this is a Mail Database and is probably ODS 20 or perhaps ODS 41.
Brooklynegg |
I assume this is on the server. Try shutting down the server, running ncompact.exe -D -M from a command line prompt. The -D updates without any view indexes, which will save size as part of this emergency compact. It also does a copy style compact instead of compacting in place, which should help with corruption. The -M increases the size quota, as you already know. That’s probably as much help as I can give. I don’t have a ton of experience. If you have trouble with the syntax while running compact from the command line, let me know.
HenryKafeman |
I am on a Client.
The .NSF File happens to be located on a Mapped Drive, but as far as Notes is concerned it is a “Local” Replica on the Client.
I did try copying the .NSF File to a local Drive but that made no difference when running NCOMPACT.
I will try with the -D Switch and let you know tomorrow as it is 5:30pm UK Time now!
Brooklynegg |
I think you are back to simply creating a new replica. I am sure you won’t lose any documents. You can compare the number of documents between them. I can’t remember these issues from the past. I reviewed several I have dealt with and can’t find that they were that tough to handle. If you have already tried making a new replica and it fails for some reason, I would call IBM Support. In the past, I have been able to compact the database with success.
SteveT101 |
I’ve seen this method used to open an older ODS nsf:
1) Close your Notes Client.
2) Add “Skip_Fixup=1″ at the beginning of your Notes Client notes.ini.
3) At a cmd prompt, type “ncompact.exe dbname.nsf -m -c -i”.
4) Remove the notes.ini parameter.
While I haven’t had a need to use this, it was submitted as a client-side approach to allow opening the file.
HenryKafeman |
“Skip_Fixup=1″ does not help - NCompact still performs a Consistency Check and then reports that the Database is too large. I have tried this with Notes v6.5.5. IS it worth trying with v5.0.12 (or even v5.0.8)?
HenryKafeman |
MAGIC!
Skip_Fixup=1 works with v5.0.12!
The Database ended up as 630MB from 957MB!
It is working fine again although it has grown somewhat as a result of Replicating (not just due to incoming Emails) and is now at 642 MB.
Also my New Replica has grown from 757MB (after compacting it) to 803 MB - I thought it was doing this uncontrollably even in between Replications (a few days ago I did see it get to 1.4GB or so before I stopped it and reverted to a saved copy!) but it seems okay at the moment!
Do you have any knowledge/experience of Replica Databases growing for no apparent reason in this way - e.g. Why and how to stop/limit it????
Thanks for your Help.
Lotus Domino, Platform Issues
I have a Notes Replica which is 957 MB, but when I try to access it I get with v6.5.5 and v5.0.12:
0
