RSM Database Problems

[Matthew Tidgewell]

I have a customer with an EVA6000, CommandView 6.02 and RSM 3.0. The problem is the size of the RSM database. It takes up to 30 minutes to open a job monitor in Run History. I think it is the solid database; it is 181M and contains a year of data. Are there any tools to purge this old data? The export files are just over 100K, is there a way to remove the database and restore the jobs?

[Patrice Bourdon]

hi Mat, did you try to compact database ? (in configuration options)

[Matthew Tidgewell]

I checked the compact box, it seems to uncheck every time the server restarts. I've solved my problem for now, I editted the solid.ini and changed the cache setting from 24M to 256M. Now the CPU spikes for about a minute instead of the disks thrashing for twenty minutes before the monitor page opens. The customer let me know that the half hour delays between jobs is now back to 15 minutes. Maybe when version 3.1 comes out all my problems will go away.