Repair on security domain hangs. Do loggedin users affect it

security Supervisor (4.x - 6.x)
1

I run a a scan repair and compact of the reporsitory early every Friday morning. I select this time frame because very few, if any, users are logged in. But this morning when I ran the repair on the security domain it hung up for about 30 minutes and then my supervisor session disappeared. I noticed that I had a couple of users already logged on, who tend to generate lots of complex queries. Could this cause the lock up and disappearance of my session. Could the unanticipated abort of the session have a negative impact on the domain? I am hesitant to try this again. :?

ehasse :us: (BOB member since 2002-08-19)

2

I will recommned doing Scan and Repair every evening instead of morning as you will be having less users in the evening as compared to morning.

I have seen Scan & repair hanging when database connectivity is slow or you are doing it after a long tme.

I will recommend doing it once again in the evening to clear things up

Hope this helps

JaiGupta (BOB member since 2002-09-12)

3

Probably not a good thing but if you are not seeing any problems I would not worry about it. On a side note, I am a little suprised you guys are doing SR/SRC’s every day?

jswoboda :us: (BOB member since 2002-06-20)

4

rule of thumb, when doing scan and repair no one should be accessing the repository, if so the chances of corrupting the repository is very high,

Bobby (BOB member since 2004-05-05)