Our current BOBj Prd file system is filling up and the drive where the logs and install is located. In the past, I was able to remove older Java log files, however we do not have any to move off at this time. Does anyone know some best places to clean up old unneeded files from a BOBj 4.0 (14.0.12) installation? Where does the system store all the PDF/XLSX/etc files from reports? Are there any other logs we can safely remove?
Thanks in advance
EmpireITtech 
(BOB member since 2017-01-24)
SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\logging
This is the BO system log directory. It can be safely emptied without affecting the system.
SAP BusinessObjects\tomcat\logs
The Tomcat log directory can be emptied, too, but it is likely not consuming a large amount of space.
SAP BusinessObjects\InstallData\InstallCache
This is the installation cache, it includes a copy of all packages that have been installed. If you’ve installed several patches, it will grow larger and larger. To save space, you can uninstall older patches (anything after the base install but prior to the most recent install). This will, of course, prevent you from rolling back to an older patch (and may not be possible if you have a mix of versions before and after BI4.2 SP03).
SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
This is the FRS. It contains all reports, universes, and other files in the BO CMS. If this is too large, then you can reduce it by deleting unneeded content.
SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data
This is the cache used by each server, and will include copies of universe and document files. Most of what’s here can be removed without impact but a few (ex., PlatformSearchData and TrendingDB) are necessary.
Joe
joepeters (BOB member since 2002-08-29)
[Moderator Note: Moved from General Discussion to Server Administration, Installation, Upgrades -> XI Server Discussion]
Marek Chladny 
(BOB member since 2003-11-27)
Ok, thank you Joe. Quick follow ups: we’ve got 55gb in the Data folder, so it seems good to start there, other than the PlatformSearchData and the TrendingDB files is there any other necessary files that I should watch out for?
The InstallCache appears to have around 20gb, so maybe I can remove some patches safely to clear some of that up (the drive is 100gb total and 75gb are in these 2 folders). I wasn’t apart of the server creation in 2013 when they set this system up, below is a snapshot of what is installed, ignoring the “install dates” which seem to be all over the place, does this mean they started with 4.0 SP4? And are now on 4.0 SP12 Patch 4? The install dates likely change for the base installation during the upgrades I assume.
EmpireITtech 
(BOB member since 2017-01-24)
I have, in the past, deleted the contents of data\ with no ill effects. If you’re going to do that, it might be a good idea to archive it somewhere for a while before permanently deleting it.
Yes, it looks like you have a base install of BI4.0 SP4 which has been patched to BI4.0 SP4 Patch 4. You should be able to uninstall all of the others. As I mentioned, doing so will prevent you from rolling back SP4 Patch 4.
joepeters (BOB member since 2002-08-29)
Yea, in the Data folder (55.3 gb total) the TrendingDB sub-folder and the PlatformSearchData sub-folder take up 36gb and 19gb…so 99.99999% of the space lol.
Did you just delete all the contents of the Data folder, including all sub-folders within? Or go down to the ends of each sub folder and remove the contents within? For example: the TrendingDB folder has a sub-folder called Derby > then a sub-folder seg0 > inside here it’s dat files with today’s date/time stamp, one of which is 17gb in size.
EmpireITtech 
(BOB member since 2017-01-24)
Whoa - ok. So those two directories represent the Monitoring data and Platform Search, respectively.
The default Monitoring application uses a Derby database and can get pretty big. If you don’t care about the historical monitoring data, you can probably safely delete the TrendingDB\Derby directory. Archive it first, of course, it should zip up pretty small. The admin guide has instructions for moving the database to a “real” database like Oracle. You’d still have to regularly prune it, but it would be easier than in Derby.
PlatformSearch contains the Platform Search data. If it’s this big, then you’re probably including content in the search and not just metadata. If this is true and you want to keep it, then your only option is to move the directory to another location, such as NAS. The admin guide has instructions for doing this. If you want to include just metadata and not content, then you can make the switch in CMC -> Applications -> Platform Search. I believe you will have to reset the search repository to do this, but the space usage will be much smaller.
For both of the above, the default installations aren’t aware of clustering. If you have more than one node in your cluster, you’ll have multiple copies of the monitoring and platform search. Again, check the admin guide – there are instructions on correctly configuring these for clustering.
joepeters (BOB member since 2002-08-29)