My company has an application suite consisting of 6 dbs, one for each of six states. For 1 db in particular when the user tries to open it the PC CPU spikes and the db takes up to 10 minutes to open. Once it opens switching to another view creates the same problem. This was fine 2 days ago. I tried deleting cache.ndk, desktop6.ndk, recreated bookmark.nsf. If I put her ID on my PC and switch to it the same thing happens so I am ruling out the client. As far as the ID goes I’m ruling that out as well since the ID can access the other 5 dbs no problem. I’ve reindexed the views still no good. Yesterday I thought I had it fixed by resaving the ACL. After I did this it worked OK but this morning it’s doing it again. Nobody else is reporting any problems. Any ldeas out there?
Subject: Maybe it is building views
Check in design when are they created and are they preserved.
Subject: RE: Maybe it is building views
obviously you did not thoroughly read my posting. I’ve already rebuilt the views. And even if the views were rebuilding it would affect everyone and not just this one user.
Subject: db wont open all of a sudden, CPU spikes
Try re creating the person doc in the domino directory. Sounds odd, but if this issue is only happening with her id (and not anyone else’s) this may work.Worst case, try a new replica of the db and see if she can access it.
Subject: RE: db wont open all of a sudden, CPU spikes
I doubt that replacing the user’s person document in the Domino directory would resolve this issue. It is most likely an issue with the database itself. Keep in mind that if you are on version 6 or above, that design elements are checked much more thoroughly than in previous versions. The view indexing sounds like a good possbility here. I’d try running compact -c, fixup (with the “t” switch if you are using transactional logging) and updall on the database. If the problem still persists, then I would try making a new replica of the database. This is definitely not a client issue.
Subject: RE: db wont open all of a sudden, CPU spikes
I was down to the point where I had to get the user up and running so I set her up with a local replica and she is working fine. This is a huge db and running utilites against it would take a long time and I cannot do them during working hours or the users will kill me. I’m going to try creating a new replica on the server over the weekend. I will let you know if it fixes it.
Subject: RE: db wont open all of a sudden, CPU spikes
ultimately, creating a new replica of the database appears to have corrected the issue.
Subject: RE: db wont open all of a sudden, CPU spikes
If it were a problem with the person doc don’t you think she would have problems elsewhere in Notes?
Subject: db wont open all of a sudden, CPU spikes
How is this user getting access to the database, Paul? I wonder if there mightn’t be a collision of roles or something that’s causing some computation to get out of control. Try an explicit ACL entry for the user to see if it makes a difference.
Subject: RE: db wont open all of a sudden, CPU spikes
Paul,
Just a stab in the dark, but there’s no agent code that’s triggered upon the db opening or switching of views, is there??? If it’s a poorly written agent, that could be hosing you up for the first 10 minutes.
+Josh+
Subject: RE: db wont open all of a sudden, CPU spikes
no agent code triggered on db open. I did create a local replica for the user and she is fine in there so she is working locally for now and replicating her changes back to the server. will post if I get a resolution but for now I am stumped.
Subject: RE: db wont open all of a sudden, CPU spikes
there are quite a few roles in the db. The user gets access via a group in the ACL. I had already tried creating an explicit entry for the user when the problem first surfaced. At first, adding the new entry appears to work but the next day was the same problem so now I am back to square one. With the role thing there are several other users with the same rights/roles and none of them are having any issues.