In planning or maintaining your CLM deployment, you may ask yourself these questions: "How do I ensure that my database size will not spiral out of control?", "Are there any strategies I can put in place to help with this in the beginning?", "Are there objects I should avoid storing in my repository?". There are some recommendations that will be captured in this page as well as some links to content that will help you understand <...>
Rational Team Concert
In Rational Team Concert, there are several items that can contribute greatly to database growth if not kept in check. These items are build results, workitem attachments, and binary content in SCM as versioned content. There are several articles and presentations that have been written on this topic.
Rational Quality Manager
For QM, there are some usages that can drive repository db growth. For example, automations generating Execution Results and attachments on the test artifacts such as HTML, images, etc. attached to either scripts or results.
Rational DOORS Next Generation
The "safest" way to reduce DB size is to archive projects and use the repotools -deleteJFSResources
command
Note that this can have consequences, for example, what if you have cross project links from other projects?. You can also run that command against unarchived projects to clean up artifacts in that project which have been deleted, but that may affect baselines and history that may be important.
One thing changed between 5.x and 6.x though, which is you can no longer run deleteJFSResources without the "force" parameter which deletes everything in the specified project. This is due to the way resources are unmapped versus archived, so running without "force" in 6.x seems to not find anything to delete.
Otherwise, there are two other tasks that can be scheduled daily/weekly to help manage the index size. See this
page for details.
Deleting data permanently from a DOORS Next Generation project
Data Warehouse
Data warehouse database size is huge and growing fast
Jazz.net forum resources
The forum contains many good suggestions from CLM Administrators who are maintaining CLM deployments.
Question: I want to store binaries in RTC. Does RTC SCM support delta compression?
Answer: Yes. RTC SCM supports delta compression of files, including binary files. In fact, one of the properties you can change in advanced properties is whether to enable or disable delta compression. If delta compression results in larger gains than other compression types it will be used to compress a given binary.
Question: Can I prevent binaries from being checked-in to RTC?
Answer: Yes, you can implement file limits in RTC.
Question:Does RTC store all versioned elements in the database?
Answer:Yes, RTC-SCM stores all versioned elements in the database.
Question:What can I do to monitor db growth and what does RTC do on its own?
Answer:
- RTC will run item cleanups daily (sometimes frequently throughout the day) to help clean stale data. You can investigate increasing this task, or the expiration time of these items (located in Advanced Properties)
- You can also run the onlineverify to ensure the consistency of the data and that there is no corruption which may be preventing the item clean up from running.
- ensure all your builds are being pruned and any results cleaned up
Question How can you scrub ChangeEvents from the repository database using IBM Rational Team Concert?
Answer http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21390701
https://jazz.net/forum/questions/92505/data-warehouse-db-sizing
https://jazz.net/forum/questions/20098/are-there-ant-way-for-me-to-reduce-size-of-the-rtc-db
https://jazz.net/forum/questions/73442/rtc-compression-for-binary-files-vs-clearcase
https://jazz.net/forum/questions/66014/rtc-large-history-complexity-and-archiving-questions
https://jazz.net/forum/questions/128039/what-is-the-latest-metrics-by-namespace-report-means
https://jazz.net/forum/questions/19251/rather-surprising-db2-growth
References
DatabaseMaintenanceFAQ
expected database growth when versioning binary data
Versioning binary artifacts
Additional contributors: TimFeeney,StefVanDijk,BenjaminSilverman,KrzysztofKazmierczyk