Hello
I have a user’s archive database that has grown over one(1)gig. I tried to create a new replica, and increase the size from 1Gig to 4Gig, like the Notes error message is suggesting has the solution, but the same “Database has grown too large” error message comes up.
I have tried using Database-Copy but I get the same error message that it can procced because database has gone too large (note also that the database-copy did not offer the features to increase the size limit like the new replica offers).
I am using Notes 6. This database I beleive was created when we were using Notes 5. I even tried opening it from a Notes 5 client, but got the same error message, it doe not even want to install the icon in the workspace. I tried tricking Notes by renaming the file to name that I already had the icon installed. But no luck… anything I tried, I got the same error message. Even with NotesPeek, I can’t view the content of that file, it just displaying the same error message… (Help!)
Anyone has an ideas on how to fix. Need to open up this database to clean it up, so user can get back to work.
(Note: I found a treat for the same error message in the Notes 5 forum… but there are no solutions yet:
http://www-10.lotus.com/ldd/46dom.nsf/0/ccbb5d31351e50e185256e7d00589166?OpenDocument
Subject: Solution
You need to add the following line to the ini of the workstation where the database resides.
SKIP_FIXUP=1
Then run compact from a command prompt on the database and you should be good to go.
I have had this many times with local archives which become inaccessable after upgrade to ND6.
Good Luck,
Rob
Subject: Question
Hi Robert,
we got an user with a mail-DB size grown to 50 GB. ODS shows as 41, so i tried to compact the DB with your solution, but it didn’t work.
And i have a question: You wrote to add the ini entry on the workstation where the db resides. What to do when the DB is on the server?
We added the SKIP_FIXUP=1 to the server.ini, since there is no notes client, and tried it with the ncompact from a command prompt, but still got the database size too large error.
If you got any helpful ideas, any hint would be appreciated 
Péter
Subject: Database has grown too large error - need help
Daniel
What is the ODS of the file - 20, 41,43
Starting with R5 the database size is virtual i.e can grow to any size [64 GB].
If it is 20 it means it is in R4 ODS format. If you have an R4 client or server in your environment you may be able to fix it by using the compact -m switch.
If it ODS 41 or ODS 43 compacting the file with an R5 client is supposed to change the ODS format and create the virtual size.
Rm