LN 6.5 – DB Consistency Control after uncontrolled LN closure.

60 pts.
Tags:
Consistency Control
Lotus Notes 6.x
Hi We have a large LN 6.5 DB which always gives us a 'consistency control' after uncontrolled closure of the PCs. Normally it takes 30-60 minutes before the 'consistency control' is ended. Meanwhile' it's not possible to use LN. How to stop or get around the 'consistency control' ? Your answers are very much appreciated. Thank you in advance
1

Answer Wiki

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

As already pointed out, you can’t get around the consistency check. However, 30-60 minutes seems like an exceedingly long time. You may be able to at least shorten it. Take note of what files are being checked and how long they’re taking. For example, if it’s perweb.nsf, you could try renaming or deleting the file before restarting – it should get re-created with no significant losses. Is the desktop large? If so, try compacting it after you’ve successfully started, so that it’s not as large the next time.

Discuss This Question: 6  Replies

 
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.
  • Brooklynegg
    I don't know how you are going to get around the consistency check if user's crash. I would work on finding the cause of the crashes. There are many reasons user might crash using a database. Recently, we found that we had bad configuration of view access controls. They did not include the servers in the ACL. User's could open the database. When they would exit, their Notes client would crash. Once the servers were given access to the view, user's quit crashing when using that database. Open a PMR with IBM technical support. You will probably have to upload the .nsd files created when the users crash and may have to make a copy of the database (with test data) to upload for analysis, as well. Also, check user's notes.ini files to ensure there are no blank lines or lines with no equal sign, which would indicate that they have an incomplete ini setting. (if you find this, please let me know, as we are the only ones who have seen this happen so far, from what I can hear from IBM).
    3,845 pointsBadges:
    report
  • LN2NICE
    Hi Thank for your help so far and all your suggestions - much appreciated. But there's another non-notes application "freezing" the PC from time to time, and to make the PC work again, the PC is booted. Then when PC is up running again, the Lotus appl. is showing consistency control for 30-60 minutes. Of course, the non-notes application should not freeze the PC, this is being worked on. But I realy like to get around this consistency control.....the user cannot use notes while the consistency control is going on.
    60 pointsBadges:
    report
  • Brooklynegg
    You can't avoid it. Find a way to fix the offending application. There is a chance that Notes is involved, of course. If you have not already, run nfixup from a command window against the pc's entire data directory, the ncompact -c -i against the entire data directory. This has helped some users in our environment.
    3,845 pointsBadges:
    report
  • LN2NICE
    Hi Thanks for your sugggestion. We know the database file names, and they are large. I had one today 1.3Gb and the other 1 Gb, I compacted both of them, and they were downsized to 400 Mb and 600 Mb. I also think, that this would improve the speed when they get consistency checks. I have to search for very stabile,easy to use solutions, because it's some of our users who have to fix the DBs themselves, preferably. One thing I do not understand is, why come you can't have Notes to automatically compact local DBs when they reach a certain percentage - like eg. 85 % or below. Or to have Notes doing it on a daily basis.
    60 pointsBadges:
    report
  • Brooklynegg
    I added code in the database open to check the fragmentation of desktop6.ndk (workspace) and the one very large local database they use and notify them to compact, along with instructions on how to do it. I will share the code. You will have to create the pages to display to your users. Also, tell your users to do a Start > Shutdown > Logoff <username> instead of rebooting the machine. This should stop all processes running under their name, including the one that is hung up, without having to crash Notes or any other app. When they start doing this instead of rebooting, they will think you are a genius. This sub is called from the database postopen. Looks like I used forms with saveoptions="0", not pages. Can't remember why. I know I tried to use a single form and set the subform that it should appear, but couldn't get that to work. Not the cleanest code in the world, but it gets it done. Sub CheckPercentUsed Dim workspace As New NotesUIWorkspace Dim db As NotesDatabase Dim used As Double Dim doc As NotesDocument Dim item As NotesItem Dim uidoc As NotesUIDocument Dim uidoc2 As NotesUIDocument desktopUsed = 100 dbUsed = 100 Set db = New Notesdatabase("", "desktop6.ndk") If Not db Is Nothing Then Desktopused = db.PercentUsed If Desktopused < 70 Then Set uidoc = workspace.ComposeDocument ( "", "", "CompactWorkspace" ) End If End If Set db = New Notesdatabase("", "PathOfBigdBRelativeToData.nsf") If Not db Is Nothing Then dbused = db.PercentUsed If dbused < 85 And dbUsed <> 0 Then Set uidoc2 = workspace.ComposeDocument ( "", "", "CompactdB" ) End If End If End Sub
    3,845 pointsBadges:
    report
  • LN2NICE
    Hi Brooklyneqq Thanks :-) I will try both things. Though I think the coding I'll keep to when the time is right to apply it. In our current environment, I do not think it's workable to maybe add extra time for them to open/close the databases in question. They DB's, are as mentioned, quite large. But you have given me some good tips.
    60 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.

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

Following

Share this item with your network: