Just want to confirm something so could you paste the screen shot for the error ? i hope this error is coming while you go for flush cache ?
if yes and you are unable to flush the cache then you need to apply mid tier hotfix . i just face the same issue in my 9.1 and after applying the hotfix problem went away
As the message indicates, flush cache fails since Preload = Yes and it's running as per the progress bar that it shows. You need to turn off preload once, restart midtier and then flush cache will work. If preload is ON, flush cache will only be allowed once preload completes.
Even if that may be what you are looking for, I suggest you look for midtier performance tuning guidelines and recommendations about preload. Refer to Configuring the mid tier preload and prefetch - BMC Remedy ITSM Deployment 9.1 and Performance tuning checklists - BMC Remedy ITSM Deployment 9.1
Hope this helpls.
Thanks and Regards,
Will there not be any impact with Preload if its turned off as every restart of the server or ARS Service will surely pop up this message at our environment too,we are on 9.1 Sp2 now and we always see this and will wait for the Progress bar to complete and then everything will be back to normal.
Would like to know if Preload can be turned Off,If yes lets know the process for it without being impacted.
We are on Server Group Environment on Production and Test Environments and Dev Standalone.
Appreciate response at your earliest availability.
Sorry for the above comment as i treat it as different issue. The hotfix i am talking about is for the error "Actor View is not Alive".
as Ashutosh suggested you pls lookinto that
Yes, preload can be disabled with some precautions that are called out in the doc:
Note that enabling preload on a freshly installed midtier is recommended for better first time user experience, since midtier already caches a lot of things (forms, activelinks, menus, etc.) as part of preload. However, once the system is in use, eventually view statistics are gathered (viewstats.dat) and they contain information about frequently accessed forms and views. So once you have good viewstats.dat file, preload is not really required. Viewstats processing at midtier startup will preload most frequently accessed forms for you rather than loading everything from AR server.
The process has been detailed out in the pdf that I have posted above.
Viewstats is effective even after flush cache so it will start preloading those form views immediately after flush in background. However, note that one of the bigger difference in viewstats and preload is - viewstats is a single threaded whereas preload has 4 threads since preload fetches too many objects from server.
Hope this helps.
Thanks and Regards,
I changed the Mid Tiers configuration in the following way:
Preload = No
Sync in cluster = Off
Enable Cache Persistence = On
Now the cache is able to be flush and sync on every Mid Tier servers reboot, or abnormaly reboot.....