Lotus Notes : Recovery Manager Error - Log file is full . Unable to open and databases or mail files.
Hi Guys,
We started getting an error this error yesterday afternoon and we are unsure of it cause or how to proceed to solve the issue.
"Recovery Manager: Log File is Full"
It first started yesterday afternoon, people were getting it while trying to use their mail.
And then it was noticed across all lotus mail files and databases.
Only way we were able to sort was by doing a full server reboot.
Same error occurred again this morning to which I again have restarted the server to get it running once again.
I have read up a bit about it and it has to do with DAOS and transitional logging? Though we have been running DAOS for over a year now with no issues. No changes to the system have been made that I know of. Seems that it should have been fixed in 8.5.1 and for previous versions the restart is only option.
We are running 8.5.3 both Domino and Lotus Clients.
Any help would be much appreciated.
Cheers
We started getting an error this error yesterday afternoon and we are unsure of it cause or how to proceed to solve the issue.
"Recovery Manager: Log File is Full"
It first started yesterday afternoon, people were getting it while trying to use their mail.
And then it was noticed across all lotus mail files and databases.
Only way we were able to sort was by doing a full server reboot.
Same error occurred again this morning to which I again have restarted the server to get it running once again.
I have read up a bit about it and it has to do with DAOS and transitional logging? Though we have been running DAOS for over a year now with no issues. No changes to the system have been made that I know of. Seems that it should have been fixed in 8.5.1 and for previous versions the restart is only option.
We are running 8.5.3 both Domino and Lotus Clients.
Any help would be much appreciated.
Cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Try these steps:
1) Stop Domino so that it shuts down cleanly - this will purge the transaction logs.
2) Delete the transaction logs and the control file from your logdir directory while Domino is offline.
3) Restart Domino.
1) Stop Domino so that it shuts down cleanly - this will purge the transaction logs.
2) Delete the transaction logs and the control file from your logdir directory while Domino is offline.
3) Restart Domino.
ASKER
Yea nice Thomas, This is the only work around we are using at mo.
Though I found just now that the drive the transaction log was on was running out of disk space (had over looked this before)
So reboot would clear the log and a few hours later it be too full again.
I am clearing up the drive to provide more free space.
Hopefully this will solve the issues as it makes sense as to why its happening if drive is full.
Though I found just now that the drive the transaction log was on was running out of disk space (had over looked this before)
So reboot would clear the log and a few hours later it be too full again.
I am clearing up the drive to provide more free space.
Hopefully this will solve the issues as it makes sense as to why its happening if drive is full.
I did ask if the disk was full in my original reply. :)
You really should plan for more free diskspace if you want your Domino server to function properly.
Depending on the platform you run Domino on, significant performance gains can be had by splitting stuff up.
On IBM i, no splitting is needed.
On everything else: splitting helps greatly. See: Building a high performance Domino Server
Splitting stuff up allows you to use different tech for different parts, like a fast SSD for view rebuilds or the Transaction log. Read the linked article (it has also has links with more explanations/guides).
Depending on the platform you run Domino on, significant performance gains can be had by splitting stuff up.
On IBM i, no splitting is needed.
On everything else: splitting helps greatly. See: Building a high performance Domino Server
Splitting stuff up allows you to use different tech for different parts, like a fast SSD for view rebuilds or the Transaction log. Read the linked article (it has also has links with more explanations/guides).
See also DAOS and Transaction Logs
Hi there Adel,
Actually, when I first implemented DAOS & TL on one of my servers Local IBM office recommended me to have 8-9 TB disk dedicated for it , Hence, a SAN Disk on the storage was used for it . Moreover, a fix was issued for this error on LND 8.5.2.
http://www-01.ibm.com/support/docview.wss?uid=swg21440744
or if you could also install the latest fix pack for your LND version it will be also better .
Best Wishes
Actually, when I first implemented DAOS & TL on one of my servers Local IBM office recommended me to have 8-9 TB disk dedicated for it , Hence, a SAN Disk on the storage was used for it . Moreover, a fix was issued for this error on LND 8.5.2.
http://www-01.ibm.com/support/docview.wss?uid=swg21440744
or if you could also install the latest fix pack for your LND version it will be also better .
Best Wishes
ASKER
Thanks for reply.
Mate Settings as per below:
Basics
Transactional logging: Enabled
Log path: logdir
Logging style: Circular
Use all available space on log device: No
Maximum log space: 1024 MB
Automatic fixup of corrupt databases: Enabled
Runtime/Restart performance: Favor restart recovery time
Quotas
Quota enforcement: Check file size when extending the file
Cheers again.