MetaManager
Vineet -
It could be because CM tools read the content tree, not the raw storage footprint.
The CM metrics don't reflect storage-level fragmentation or large-object behavior in the database.
OR
...and I am not 100% sure but does this process orphan some Cognos reference-only entries. That could be the case because metadata might not be removed by the standard cleanup job.
Using MetaManager could help clean up and clear up any questions with deeper visibility and more aggressive cleanup.
Happy to walk through typical cleanup checks if you want to validate whether anything was missed.
------------------------------
Daryl Baker
Director of Software Solutions
BSP Software - Micro Strategies Inc.
IL
------------------------------
Original Message:
Sent: Tue December 09, 2025 09:26 AM
From: Vineet Joshi
Subject: Cognos Content Removal Job
Hello All
I ran the Cognos content removal job for anything greater than 6 months for saved output. The UI showed it removed it whole lot of entries and I myself deleted some saved output which was way too old (in GBs at least 25-30 GB)
DBAs ran the Reorg scripts on the database after that, based on this document from IBM and it saved in just MB Reclaiming Content Store database storage space after Content Archival and Removal maintenance.
Am I missing anything? The CM tools show less space than what is in the database.
Thanks
Vineet Joshi
------------------------------
Vineet Joshi
------------------------------