size of mail file

115 pts.
Tags:
Lotus Notes
Lotus Notes 6.5
Lotus Notes 6.5.x
Lotus Notes 6.x
Lotus Notes Domino storage management
Lotus Notes Mail File
I have a user that had a very large mail file. I deleted alot of her mail. I ran a fixup and compact on it and the mail file has not gotten smaller at all. We have no restrictions on the size of our mail files. We are running it on an AS/400. We are running 6.5. Her mail file size is still saying 4.5G.

Answer Wiki

Thanks. We'll let you know when a new response is added.

I would go to the mail file on the workspace and then go to new copy. After creating the new copy locally it will create a new local replica ID. Then take the local copy and replace it with what is currently on the server.

***NEW THOUGHT***
I would not do as the above suggests, not because it won’t work though. To reduce file size using the compact command at the server you need to use 1 of 2 switches. Either you can use -B after the rest of the compact command, or a more efficient way is to use the -c command – BTW, the switches are case sensitive, that is an upper case b or a lower case c.

For example, run the following at the console

load compact mail\userfilename.nsf -c -i

This should compact and remove the white space.

Mike Kinder

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Davidkillingsworth
    I agree with Mike, you shouldn't replace the local replica with the server's copy of the replica. It will work, but generally server replicas of databases are much more stable than local replicas. This is mostly because maintenance is run regularly on server copies of databases. That is if you have program documents which run fixup and compact on all databases at least once a week. You shouldn't necessarily need to run compact with the switches that Mike mentions, but sometimes databases get to the point where they need special attention. A 4 or 5 GB database can get into a state where it needs special attention. If you go to the Administrator Help, do a search for "compact options" it will produce a document with all of the switches for compact. Here's the ones that Mike lists: -B = Uses in-place compacting, recovers unused space and reduces file size, unless there's a pending structural change in which case copy-style compacting occurs. If you use transaction logging, do full database backups after compacting completes. -c = Uses copy-style compacting. Use this option, for example, to solve database corruption problems. -i = Enables compacting to continue even if it encounters errors such as document corruption. Only used for copy-style compacting.
    175 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following