Locking memory trend files
Hi,
I have a number of memory trend files that were created with the locking option not set but we have now decided they should be kept for longer than the expiry time of the general session storage (which is about 7 days). The reason is some new releases will be rolled out in the next 2-3 months and we'd like to keep trend sessions that have been created (there are 100 per day for 2 applications, the reason is the application has some intermittent memory issues we are trying to pin down)
I can't see a way to lock them through the client. Is the best option to export a sample of them or make offline sessions? If so can this be automated? If we go the route of exporting sessions can we combine two or more exported sessions to allow comparisons of the trend snapshot?
Moving forwards I'll lock the sessions and then selectively delete them manually keeping every 10th or so. Could I do this by just deleting the underlying file (ie from script) or must I do it via the GUI?
thanks,
Alex.
Right click on the Session Storage (in the cockpit dashlet)
Then Right click on memory entry, and click Lock to prevent deletion.
Hi Alex,
A bit late to the party, but my 2c.
If you have that many trending dumps, I assume you have a task running that is capturing the sessions for you. There's a checkbox to lock the sessions when they're captured (System Profile -> Tasks -> Edit memory snapshot task).
For existing sessions, you should be able to lock them through the session storage dashlet like Jerry said (double click "Session storage" in the cockpit, then right click on the session(s) and choose "Lock to prevent deletion"). I thought you could also do this through the Total memory dashlet, but it looks like you can't. Perhaps an ease-of-use RFE?
One thing to be conscious of is that these locked sessions will contribute to the storage quota, so you'll be eating into the amount of purepaths you can store.
Also, I'd be careful about deleting the sessions out of the file system (though it can be done). Deleting through the UI is safer since it will clean up any dependencies that might exist as well.
Andrew
