Preparing your Solution Manager 7.1 today
When planning the upgrade to Solution Manager 7.2, it’s a good idea to clean up your Solution Manager system.
Over time, huge amounts of data are collected in your system. For instance, when you use complex SLD landscapes, the change log stored in SLD grows instantly. So here are some hints how to reduce the database size. It’s nothing new, it’s just a sumup of reorganization possibilities.
Reducing SLD change log
First login to your SLD, normally the URL is http://<hostname>:50000/sld if your Solution Manager has instance number 00 (port = 5xx00). Go to administraton tab and open the Change Log link:
Switch to “Reduce Size of Change Log”:
If you can’t delete anything, you first have to backup the SLD. To do this, switch to “full export”:
Do a full Export of “LD”:
After that, you’re able to remove the old change logs. If you’re using Oracle or another database which doesn’t free the space immediately, you should reorganize the BC_SLD* tables on database level.
As you have a clean SLD now, you can clean up LMDB using report RLMDB_CLEAR_CHANGELOG:
Just enter a date and run the report in background.
Reducing Application Log
The next thing is to reduce size of Application Log – just call Report SBAL_DELETE and create a variant. It’s a good idea to create a variable variant:
Save as variant:
Then create a selection variable e. g. older than 90 days:
You can run this variable periodically as background job. When your BAL* tables are already huge, you should reorganize them and rebuild the indexes.
Reducing EWA tables
Another thing is growing constantly: The tables which store EWA data (DSVAS*). SAP delivers a standard report to delete the documents and dependent data: RDSMOPREDUCEDATA. Just start it and put in suitable selection criteria:
You can choose to delete all data older than some date or delete only data from one solution etc.