We recently upgraded our mail server running on iSeries to Domino 8.5.1 FP2. We were previously on 7.0.2 FP2.
I have a batch file I run from my computer that connects to the Domino server and copies the mail journals over to my PC so I can save them offsite. The batch file worked fine with 7, but with 8.5.1 I get an error message on some of the mail journals:
“The process cannot access the file because another process has locked a portion of the file.”
I get a similar message if I try to copy and paste the file from iSeries Navigator:
“ is currently in use. The operation did not complete.”
Some of the files WILL copy. If I look at the file attributes through Client Access, the difference I see is with an attribute called “Allow write during save”. On the journals files that cannot be copied, that is set to Yes. On the ones that can be copied, it is set to No.
Also, at the same time we upgrade this server to 8.5.1 FP2, we set up a cluster server on another iSeries on Domino 8.5.1 FP2. The mail journals from that server copy fine.
Any ideas?
Subject: Fighting a similar issue
I’m fighting a similar issue since upgrading my Journal Server from 8.5FP1 to 8.5.1FP1 - the Journals do not rollover - the log shows: “Router: Cannot rollover journal db, current db will still be used. Reason: Database is currently in use by you or another user”
The only way to roll the Journal is to restart the server.
I suspect that there is a server process locking the file, but in the month that I’ve had the PMR open, I have yet to convince Support that nothing has changed except the upgrade from 8.5FP1 to 8.5.1FP1.
Long story short - the only way I found to unlock the Journal is to restart the server.
Subject: Any update?
Did you ever hear anything back from IBM on this? If not I think I will open a ticket with them also.
Thanks
Subject: Appears to be Update and possibly Mail tracking
We’re still working on it - I’ve been sending logs & procmon logs for awhile.
I just heard back from IBM on Monday that the problem appears to be the update task and/or Mail tracking.
I think I confirmed that Update is the culprit by ending the update task, and the journal then rolled over.
I get the impression that they (still) don’t feel that the problem is due to a change from 8.5 to 8.5.1 - yet I haven’t changed any settings.
My next rollover should be Saturday AM, so we’ll see what happens then.
It might be helpful if you also reported the problem, right now I think they think it’s just me!
Subject: Update - Update Task
Appears to be the update task only - latest is that they want me to change the template & database properties to keep the Update task from trying to update views in the database. Also need to disable template inheritance in mailjrn.ntf.
It sounds for sure that something has changed since 8.5 - not sure yet if they plan to fix it in future releases or not.
Subject: Now i need to open a new PMR?
It seems that we’ve narrowed it down to Update task - now I need to open a new PMR to continue to work on this issue.
No SPR number to reference.