Hi Antony,
One workaround I would suggest is to get rid of multiple users trying to access server at one instance when CPU utilization is high.
To monitor this you can use CLIX Command and identify the user because of whom entire repository is locked and based on that result , request the user to log off from current search operation until following locks are cleared (X-Exclusive, S-Shared)
Alphabet “X” represents exclusive lock and this happens when lot of activities keep server busy increasing CPU Utilization. We cannot define the exact time for each lock. It depends on the number of processes and no. of users logged on to specific repositories.
Shared lock (S) is another type with which users can still perform search and use client systems. With exclusive lock, it will be difficult for users to access clients and parallel operations will be on hold until this lock is cleared.
Regards,
Mir Kasim Ali